# Managing a Stage Boundary Process

> Chapter 17 of the Courseiva PEOPLECERT-PRINCE2-FOUNDATION curriculum — https://courseiva.com/learn/peoplecert-prince2-foundation/managing-a-stage-boundary-process

**Official objective:** 3.7 — Describe the purpose, objectives, and key activities of the managing a stage boundary process, including stage assessments and exception plans.

## Introduction

How do you formally check if a project is still on track before spending more money on the next chunk of work? The managing a stage boundary process gives you a structured moment to stop, review the completed stage, compare actual results against the plan, and decide whether to continue, adjust, or stop entirely — which prevents runaway budgets and missed deadlines.

## The House Renovation Phase-Gate Analogy

Your kitchen renovation is half-finished. The old cabinets are ripped out, the new plumbing is roughed in, and the electrician has run the wires. You are standing in the dusty shell of what will become your dream kitchen, and it is time to make a critical decision: do you push forward with the agreed plan, or do you pause, inspect the work so far, check the budget, and then decide if the original plan still makes sense?

This exact moment is the managing a stage boundary in the world of PRINCE2. In a house renovation, every phase has a go/no-go gate. Your contractor does not just blindly start tiling the backsplash. Instead, they formally finish the current phase — say, rough-in work — and present you with a report. They show you the actual costs versus the planned budget. They update the schedule based on real-world delays (the custom cabinets took six weeks, not four). They also remind you of the original plan: the high-level blueprint for the entire house.

Now you look at your bank account. Costs are creeping up. You might decide to drop the fancy Italian marble and pick cheaper quartz. That is an exception plan — a revised plan to handle a deviation from the original budget, without scrapping the whole project. The managing a stage boundary process is the formal checkpoint where you, the project board (representing the client), review the stage's performance, update the big-picture plan, and give the green light — or a revised, exception-based plan — for the next phase. It keeps the project from drifting off course without anyone noticing until it is too late.

## Core explanation

The managing a stage boundary (SB) process is one of the seven PRINCE2 processes. It is triggered at the end of each management stage (except the final one) to provide a formal review point. Think of it as a safety checkpoint between finishing one chunk of work and starting the next.

Let us define the key terms:

- Management stage: A section of the project where the project manager is given authority to spend a specific amount of time and money. Each stage ends with a decision point.
- Project board: The group of key decision-makers — typically the executive (who owns the business case), the senior user, and the senior supplier — who approve plans and make major decisions.
- Business case: The document that justifies the project's existence. It contains costs, benefits, risks, and the reason for doing the project.
- Exception plan: A detailed plan created when a stage is forecast to exceed its tolerances (like going over budget by more than 10%). It replaces the current stage plan, not the whole project plan.
- Tolerances: The acceptable deviation allowed for a plan (time, cost, scope, risk, quality, benefits) without needing to escalate to the project board.

Now, why does this process exist? Without it, a project manager could keep spending money stage after stage, and the project board would only find out about problems at the very end — when it is too late to correct course. The SB process forces transparency. It answers three questions: Did we deliver what we promised in this stage? Is the business case still viable? And what is the plan for the next stage?

The process has several key activities:

1. Assure the project board that all products in the current stage have been completed and approved. A product is any deliverable — a document, a piece of software, a report.
2. Provide the project board with information needed to evaluate the stage's performance. This includes comparing actual costs and time against the stage plan.
3. Update the project plan with actual figures from the completed stage, making the big-picture plan more accurate.
4. Update the business case with any new information. For example, if a new competitor entered the market, the benefits forecast might need adjusting.
5. Report any lessons learned from the stage so the next stage (or future projects) can avoid the same mistakes.
6. Produce the next stage plan, which details the work for the upcoming stage.
7. Create an exception plan if the current stage has exceeded, or is forecast to exceed, its tolerances. This is a major event — it signals the original plan is no longer viable.
8. Seek approval from the project board to proceed with the next stage (or to implement an exception plan).

The SB process directly replaces the idea of simply 'the next stage starts when the previous one ends.' Instead of a handover with no review, it creates a formal gateway. The project board cannot just sit back; they must actively approve the next stage or ask for changes.

Crucially, the SB process is not used at the end of the final stage. At that point, the project closure process takes over, because there is no next stage to plan for.

Think of it as a series of checkpoints on a road trip. You planned a route from London to Edinburgh with stops at five cities. After each city, you do not just drive to the next one blindly. You check your fuel, your time against the schedule, whether the destination is still worth it, and you update the route on your map for the remaining legs. The SB process is that stop-and-check ritual, formalised into a repeatable procedure.

For the PRINCE2 Foundation exam, you need to remember that the SB process is all about control. It ensures the project board remains in charge, not the project manager. It also provides a structured way to handle problems — through exception plans — before they derail the whole project.

## Real-world context

Let us walk through a realistic scenario. Sarah is a project manager at a mid-sized logistics company, LogiMove. She is managing a project to implement a new warehouse management system (WMS). The project has five stages: requirements gathering, system configuration, testing, deployment, and handover.

