# Issue Log

A controlled record of current problems, questions, or decisions affecting delivery, with ownership, priority, actions, due dates, and resolution evidence.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/issue-log/>)

## What it means

An issue log captures conditions that already exist and require resolution, unlike risks, which concern uncertain future events. Entries commonly include an identifier, description, date raised, impact, priority or severity, owner, action plan, target resolution date, status, escalation route, links to changes or decisions, and the evidence and rationale used to close the issue.

## Why it matters

Issues consume time and value whether or not they are recorded. A shared log prevents them from being lost across messages and meetings, makes accountability explicit, and shows when resolution is blocked by authority or dependencies. It also provides evidence for status reporting and helps teams recognize repeated operational or governance failures.

## When to use it

Use an issue log whenever unresolved problems can affect scope, quality, schedule, cost, benefits, safety, or stakeholder confidence. Establish a simple route for anyone involved to raise an issue. Review urgent items frequently and integrate the log with risk, decision, and change processes where resolution alters an approved baseline.

## How it works

1. Capture the issue promptly with observable facts, affected objectives, reporter, date, and supporting evidence.
2. Assess impact, urgency, severity, ownership, and whether immediate containment or specialist escalation is required.
3. Define resolution actions, action owners, target dates, dependencies, decision needs, and success conditions.
4. Review overdue or blocked items at the governance level able to remove the constraint or accept the consequence.
5. Confirm the resolution, link resulting changes and decisions, record closure evidence, and identify preventive learning.

## A practical example

During a payroll launch, testing shows that overtime rules calculate incorrectly for one union group. The issue log records affected employees, severity, owner, containment, fix and retest dates, and a go-live decision deadline. Because resolution changes the rollout sequence, the entry links to a formal change request and approval record.

## Where it breaks

A log does not solve problems by itself. Too many low-value entries can hide urgent decisions, while subjective priority labels may invite lobbying. Some issues require incident, safety, legal, or security procedures with stricter confidentiality and response times. Closure can also be premature when a workaround masks the root cause.

## Common mistakes

- Recording uncertain future events as issues instead of risks.
- Assigning an owner who lacks the authority or capacity to resolve the problem.
- Reporting status repeatedly without a specific next action or decision date.
- Closing an issue when a workaround is deployed without confirming the intended outcome.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/issue-log/#visualization-issue-log>)

## Sources

1. [Programme and Project Issues Management](<https://www.finance-ni.gov.uk/articles/programme-and-project-issues-management>) — Northern Ireland Department of Finance · Government project guidance
2. [Gate 2 Review: Delivery Strategy](<https://www.gov.uk/government/publications/gate-review-2-delivery-strategy/gate-2-review-delivery-strategy>) — UK Infrastructure and Projects Authority · Government assurance guidance

## Related topics

- [RAID Log](<https://wiki.soroush.uk/topic/raid-log/>)
- [Risk Register](<https://wiki.soroush.uk/topic/risk-register/>)
- [Change Control](<https://wiki.soroush.uk/topic/change-control/>)
