Yes, It is a PRINCE2 Issue
July 2025

Yes, It is a PRINCE2 Issue

The term "issue" in PRINCE2 carries more meaning than in everyday language. Project managers often underuse the Issue Register because they reserve it for dramatic problems — a supplier going bankrupt, a key team member leaving, a major scope change. But the PRINCE2 issue management process is designed to handle a much wider range of events, concerns, and decisions.

The PRINCE2 Issue Register and Issue Reports are crucial tools to keep your projects under control. Underusing them means important items get handled informally — in emails, in meetings, in people's heads — with no formal record, no tracked decision, and no audit trail.

When Something Qualifies as a PRINCE2 Issue

Log an issue whenever any of the following occur:

Three Types of PRINCE2 Issue

PRINCE2 defines three types of issue, each handled through the same capture-examine-propose-decide-implement process:

Use the Structured Process

For each issue, use PRINCE2's five-step process from the Change practice: capture, examine, propose, decide, implement. This ensures that every issue is assessed for its impact, a response is proposed, a decision is made and recorded, and the outcome is tracked. A structured Issue Report template makes this process fast and consistent.

See also: What is the Issue? — on defining issues by root cause, not consequence.