What are PRINCE2 Stages?
PRINCE2 stages divide a project into manageable sections so that work can be planned, monitored, controlled, and authorised without committing to the entire project in one go. Every PRINCE2 project has at least two management stages: an initiation stage and at least one further stage. Larger or more complex projects may use additional stages.
Remember: PRINCE2 stages are not the same as the seven PRINCE2 processes. Processes describe management activities across the project lifecycle, while stages provide controlled sections in which the project is managed.
What Are the Different PRINCE2 Stages?
PRINCE2 stages (more specifically called management stages) divide a project into sections that the Project Manager manages on behalf of the Project Board. PRINCE2 uses stages to create manageable periods of work and regular decision points. Every project has at least two management stages, but the exact number and length are tailored to the project.
Instead of approving all detailed work at the beginning, the Project Board authorises the project one stage at a time. The Project Manager can then manage the current stage within agreed tolerances.
At the end of a stage, the project can be reviewed before further resources are committed.
This is part of the Manage by Stages principle and helps PRINCE2 balance two important needs: giving the Project Manager enough authority to manage day-to-day work while allowing the Project Board to retain overall control.
You can explore how this principle fits alongside the other six in our guide to the seven PRINCE2 principles.
Pre-project
The initial project idea is examined to determine whether it is worthwhile committing resources to detailed initiation.
Key business representatives, the Project Executive, the Project Manager, and the developing Project Board.
Establish whether there is enough justification and information to initiate the project properly.
Starting Up a Project and Directing a Project.
How Many Stages Are There in PRINCE2?
A PRINCE2 project has at least two management stages: an initiation stage and at least one further management stage. PRINCE2 does not prescribe one fixed number of stages for every project. Additional stages can be used where they provide useful planning, control, and decision points.
This is one of the easiest areas of PRINCE2 to misunderstand.
There are seven PRINCE2 processes, yes – but that doesn’t mean there are seven PRINCE2 stages.
The appropriate stage structure depends on the project. Factors like risk, complexity, uncertainty, important decision points, and the wider organisational context can all influence where stage boundaries are most useful.
In other words, a relatively straightforward project may need fewer management stages than a larger or more uncertain project.
Stage lengths don’t have to be equal either. A project might benefit from a relatively short stage around a high-risk or uncertain area, and a longer stage where work is more predictable.
What Does the PRINCE2 Project Lifecycle Look Like?
The PRINCE2 project lifecycle moves from early pre-project activity into initiation, through one or more further management stages, and eventually into the final stage and controlled project closure. Processes operate around and within this lifecycle rather than representing individual stages themselves.
A simplified journey looks a bit like this:
- Pre-project – the initial idea is examined to determine whether detailed initiation is justified.
- Initiation stage – the foundations for managing the project are established.
- Subsequent management stage or stages – authorised project work is managed and delivered in controlled sections.
- Final management stage – the remaining authorised work is managed as the project approaches its planned end.
- Closure – acceptance, performance, lessons, follow-on actions, and formal closure are addressed.
The seven processes provide the management activity around this journey. For example, Directing a Project operates at Project Board level across much of the lifecycle, while Controlling a Stage is used to manage authorised delivery stages.
For a process-by-process explanation, explore how the seven PRINCE2 processes work across the project lifecycle.
PRINCE2 Project Stages at a Glance
| Lifecycle point | What is happening? | Main management focus | Relevant process activity |
|---|---|---|---|
| Pre-project | The project idea is assessed before detailed initiation | Establish whether initiation is justified | Starting Up a Project and Directing a Project |
| Initiation stage | The basis for managing and controlling the project is established | Business justification, planning, controls, approaches, and project definition | Initiating a Project and Directing a Project |
| Subsequent management stage(s) | Authorised project work is managed and products are delivered | Progress, delivery, risks, issues, quality, tolerances, and control | Controlling a Stage, Managing Product Delivery, and Directing a Project |
| Stage boundary | Current performance and future plans are reviewed | Continued justification and readiness for what comes next | Managing a Stage Boundary and Directing a Project |
| Final management stage | Remaining project work is managed as the project approaches completion | Delivery, acceptance readiness, and controlled conclusion | Controlling a Stage, Managing Product Delivery, Closing a Project, and Directing a Project |
| Closure | The project is brought to a controlled end | Acceptance, evaluation, lessons, follow-on actions, and formal closure | Closing a Project and Directing a Project |
What Is a Management Stage in PRINCE2?
A management stage is a section of the project that the Project Manager manages on behalf of the Project Board at one time. Each stage has an authorised Stage Plan and agreed tolerances, giving the Project Manager room to manage day-to-day work while keeping the Project Board in overall control.
Think of it as a management control window: instead of asking the Project Board to approve every daily decision, PRINCE2 establishes what the Project Manager is authorised to manage during the current stage.
The Project Manager can then monitor progress, authorise work, respond to issues and risks, take appropriate corrective action, and report upwards while the stage remains within the authority delegated to them.
This connects Managing by Stages closely with another PRINCE2 principle: Manage by Exception.
Why Does PRINCE2 Manage Projects by Stages?
PRINCE2 manages projects by stages so that detailed planning, control, investment, and major decisions can happen at appropriate points rather than all being fixed at the start. Stage boundaries give decision-makers opportunities to review current information before committing to further work.
This has several practical benefits.
1. You don’t have to plan everything in equal detail on day one
The immediate stage can be planned at a useful level of detail while later work remains at a higher level until better information becomes available.
2. Major decisions can happen when they matter
Stage boundaries can be positioned around meaningful business, investment, risk, or technical decisions.
3. The Project Board retains control without micromanaging
Once a stage is authorised, day-to-day control is delegated to the Project Manager within agreed tolerances.
4. The project can respond to change
Information available several months into a project may be very different from the assumptions made at the beginning. Reviewing the project stage by stage creates opportunities to adapt future plans.
5. Continued business justification can be checked
A project shouldn’t continue simply because it was worthwhile when it started. Stage boundaries provide natural points for checking whether continuing still makes sense.
For a broader explanation of how Business Case, Plans, Progress, Risk, and the other management areas work throughout PRINCE2, explore the seven PRINCE2 practices.
What Happens During a PRINCE2 Management Stage?
During an authorised management stage, the Project Manager controls the stage within the authority and tolerances agreed by the Project Board. Work is authorised and monitored, products are delivered, progress is reported, risks and issues are managed, and exceptions are escalated when necessary.
Imagine a company is introducing a new customer booking platform.
One management stage might cover a particular period of development and testing.
During that stage:
- the Project Manager authorises appropriate work;
- delivery teams create and test agreed products;
- progress is monitored against the Stage Plan;
- issues and risks are reviewed;
- quality activities take place;
- the Project Board receives agreed progress information; and
- anything forecast to exceed the Project Manager’s delegated tolerance is escalated.
So, the stage is more than a collection of technical tasks – it’s a defined management and control period.
What Happens at a PRINCE2 Stage Boundary?
At a PRINCE2 stage boundary, the current stage is evaluated, and the Project Board receives the information it needs to decide whether and how the project should continue. The Project Manager reviews performance, updates relevant project information, prepares the next Stage Plan where appropriate, and requests authorisation for the next stage.
A stage boundary is not just:
“Stage 1 finished. Start Stage 2.”
It’s a very deliberate control point.
The Project Manager considers what has actually happened during the current stage and what that means for the rest of the project.
This can include:
- evaluating current stage performance;
- reviewing lessons;
- updating the Project Plan;
- reviewing and updating the Business Case where necessary;
- considering the current risk position;
- preparing the next Stage Plan;
- confirming readiness to proceed; and
- requesting authority for the next stage.
The Project Board can then make its decision using more current information rather than relying solely on assumptions made at the beginning of the project.
Who Authorises the Next PRINCE2 Stage?
The Project Board authorises the next management stage. The Project Manager prepares and presents the information needed to support that decision and requests authority to proceed. Once a stage is authorised, day-to-day control is delegated to the Project Manager within agreed tolerances.
Remember:
The Project Manager manages the stage.
The Project Board authorises the stage.
The Board isn’t expected to manage every work package or daily decision. Instead, PRINCE2 establishes different levels of authority so that decisions can be made at the appropriate management level.
For a closer look at these relationships, see our guide to PRINCE2 roles and responsibilities.
How Do Tolerances Work Within a PRINCE2 Stage?
Tolerances establish the limits within which a management stage can be managed without escalating every variation to the Project Board. If the stage is forecast to remain within its agreed tolerances, the Project Manager can make appropriate adjustments within their delegated authority. A forecast that tolerances will be exceeded requires escalation.
This is what makes stage-based management practical.
Projects rarely unfold exactly as planned. Small variations don’t necessarily require senior management intervention.
PRINCE2 uses tolerances across areas including:
- time;
- cost;
- quality;
- scope;
- risk;
- benefits; and
- sustainability.
The exact tolerances need to make sense for the project.
For example, an iterative project might have very little flexibility around the length of a timebox but greater flexibility around which lower-priority scope is delivered within it.
Stages therefore work alongside Manage by Exception: authority is delegated, limits are established, and exceptions move upwards when those limits are forecast to be exceeded.
What Is the Difference Between PRINCE2 Stages and Processes?
PRINCE2 stages are controlled sections of the project, while PRINCE2 processes describe management activities used to direct, manage, and deliver it. There are seven processes, but there is no rule saying a project must have seven stages. Different processes operate across, within, or around different management stages.
PRINCE2 Stages vs Processes
| PRINCE2 stages | PRINCE2 processes |
|---|---|
| Divide the project into controlled management sections | Describe structured management activities |
| Used for planning, monitoring, control, and authorisation | Explain management activity across the lifecycle |
| At least two management stages are required | There are seven processes |
| Number and length can vary | The seven processes form part of the PRINCE2 method |
| Management stages do not overlap | Different processes can operate across or repeat during different stages |
| The Project Board authorises stages one at a time | Processes involve activity at different management levels |
This means you shouldn’t picture PRINCE2 as:
Process 1 = Stage 1 → Process 2 = Stage 2 → Process 3 = Stage 3…
Instead, imagine stages as sections along the project journey and processes as management activity happening around that journey.
For example:
- Directing a Project operates at Project Board level across much of the lifecycle.
- Controlling a Stage is used during authorised delivery stages.
- Managing Product Delivery supports the interface between the Project Manager and delivery teams.
- Managing a Stage Boundary becomes particularly important as one stage approaches its end and another may need to be authorised.
If you want to understand those activities individually, explore our full guide to the seven PRINCE2 processes.
Are PRINCE2 Stages the Same as Project Phases?
Not necessarily. “Project phase” is a common general Project Management term, while PRINCE2 specifically uses “management stages” to divide the project for management and control. An organisation’s “delivery phases” can exist alongside PRINCE2 “management stages”, but the terms shouldn’t automatically be treated as interchangeable.
Imagine a software project with delivery activities like:
Discovery → Design → Development → Testing → Deployment
Those may be useful ways of organising specialist delivery work.
But PRINCE2 management stages answer a different question:
Where should the project have clearly defined management, planning, control, and authorisation points?
The organisation can design its PRINCE2 management stages around the realities of its delivery approach rather than replacing its existing technical workflow.
In particular, PRINCE2 management stages don’t overlap (although the work happening within them can include activities or work packages that run concurrently).
Can PRINCE2 Stages Be Tailored?
Yes. The number, length, controls, and positioning of PRINCE2 management stages should suit the project context. PRINCE2 still requires stage-based management, but that doesn’t mean every project should be divided into the same number of equally sized stages.
Factors that can influence stage design include:
- project complexity;
- risk;
- how far ahead reliable detailed planning is possible;
- important business or technical decisions;
- significant investment commitments;
- organisational policies and standards; and
- alignment with wider programme activity.
A useful principle is that more stages can provide more frequent control points, but every boundary also introduces management activity.
So, the aim isn’t to create as many stages as possible; it’s to put decision and control points where they add value.
Example
Imagine two projects.
Project A is a relatively straightforward internal improvement with familiar technology, limited uncertainty, and a short delivery period.
Project B is a complex transformation involving several suppliers, substantial investment, evolving requirements, and several major decisions.
It would make very little sense to force both into an identical stage structure.
PRINCE2 allows the method to be tailored while retaining stage-based control.
Can PRINCE2 Stages Overlap?
No. PRINCE2 management stages do not overlap. They divide the project into consecutive management sections with decision points between them. But delivery activities and work packages within the project can run in parallel, and sometimes work may need to span a stage boundary.
This distinction helps separate management structure from delivery activity.
You could therefore have several teams working simultaneously on different products while still being inside one authorised management stage.
At the boundary, the project reaches a management decision point before moving into the next stage.
Can PRINCE2 Stages Work With Agile or Hybrid Delivery?
Yes. PRINCE2 management stages can be used with iterative, incremental, Agile, linear-sequential, or hybrid delivery approaches. A management stage can contain multiple sprints or timeboxes, allowing Agile delivery to continue within the governance and control structure provided by PRINCE2.
For example:
Management Stage: Sprint 1 → Sprint 2 → Sprint 3 → Sprint 4
Stage Boundary: Review → Decision → Next Management Stage
The sprints organise iterative delivery.
The management stage provides a wider planning, authority, and control period.
They aren’t competing structures.
As we can see, PRINCE2 manages the project without requiring every specialist team to use one particular delivery technique.
How Do PRINCE2 Stages Fit Into PRINCE2 Training?
Understanding management stages helps you connect several parts of the PRINCE2 method.
Rather than learning principles, practices, processes, roles, and tolerances as isolated concepts, stages help show how they interact during a project.
PRINCE2® Project Management Foundation develops your understanding of the method’s core concepts, while PRINCE2® Project Management Practitioner develops your ability to apply and tailor PRINCE2 in project situations.
If you’re deciding which level is appropriate for you, our guide to PRINCE2 Foundation vs Practitioner explains the difference.
Frequently Asked Questions About PRINCE2 Stages
What are the PRINCE2 stages?
PRINCE2 stages are management sections used to plan, monitor, control, and authorise a project. A management stage is the section of the project that the Project Manager manages on behalf of the Project Board at one time. Projects have at least an initiation stage and one further management stage, with additional stages added where appropriate.
How many stages are there in PRINCE2?
Every PRINCE2 project has at least two management stages: an initiation stage and one further stage. There is no single fixed number that applies to every project. The number and length of additional stages are tailored according to factors such as risk, complexity, uncertainty, planning needs, and important decision points.
Are there seven stages in PRINCE2?
No. PRINCE2 has seven processes, but this does not mean it has seven project stages. Processes describe management activities, whereas management stages divide the project into controlled sections. A project requires at least two management stages and may use more according to its context.
What is a management stage in PRINCE2?
A management stage is a section of the project managed by the Project Manager on behalf of the Project Board at one time. The Project Board authorises a stage and delegates day-to-day control to the Project Manager within agreed tolerances. This creates clear periods for planning, control, reporting, and decision-making.
What is the PRINCE2 project lifecycle?
The PRINCE2 project lifecycle moves from early pre-project activity into an initiation stage, through subsequent management stages as required, into a final management stage and controlled closure. The seven PRINCE2 processes operate around and within this journey rather than forming seven separate lifecycle stages.
Are PRINCE2 stages the same as project phases?
Not automatically. “Project phase” is a common general Project Management term, while PRINCE2 uses management stages specifically for management and control. Delivery phases such as design, development, testing, or implementation can exist within a project using PRINCE2, but they shouldn’t automatically be treated as equivalent to PRINCE2 management stages.
What happens at a PRINCE2 stage boundary?
At a PRINCE2 stage boundary, the Project Manager evaluates the current stage, reviews and updates relevant project information, prepares the next Stage Plan where appropriate, and requests authority to proceed. The Project Board uses this information to assess continued viability and decide whether the next management stage should be authorised.
Who approves the next PRINCE2 stage?
The Project Board authorises the next PRINCE2 management stage. The Project Manager prepares the relevant information, including the next Stage Plan where appropriate, and requests authority to proceed. Once authorised, the Project Manager manages that stage day to day within the tolerances and authority delegated by the Project Board.
What does Manage by Stages mean in PRINCE2?
Manage by Stages means that a PRINCE2 project is planned, monitored, controlled, and authorised on a stage-by-stage basis rather than managing the entire project as one uninterrupted block. This provides regular control and decision points while allowing the Project Manager to manage an authorised stage within agreed tolerances.
Can PRINCE2 stages overlap?
No. PRINCE2 management stages do not overlap. They divide the project into consecutive management sections and create clear decision points between stages. However, individual delivery activities or work packages can operate concurrently within a stage, so the fact that management stages don’t overlap doesn’t mean all project work must happen sequentially.
Can PRINCE2 stages be tailored?
Yes. PRINCE2 management stages should be tailored to suit the project. Their number, length, controls, and boundaries can reflect factors such as complexity, risk, planning uncertainty, important decisions, organisational requirements, and programme dependencies. Tailoring changes how stage-based management is applied, rather than removing the principle altogether.
Can PRINCE2 stages work with Agile projects?
Yes. A PRINCE2 management stage can contain iterative or Agile delivery activity such as multiple sprints or timeboxes. PRINCE2 provides the wider project management and governance structure, while Agile techniques can organise how specialist products are developed and delivered within an authorised stage.
What to Explore Next
Understanding PRINCE2 stages gives you the structure of the project journey. The next step is seeing how the other parts of the method operate within and around that structure.
You can continue with:
- Explore the seven PRINCE2 processes to understand the management activity that operates across the lifecycle.
- Explore the seven PRINCE2 principles to understand Manage by Stages, Manage by Exception, and the other guiding requirements.
- Explore the seven PRINCE2 practices to understand the areas requiring continual management attention.
- Explore PRINCE2 roles and responsibilities to see who manages, directs, assures, and delivers the project.
- Read our complete guide to PRINCE2 Project Management to bring the complete method together.
Want help understanding which PRINCE2 qualification fits your goals?
Sources
PeopleCert (2026) PRINCE2® Project Management (Version 7). PeopleCert.
