Project control
Manage by Stages
Use stage boundaries to make active continuation decisions.
What this helps you do
Avoid drift by giving sponsors regular points to continue, pause, reset, or stop.
Use this when
- Planning delivery
- Creating governance calendar
- Preparing boundary review
What good looks like
- Each stage has a control purpose
- Next stage is planned in detail only when needed
- Tolerance threats are visible
Minimum viable version
- Stage objective
- Milestones
- Tolerances
- Boundary decision date
Stronger version
- Assurance activities
- Supplier checkpoints
- Benefits confidence update
Step-by-step
- Define stage goal
- Plan products
- Set tolerances
- Run weekly control
- Review boundary
Inputs needed
- PID Lite
- Stage plan
- RAID log
Outputs produced
- Stage plan
- Highlight reports
- Stage boundary pack
Common mistakes
- Making stages mirror calendar quarters without control logic
- Skipping boundary decisions
Tailoring notes
- Shorter stages for recovery
- Rolling-wave stages for agile or hybrid delivery
Related templates
stage-plan, stage-boundary-pack
Related tools
Weekly Control Room, Project Health Check
PRINCE2 mapping
Maps to manage by stages and the plans, progress, and business case practices.