[Insert Department Name]

[Insert Department/Project Logo] [Insert

Project Name]

Introduction to the Issue Log Template

The purpose of an issue log is to ensure that issues are properly documented so that they may be managed to reduce negative impacts on the
project. Issues are defined as something in dispute or something to be resolved. The resolution of issues may have an impact on the project’s
scope, schedule, cost, or quality.

In simple terms, an issue is commonly described as something affecting the project that has occurred or is happening, while a risk is described as
an event that has not yet occurred but might in the future.

See the Issue Management Plan for additional information on documenting issues, issue escalation, issue tracking, and communicating issues.

This Issue Log Template with Instructions contains directions for properly initiating and maintaining an Issue Log. Additional hints, examples and
suggestions are included within each of the template tables where key information is recorded.

Template style conventions are as follows:

Style Convention

Indicates placeholder text that can be used for any

Normal text project
[Indicates text that is to be replaced/edited/deleted by
[Instructional text in brackets] document author]
Indicates example text that might be
Example text in italics
replaced/edited/deleted by user

Project Sample Library:

The CA-PMF has a Project Sample Library that contains real-world project artifacts from approved projects that you can reference to
help you complete CA-PMF templates. Visit the CA-PMF website to access the Project Sample Library.

CA-PMF website: http://capmf.cio.ca.gov/

Issue Log | Page 1_____

 [Insert Department Name]
[Insert Department/Project Logo]
[Insert Project Name]

Issue Log Template Instructions and Guidance

1 Introduction
[The Issue Log is a tool used to capture project issue information in support of the project’s issue management process. Issue Management
consists of the five processes listed below:

·        Issue Identification

·        Issue Resolution
·        Issue Control
·        Issue Tracking and Reporting
·        Issue Escalation
The Issue Log is used to document the results of the activities within these five management processes with a particular focus on issue
identification, issue resolution, and issue control.

The following sections describe the attributes used in each of the three sections listed above and provide instructions and guidance for how
to fill in the Issue Log tool. See the Issue Management Plan for more detailed information about the Issue Management processes.]

2 Issue Identification
[Issue identification is an integral process to ensure successful delivery of any project. Issues arise throughout the project lifecycle, and
require swift recognition, attention, and resolution to minimize their impact to the project. Any project team member can identify an issue
and issues should be raised to the team lead, Project Manager, or Risk/Issue Manager. Project documents should indicate who has primary
responsibility for issue management – beginning with identification activities and analyzing the issue’s project impact. The Issue Identification
section of the Issue Log consists of the following attributes. Attribute descriptions are provided to help understand usage.

• ID # - Enter a unique identifier used to reference the issue.

• Issue Title – Enter the issue title that will appear on issue reports. It should be brief but also convey the issue implications.
• Issue Statement or Description –Enter an issue description that contains enough detail to provide project Stakeholders with an
understanding of the issue and its impact to the project.

• Date Issue Identified – Enter the date the issue was added to the issue log.
• Issue Originator – Enter the person(s) who identified the issue.
• Impact Rating – Enter the issue’s impact to the project. In the sample table below, the project has defined impact ratings as High,
Medium and Low and provided a definition for each.

Impact Criteria

Issue presents a significant negative impact on project budget, schedule, or

quality.

High * Project cost increase of 10% or more

* Project schedule increase of 10% or more
* Failure to meet required performance
* Failure to provide required functionality
Issue presents a material impact that would significantly affect users,
clients, or key Stakeholders.

* Project cost increase of 5 - 10%

Medium * Project schedule increase of 5 - 10%

Issue Log | Page 2_____

 * Significant discrepancies in desired system-wide performance
* Significant discrepancies in desired system-wide functionality

Issue does not present a significant or material impact on project budget,

schedule or quality.

Low * Project cost increase of less than 5%

* Project schedule increase of less than 5%
* Minor discrepancies in desired performance
* Minor discrepancies in desired functionality

The following table provides a sample entry for Issue Identification.]

Example:

