HKSM

An issue log is a living register of current problems, decisions needed, and questions that require action during the project. It records ownership, priority, status, and due dates to drive timely resolution and transparent communication.

Key Points

• Tracks present, confirmed problems that require action, unlike a risk register which tracks uncertain events.
• Created early and maintained throughout the project as a single source of truth for issues.
• Supports accountability by assigning each issue to an owner with a clear due date and action plan.
• Prioritization typically considers impact and urgency to focus the team on what matters most.
• Links to related artifacts such as the change log, risk register, and decision log for full traceability.
• Regular review in status meetings ensures timely escalation and resolution.

Purpose

The issue log enables the team to capture, prioritize, assign, and resolve issues in a structured, visible manner. It improves coordination, informs stakeholders, and reduces schedule or quality impacts by ensuring no issue is forgotten.

Field Definitions

• Issue ID - Unique identifier for traceability.
• Date Raised - When the issue was logged.
• Raised By - Person or group that reported the issue.
• Description - Clear, concise statement of the problem or decision needed.
• Category/Type - Classification such as scope, schedule, resource, vendor, technical, or stakeholder.
• Impact Area - Affected objective or deliverable (scope, schedule, cost, quality, stakeholder satisfaction, compliance).
• Impact Summary - Brief explanation of consequences if unresolved.
• Urgency - How quickly action is required (for example: low, medium, high, critical).
• Priority - Overall ranking that drives order of work (may combine impact and urgency).
• Owner - Person accountable for driving resolution.
• Action Plan/Next Steps - Agreed actions to resolve or mitigate the issue.
• Target Resolution Date - Planned date to resolve the issue.
• Status - Current state such as new, under analysis, in progress, on hold, escalated, or closed.
• Status Date/Last Update - Most recent date the entry was updated.
• Escalation Level - Governance level engaged if needed (team lead, PM, sponsor, steering committee).
• Related Links - References to change requests, risk entries, decisions, or tickets.
• Resolution/Outcome - Final result when the issue is closed.

How to Create

• Select a simple format (spreadsheet, register in a PPM tool, or board) that the team will actually use.
• Adopt standard fields, define scales for urgency and priority, and agree on status values.
• Establish logging rules at kickoff: who can add issues, required fields, and when to escalate.
• Set service-level expectations for triage and updates (for example, triage within 1 business day).
• Pre-populate with known open items from initiation or handovers to start with a complete picture.
• Publish the log location and access instructions to all contributors and stakeholders.

How to Use

• Capture new issues as they arise with enough detail to assess impact and assign ownership.
• Triaging: validate the issue, assess impact and urgency, set priority, and assign an owner and due date.
• Track progress by updating status, actions, and dates; add notes from meetings and stakeholder input.
• Escalate per agreed thresholds when ownership, resources, or decisions block resolution.
• Communicate status in reports and meetings, highlighting high-priority and aging issues.
• Upon resolution, record the outcome, link related change requests or decisions, and formally close the entry.
• Periodically review trends to identify systemic causes and preventive improvements.

Ownership & Update Cadence

• Primary Owner: Project manager (or issue manager) maintains the log and facilitates triage and escalation.
• Issue Owners: Assigned individuals update actions, dates, and status for their issues.
• Review Cadence: Brief review in each team standup or weekly status meeting; deeper review in governance meetings as needed.
• Update Frequency: Status and notes updated as work occurs, at least weekly for active issues and within one business day after major changes.
• Audit Trail: Keep a brief change history or timestamped notes to preserve context and decisions.

Example Rows

• ID: I-001; Date Raised: 2025-03-02; Description: Supplier shipment delayed 2 weeks; Category: Schedule/Vendor; Impact: Milestone slip risk; Urgency: High; Priority: High; Owner: Procurement Lead; Target Date: 2025-03-10; Status: Escalated; Action: Engage alternate supplier and rebaseline if needed; Related: CR-12; Resolution: Pending sponsor decision.
• ID: I-002; Date Raised: 2025-03-05; Description: Testing environment unstable during peak hours; Category: Technical; Impact: Test cycles blocked; Urgency: Critical; Priority: High; Owner: IT Ops Manager; Target Date: 2025-03-07; Status: In progress; Action: Add capacity and schedule maintenance window; Related: INC-453; Resolution: TBD.
• ID: I-003; Date Raised: 2025-03-06; Description: Conflicting stakeholder expectations on reporting frequency; Category: Stakeholder; Impact: Rework and dissatisfaction; Urgency: Medium; Priority: Medium; Owner: PM; Target Date: 2025-03-09; Status: Under analysis; Action: Facilitate decision meeting and document agreement; Related: DEC-08; Resolution: Weekly report cadence agreed.

PMP Example Question

Midway through the project, a team member reports a confirmed problem blocking a critical task. Which artifact should the project manager update to assign an owner, set a due date, and track resolution?

1. Risk register
2. Change log
3. Issue log
4. Assumption log

Correct Answer: C — Issue log

Explanation: The issue log records current problems needing action, along with ownership, priority, and status. Risks and assumptions address uncertainties, while change logs track approved changes.