Study guide

13.1 Managing a Stage Boundary

PRINCE2 Practitioner Version 7

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Exam Strategy & Open-Book Technique

2 PRINCE2 7 Method Overview

2.1 The PRINCE2 7 Method 2.2 What Changed in PRINCE2 7 2.3 Performance Targets, Tolerances & Project Context

3 PRINCE2 Principles (1–4)

3.1 Continued Business Justification 3.2 Learn from Experience 3.3 Defined Roles, Responsibilities & Relationships 3.4 Manage by Stages

4 PRINCE2 Principles (5–7) & Applying Principles

4.1 Manage by Exception 4.2 Focus on Products 4.3 Tailor to Suit the Project 4.4 Applying Principles in Context

5 People Management in Projects

5.1 Organisational & Project Ecosystems 5.2 Leadership in Projects 5.3 Team Culture & Diversity 5.4 Communication, Stakeholder Engagement & Change Management

6 Practices Overview & Business Case

6.1 The Seven Practices & Tailoring 6.2 Business Case: Desirability, Viability & Achievability 6.3 Business Case Lifecycle & Management Products 6.4 Business Case Application & Tailoring Scenarios

7 Practices: Organising & Plans

7.1 Organising: Roles & Accountability 7.2 Organising: 5-Step Ecosystem Technique 7.3 Plans: Three Levels & Product-Based Planning 7.4 Plans: Techniques, Tolerances & Tailoring

8 Practices: Quality & Risk

8.1 Quality: Planning, Control & Assurance 8.2 Quality Techniques & Management Products 8.3 Risk: Threats & Opportunities 8.4 Risk 5-Step Technique & Application

9 Practices: Issues

9.1 Issues Practice: Issue vs Change & Categories 9.2 Issues 5-Step Technique & Supporting Techniques 9.3 Change Control, Configuration & Priority/Effort Assessment

10 Practices: Progress, Sustainability & Application

10.1 Progress: Controls, Tolerances & Reports 10.2 Sustainability as the 7th Performance Target 10.3 Tailoring the Practices 10.4 Practices Application Scenarios (BL4)

11 Processes: Model, Starting, Directing & Initiating

11.1 The Seven Processes & Process Model 11.2 Starting Up a Project 11.3 Directing a Project 11.4 Initiating a Project

12 Processes: Controlling a Stage & Product Delivery

12.1 Controlling a Stage 12.2 Managing Product Delivery 12.3 Stage Control & Exception Scenarios (BL4) 12.4 Work Packages & Reporting Cycle

13 Processes: Stage Boundary, Closing & Tailoring

13.1 Managing a Stage Boundary 13.2 Closing a Project 13.3 Tailoring the Processes 13.4 Process Application Scenarios (BL4)

14 Tailoring, Management Products & Exam Technique

14.1 Tailoring to Project Environment, Scale & Agile 14.2 Management Products & the v7 Project Log 14.3 Final Exam Technique, Full Scenarios & Common Traps

13.1 Managing a Stage Boundary

Key Takeaways Explain This Topic AI

Managing a Stage Boundary is performed by the Project Manager at the end of every management stage except the final one, which is closed by the Closing a Project process.

Its purpose is to give the Project Board the information it needs to decide whether to authorise the next stage: an End Stage Report, an updated Project Plan, an updated Business Case, and the next Stage Plan.

If the stage is forecast to breach its tolerances, the PM produces an Exception Plan for board approval rather than simply reporting stage end.

Key outputs are the End Stage Report, the next Stage Plan, the updated Project Plan and PID, and the request to authorise the next stage.

Last updated: August 2026

When the Process Runs

Managing a Stage Boundary (SB) is performed by the Project Manager at the end of each management stage — with one important exception. It is not performed at the end of the final stage, because the final stage is closed by the Closing a Project process instead. It also does not run when a project is being prematurely closed : in that situation the PM moves straight into the premature-closure path within Closing a Project.

The process exists because PRINCE2's manage by stages principle demands that the Project Board re-authorises the project at every stage boundary. A stage is the period for which the board has delegated authority to the PM; once that period ends, the board must look again at the Business Case, the plan, and the risks before committing further investment.

Purpose and Objectives

The purpose of Managing a Stage Boundary is to:

Provide the board with the information it needs to decide whether to authorise the next stage .

Confirm that the Business Case remains viable and that the project is still worth doing.

Update the Project Plan so that it reflects actual progress and the latest forecast for the remainder of the project.

Update the PID where any baseline has changed.

Review and update risks and the Risk Management Approach .

In short, the process refreshes the project's baselines and its justification, and it packages them for the board's decision.

Activities and Their Outputs

Activity What the PM does Primary output

Plan the next stage Draft the next Stage Plan with its tolerances, dependencies, and resource needs Next Stage Plan

Update the Project Plan Roll actuals into the Project Plan and re-forecast the remainder Updated Project Plan

Update the Business Case Re-examine costs, benefits, and timescales; update the Benefits Management Approach Updated Business Case

Review and update risks Re-assess the risk register and refresh the Risk Management Approach Updated Risk Register

  • Update the PID Record any changes to scope, roles, controls, or approaches Updated PID
  • Report stage end Compile the End Stage Report and request authorisation End Stage Report

Produce an Exception Plan (if needed) If the stage is forecast to breach tolerance, propose an Exception Plan instead Exception Plan

End Stage Report vs Exception Plan

The End Stage Report is the normal boundary product. It summarises what the stage set out to do, what it actually achieved, how the Project Plan and Business Case have moved, the key risks and issues, and the PM's recommendation for the next stage. The board uses it, alongside the next Stage Plan and the updated Business Case, to decide whether to authorise the next stage.

An Exception Plan is a different beast. If, during the stage or at its boundary, the PM forecasts that the stage will breach its tolerances , the PM first raises an Exception Report to the board. The board can then ask the PM to produce an Exception Plan — a replacement plan for the remaining work that brings the project back within (or proposes revised) tolerances. Where an Exception Plan is produced for the remainder of the current stage, it is submitted for board approval instead of a routine End Stage Report and next Stage Plan.

What the board reviews at the boundary

The End Stage Report (actuals versus plan for the stage just completed).

The updated Business Case — is the project still justified?

The updated Project Plan — is the overall forecast still acceptable?

The next Stage Plan — is the proposed next chunk of work worth authorising, with tolerances the board is content to delegate?

The updated risk picture and any PID changes.

The board's decision options are straightforward: authorise the next stage , authorise the next stage with conditions , defer the decision pending more information, or stop the project (triggering premature closure).

Exam-relevant distinctions

Who performs it? The Project Manager — not the Project Board. The board receives and decides on the outputs.

When is it NOT performed? At the end of the final stage (Closing a Project takes over) and when the project is being prematurely closed.

What is the difference between an End Stage Report and an Exception Plan? The End Stage Report reports a completed stage and proposes the next one; an Exception Plan is a recovery plan produced when tolerances are forecast to be breached.

What does the PM update at a boundary? The Project Plan, the Business Case (and Benefits Management Approach), the Risk Management Approach, and the PID where anything has changed.