Study guide
2.5 Principle 5: Manage by Exception
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
2.5 Principle 5: Manage by Exception
Key Takeaways Explain This Topic AI
PRINCE2 projects establish distinct tolerance limits for seven performance targets: Time, Cost, Quality, Scope, Risk, Benefits, and Sustainability.
Authority is delegated across four management levels; each level only escalates when a forecast indicates a tolerance breach (an exception).
An Exception Report informs the next higher management level of a forecast breach and presents options for decision.
An Exception Plan replaces the remainder of the current plan when the Project Board authorizes recovery after an exception.
Team Managers escalate Work Package tolerance threats to the Project Manager via issue notification and Checkpoint reporting—not Highlight Reports.
Last updated: July 2026
2.5 Principle 5: Manage by Exception
In traditional management environments, senior executives are frequently bombarded with routine operational updates, minor variance requests, and endless status meetings. This micro-management wastes executive time and slows down operational execution. Conversely, if executives delegate completely without controls, projects can drift off course without warning until catastrophic overruns occur.
PRINCE2 Principle 5: Manage by Exception establishes an efficient control model by setting pre-agreed boundaries—called tolerances —for project performance targets. Higher management levels delegate day-to-day authority to lower levels, intervening only when tolerances are forecasted to be exceeded .
PRINCE2 Principle Rule: A PRINCE2 project has defined tolerances for each project objective to establish limits of delegated authority.
The Seven Performance Targets (Aspects) for Tolerances
PRINCE2 7 establishes tolerances across seven project performance targets (frequently tested on Foundation exams): +-----------------------------------------------------------------------------------+
- | THE SEVEN PERFORMANCE TARGETS (ASPECTS) |
- +-----------------------------------------------------------------------------------+
- | 1. TIME | Permissible deviation on schedule dates (e.g. +/- 2 weeks) |
- | 2. COST | Permissible deviation on financial budget (e.g. +/- $50k) |
- | 3. QUALITY | Permissible variation in quality criteria metrics |
- | 4. SCOPE | Permissible variation in deliverable features (e.g. MoSCoW) |
- | 5. RISK | Permissible aggregated risk exposure / appetite thresholds |
- | 6. BENEFITS | Permissible variation in expected outcome realization |
- | 7. SUSTAINABILITY| Permissible environmental and social impact thresholds |
- +-----------------------------------------------------------------------------------+
- 1. Time Tolerance
Defines acceptable schedule variance. Example: "Target completion date is October 15, with a time tolerance of +1 week / -2 weeks."
2. Cost Tolerance
Defines acceptable budget variance. Example: "Stage budget is $200,000, with a cost tolerance of +$15,000 / -$10,000."
3. Quality Tolerance
Defines acceptable variance in physical or technical performance targets defined in Product Descriptions. Example: "System response time target is 1.8 seconds, with an acceptable quality tolerance of up to 2.2 seconds."
4. Scope Tolerance
Defines acceptable variation in deliverables or requirements. Usually tied to prioritized features (e.g., using MoSCoW: Must Have items are mandatory; Should Have items represent scope tolerance that can be dropped if time/cost pressure arises).
5. Risk Tolerance
Defines acceptable aggregated risk exposure for the plan. Example: "No single residual threat may exceed $40,000 exposure without Project Board review; stage risk budget $25,000."
6. Benefits Tolerance
Defines acceptable variance in expected post-project benefits. Example: "Target operational savings of $500k/year, with a benefit tolerance of -$50k/year (minimum acceptable $450k/year)."
7. Sustainability Tolerance (Elevated in PRINCE2 7!)
Defines acceptable thresholds for environmental and social impacts. Example: "Project carbon footprint target is 50 tonnes CO2e, with a sustainability tolerance of +5 tonnes CO2e maximum."
Delegating Tolerances Across Management Levels
Tolerances flow down through the four management levels, establishing precise boundaries of authority at each tier: Corporate / Programme Management
- │ (Sets Project Tolerances)
- ▼
- Project Board (Directing)
- │ (Sets Stage Tolerances)
- ▼
- Project Manager (Managing)
- │ (Sets Work Package Tolerances)
- ▼
- Team Manager (Delivering)
Management Level Tolerances Set Controlled By Action if Tolerance Breached
Corporate / Programme Project Tolerances Corporate / Programme Management Project Board escalates to Corporate via Exception Report.
Project Board Stage Tolerances Project Board Project Manager escalates to Board via Exception Report.
Project Manager Work Package Tolerances Project Manager Team Manager escalates to Project Manager via Issue / Checkpoint notification.
The Exception Escalation Workflow
Exam Trap / Critical Rule: Escalation must occur when a tolerance is FORECASTED to be exceeded, NOT after the breach has already occurred!
If a Project Manager monitors stage progress and calculates that upcoming material delays will cause the stage to finish 10 days late (when time tolerance is +5 days), the Project Manager must not wait until day 5 of the overrun to act.
Step-by-Step Escalation Procedure:
Detection & Forecast: Project Manager identifies that a stage or project target is forecasted to exceed agreed tolerance.
Raise Exception Report: Project Manager creates an Exception Report detailing:
The nature of the forecasted breach.
Root cause analysis.
Available options for resolution (with pros, cons, and costs for each option).
Recommended option.
Escalate to Project Board: Submit the Exception Report to the Project Board.
Board Direction (Directing a Project): The Project Board reviews the report and directs an action:
Option A: Increase tolerances to cover the variance.
Option B: Instruct the Project Manager to submit an Exception Plan to replace the current plan.
Option C: Terminate the project prematurely if business justification is broken.
Execute Exception Plan: If requested, the Project Manager drafts an Exception Plan (re-planning the remainder of the stage or project). Upon Board approval, the Exception Plan baselines and replaces the old plan.
Benefits of Managing by Exception
Applying Principle 5 delivers profound organizational benefits:
Executive Efficiency: The Project Board does not need to attend weekly operational status meetings; they receive concise Highlight Reports and intervene only when exceptions occur.
Empowerment: Project Managers and Team Managers have clear operational autonomy to make decisions within their delegated tolerances.
Early Warning System: Proactive forecasting ensures senior leadership is never surprised by sudden, unmanaged project failures.
Summary Matrix: Tolerances Across the 6 Aspects
- Performance Target Typical Metric Example Target Permissible Tolerance
- Time Schedule dates / Durations Complete Stage 2 by Dec 1 +/- 1 Week
- Cost Financial budget / Expenditure Stage 2 Budget $150,000 +$10,000 / -$5,000
- Quality Technical specifications Battery life 12 hours +/- 30 Minutes
- Scope Feature count / Requirements Deliver 20 user stories Drop up to 3 "Should Have" stories
- Benefits Operational ROI / Metrics Reduce call volume by 25% Minimum acceptable 20% reduction
- Sustainability Carbon / Waste metrics Recycling rate 90% Minimum acceptable 85%