Skip to content
P2

Project boundary

Managing a Stage Boundary

Prepare the evidence and options needed for a confident continue, adjust, reset, or stop decision at stage end.

What this helps you do

Turn stage closure into an active governance decision rather than a routine status checkpoint.

Use this when

  • Approaching end of stage.
  • Before major funding or continuation decisions.
  • After significant variance or scope/value change.

What good looks like

  • Actual performance is compared honestly with baseline and tolerance.
  • Business case confidence is refreshed, not recycled.
  • Lessons and risk trends inform the next stage plan.
  • Sponsor receives clear options with recommendation and impact.
  • Decision outcome is recorded with conditions and follow-up actions.

Minimum viable version

  • Boundary pack with actuals, current forecast, and decision ask.
  • Updated business case lite and stage plan.
  • Lessons summary and top residual risks.
  • Explicit recommendation: continue, adjust, reset, or stop.

Stronger version

  • Benefit confidence and disbenefit movement by stage.
  • Assurance evidence and supplier performance assessment.
  • Scenario options with quantified impact ranges.
  • Decision conditions and contingency triggers for next stage.

Step-by-step operating flow

  1. Close current stage data and compare to baseline/tolerance.
  2. Update value position, key risks, and benefit confidence.
  3. Capture lessons that materially affect next-stage execution.
  4. Draft next-stage plan with realistic scope and constraints.
  5. Prepare options and recommendation for governance decision.
  6. Run boundary review and capture direction with conditions.
  7. Communicate decision outcome and update control artefacts.
  8. Launch next stage only after decision conditions are met.

Inputs needed

  • Stage performance data and forecast variance.
  • Current business case and benefits view.
  • RAID, decision, and change logs.
  • Assurance findings and supplier performance insights.

Outputs produced

  • Stage boundary decision pack.
  • Updated business case and next-stage plan.
  • Recorded continuation decision and conditions.
  • Revised controls for the next stage.

Common mistakes

  • Treating the boundary as a status ritual with no real decision.
  • Presenting optimistic forecasts without risk weighting.
  • Ignoring lessons when designing the next stage.
  • Starting the next stage before governance conditions are closed.

Tailoring notes

  • Lite projects can use a concise boundary summary if decision quality remains high.
  • Enhanced projects should include stronger assurance and evidence annexes.
  • Recovery boundaries should shorten cycle length and tighten tolerance controls.
  • Public-sector contexts should keep traceable rationale for continuation choices.

Related templates

Related tools

PRINCE2 mapping

Operational translation of PRINCE2 Managing a Stage Boundary, focused on evidence-led continuation decisions and next-stage readiness.

FAQ

Common questions for this process

What is the most important output of a stage boundary?

A clear continuation decision with rationale, conditions, and an executable next-stage plan.

Should boundaries be skipped on short projects?

Only if control logic is preserved elsewhere. Even short projects need explicit continuation checks.

How detailed should option analysis be?

Proportional to risk and spend. Enough to compare credible choices and consequences.