Study guide

3.4 Manage by Stages

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

3.4 Manage by Stages

Key Takeaways Explain This Topic AI

PRINCE2 breaks a project into management stages; the Project Board authorises one stage at a time and re-asserts control at each stage boundary.

Management stages (Project Board control/review points) are distinct from technical stages (work phases run by Team Managers); the two must not be conflated.

At each stage boundary the board reviews the End Stage Report, the next Stage Plan, and updated PID/Business Case/Project Plan before authorising continuation.

Last updated: August 2026

What the principle means

Manage by stages is the control architecture of PRINCE2. The project is divided into management stages , and the Project Board authorises one stage at a time . At the end of each stage the board is given a decision point — a stage boundary — at which it reviews progress, re-confirms the business case, and decides whether to authorise the next Stage Plan. The board never signs a blank cheque for the whole project at initiation; it signs a series of stage-by-stage cheques.

This is the mechanism through which several other principles actually bite:

Continued business justification is re-tested at the stage boundary, not only at start.

Manage by exception is enabled because each stage has its own tolerances set by the board.

Directing by the Project Board is exercised concretely at each boundary.

Management stages versus technical stages

The exam will test the distinction between management stages and technical stages , because they are often confused:

  • Dimension Management stage Technical stage
  • Purpose Control and review point for the Project Board A work phase producing specific products
  • Decided by Project Board (authorises each one) Team Manager (plans the work)
  • Planning unit A Stage Plan approved by the board A Team Plan within a Work Package
  • Boundary output End Stage Report + next Stage Plan Completed products, quality records

A management stage may contain one or several technical stages; the two do not have to align. The board cares about the management stage boundary because that is where its decision rights are exercised.

What is produced at a stage boundary

A stage boundary is a controlled event, and a defined set of outputs is produced so the board can take an informed decision:

  • Output Purpose
  • End Stage Report Reports actual progress for the stage just completed against its Stage Plan
  • Next Stage Plan The plan for the stage the board is being asked to authorise
  • Updated Project Plan Rolled forward to reflect actual progress and revised forecasts
  • Updated Business Case Re-justifies the project on the basis of current costs, benefits, and risks
  • Updated PID (if needed) Reflects any change to scope, scope baseline, or project controls
  • Lessons captured New experience recorded to the Project Log for future application

The board's decision at the boundary is a go/no-go: authorise the next stage, request a revised plan, or move to premature closure. This is the single most important decision moment in the PRINCE2 control cycle.

Application in exam scenarios

At Bloom's Level 4 the exam tests whether you can analyse a scenario and identify either the correct boundary action or a misunderstanding of stages. Typical scenarios:

A board that authorises stages 2 and 3 together at the end of stage 1. The correct analysis: this breaches manage by stages — the board may only authorise the next stage, not several in advance, because each authorisation must be informed by the End Stage Report of the preceding stage.

A team that treats the closure of a development phase as a stage boundary. The correct analysis: a development phase is a technical stage , not a management stage; the boundary decision lies with the Project Board, not the Team Manager.

A question on what the board reviews at the boundary: the End Stage Report, the next Stage Plan, and the updated Business Case — together these let it re-test continued business justification before authorising more spend.

Why the distinction matters in practice

If technical stages were used as the control unit, the board would be reviewing at points chosen by the delivery team — points that may not coincide with the moments where the business case or risk profile materially changes. Management stages are deliberately placed at the points where the board needs to re-assert control, regardless of where the technical work happens to sit.

How many stages, and where to place boundaries

PRINCE2 does not prescribe a fixed number of management stages, but the guidance gives principles for placing them. A stage boundary should sit where the board needs to re-assert control — typically where significant spend is committed, where a major risk is due to materialise, or where the business case is sensitive to new information. A short, low-risk project may need only two stages (initiation plus one delivery stage); a multi-year programme of work may need many more. The common trap is either to use too few stages (so the board loses control between boundaries) or too many (so the overhead of boundary reporting exceeds the value of the control). The exam may present a scenario with a single year-long stage and expect you to identify that the board has surrendered its control architecture.

Project Plan versus Stage Plan

The distinction between the Project Plan (the whole-project view, high level, rolled forward at each boundary) and the Stage Plan (the detailed plan for the next management stage only, approved by the board at the boundary) is central to the principle. The board never approves a detailed plan for the whole project at initiation — that would be a blank cheque. It approves the Project Plan as a coarse roadmap and a Stage Plan as the binding commitment for the next period. A scenario in which a PM presents a fully detailed 18-month plan at initiation and asks the board to approve it all is breaching the principle: the detail belongs in successive Stage Plans, each authorised at its boundary.

Exception path versus stage boundary

If a stage is heading off-track within its tolerances, the PM manages it. If a stage is forecast to breach its tolerances, the PM raises an Exception Report and the board takes a decision through the exception mechanism — without waiting for the stage boundary. The exception path is the principle's safety valve: it means the board is never trapped into inaction between scheduled boundaries. The exam may test whether you can distinguish an exception (triggered by tolerance breach) from a stage boundary (a scheduled control point).

Worked scenario: placing a boundary

A construction project has a design phase (6 months, £2m) and a build phase (18 months, £14m). The PM proposes a single management stage covering both. The correct analysis: this breaches manage by stages because the board would authorise £16m and 24 months at one point with no scheduled re-test. A better structure places a boundary between design and build, so the board reviews the design outputs, re-tests the Business Case against actual design costs, and authorises the build stage separately.