The Issue Log Template is the central register used to document, track, and manage issues that arise during project execution. In PMBOK 8, the issue log is a key project document maintained throughout the Monitor and Control Project Performance process. Unresolved issues can escalate into risks or cause project delays — a structured Issue Log Template ensures nothing falls through the cracks.

What's Included in This Issue Log Template?

This free PMBOK 8 Issue Log Template is an Excel spreadsheet designed for practical daily use. It includes:

• Issue ID — a unique identifier for each issue (e.g., ISS-001).
• Description — a clear statement of the issue and its impact.
• Date Raised — when the issue was identified.
• Raised By — the team member or stakeholder who identified it.
• Category — scope, schedule, resources, technical, stakeholder, etc.
• Priority — High, Medium, or Low.
• Owner — the person responsible for resolving the issue.
• Due Date — the target resolution date.
• Status — Open, In Progress, Resolved, or Closed.
• Resolution — what action was taken to resolve the issue.
• Resolution Date — when the issue was formally closed.

Issues vs. Risks: Key PMBOK 8 Distinction

In PMBOK 8, risks are uncertain future events, while issues are problems that have already occurred. The issue log captures what is happening now and requires immediate action. Key differences:

• Risk Register: Tracks uncertain events that may or may not happen, with probability and impact assessments.
• Issue Log: Tracks confirmed problems that need resolution today.

Many issues originate from risks that materialised. When a risk occurs, move it from the risk register to the issue log.

How to Use the Issue Log Template

1. Create an issue: As soon as an issue is identified, log it with a unique ID, description, and date raised.
2. Classify and prioritise: Assign a category and priority (High/Medium/Low) based on impact to project objectives.
3. Assign an owner: Every issue needs a single accountable owner — not a team.
4. Set a due date: High-priority issues should have resolution dates within the current reporting period.
5. Review in status meetings: Walk through open issues in every project status meeting.
6. Close resolved issues: Document the resolution action and close the issue formally.

Related PMBOK 8 Templates

• Risk Register Template — track uncertain events before they become issues.
• Change Request Template — issues often trigger formal change requests.
• Status Report Template — include the open issue count in every status report.
• Lessons Learned Template — document recurring issues to prevent them in future projects.

Issue Management Best Practices

Effective issue management separates reactive project teams from proactive ones. Follow these best practices:

• Log issues immediately: Delay in recording leads to forgotten context and missed resolution deadlines.
• Escalate early: If an issue cannot be resolved at the team level within 48 hours, escalate to the project manager or sponsor.
• Review weekly: Make the issue log a standing agenda item in weekly team meetings.
• Link issues to decisions: When an issue is resolved through a project decision, document the decision in the log.

The Project Management Institute (PMI) emphasises that proactive issue management is a hallmark of experienced project managers. Download this free PMBOK 8 Issue Log Template to build that discipline into your projects.