An issue log template is a project document used to record, track, and monitor issues that arise during project execution and require attention or resolution. According to the Project Management Institute (PMI), the issue log is a key artifact used across multiple processes in PMBOK 8, including Manage Stakeholder Engagement, Manage Communications, and Monitor Risks. An issue is a current problem — not a future risk — that is already impacting or imminently threatening the project. A disciplined issue log ensures that no problem falls through the cracks and that resolution accountability is always clear.

What is an Issue Log?

An issue log template is a structured register where each identified issue is recorded with a unique ID, description, owner, priority, status, and resolution plan. Unlike the risk register, which tracks potential future events, the issue log captures problems that have already occurred or are occurring now. In PMBOK 8, the issue log is maintained throughout the project and is an input to stakeholder engagement, communications management, and risk monitoring processes. Issues that cannot be resolved at the project level may escalate to the project sponsor or governance board via a change request.

What's Included in This Issue Log Template?

• Issue ID and Title - A unique identifier and short descriptive title for each issue, enabling quick reference in status reports and stakeholder communications.
• Issue Description - A clear statement of the problem, including what happened, which deliverable or process is affected, and the observed or potential impact on scope, schedule, cost, or quality.
• Issue Type and Category - Classification of the issue (technical, resource, stakeholder, external, process) to identify patterns and enable root cause analysis across the project.
• Priority and Severity - A rating that determines how urgently the issue must be resolved, distinguishing between issues that are blocking project progress and those that can be managed within existing plans.
• Issue Owner - The named person responsible for driving resolution of the issue. Without a named owner, issues remain open indefinitely.
• Date Raised and Target Resolution Date - The date the issue was identified and the agreed deadline for resolution, enabling tracking of overdue issues.
• Resolution Plan - The specific actions being taken to resolve the issue, who is responsible for each action, and the expected outcome.
• Status and Closure Date - Current status (open, in-progress, escalated, resolved, closed) and the date the issue was formally closed with a record of the resolution achieved.

How to Use This Issue Log Template (PMBOK 8)

1. Log every issue at the moment it is identified - Delays in logging issues create gaps in the project record and allow problems to compound. Any team member should be able to raise an issue; the project manager is responsible for ensuring it is logged and assigned.
2. Distinguish clearly between issues and risks - A risk has not yet occurred; an issue has. The issue log and risk register are separate documents with different management approaches. Confusing the two leads to missed responses.
3. Assign an owner to every open issue - An issue without an owner is not being managed. The owner is the person accountable for driving resolution, not necessarily the person who will do the technical work.
4. Review the issue log at every status meeting - Issues that are not reviewed regularly tend to age without resolution. Make the issue log a standing agenda item and escalate any issue that has been open beyond its target resolution date.
5. Escalate issues that exceed project-level authority - If an issue cannot be resolved within the project team's authority — due to budget, scope, or stakeholder constraints — raise a change request and escalate to the sponsor or governance board.
6. Close issues formally with documented resolution - Do not simply delete resolved issues. Close them with the date resolved and a description of the outcome. This data supports lessons learned and post-project reviews.

When to Create This Document (PMBOK 8)

The issue log is created at the start of project execution and maintained continuously until project close. In PMBOK 8, it is first established as part of the Manage Stakeholder Engagement process but is referenced as an input and updated as an output in numerous processes throughout execution and monitoring. The issue log should be reviewed at every project status meeting and formally closed as part of the project closure documentation.

Related Templates

• Risk Register Template
• Change Requests Log Template
• Assumption Log Template
• Status Report Template
• Lessons Learned Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• Issue Log in PMBOK 8 - Complete Guide - Understand the purpose, key elements, and best practices before filling in the template.
• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.