Study guide
4.1 Manage by Exception
PRINCE2 Practitioner Version 7
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Strategy & Open-Book Technique
2 PRINCE2 7 Method Overview
2.1 The PRINCE2 7 Method 2.2 What Changed in PRINCE2 7 2.3 Performance Targets, Tolerances & Project Context
3 PRINCE2 Principles (1–4)
3.1 Continued Business Justification 3.2 Learn from Experience 3.3 Defined Roles, Responsibilities & Relationships 3.4 Manage by Stages
4 PRINCE2 Principles (5–7) & Applying Principles
4.1 Manage by Exception 4.2 Focus on Products 4.3 Tailor to Suit the Project 4.4 Applying Principles in Context
5 People Management in Projects
5.1 Organisational & Project Ecosystems 5.2 Leadership in Projects 5.3 Team Culture & Diversity 5.4 Communication, Stakeholder Engagement & Change Management
6 Practices Overview & Business Case
6.1 The Seven Practices & Tailoring 6.2 Business Case: Desirability, Viability & Achievability 6.3 Business Case Lifecycle & Management Products 6.4 Business Case Application & Tailoring Scenarios
7 Practices: Organising & Plans
7.1 Organising: Roles & Accountability 7.2 Organising: 5-Step Ecosystem Technique 7.3 Plans: Three Levels & Product-Based Planning 7.4 Plans: Techniques, Tolerances & Tailoring
8 Practices: Quality & Risk
8.1 Quality: Planning, Control & Assurance 8.2 Quality Techniques & Management Products 8.3 Risk: Threats & Opportunities 8.4 Risk 5-Step Technique & Application
9 Practices: Issues
9.1 Issues Practice: Issue vs Change & Categories 9.2 Issues 5-Step Technique & Supporting Techniques 9.3 Change Control, Configuration & Priority/Effort Assessment
10 Practices: Progress, Sustainability & Application
10.1 Progress: Controls, Tolerances & Reports 10.2 Sustainability as the 7th Performance Target 10.3 Tailoring the Practices 10.4 Practices Application Scenarios (BL4)
11 Processes: Model, Starting, Directing & Initiating
11.1 The Seven Processes & Process Model 11.2 Starting Up a Project 11.3 Directing a Project 11.4 Initiating a Project
12 Processes: Controlling a Stage & Product Delivery
12.1 Controlling a Stage 12.2 Managing Product Delivery 12.3 Stage Control & Exception Scenarios (BL4) 12.4 Work Packages & Reporting Cycle
13 Processes: Stage Boundary, Closing & Tailoring
13.1 Managing a Stage Boundary 13.2 Closing a Project 13.3 Tailoring the Processes 13.4 Process Application Scenarios (BL4)
14 Tailoring, Management Products & Exam Technique
14.1 Tailoring to Project Environment, Scale & Agile 14.2 Management Products & the v7 Project Log 14.3 Final Exam Technique, Full Scenarios & Common Traps
4.1 Manage by Exception
Key Takeaways Explain This Topic AI
Authority is delegated with defined tolerances for each performance target; each management level operates within its tolerance and escalates only when a forecast breaches it.
Three tolerance levels exist: project (set by programme or corporate management), stage (set by the Project Board), and team/Work Package (set by the Project Manager).
When a forecast breaches a tolerance, the level below produces an Exception Report to the level above; the Project Board may give advice, defer, halt, or order premature closure.
PRINCE2 7 defines seven performance targets for tolerances: time, cost, scope, quality, risk, benefits, and sustainability.
Last updated: August 2026
What Manage by Exception Means
Manage by exception delegates authority to a lower level with defined tolerances for each performance target, so that each level can self-manage within agreed limits and escalate only when a forecast breaches those limits. The principle prevents micro-management: the Project Board does not need to supervise every task the Project Manager performs, and the Project Manager does not need to supervise every Team Manager task — provided work stays within tolerance.
Tolerances and performance targets
PRINCE2 7 defines tolerances against seven performance targets : time, cost, scope, quality, risk, benefits, and sustainability. A tolerance is the permitted deviation from a planned target before the next level of management must be informed. Tolerances may be expressed as plus/minus percentages, absolute ranges, or qualitative bands.
- Performance target Example tolerance expression
- Time Stage end no later than 5 working days after plan
- Cost Stage spend within ±5% of stage budget
- Scope No change to agreed products without change control
- Quality Acceptance criteria fixed; no relaxation
- Risk Aggregate risk exposure below agreed threshold
- Benefits Forecast benefit within −5% of baseline
- Sustainability Carbon footprint within agreed cap
- Three tolerance levels
Tolerances are set at three levels, each by the level above:
Project tolerance — set by programme or corporate management ; defines the permitted deviation for the whole project against the mandate and business case.
Stage tolerance — set by the Project Board for each management stage; the Project Manager manages the stage within these limits.
Team/Work Package tolerance — set by the Project Manager for each Work Package; the Team Manager works within these limits and escalates to the PM on breach.
Exception reporting
When a forecast indicates a tolerance will be breached, an Exception Report is produced by the level below and sent to the level above. For a stage tolerance breach, the Project Manager produces the Exception Report and submits it to the Project Board. For a Work Package tolerance breach, the Team Manager produces one for the Project Manager. The Exception Report describes the deviation, its impact, and options for recovery.
The receiving level then decides between:
Give advice and ask the lower level to recover the situation within tolerance.
Defer the decision (for example, request more information or an updated plan).
Halt the project or stage.
Premature closure of the project.
Six exception types
PRINCE2 recognises six exception types, each tied to a performance target where tolerance is forecast to be exceeded: scope exception, quality exception, benefit exception, risk exception, cost exception, and time exception. A deviation against a sustainability target is handled the same way where a sustainability tolerance has been agreed. The principle is that the right people are informed at the right time — not every variance, only those that exceed the permitted deviation.
Who sets tolerance for whom
A common exam trap is confusing which level sets tolerance for which. The rule is tolerances are always set by the level above the one that works within them :
- Tolerance level Set by Worked within by Breach reported to
- Project Programme or corporate management Project Board Programme or corporate management
- Stage Project Board Project Manager Project Board
- Team / Work Package Project Manager Team Manager Project Manager
A Project Manager cannot set stage tolerance — only the board can. A Team Manager cannot set Work Package tolerance — only the PM can. Corporate or programme management sets project tolerance because the board itself is the delegated authority working within it.
Worked scenario — a stage cost-tolerance breach
A stage has a budget of £400,000 with a cost tolerance of +5% (i.e. a £420,000 ceiling). Six weeks in, the Project Manager's latest forecast puts stage spend at £435,000 — a forecast breach of £15,000 above the permitted ceiling.
The Project Manager does not wait for the stage to end over budget. Because the forecast breaches tolerance, the PM raises an Exception Report now.
The Exception Report describes the deviation (forecast £435,000 vs ceiling £420,000), the cause (a supplier rate increase), the impact (project-level cost tolerance still intact, but stage tolerance gone), and options (descoping one optional product, renegotiating the rate, or requesting a stage tolerance increase).
The Project Board receives the Exception Report and chooses one of four responses: give advice (direct the PM to descope the optional product and recover within the existing ceiling), defer (request an updated plan or more information before deciding), halt the stage while the situation is resolved, or order premature closure of the project if the Business Case is no longer viable.
Only the Project Board can adjust stage tolerance . If the board agrees a +10% ceiling (£440,000), the PM continues within the new limit. The PM cannot authorise that increase themselves.
If the forecast had also threatened project tolerance , the board would escalate to corporate or programme management — because only that level can adjust project tolerance.
Common traps in exception questions
Waiting for actual breach. A forecast breach is enough — the Exception Report is raised when the deviation is predicted , not when it is confirmed at stage end.
PM adjusting stage tolerance. Only the board can do this; the PM can only adjust Work Package tolerance (and only for Work Packages they set).
Confusing Exception Report with Issue Report. An Issue Report records a problem that may or may not breach tolerance; an Exception Report is specifically a forecast breach of tolerance requiring the level above to decide.
Assuming every variance escalates. Small variances within tolerance are handled by the level that holds the tolerance — only breaches go up.
Forgetting sustainability. Where a sustainability tolerance has been agreed (e.g. a carbon cap), a forecast breach is a sustainability exception handled the same way as the other six types.
Common exam scenarios
Exam questions often describe a forecast breach and test who is notified, what the PM produces, and what the board may do. Remember: a forecast breach triggers the Exception Report — you do not wait until the tolerance is actually broken at the end of the stage. The Project Board, not the PM, decides how to respond to a stage-level exception. The PM cannot authorise their own tolerance increase for the stage; only the board can adjust stage tolerance, and only corporate or programme management can adjust project tolerance.