Exception Report: When It Is Raised and What It Contains
An exception report is raised when a tolerance on time, cost, scope, quality, risk or benefit is forecast to be breached. It states the deviation, its cause, the effect on the project and the business case, the options available, and the project manager's recommendation. It goes to the board outside the normal reporting cycle, at the point of forecast rather than after the fact.
What it contains
| Section | What it has to say |
|---|---|
| Exception | Which tolerance is affected and by how much, in numbers |
| Cause | Why it happened, without narrative defence |
| Consequences | Effect on the stage, on the project, and on the business case |
| Options | Normally three or four, each with cost, time and risk consequences |
| Recommendation | Which option the project manager proposes, and why |
| Lessons | Anything already learned that changes how the rest is run |
| Decision needed by | The date after which the options start closing off |
How it is used
The trigger is a forecast, not an actual. The whole mechanism depends on raising the report when the breach is predicted, while options still exist. Once the date has passed or the money is spent, the board is being informed rather than being asked to decide, and the options section is empty.
The board's response is usually one of four: approve the recommended option, choose a different one, request an exception plan for the remainder of the stage, or stop the project. The report is written to make that choice possible, which is why the options section is the part that takes the work. A single option with a recommendation attached is not an exception report; it is a request for approval.
Exception reporting only functions where tolerances were set in the first place. That is a governance design question — which limits, at what level, escalating to whom — covered in programme governance. In practice the exception lands at the next available governance forum or triggers an extraordinary session, and it is presented alongside the material described in the steering committee report guide. The SteerCo deck carries a decision slide built for exactly this: options with a recommendation, and space for the decision to be recorded.
Where the exception is a cost or scope breach, the underlying change usually needs a change request behind it, logged with its impact assessment in the change request log. Where the exception is severe enough that the delivery approach itself is in question, the response is a structured recovery rather than a single decision, which is what the project recovery plan is built around.
Where it goes wrong
- Raised after the breach. The most common failure. The report becomes a notification and the board's only real option is to accept it.
- No tolerances set. Without an agreed limit there is no defined trigger, so escalation depends on individual judgement and varies by person.
- One option. A report offering only the recommendation removes the decision the board exists to take.
- Cause written as defence. Where the cause section is an argument about blame, the rest of the report gets read sceptically.
- Business case impact omitted. A schedule slip that delays benefits by two quarters changes the investment, and the board needs that stated.
- Buried in the routine report. A forecast breach mentioned in a status update has not been escalated, whatever the author intended.
Related terms
Tolerance — the agreed limit whose forecast breach triggers the report. Highlight report — the routine report the exception sits outside. Exception plan — the replacement plan for the remainder of the stage, where the board asks for one. Project board — the recipient and decision maker. Change request — often the mechanism that implements whatever the board decides.
Questions
What triggers an exception report?
A forecast breach of an agreed tolerance on time, cost, scope, quality, risk or benefit. The trigger is the forecast, not the actual breach, which is what leaves the board with options.
Who writes an exception report?
The project manager, to the project board. In programme structures a programme manager raises the equivalent to the sponsoring group when a programme-level tolerance is at risk.
How quickly should an exception report be raised?
As soon as the breach is forecast. Waiting for the next scheduled report removes options and converts a decision into a notification.
What is an exception plan?
A replacement plan covering the remainder of the stage or project, prepared when the board decides to continue on a changed basis. It is approved in the same way the original plan was.