HKSM

An issue log is a living project document used to record, track, and resolve current problems, conflicts, and decisions that require action. Project documents updates - Issue log means the log is revised whenever issues are identified, analyzed, assigned, escalated, or closed throughout the project life cycle.

Key Points

• The issue log tracks present problems needing action, not uncertain future events like risks.
• It is updated continuously as issues are raised, reprioritized, reassigned, escalated, or resolved.
• Each issue should have a unique ID, clear owner, priority, due date, and current status.
• Entries may link to decisions, change requests, requirements, and other records for traceability.
• Regular review in team or stakeholder meetings helps drive accountability and timely resolution.
• Closure includes verifying results and capturing lessons learned for future reference.

Purpose

The issue log provides a single, transparent source of truth for all active project issues. It ensures accountability, enables timely decision-making, and supports communication with stakeholders about impacts and resolution progress.

Field Definitions

• Issue ID: Unique identifier used for tracking and reference.
• Date Raised: The date the issue was identified.
• Raised By / Source: Person or group who reported the issue.
• Description: Clear statement of the problem and context.
• Category / Type: Classification such as technical, resource, vendor, scope, compliance, or communication.
• Impact Summary: What is affected (scope, schedule, cost, quality, resources, stakeholder satisfaction).
• Priority / Severity: Relative importance or urgency (e.g., High, Medium, Low) with defined criteria.
• Owner: Person responsible for driving resolution.
• Actions / Next Steps: Agreed tasks to resolve or mitigate the issue.
• Due Date / Target Resolution: Planned date to complete resolution or next milestone.
• Status: Current state such as New, In progress, On hold, Escalated, Resolved, or Closed.
• Escalation Level: Current escalation (e.g., team lead, PM, sponsor, governance board).
• Links / References: Related decisions, change requests, requirements, risks, or contracts.
• Comments / Notes: Updates, meeting outcomes, and context.
• Date Closed / Outcome: When the issue was closed and the final result.

How to Create

• Select a simple, accessible tool (spreadsheet, backlog tool, PPM system) and create a single shared log.
• Define standard fields, priority criteria, and status values so everyone uses the same terms.
• Set a clear workflow for logging, triage, assignment, escalation, and closure.
• Number issues sequentially and pre-fill project metadata (project name, version, owner).
• Establish RACI for issue management and communicate how to raise new issues.
• Integrate with related processes such as change control and risk management.

How to Use

• Log new issues immediately with enough detail for triage and traceability.
• Assess impact and set priority based on defined criteria; assign an owner and target date.
• Track actions and update status after each meeting or work session.
• Escalate per thresholds when deadlines or impacts exceed team authority.
• Communicate high-impact issues in status reports and stakeholder updates.
• Link issues to decisions and change requests when scope, schedule, or budget must be altered.
• Verify resolution, obtain acceptance if needed, and close the entry with outcomes and lessons.

Ownership & Update Cadence

• Overall Log Owner: Project manager or designated issue manager maintains the log and process.
• Issue Owner: Assigned individual accountable for driving each issue to resolution.
• Contributors: Team members and stakeholders provide updates and evidence of progress.
• Cadence: Update continuously as changes occur; review in standups or weekly status meetings.
• Escalation: Time-bound reviews trigger escalation to sponsor or governance per defined thresholds.
• Access: Keep the log visible to the team and key stakeholders to promote transparency.

Example Rows

• ID: ISS-012; Date: 2025-03-05; Source: QA; Description: Test environment unstable during performance tests; Category: Technical; Impact: Schedule risk to UAT; Priority: High; Owner: Env Lead; Actions: Provision new nodes, rerun tests; Due: 2025-03-10; Status: In progress; Links: CR-004; Notes: Vendor engaged; Escalation: PM.
• ID: ISS-019; Date: 2025-03-08; Source: Sponsor; Description: Conflicting stakeholder expectations for reporting frequency; Category: Communication; Impact: Rework in reporting; Priority: Medium; Owner: PM; Actions: Facilitate alignment meeting, update comms plan; Due: 2025-03-12; Status: New; Links: Decision-021; Notes: Add to agenda.
• ID: ISS-023; Date: 2025-03-09; Source: Compliance; Description: Missing audit evidence for supplier onboarding; Category: Compliance; Impact: Release blocked; Priority: High; Owner: Procurement Lead; Actions: Collect artifacts, update checklist; Due: 2025-03-11; Status: Escalated; Links: Risk-R15; Notes: Board review set for 2025-03-10.

PMP Example Question

During execution, a stakeholder reports a regulatory non-compliance found in testing that must be fixed before go-live. What should the project manager do first?

1. Add the item to the risk register and plan a response.
2. Record the item in the issue log, assign an owner, and set a due date.
3. Escalate to the sponsor immediately without documenting it.
4. Update the lessons learned register and inform the PMO.

Correct Answer: B — Record the item in the issue log, assign an owner, and set a due date.

Explanation: This is a current problem requiring action, so it belongs in the issue log for tracking and accountability. Risks address uncertain future events; escalation comes after proper logging and initial triage.