danielpradilla PRINCE2 Stage Boundary Pack
For detailed management product definitions, read ../../references/prince2-management-products.md when the user needs a complete PRINCE2 document set or asks what each artifact is for.
Use this workflow when one stage is ending and the project board needs evidence to authorize the next stage.
Inputs To Ask For
- Current stage plan and actuals
- Product completion and quality status
- Latest business case
- Risk, issue, change, and lessons logs
- Forecast for the remaining project
- Proposed next stage scope
- Any exception conditions
Output Structure
1. Stage Boundary Decision
- Recommendation: continue, revise, pause, stop, or approve exception plan
- Conditions for the next stage
- Decisions needed from the project board
2. End Stage Report
- Stage objectives
- Products delivered
- Products not delivered
- Performance against time, cost, quality, scope, benefits, risk, and sustainability tolerances
- Key issues and resolutions
- Lessons
3. Updated Business Case
- Benefits still valid
- Costs and forecast
- Risks to justification
- Changes since last approval
- Continue or stop rationale
4. Next Stage Plan
- Products
- Activities
- Owners
- Dates
- Budget
- Tolerances
- Risks and dependencies
- Reporting rhythm
5. Updated Project Baseline
- Project plan changes
- Product description changes
- Management approach changes
- Risk, issue, and lessons updates
6. Exception Plan
Include only if tolerance is forecast to be breached:
- Cause of exception
- Options
- Recommended recovery plan
- Impact on business case
- Board decision required
Quality Bar
- The board should see both performance to date and confidence in the next stage.
- Do not hide unfinished products.
- Reconfirm business justification before asking for the next stage.
- Capture lessons while the evidence is fresh.