7.3 Managing a Stage Boundary (SB) Process
Key Takeaways
- Managing a Stage Boundary (SB) is executed by the Project Manager at or near the end of each management stage (except the final stage).
- It is also invoked when the Project Board requests an Exception Plan following an escalated Exception Report.
- SB enables the Project Manager to provide the Project Board with key evaluation data: End Stage Report, Next Stage Plan, and updated Business Case.
- The process ensures that project viability is explicitly reassessed before committing corporate funds to the next stage.
- SB is NOT used at the end of the final management stage; the final stage transitions directly to Closing a Project (CP).
Last updated: July 2026
7.3 Managing a Stage Boundary (SB) Process
Exam Focus: Managing a Stage Boundary (SB) is the process that supports the principle of Manage by Stages. It provides a structured mechanism for the Project Manager to report stage completion, prepare the Next Stage Plan, update project baselines, and re-evaluate Business Case viability. Candidates must understand when SB is triggered, what products are created, and why SB is never used at the end of the final management stage.
Purpose and Triggers of Managing a Stage Boundary
The purpose of Managing a Stage Boundary (SB) is to enable the Project Manager to provide the Project Board with sufficient information to review the success of the current stage, approve the next Stage Plan, review the updated Project Plan, and confirm continued business justification.
Two Key Triggers for SB:
- Planned Stage Boundary: Approaching the end of a management stage (as scheduled in the current Stage Plan).
- Exception Stage Boundary: The Project Board instructs the PM to produce an Exception Plan after receiving an Exception Report during Controlling a Stage.
+----------------------------------+
| PLANNED STAGE END SCHEDULED |
+----------------------------------+
|
v
+-----------------------------------------------------------------------------+
| MANAGING A STAGE BOUNDARY (Project Manager) |
| |
| +-------------------+ +-------------------+ +-------------------------+ |
| | PLAN NEXT STAGE |->| UPDATE PROJ PLAN |->| UPDATE BUSINESS CASE & | |
| | (or Exception Plan| | & Management | | REGISTERS | |
| +-------------------+ | Approaches | +-------------------------+ |
| +-------------------+ | |
| v |
| +-------------------------+ |
| | REPORT STAGE END | |
| | (End Stage Report) | |
| +-------------------------+ |
+-----------------------------------------------------------------------------+
|
v Submits End Stage Report & Next Stage Plan
+-----------------------------------------------------------------------------+
| DIRECTING A PROJECT (Project Board) |
| Decision: Authorize Stage or Terminate Project |
+-----------------------------------------------------------------------------+
Key Objectives of the SB Process
The SB process allows the Project Manager to:
- Assure Board Control: Demonstrate to the Project Board that all products planned for the current stage have been completed and approved.
- Plan Next Management Stage: Create a detailed Next Stage Plan (or Exception Plan) defining products, costs, schedules, quality criteria, and stage tolerances for the upcoming period.
- Update Baseline Documents: Update the Project Plan to reflect actual performance to date and revised forecasts for future stages.
- Re-evaluate Viability: Revise the Business Case and Risk Register to verify that the project remains desirable, viable, and achievable.
- Review Management Approaches: Assess whether project management strategies (Digital and Data, Commercial, Quality, Risk, Communication) require adjustment for the next stage.
- Request Board Authorization: Formalize the request for Project Board authorization to proceed into the next management stage (via DP).
Step-by-Step Activities in Managing a Stage Boundary
SB comprises five core management activities:
1. Plan the Next Stage (or Produce an Exception Plan)
- Next Stage Plan: If at a planned boundary, the PM creates a detailed Stage Plan for the upcoming management stage, identifying products, dependencies, resources, and schedule.
- Exception Plan: If invoked due to a tolerance breach, the PM creates an Exception Plan covering the remaining period from the point of exception to the end of the current stage or project. If approved, the Exception Plan replaces the plan that was breached.
2. Update the Project Plan
- The PM updates the overall Project Plan by incorporating actual performance metrics from the completed stage and the updated forecast from the Next Stage Plan (or Exception Plan).
3. Update the Business Case
- The PM reviews the Business Case in light of actual costs, schedule variances, revised forecasts, and changed external market factors.
- Expected benefits, risks, and ROI calculations are updated to ensure the business justification remains robust.
4. Update Project Management Approaches & Registers
- The PM reviews and updates the management approaches (Quality, Risk, Communication, Commercial, Digital & Data) based on lessons learned.
- The Risk Register, Issue Register, Quality Register, and Lessons Register are brought fully up to date.
5. Report Stage End (Prepare End Stage Report)
- The PM prepares the End Stage Report, summarizing overall stage performance against the Stage Plan, product completion, quality achievements, budget/schedule variances, and risk profile.
- The End Stage Report, Next Stage Plan, and updated Business Case are submitted to the Project Board for review.
Deep Dive: Management Products Created or Updated in SB
| Product | Status in SB | Description & Key Purpose |
|---|---|---|
| End Stage Report | Created | Summarizes stage results, product handovers, target vs. actual metrics, and total stage expenditure. |
| Next Stage Plan | Created | Detailed plan for the upcoming management stage, providing target baselines for CS. |
| Exception Plan | Created (if applicable) | Replaces a breached Stage Plan or Project Plan to chart a recovery path to project completion. |
| Business Case | Updated | Revised to reflect current costs, revised benefit realization estimates, and ongoing ROI viability. |
| Project Plan | Updated | Revised master timeline and budget showing actuals to date and updated forecast for future stages. |
| Registers | Updated | Risk, Issue, Quality, and Lessons Registers refreshed with stage end data. |
Exception Plan vs. Stage Plan vs. Project Plan
+-----------------------------------------------------------------------------+
| PROJECT PLAN |
| Master plan covering the entire project timeline from start to finish. |
+-----------------------------------------------------------------------------+
|
+----------------------------+----------------------------+
v v
+------------------------------------+ +--------------------------+
| STAGE PLAN | | EXCEPTION PLAN |
| Detailed operational plan covering | REPLACES | Plan produced to recover |
| a single management stage. | <========== | from a forecast stage or |
| | Breached | project tolerance breach.|
+------------------------------------+ Stage Plan +--------------------------+
Key Rule for the Exam: An Exception Plan does not exist in parallel with a Stage Plan—it replaces the Stage Plan (or Project Plan) that exceeded tolerance once approved by the Project Board.
Why SB is NOT Used at the End of the Final Stage
A critical PRINCE2 7 exam distractor involves stage boundary execution at project completion:
- At the end of intermediate stages, the PM executes Managing a Stage Boundary (SB) to prepare for the next stage.
- At the end of the final management stage, there is no next stage to plan! Therefore, the PM does NOT execute SB. Instead, the PM executes Closing a Project (CP) to prepare for formal project shutdown and product handover.
Roles and Responsibilities in SB
- Project Board: Reviews the End Stage Report, Next Stage Plan, and updated Business Case during DP, and decides whether to authorize the next stage.
- Project Manager: Executes all SB activities—plans the next stage or drafts an Exception Plan, updates Project Plan/Business Case/registers, and writes the End Stage Report.
- Team Manager: Assists the PM by providing technical input, resource estimates, and draft Product Descriptions for the Next Stage Plan.
- Project Assurance: Verifies that Next Stage Plans are realistic, quality checks are complete, and the updated Business Case is credible.
High-Yield Exam Tips & Distractor Warnings
- Who approves the Next Stage Plan? The Project Board (in Directing a Project), NOT the Project Manager.
- When is an Exception Plan created? In SB, but ONLY after the Project Board instructs the PM to produce one following an Exception Report.
- What happens to the Business Case in SB? It is always updated and re-evaluated in SB to verify continued business justification before starting the next stage.
- Is SB executed during an exception? Yes! When an Exception Report is escalated in CS, the Project Board instructs the PM to run SB to produce an Exception Plan.
Test Your Knowledge
When is the Managing a Stage Boundary process executed?
A
B
C
D
Test Your Knowledge
What happens to a breached Stage Plan when an Exception Plan is approved by the Project Board?
A
B
C
D
Test Your Knowledge
Which management product compiled during SB provides the Project Board with a summary of the completed stage's performance?
A
B
C
D