2.5 Principle 5: Manage by Exception

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)

---

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:

1. Detection & Forecast: Project Manager identifies that a stage or project target is forecasted to exceed agreed tolerance.
2. 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.
3. Escalate to Project Board: Submit the Exception Report to the Project Board.
4. 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.
5. 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% |