Issue Identification

Date Issue
ID # Issue Title Issue Statement or Description Issue Originator Impact Rating
Identified

The current project costs are 12%

1 Current costs exceed project budget XX/XX/XXXX Project Manager High
higher than budgeted

The project’s Enterprise Architect has

2 Staff attrition left the project leaving the position XX/XX/XXXX Project Sponsor High
vacant

3 Issue Resolution
[As they are determined, resolutions to specific issues are recorded in the issue log. Issue resolution begins with assigning an owner to the
issue who is responsible for monitoring, and sometimes managing, issue resolution activities until the issue is resolved. The Issue Resolution
section of the Issue Log consists of the following attributes. Attribute descriptions are provided to help understand usage.

·  Issue Owner - Enter the name of the person assigned to resolve the issue.
·  Date Assigned – Enter the date that the Issue Owner was assigned.
·  Target Resolution Date – Enter the planned date for resolution
·  Issue Resolution Description – Enter a description of the plan for resolving the issue.
The following table shows an example of recording issue resolution information in the issue log. The resolution addressess Issue #2 in the
sample table above.]

Example:

Issue Resolution
Issue Owner Date Assigned Target Resolution Date Issue Resolution Description
[Name] [Date] [Date] The Department will re-assign an
architect from a lesser priority project
temporarily until a new architect is
hired

4 Issue Control
[Once a resolution plan has been determined, efforts to resolve the issue are monitored and the issue’s status is documented. Suggested
status entries include the following, but others could be added based upon project needs.

Issue Log | Page 3_____

 ·  Assigned – the issue has been assigned to an owner for resolution
·  Implementing – A resolution plan has been developed and is being implemented
·  Escalated – The issue has been escalated for resolution
·  Completed – the resolution plan has been completed
·  Closed – the issue has been closed

The Issue Control section of the Issue Log consists of the following attributes. Attribute descriptions are provided to help understand usage.

·  Issue Priorty – Ranks the importance of resolving the issue relative to other issues.
·  1 – The issue must be resolved as quickly as possible
·  2 – The issue should be resolved as quickly as possible
·  3 – Issue resolution can be deferred
·  Issue Status – a notation regarding the current state of the issue.
·  Issue closure date – Enter the date that the issue was closed.
·  Comments – enter clarifying information as needed

The table on the following page shows an example of recording issue control information in the issue log which completes an issue log entry.
This entry addresses Issue # 2 in the table above.]

Example:
Issue Control
Priority Issue Status Issue Closure Date Comments
New Architect hired and currently
1 Closed XX/XX/XXXX
being on-boarded

[The Issue Log incorporates Issue Identification, Issue Resolution and Issue Control.]
Example:

Issue Identification Issue Resolution Issue Control

Issue
Date Issue Date Target Resolution Issue Resolution
ID # Issue Title Issue Statement or Description Issue Originator Impact Rating Issue Owner Priority Issue Status Closure Comments
Identified Assigned Date Description Date
Current costs exceed project budget The current project costs are 12% XX/XX/XXXX Project Manager High [Name] [Date] [Date]
higher than budgeted
Review existing budget.
Determine root cause for
1 over budget condition 2 Assigned
and initiate a cost
control strategy.

[Name] [Date] [Date] The Department will re- New Architect hired and currently
assign an architect from being on-boarded
a lesser priority project
temporarily until a new
The project’s Enterprise Architect has architect is hired.
2 Staff attrition left the project leaving the position XX/XX/XXXX Project Sponsor High 1 Closed XX/XX/XXXX
vacant

Issue Log | Page 4_____

 [Insert Department Name]
[Insert Department/Project Logo]
[Insert Project Name]

Issue Log

Issue Identification Issue Resolution Issue Control

Target
Issue Statement or Date Issue Impact Date Issue Resolution
ID # Issue Title Issue Originator Issue Owner Resolution Priority Issue Status Issue Closure Date Comments
Description Identified Rating Assigned Description
Date

Issue Log | Page 5_____