Which PRINCE2 principle is being applied when the Project Manager escalates a tolerance deviation to the Project Board?
Manage by Exception defines tolerances for each level and mandates escalation only when a forecast breach occurs. Escalating the deviation to the Project Board therefore enacts that principle, since the Project Manager acts within delegated limits and refers exceptions upward.
Why this answer
The 'Manage by Exception' principle is applied when the Project Manager escalates a tolerance deviation to the Project Board. This principle delegates decision-making authority to the Project Manager within defined tolerances (e.g., time, cost, quality, scope, risk, and benefit). When a forecast indicates that a tolerance will be exceeded, the Project Manager must escalate the issue to the Project Board, which then decides on corrective action.
This ensures that the Project Board only becomes involved when a deviation threatens the project's agreed limits, embodying the 'manage by exception' approach.
Exam trap
Candidates often confuse 'Manage by Exception' with 'Continued Business Justification' — the escalation of a tolerance breach is about exceeding delegated limits, not about the project's ongoing viability.
How to eliminate wrong answers
Option A is wrong because Continued Business Justification ensures the project remains viable and aligned with business objectives throughout its lifecycle, but it does not directly address the escalation of tolerance deviations; that is the role of Manage by Exception. Option C is wrong because Learn from Experience involves capturing and applying lessons learned from previous projects or phases to improve current and future work, not the escalation of tolerance breaches. Option D is wrong because Focus on Products emphasizes defining and delivering the project's products (outputs) with agreed quality criteria, not the mechanism for handling deviations from tolerances.