Study guide
5.2 Issues Practice & Issue Management Approach
PRINCE2 7 Foundation Certification Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Key Concepts, Framework & Integrated Elements
1.1 PRINCE2 7 Method Overview & Project Context 1.2 Seven Performance Aspects & Delivery Approaches 1.3 Outputs, Outcomes, Benefits & Value Creation 1.4 Management Products vs Specialist Products 1.5 PRINCE2 Governance, Tailoring & Distinct Features
2 Chapter 2: The Seven PRINCE2 7 Principles
2.1 Principle 1: Continued Business Justification 2.2 Principle 2: Learn from Experience 2.3 Principle 3: Define Roles, Responsibilities and Relationships 2.4 Principle 4: Manage by Stages 2.5 Principle 5: Manage by Exception 2.6 Principle 6: Focus on Products 2.7 Principle 7: Tailor to Suit the Project
3 Chapter 3: The People Element in PRINCE2 7
3.1 Capable People & Organizational Culture 3.2 Project Teams & Team Dynamics 3.3 Leading Project Teams 3.4 Communication & Stakeholder Engagement 3.5 Organizational Change Management (OCM)
4 Chapter 4: The PRINCE2 7 Practices - Strategy, Organization & Planning
4.1 Business Case Practice 4.2 Organizing Practice & Project Management Team 4.3 Commercial & Stakeholder Aspects of Organizing 4.4 Plans Practice & Levels of Plans 4.5 Product-Based Planning Technique 4.6 Quality Practice & Quality Control
5 Chapter 5: The PRINCE2 7 Practices - Risk, Change & Progress Control
5.1 Risk Practice & Risk Management Approach 5.2 Issues Practice & Issue Management Approach 5.3 Change Control & Configuration Management 5.4 Progress Practice & Control Mechanisms 5.5 Management Reports & Logs/Registers 5.6 Sustainability & Digital Integration in Practices
6 Chapter 6: The PRINCE2 7 Processes - Pre-Project & Initiation
6.1 Overview of PRINCE2 7 Process Model & Flow 6.2 Starting Up a Project (SU) Process 6.3 Directing a Project (DP) Process 6.4 Initiating a Project (IP) Process 6.5 Assembling the Project Initiation Documentation (PID)
7 Chapter 7: The PRINCE2 7 Processes - Delivery, Boundary & Closure
7.1 Controlling a Stage (CS) Process 7.2 Managing Product Delivery (MP) Process 7.3 Managing a Stage Boundary (SB) Process 7.4 Closing a Project (CP) Process 7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
5.2 Issues Practice & Issue Management Approach
Key Takeaways Explain This Topic AI
The Issues practice (formerly the Change theme) controls how unplanned events and change proposals are captured, assessed, and decided.
PRINCE2 7 issue types include: change, problem/concern, business opportunity, request for change, and off-specification.
The Issue Management Approach (PID), Issue Register (project log), and Issue Report are the key management products.
The recommended issue and change control procedure is Capture → Assess → Propose → Decide → Implement.
A Change Authority and change budget may be delegated by the Project Board to speed decisions within agreed limits.
Last updated: July 2026
5.2 Issues Practice & Issue Management Approach
No matter how thoroughly a project is planned, unexpected events will occur during execution. Requirements change, stakeholders request new features, deliverables fail quality tests, and external environmental shifts introduce problems. In PRINCE2 7, the Issues Practice establishes a reliable, controlled mechanism for identifying, assessing, and acting upon any unplanned event or proposal for change.
PRINCE2 7 Definition: An issue is any relevant event that has happened, was not planned, and requires management action.
Without formal issue management, projects fall victim to unmanaged change—commonly known as scope creep —where gradual additions to project deliverables erode budgets, delay deadlines, and compromise quality without executive approval.
Types of Issues in PRINCE2 7
The Foundation syllabus requires candidates to recognize these issue-related types (they are not mutually exclusive labels in every scenario—an issue may be classified and then handled as an RFC or off-specification): ┌───────────────────────────────┐
- │ PRINCE2 ISSUE TYPES │
- └───────────────┬───────────────┘
- │
- ┌─────────────────────────────────────┼─────────────────────────────────────┐
- ▼ ▼ ▼
- ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
- │ Request for │ │ Off- │ │ Problem / │
- │ Change │ │ Specification│ │ Concern │
- └──────────────┘ └──────────────┘ └──────────────┘
- Change (general issue classification)
Any relevant event that has happened (or is happening) that requires management attention may be recorded as a change -related issue before more specific classification.
Not every issue is a formal Request for Change; some are problems, opportunities, or off-specifications.
Business Opportunity
A business opportunity is a type of issue representing a beneficial possibility that was not in the original plan (for example, a supplier offers a higher-value feature at no extra cost, or a regulatory change unlocks an additional market).
Opportunities still require controlled assessment—accepting them can affect scope, cost, benefits, and sustainability tolerances.
Exam trap: do not confuse a business opportunity (a certain event/offer requiring a decision) with a risk opportunity (an uncertain future event).
1. Request for Change (RFC)
Definition: A proposal to modify an agreed baseline product specification, project objective, or project scope.
Origin: Submitted by any stakeholder (e.g., customer requesting an extra module, business user requesting modified workflow).
Financial Impact: Always requires evaluation against project cost, time, and quality targets; usually funded via the Change Budget if approved.
2. Off-Specification (Off-Spec)
Definition: Something that should be delivered by the project but is not delivered, or does not satisfy agreed quality criteria or product specifications.
Origin: Usually identified during testing, quality reviews, or technical audits (e.g., a delivered software module fails to achieve required throughput of 1,000 transactions per second).
Action Required: The Project Board must decide whether to grant a concession (accepting the product as-is), order refactoring, or mandate alternative remedial action.
3. Problem / Concern
Definition: Any other event, query, or observation that requires management attention and does not involve a direct change to a baseline product or off-specification.
Origin: Operational issues, team resource shortages, supplier disputes, or technical queries (e.g., loss of a key senior developer during stage 2).
Attribute Request for Change Off-Specification Problem / Concern
Nature Proposal for new/modified scope Failure to meet agreed baseline spec Unplanned event or operational query
Baseline Impact Changes baseline specifications Deviates from baseline specifications Does not alter baseline spec directly
Funding Source Change Budget (if approved) Supplier/Stage budget (remediation) Stage budget or operational funds
- Key Decision Approve, Reject, Defer Grant concession or require rework Approve resolution or escalate
- The Issue Management Approach
Created during the Initiating a Project process, the Issue Management Approach defines how issues and changes will be handled throughout the project lifecycle. It outlines:
Issue Logging Rules: How issues are logged, categorized, and assigned unique reference numbers.
Severity & Priority Scales: Standardized matrices to rate issue severity (e.g., Minor, Major, Critical) and priority (e.g., Low, Medium, High, Must Have).
Escalation Thresholds: Criteria defining when an issue can be resolved by the Project Manager versus when it must be escalated to the Change Authority or Project Board.
Change Authority Setup: Composition, financial authority limits, and decision rules for the delegated Change Authority.
Change Budget Rules: Administrative rules governing how the Change Budget is allocated and accounted for.
The 5-Step Issue and Change Control Procedure
PRINCE2 defines a rigorous 5-step procedure for processing every logged issue:
Step 1: Capture
Receive the issue and determine whether it should be dealt with informally or formally.
If informal, record it in the Daily Log .
If formal, create an entry in the Issue Register , assign an Issue ID, and draft an Issue Report .
Step 2: Assess
Evaluate the impact of the issue on the project's performance targets ( Time, Cost, Quality, Scope, Risk, Benefit, Sustainability ).
Assess the impact on the Business Case, stage plans, and downstream operations.
Determine issue priority and confirm whether resolving it would breach stage tolerances.
Step 3: Propose
Identify and evaluate potential options for resolving the issue.
For each option, analyze costs, benefits, secondary risks, schedule impact, and trade-offs.
Formulate a recommended course of action.
Step 4: Decide
Submit the Issue Report and recommendations to the appropriate decision body:
Project Manager: Resolves minor issues within granted stage tolerances.
Change Authority: Approves or rejects Requests for Change within delegated change budget limits.
Project Board: Decides on issues that exceed stage tolerances or require project baseline alterations.
Step 5: Implement
Execute the approved decision.
Update the relevant management products (Project Plan, Stage Plan, Product Description, Work Packages).
Update the Issue Register and notify affected stakeholders.
- Change Authority & The Change Budget
- The Change Authority
While the Executive holds overall accountability for approving project changes, reviewing every minor Request for Change can overwhelm the Project Board. Therefore, the Project Board may delegate authority for approving change requests to a designated person or group known as the Change Authority .
Delegation Scope: Clear financial and scope limits must be defined in the Issue Management Approach (e.g., Change Authority may approve RFCs up to $10,000 per item).
Composition: Can be the Project Manager (for minor changes), a user representative, a technical expert, or a formal change advisory committee.
The Change Budget
PRINCE2 7 Definition: A Change Budget is a sum of money allocated by the Executive to fund approved Requests for Change.
Purpose: Ensures money is readily available to fund agreed scope additions without requiring constant corporate funding requests.
Separation: The Change Budget is distinct from the stage baseline budget and the Risk Budget. It belongs to the Executive/Change Authority, not the Project Manager.