Sarah has just finished the testing stage. The budget for testing was £50,000, and the actual spend was £58,000. The testing took 12 weeks instead of the planned 10. But the quality was high, with fewer bugs than expected. Now she must perform the managing a stage boundary process.

Step by step, here is what Sarah does:

- She reviews the 'test completion report' to confirm that all test products (test scripts, bug reports, sign-off documents) are complete and approved by the quality team.
- She gathers the actual cost and time data from the accounting system and her project schedule.
- She updates the project plan: she replaces the estimated figures for the testing stage with actual figures. Now the remaining budget for deployment and handover is recalculated.
- She updates the business case. The testing revealed that the WMS is more complex than expected, which might reduce the expected efficiency benefits by 5%. She adds this as a note for the project board.
- She collects lessons learned from the testing team. One major lesson: the test environment was too small, causing delays. She adds this to the lessons log so the deployment stage can plan for a bigger environment.
- She prepares the next stage plan for deployment. The plan includes activities like data migration, user training, and go-live support. The budget for this stage is £100,000, duration 8 weeks.
- She notices that the testing stage exceeded its tolerance for cost (the tolerance was £5,000 over, but actual overspend was £8,000). This means she must create an exception plan for the testing stage. However, since testing is already complete, the exception plan covers a different scenario: she proposes reducing the deployment stage budget by £3,000 and duration by 1 week to compensate.
- She presents the end stage report and the exception plan to the project board in a meeting. The board discusses whether the benefits still justify the cost, given the reduced benefits. They approve the exception plan and give the go-ahead for deployment.

What does Sarah actually do differently from a manager who is not using PRINCE2? She does not just assume everything is fine. She documents every deviation, presents it formally, and lets the board make an informed decision rather than covering up the overspend. This protects her — and the company — from accusations of mismanagement later.

## Exam focus

The PRINCE2 Foundation exam tests the managing a stage boundary process in several specific ways. Here is what you must know.

Key concepts they love to test:

- The purpose of the SB process: to provide the project board with enough information to review the current stage, approve the next stage, or approve an exception plan.
- When SB is used: at the end of every management stage except the final one. The final stage ends with the closing a project process, not SB.
- What triggers SB: the completion of the current stage's work, or a request from the project board to produce an exception plan.
- The difference between a stage plan and an exception plan: a stage plan is created at the beginning of a stage; an exception plan replaces it when tolerances are forecast to be exceeded.
- The relationship between SB and the business case: SB is the main opportunity to re-evaluate the business case and decide if the project is still worthwhile.
- Who approves the next stage: the project board. Not the project manager, not the team.
- What outputs the SB process produces: an end stage report, a next stage plan (or exception plan), and updated project plan, business case, and risk register.

Common exam traps:

- Trap 1: They ask 'Which process is used at the end of every stage?' The answer is not SB at the final stage. Many candidates choose SB for all stages, but the final stage uses closing a project.
- Trap 2: They ask 'Who creates the exception plan?' The answer is the project manager, not the project board. The project board approves it, but the manager writes it.
- Trap 3: They ask 'Is an exception plan a type of project plan?' No. An exception plan replaces a stage plan, not the project plan. The project plan still covers the entire project; the exception plan just covers the revised way to finish the current stage.
- Trap 4: They ask 'What does the end stage report contain?' Remember: it summarises performance of the current stage against the stage plan, not the whole project.
- Trap 5: They ask 'What happens if the project board does not approve the next stage?' The project can be stopped or directed to create an exception plan. It is not automatic that the project continues.

Question types:

- Multiple choice questions asking which process is triggered by a scenario.
- Multiple choice questions asking which document is produced by SB.
- Multiple choice questions asking who is responsible for an activity within SB.
- True/false statements about when SB is used.
- Matching questions linking outputs to processes.

For each exam question, read carefully whether the scenario describes a stage boundary (SB is relevant) or the end of the final stage (closing a project is relevant). This distinction is the most common discriminator.

## Step by step

1. **Receive notification of stage completion** — The project manager is informed that all products (deliverables) planned for the current stage are complete and approved. This triggers the start of the managing a stage boundary process.
2. **Prepare the end stage report** — The project manager documents the stage's actual performance against the stage plan — including cost, time, quality, and risk. This report gives the project board a clear picture of what happened.
3. **Update the project plan and business case** — The project manager replaces estimated figures from the completed stage with actual figures in the project plan. Any new information that affects the business case (e.g., changed benefits or costs) is added.
4. **Plan the next stage (or produce an exception plan)** — If the current stage stayed within tolerances, the project manager creates a detailed stage plan for the next stage. If tolerances were exceeded, an exception plan for the current stage is created instead.
5. **Seek project board approval** — The project manager presents the end stage report, the next stage plan (or exception plan), and any updated documents to the project board. The board reviews and decides whether to approve the next stage, request an exception plan, or stop the project.

