This guide covers everything you need to know about the issue log in PMBOK 8. The issue log is the project’s central tracker for problems that have already occurred and require resolution — unlike risks, which are potential future events, issues are current problems actively affecting or threatening the project.
What Is the Issue Log?
The issue log is a project document that records all issues identified during project execution, tracks their assignment, status, and resolution, and provides an audit trail of how problems were managed. An issue is any problem, gap, inconsistency, or conflict that occurs during the project and cannot be immediately resolved by the project manager alone.
Issues differ from risks in one critical way: risks are uncertain future events; issues have already happened. When a risk materializes, it becomes an issue. The issue log captures all of these events — technical problems, stakeholder conflicts, resource shortfalls, vendor failures, and process breakdowns — and ensures each one is assigned to an owner with a resolution target date.
The issue log is a living document reviewed at every status meeting. Its value lies not just in tracking current problems but in building an organizational memory of how similar problems were resolved, supporting future project planning and risk identification.
Issue Log in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the issue log belongs to the Governance Performance Domain and is maintained during the Manage Project Execution process. PMBOK 8 emphasizes that unresolved issues are a leading indicator of project health deterioration — a growing issue backlog without resolution dates is a warning sign requiring management attention.
The issue log feeds into work performance reports, the lessons learned register, and change requests when issue resolution requires a formal scope, schedule, or cost change.
Key Elements of the Issue Log
A well-structured issue log typically includes:
- Issue ID — unique identifier for tracking and referencing
- Issue Description — clear, specific statement of the problem
- Priority — high, medium, or low based on impact on project objectives
- Owner — team member responsible for resolving the issue
- Target Resolution Date — the deadline by which the issue must be resolved
- Status — open, in progress, resolved, or escalated
- Resolution Notes — what action was taken and what the outcome was
Issue Log Example — Project Phoenix
Project Phoenix’s issue log captured 11 issues over the project lifecycle. The most critical was ISS-004, logged on March 28, 2024: John Tran took unplanned medical leave, removing 40% of the development team’s capacity during the peak coding sprint. Alex Morgan assigned the issue to herself, escalated it to Riley Park within 24 hours, and resolved it within three days by negotiating 20 additional hours with Sam Lee (covered by contingency reserve) and deferring two non-critical features to a post-launch sprint.
ISS-007 involved a vendor conflict: BrightFrame’s designer was reassigned to another client mid-project, delaying design asset delivery by four days. Alex escalated directly to BrightFrame’s account manager and had a replacement designer assigned within 48 hours with no impact to the project schedule. By project close, 10 of 11 issues were fully resolved; one low-priority issue was handed over to the operations team as a post-launch action.
You can download the complete filled-in example below — it shows exactly how the issue log was maintained in a real project context.
Download Free Issue Log Template and Example
We have prepared two free resources to help you maintain an issue log on your own projects:
- Download the Issue Log Template — PMBOK 8 (blank, ready to fill in)
- Download the Issue Log Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Issue Log — Best Practices and Common Mistakes
Log every issue, no matter how small it seems. Small unlogged issues have a way of compounding into large problems. Assign every issue to a specific owner with a specific resolution date — “team responsibility” with no deadline means the issue will stay open indefinitely. Review the issue log at every status meeting and escalate any issue open beyond its target resolution date.
The issue log is most effective when it is treated as a live management tool rather than a reporting artifact. Teams that skip or rush this document often find themselves managing crises reactively instead of resolving issues systematically before they escalate.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Project Management