Without a way to track progress, your project will drift off course and you will only discover the disaster when it is too late to fix. The progress theme is your project's instrument panel: it gives you the gauges, warning lights, and checkpoints you need to steer the project to success. For the PRINCE2F exam, you need to understand how management stages, tolerances, and exception management work together to keep a project on track – and how the official management products (reports and logs) capture that progress formally.
Jump to a section
You plan a 250 km road trip from London to Manchester. Before you leave, you decide you will break the trip into three management stages: London to Birmingham (100 km), Birmingham to Stoke-on-Trent (60 km), and Stoke-on-Trent to Manchester (90 km). You set tolerances for each stage: you are willing to arrive at each checkpoint up to 15 minutes late, and you are prepared to spend up to £10 more on fuel than you budgeted. These are your time and cost tolerances.
As you drive the first stage, your fuel gauge drops faster than expected. You are still within your £10 cost tolerance, so you continue without calling anyone. This is working within tolerance. Halfway through the second stage, you realise you will arrive in Stoke 45 minutes late – far beyond your 15-minute tolerance. You pull over and phone your trip sponsor (your partner). You explain the delay and agree on an exception plan: you will skip a planned lunch stop and drive directly to Stoke. This is exception management. The project board (your partner) approves the plan, and you continue.
At the end of each stage, you send a highlight report (a quick text message) summarising progress. At the final destination, you produce an end project report (a summary of the whole trip). This analogy maps directly to the PRINCE2 progress theme: management stages replace the whole journey, tolerances are your buffers, and exception management is the emergency call when those buffers are breached.
The progress theme is one of the seven themes in PRINCE2. It answers the question: 'How do we know where we are, and how do we decide if we can continue?' It provides the governance mechanism to monitor actual progress against the plan, detect deviations, and decide what to do about them.
At the heart of the progress theme are three key concepts: management stages, tolerances, and exception management.
Management stages. A management stage is a section of the project that the project manager manages and for which the project board gives a one-time authorisation. PRINCE2 insists that a project is divided into at least two management stages: an initiation stage (where you plan the whole project in detail) and at least one delivery stage (where you do the work). You cannot skip stages or merge them. Why? Because the project board needs a formal control point at the end of each stage to check that everything is still viable before committing more money and resources. Each stage ends with a stage boundary assessment, where the project manager presents an end stage report and a next stage plan for approval.
Tolerances. Tolerances are the permissible deviations from a plan before the deviation becomes an issue that needs to be escalated. PRINCE2 defines six tolerance types: time, cost, quality, scope, risk, and benefit. Think of tolerances as a 'buffer zone'. For example, if a stage plan says the work will take 10 days, you might set a time tolerance of +/- 2 days. As long as the actual time stays between 8 and 12 days, the project manager can make decisions without involving the project board. Tolerances are set at three levels: project tolerances (the big limits for the whole project), stage tolerances (for each management stage), and work package tolerances (for teams doing specific work). If a forecast shows a deviation will exceed the stage tolerance, the project manager must escalate to the project board. This is a 'tolerance deviation'.
Exception management. Exception management is the process you follow when a forecast predicts that a tolerance will be exceeded. It is not a punishment – it is a safety valve. When a deviation is forecast, the project manager does not just keep going and hope for the best. Instead, they produce an exception report, which describes the deviation, its cause, the impact on the project, and options for recovery. The project board then decides what to do. They can either revise the plan (if the deviation is acceptable) or stop the project. If they decide to continue, they approve an exception plan, which replaces the current stage plan for the rest of the stage. The exception plan becomes the new plan for that stage, with its own tolerances.
Management products of the progress theme. PRINCE2 defines several formal documents (management products) that support the progress theme:
Business Case: Although it is the subject of its own theme, the business case is also a progress product because it contains the benefits and cost tolerances. The project board uses it to decide if the project is still worthwhile.
Project Plan: The high-level plan for the whole project, including project-level tolerances.
Stage Plan: The detailed plan for the current management stage, with stage-level tolerances.
Exception Plan: A plan that replaces a stage plan when a tolerance has been exceeded.
Work Package: An assignment of work to a team, including work package tolerances.
Checkpoint Report: A time-based report from the team manager to the project manager, usually weekly or bi-weekly, showing progress on the work package.
Highlight Report: A report from the project manager to the project board at intervals defined in the communication management strategy. It summarises progress, achievements, and any issues.
End Stage Report: A report produced at the end of each management stage, summarising performance against the stage plan.
End Project Report: A report produced at the end of the project, summarising overall performance and lessons.
Lessons Log: Although used throughout the project, it stores lessons from progress checks.
Issue Register: Records any issues that arise, including tolerance deviations.
Quality Register: Tracks quality checks, which are part of progress monitoring.
The progress theme replaces an ad-hoc 'hope for the best' approach with a structured control system. Without it, a project manager might hide problems until it is too late. With it, the project board can 'steer by exception' – meaning they only get involved when a tolerance is forecast to be breached. This allows the project manager to manage day-to-day without interference, while the project board retains overall control.
Set project tolerances
Before the project starts, corporate or programme management sets the overall tolerances for the six tolerance types (time, cost, quality, scope, risk, benefit). These are recorded in the project plan and the business case. This step defines the boundaries within which the project manager can operate without escalation.
Divide the project into management stages
The project manager and project board agree on the number and duration of management stages. Each stage will end with a formal approval point. The first stage is always initiation; you need at least one delivery stage. This step creates the control points that drive progress monitoring.
Set stage tolerances
At the beginning of each stage (including initiation), the project board sets stage-specific tolerances. These are tighter than project tolerances. For example, if the project time tolerance is +2 months, the stage tolerance might be +2 weeks. The project manager uses these to manage the stage day-to-day.
Monitor progress using checkpoint and highlight reports
Throughout the stage, the project manager receives checkpoint reports from team managers (covering work packages) and produces highlight reports for the project board. These reports compare actual progress against the stage plan's tolerances. If progress is within tolerance, no escalation is needed.
Escalate if tolerance is forecast to be exceeded
If the project manager forecasts any deviation that will exceed the stage tolerance, they do not wait. They produce an exception report, describing the deviation, its cause, impact, and options. This step triggers the exception management process, which moves decision-making to the project board.
Project board reviews and approves an exception plan
The project board reviews the exception report. They can reject the plan (which effectively stops the project) or approve it. If they approve, the project board authorises an exception plan, which replaces the current stage plan for the rest of the stage. The stage continues under the new plan with revised tolerances.
Produce end stage report and seek authorisation for next stage
At the end of each management stage, the project manager produces an end stage report, summarising performance against the stage plan (or exception plan). The project board reviews it and decides whether to authorise the next stage. This step repeats for each stage until the project ends.
An IT professional – let us call her Priya, a project manager at a UK retail bank – uses the progress theme every single day. Here is a concrete scenario.
Priya is managing a project to replace the bank's legacy customer account system with a modern cloud-based platform. The project board has set project tolerances: the project must finish within 18 months (time tolerance of +2 months) and cost no more than £2.5 million (cost tolerance of +£200,000). The project is divided into three management stages: Stage 1 (initiation – 2 months), Stage 2 (build – 10 months), Stage 3 (test and go-live – 6 months).
Step-by-step, here is what Priya does with the progress theme.
During Stage 1: Priya produces a detailed stage plan for Stage 2. She assigns work packages to her development team with clear tolerances: the team has 12 weeks to build the core migration module, with a cost tolerance of £50,000 and a quality tolerance of zero defects in the unit tests.
Weekly checkpoint reports: Every Friday, the team manager sends Priya a checkpoint report. It shows that the development team is on track but has used 80% of the time budget by week 9. Priya sees this is still within the stage tolerance (12 weeks +/- 1 week), so she does not escalate. She simply notes it in her highlight report.
Month 6 – an issue emerges: The development team hits an unexpected technical snag. The legacy system's data format is incompatible with the new cloud platform. The team forecasts a 3-week delay. Priya calculates that this delay will push completion of Stage 2 beyond the stage's time tolerance of 10 months +/- 2 weeks. She follows the exception management process.
Priya writes an exception report. She documents the cause (data format incompatibility), the impact (3-week delay, additional £30,000 cost for a data conversion tool), and three options: (A) accept the delay, (B) hire an external consultant to accelerate the fix (costs £50,000 but reduces delay to 1 week), or (C) skip the data conversion and lose some historical data (reduces scope). She submits the exception report to the project board.
Project board decides: The senior user (the bank's head of retail operations) reviews the options. They choose option A – accept the 3-week delay – because the overall project tolerance of +2 months is still not at risk. They approve an exception plan that extends Stage 2 to 10 months and 3 weeks, with the same cost tolerance adjusted to include the extra £30,000.
Priya implements the exception plan. She updates the stage plan, communicates the change to the team, and continues. She now reports progress against the new exception plan for the remainder of Stage 2.
End of Stage 2: Priya produces an end stage report. She compares actual performance against the original stage plan and the exception plan. She includes lessons learned (e.g., 'always test data format compatibility early'). The project board reviews the end stage report and approves Stage 3.
Throughout this process, Priya also updates the lessons log (recording the data format issue), the issue register (logging the tolerance deviation), and the quality register (recording that the data conversion tool passed quality checks). The highlight reports continue monthly to the project board, keeping them informed without micro-managing. This is a real, practical use of the progress theme – it provides a structured way to handle problems without panic, giving the project manager authority to act within tolerances and a clear escalation path when those tolerances are breached.
The PRINCE2F exam tests the progress theme heavily. Expect around 6-8 questions on this theme. The exam loves to test definitions and the flow of management products. Here is exactly what you need to know.
Key concepts tested: - Management stages: Know the definition: a section of the project that the project manager manages and the project board authorises one at a time. Remember that there must be at least two stages – initiation and at least one delivery stage. A common trap is confusing management stages with technical phases (like 'design phase' or 'testing phase'). PRINCE2 stages are management control points, not technical phases. - Tolerances: Memorise the six tolerance types: time, cost, quality, scope, risk, benefit. Know the hierarchy: project tolerances > stage tolerances > work package tolerances. The exam will ask who sets each: the corporate/programme management sets project tolerances, the project board sets stage tolerances, and the project manager sets work package tolerances. - Exception management: Understand the trigger: a forecast that a tolerance will be exceeded. The steps are: project manager produces an exception report (not an issue report or a highlight report – this is a common trap), project board reviews, project board approves an exception plan (which replaces the current stage plan). The exception plan is not a revision of the project plan; it is a new plan for the remainder of the stage.
Traps to watch for: - 'Which report is produced when a tolerance is forecast to be exceeded?' Answer: an exception report, not a highlight report or an end stage report. The highlight report is for routine reporting. - 'Can a project have only one management stage?' No, PRINCE2 requires at least two. A common distractor is 'yes, if it is a small project' – that is false. - 'Are tolerances optional?' No. Every plan must have tolerances. The exam might present a scenario where a plan has no tolerances and ask you to identify the omission. - 'What is the difference between an exception plan and a stage plan?' The exception plan replaces the current stage plan for the remaining portion of the stage. It is not a separate type of stage; it is a revised plan.
Management products to memorise: - Checkpoint report: produced by the team manager for the project manager. Covers a work package. - Highlight report: produced by the project manager for the project board. Covers the whole project (or stage). - End stage report: produced by the project manager at the end of each stage. - End project report: produced at the end of the project. - Exception report: produced when tolerance is forecast to be exceeded.
Correct answer pattern: When you see a question asking 'What should the project manager do next?' and the scenario describes a forecast tolerance breach, the correct answer is almost always: 'Produce an exception report'. If the scenario says the tolerance has already been breached (not just forecast), the answer is still the same – produce an exception report. Do not choose 'update the business case' or 'inform the project board informally' – the process demands a formal exception report first.
For questions about 'who sets tolerances', remember: project tolerances come from above the project board (corporate or programme), stage tolerances are set by the project board, work package tolerances are set by the project manager. This is a frequent multiple-choice trap where they swap the levels.
Finally, distinguish between 'Exception management' and 'Issue management': exception management is specifically for tolerance deviations, while issue management handles other problems (risks, issues, changes). They are not the same – but the exam might try to trick you into thinking an issue report is used for a tolerance breach (it is not).
Management stages are sections of a project that the project board authorises one at a time, and every PRINCE2 project must have at least two stages: initiation and at least one delivery stage.
Tolerances are mandatory on every plan and come in six types: time, cost, quality, scope, risk, and benefit.
Project tolerances are set by corporate or programme management, stage tolerances by the project board, and work package tolerances by the project manager.
When a forecast shows a tolerance will be exceeded, the project manager must produce an exception report, not a highlight report or an issue report.
An exception plan replaces the current stage plan for the remainder of the stage; it does not create a new management stage.
The checkpoint report is produced by the team manager for the project manager, while the highlight report is produced by the project manager for the project board.
The end stage report is produced at the end of every management stage and is the basis for the project board's decision to authorise the next stage.
Exception management is the formal process for handling tolerance deviations, and it is distinct from issue management which deals with other problems.
These come up on the exam all the time. Here's how to tell them apart.
Management Stage
A control point where the project board authorises the next set of work
Defined by governance decisions, not by the nature of the work
Each stage ends with a formal stage boundary assessment
Technical Phase
A grouping of similar technical activities (e.g., coding, testing)
Defined by the work itself, not by governance
No formal boundary assessment required between technical phases
Exception Report
Triggered by a forecast tolerance breach
Produced by the project manager for the project board
Contains options for recovery and asks for a decision
Highlight Report
Triggered by the regular reporting cycle (e.g., monthly)
Produced by the project manager for the project board
Summarises routine progress, issues, and next steps without requesting a decision
Exception Plan
Replaces a stage plan when tolerance is breached
Covers only the remainder of the current stage
Approved by the project board as part of exception management
Stage Plan
Created at the start of a management stage for the entire stage
Covers the full duration of the stage from beginning to end
Approved by the project board at the stage boundary
Project Tolerance
Applies to the entire project from start to finish
Set by corporate or programme management
Broader than stage tolerances (e.g., +2 months)
Stage Tolerance
Applies to a single management stage
Set by the project board
Tighter than project tolerances (e.g., +2 weeks)
End Stage Report
Produced at the end of each management stage
Compares actual performance against the stage plan
Leads to a decision to authorise the next stage or close the project
End Project Report
Produced once, at the end of the entire project
Summarises overall project performance, benefits realised, and lessons
Signals the formal closure of the project
Mistake
Management stages are the same as project phases like 'design phase' or 'testing phase'.
Correct
Management stages are control points based on management decisions, not technical activities. A stage can contain multiple technical phases, and a technical phase can span multiple stages.
Beginners often map stages to the natural sequence of work (design, build, test) because that is how life feels. PRINCE2 stages are about authorisation and governance, not technical process.
Mistake
Tolerances are optional; you can set them if you want, but it is fine to leave them blank.
Correct
Tolerances are mandatory on every plan (project plan, stage plan, work package). Without tolerances, the project manager has no defined authority and must escalate every minor deviation.
In everyday life, we sometimes work without formal buffers. People assume PRINCE2 is similarly flexible. But the exam and the method require tolerances to be stated explicitly.
Mistake
If a tolerance is exceeded, the project manager should immediately stop the project.
Correct
The project manager should first produce an exception report and escalate to the project board. The project board decides whether to stop, revise tolerances, or approve an exception plan. Stopping is one possible outcome but not automatic.
People think breach equals failure. In PRINCE2, a tolerance breach is a signal to reassess, not a death sentence. The exam wants you to know the correct escalation process, not the panic response.
Mistake
The highlight report is used to report a tolerance deviation.
Correct
The highlight report is for routine progress reporting to the project board. A tolerance deviation requires a formal exception report, which is a separate product with a different audience and purpose.
Because highlight reports are frequent (monthly, bi-monthly), beginners assume they are used for everything. The exam explicitly tests the distinction between routine reports and exception reports.
Mistake
An exception plan is a new management stage.
Correct
An exception plan is not a new stage. It is a revised plan for the current stage that replaces the existing stage plan. The stage itself remains the same; the plan for completing it changes.
The word 'plan' and 'stage' sound similar, so people confuse a new plan with a new stage. The exam includes this trap: 'The project board approves an exception plan, so a new management stage begins' – that is false.
Mistake
The business case is not part of the progress theme.
Correct
The business case is a key management product for the progress theme because it contains the benefit and cost tolerances. The project board uses the business case to decide if the project remains viable at each stage boundary.
PRINCE2 has seven themes, so beginners tend to silo them. The business case is covered in its own theme, but the progress theme uses it heavily. The exam tests cross-theme knowledge.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A management stage is a governance control point defined by when the project board decides to commit more resources. A technical stage (like 'coding' or 'testing') is a group of related work activities. Management stages and technical stages do not have to align; a management stage can contain multiple technical stages, and a technical stage can span management stages.
PRINCE2 defines six tolerance types: time, cost, quality, scope, risk, and benefit. Every plan must have tolerances for at least time and cost, and ideally for all six. The exam expects you to know all six by name.
Project-level tolerances are set by the corporate or programme management that commissions the project. The project board then sets stage-level tolerances, and the project manager sets work package tolerances. This is a three-level hierarchy.
An exception report is specifically for tolerance deviations – when a forecast shows a tolerance will be exceeded. An issue report is for any problem, change, or risk that does not involve a tolerance breach. They are two different management products with different triggers.
No, not without escalation. Once a tolerance is forecast to be exceeded, the project manager must stop other work and produce an exception report. The project board decides whether to approve an exception plan, which then allows work to continue. Working beyond tolerance without escalation is a governance failure.
A checkpoint report is a time-based report from the team manager to the project manager, detailing progress on a work package. It is usually produced weekly or bi-weekly. It gives the project manager detailed insight into whether the work package is on track within its tolerances.
Yes, because the business case contains the benefit and cost tolerances. At each stage boundary, the project board uses the business case to decide if the project should continue. So the business case is a key management product for both the business case theme and the progress theme.
If the project board does not approve the exception plan, the project cannot continue with the current plan. The project board may decide to close the project (premature closure) if the deviation is too severe or if the business case is no longer viable. The project manager would then produce an end project report.
You've finished Progress Theme. Continue through the PRINCE2F study guide to build a complete picture of the exam.
Done with this chapter?