## Comparisons

### Managing a Stage Boundary (SB) vs Closing a Project (CP)

**Managing a Stage Boundary (SB):**
- Used at the end of every management stage except the final one
- Produces an end stage report and a next stage plan (or exception plan)
- Focuses on reviewing the current stage and planning the next one

**Closing a Project (CP):**
- Used only at the end of the final stage
- Produces a project closure report and handover plan
- Focuses on closing the project, releasing resources, and archiving documents

### Exception Plan vs Stage Plan

**Exception Plan:**
- Created when a stage is forecast to exceed tolerances
- Replaces the current stage plan, not the project plan
- Approved by the project board as a corrective action

**Stage Plan:**
- Created at the start of a management stage
- Defines the work, budget, and schedule for the upcoming stage
- Approved by the project board as the original plan

### End Stage Report vs Lessons Log

**End Stage Report:**
- Summarises the current stage's performance against the stage plan
- Mandatory output of the managing a stage boundary process
- Covers cost, time, quality, and risk for that single stage

**Lessons Log:**
- Records lessons learned throughout the entire project
- Updated continuously, not just at stage boundaries
- Used for future projects and stages, not just one stage

## Common misconceptions

- **Misconception:** The managing a stage boundary process is the same as the 'closing a project' process because both involve ending something. **Reality:** SB ends only a middle or first stage and plans the next one, while closing a project ends the entire project with no further stages. They are separate processes with distinct purposes. (Beginners hear 'end of stage' and think 'finish' without realising that at a stage boundary, the project is still ongoing — it is a break, not an ending.)
- **Misconception:** The project manager can approve the next stage plan without waiting for the project board. **Reality:** Only the project board can approve the next stage plan. The project manager prepares it, but the board must authorise it formally. (In many non-PRINCE2 environments, managers have more autonomy. The rigid separation of duties in PRINCE2 (where the board controls stage boundaries) feels unnatural to people used to flatter structures.)
- **Misconception:** An exception plan is created only when a problem has already happened and the stage is over. **Reality:** An exception plan is created when a stage is forecast to exceed its tolerances — meaning it can be created during a stage, before the problem gets worse, to prevent failure. (People think 'exception' means 'after the fact', but in PRINCE2, it is a preventive tool. The confusion comes from everyday language where 'exception' means 'an error that already occurred'.)
- **Misconception:** The end stage report is optional — you can skip it if the stage went well. **Reality:** The end stage report is a mandatory output of the managing a stage boundary process. It must be produced for every stage boundary, regardless of how well the stage performed. (In practice, many organisations skip documentation when things go smoothly. PRINCE2 requires it every time to maintain discipline, which feels bureaucratic to beginners.)
- **Misconception:** The managing a stage boundary process only reviews the current stage — it does not look ahead. **Reality:** SB reviews the current stage's performance AND plans the next stage (or creates an exception plan for the current stage). It is both backward-looking and forward-looking. (The name 'stage boundary' sounds like a fence around the finished stage, not a launchpad for the next one. Beginners overlook the forward-planning aspect.)

## Key takeaways

- The managing a stage boundary process is triggered at the end of every management stage except the final one.
- The process produces two essential outputs: an end stage report (reviewing the completed stage) and a next stage plan (or exception plan).
- Only the project board can approve the next stage plan — the project manager prepares it but cannot authorise it.
- An exception plan replaces a stage plan, not the whole project plan, and is created when tolerances are forecast to be exceeded.
- The business case is re-evaluated at each stage boundary to confirm the project is still worth doing.
- The SB process is not used at the end of the final stage — the closing a project process handles that instead.
- Lessons learned from the current stage are documented and used to improve the next stage and future projects.
- The SB process ensures the project board stays in control by formalising decision points between stages.

## FAQ

**Does the managing a stage boundary process happen at the end of every stage?**

No, only at the end of every management stage except the final one. The final stage uses the closing a project process instead.

**Who approves the next stage plan in the managing a stage boundary process?**

The project board approves the next stage plan. The project manager prepares it but cannot authorise it without the board's decision.

**What is an exception plan in PRINCE2?**

An exception plan is a plan that replaces a stage plan when the stage is forecast to exceed its tolerances. It describes a revised approach to complete the stage.

**What is the difference between a stage plan and an exception plan?**

A stage plan is the original plan for a management stage, created at the start. An exception plan replaces that stage plan when tolerances are breached, and is approved by the project board.

**Is the end stage report the same as the lessons log?**

No. The end stage report summarises the stage's performance (cost, time, quality). The lessons log is a separate document that records lessons learned, which is updated during the SB process but is not the same report.

**Can the project manager decide to skip the stage boundary if the stage went perfectly?**

No. The managing a stage boundary process is mandatory at every stage boundary (except the final one), even if the stage performed perfectly. It ensures discipline and decision-making.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/peoplecert-prince2-foundation/managing-a-stage-boundary-process