Imagine a project board that only gets a phone call when something is genuinely wrong, instead of drowning in a 40-slide status deck every week. Senior leaders are busy, and most project updates say the same thing: everything is fine. The smarter question is how to make sure decision-makers see problems early without being buried in noise. That's exactly the gap this governance principle fills, and here's how it works in practice.
What Management by Exception Really Means
Management by exception means higher levels of authority only step in when a project is forecast to go beyond agreed limits. Everyone else gets on with their work. Professionals who pursue PRINCE2 certification learn that this principle is built into the method itself, which makes governance lighter, faster and far more focused.
How Tolerances Set the Boundaries
Tolerances are the permitted wiggle room around a plan. They can be set for six areas:
Time: How far a deadline can slip.
Cost: How much the budget can flex.
Quality: The acceptable range for deliverables.
Scope: Which features are flexible and which are fixed.
Risk: How much exposure the organization will accept.
Benefits: How far expected value can vary.
As long as the forecast stays inside these limits, the project manager keeps control.
What Happens When a Tolerance Is Threatened
The escalation path is clear and repeatable:
The project manager spots a forecast breach, not just an actual one.
They raise an exception report to the project board.
The report explains the cause, the options and a recommendation.
The board decides whether to approve a revised plan, adjust tolerances or stop the project.
Work continues under the new direction.
Why This Strengthens Governance
Clearer accountability: Each management level knows what it can decide alone.
Better use of senior time: Executives focus on real risks, not routine updates.
Earlier warnings: Forecasting breaches means problems surface before they become crises.
Faster decisions: Teams aren't waiting on approvals for small changes.
Many organizations also run live services alongside projects, so some professionals add an ITIL certification to understand how change, incident and service processes connect to project delivery. That combination gives teams a shared language when a project hands over to operations.
Common Pitfalls to Avoid
Management by exception only works when it's set up properly. Watch for these mistakes:
Setting tolerances so wide that nothing ever triggers an escalation.
Setting them so tight that the board is flooded with exception reports.
Reporting only actual breaches instead of forecasts.
Skipping regular highlight reports, which still keep the board informed.
Structured training, such as a PRINCE2 certification course, helps project managers practise setting realistic tolerances and writing clear exception reports before they face a live project.
Getting Started in Your Organization
You don't need a full methodology rollout to benefit. Begin with a pilot project and agree on tolerances with your sponsor before work starts. Define who can approve what, and write down the escalation triggers so no one has to guess. Review how it performs at each stage boundary, then refine. If your team is also responsible for service delivery, building skills toward an ITIL certification alongside project governance helps keep handovers smooth and expectations aligned.
Conclusion
Management by exception gives governance a sharper focus: set clear limits, trust the project manager inside them, and escalate quickly when those limits are threatened. The result is fewer pointless meetings, earlier warnings and better decisions at the right level. Start small, agree on tolerances up front, and let the exceptions do the talking.
