Issue Log

Don't just sound-off about your issues! Log and validate, then act on the valid issues.

Issues will arise during your project. Maintain a written issue log to document and monitor all issues. Be sure issues are resolved by their target date, or escalated if necessary. Don't let unresolved issues bring your project down.

If you like our Issue Log Template be sure to let your friends know about it.
We like to be Liked.

1 1 1 1 1 1 1 1 1 1 Rating 4.10 (31 Votes)
Issue Log - 3.9 out of 5 based on 23 votes

ISSUE LOG TEMPLATE

Project management is, by its very nature, a complex process which often includes many people, influences, variables, tasks, and other considerations to successfully manage. In order to be successful a project manager must effectively use various tools and methodologies to communicate and manage the project. Two of the most important characteristics of a successful project are documentation and accountability. Project documentation is used to formally capture and communicate important project information so it is available to everyone who needs it. The documentation must be carefully managed and updated as any changes occur in order to prevent gaps and/or overlaps in project work. Accountability must be established so the project team and stakeholders understand who is responsible for the work to be performed. If tasks are not specifically assigned and managed, they will sit idle and may significantly impact the overall project performance.

The issue log is one example of project documentation and accountability. The issue log is used throughout a project’s lifecycle to capture any issues brought forward, communicate the issues to the project team and stakeholders, establish categories and priorities of all issues, assign responsibility to each issue, and ensure that each issue is resolved with minimal impact to the project’s performance. Like most other project documentation, the issue log should be reviewed by the project team regularly to ensure issues are being resolved. The document should be updated and communicated to all project stakeholders as updates are made.

Sample Issue Log with Explanations:

Issue Log
Project: Date:
Issue Description Priority (H,M,L) Category Reported By Assigned To Status Date Resolved Resolution/ Comments
This should be a standard numbering system. Detailed description of the issue. High, Medium or Low priority. Assign to a category. Who reported the issue? Who is the issue assigned to? What is the status of the issue? What date was the issue resolved? What was the resolution or what is being done to resolve the issue?

Issue Log Example with Sample Data:

Issue Log
Project: Date: 04/21/20xx
Issue Description Priority (H,M,L) Category Reported By Assigned To Status Date Resolved Resolution/ Comments
001 Broken plotter is preventing engineers from publishing project drawings. M Technology A. White B. Brown Closed 2/25/xx Submitted a help desk ticket (# 6051232) and the plotter was repaired and operational on 2/25/xx.
002 Lease for the new facility is in jeopardy of missing 5/1/12 cutoff date for approval. M Resources C. Black D. Green Open Escalated the issue with the VP of Facilities on 4/1/12. He indicated that he should obtain approval of the lease by 4/25/12. Will follow up twice a week until issue is resolved.
003 Testing group director recently retired and has a new director. We must ensure support and resource allocation for the project. M Resources E. Blue J. Doe Closed 4/3/xx J. Doe met with new testing group director on 4/3/12 and received formal support for the project and resources that have already been assigned by previous director.