PRINCE2® wiki

Exception report

An exception report is typically an issue report that documents a situation where a project element has exceeded its agreed tolerance levels. The project manager produces this report when a stage plan or project plan is forecasted to surpass its predefined tolerances. The report is submitted to the project board, providing options and recommendations for proceeding so the board can make an informed decision.

Tolerances

PRINCE2 recognizes seven types of tolerances:

From an issue management perspective, an exception report can be seen as a major issue report detailing a significant problem that requires escalation.

Timeline

An exception report is typically created during the controlling a stage process when the project manager reviews new or existing issues. If an issue or risk is forecasted to exceed tolerance and put the stage or project at risk, the project manager must escalate it by creating an exception report.

Sometimes, the project manager may relabel an issue report as an exception report when an issue grows beyond tolerance limits and requires project board intervention.

Source data

The exception report is compiled using the following key project documents and sources:

Format

The exception report can be communicated in various formats, depending on urgency and organizational preferences:

If the situation is urgent, an oral exception report can be given first (stay calm and concise). Follow up with a written report if necessary.

Tips

The following tips help you have better exception reports:

—o—

Written by Frank Turley.

If you have questions or doubts after using this wiki, you can ask for help on the Facebook or LinkedIn study groups.