Project Delivery · Project Control Methods
Managing Stage Boundaries and Exception Plans
A stage boundary is a controlled investment decision. The project manager closes the current management view, plans the next stage in useful detail, updates the overall forecast, business justification, benefits and risk, reports performance and lessons, and asks governance to renew authority. The same process can create an exception plan when an approved stage or project forecast leaves tolerance.
Executive summary
What this guide enables
A stage boundary is a controlled investment decision. The project manager closes the current management view, plans the next stage in useful detail, updates the overall forecast, business justification, benefits and risk, reports performance and lessons, and asks governance to renew authority. The same process can create an exception plan when an approved stage or project forecast leaves tolerance.
Learning outcomes
- Explain the purpose and lifecycle position of managing stage boundaries and exception plans.
- Recognise the entry triggers, control evidence and completion conditions.
- Assign activities and decisions to the correct governance, management and delivery roles.
- Tailor the process without weakening accountability, product focus or exception control.
Control guidance
Purpose and lifecycle position
The purpose is to give the governing body enough reliable information to review current-stage success, approve the next stage, review the updated project plan and confirm continued justification and acceptable risk. It prevents automatic continuation and limits future commitment to an evidence-backed planning horizon.
Lifecycle position: This process occurs near the end of each management stage except normal final-stage closure, and it is triggered when governance requests an exception plan. Boundary work begins early enough to prepare the next plan without distracting from completion of the current stage. It integrates progress, product, financial, risk, issue, quality, lesson, benefit and resource evidence.
Control depends on the resulting decision and evidence, not on reproducing a particular flowchart. The process begins on a recognised trigger, uses current controlled inputs and ends with an explicit status, product, authorisation or request.
Control guidance
Entry triggers and prerequisites
Treat the trigger as the reason to act and the prerequisite as evidence needed to act safely. Confirm authority, applicable tolerance, status date and current product or plan versions; expose missing inputs rather than silently assuming them.
Stage boundary approaching
The current plan identifies an upcoming management decision point.
Current product status available
Completed, incomplete, approved and deferred products can be assessed.
Next-stage information available
Products, resources, dependencies, risks and estimates can be planned credibly.
Exception plan requested
A forecast breach causes governance to ask for a replacement stage or project plan.
Control guidance
Activity sequence
Activities may overlap or be combined, but each outcome must remain visible: what was considered, who acted or decided, and which authorised position now applies.
- 1
Plan the next management stage
Define products, work packages, resources, controls, quality, dependencies, cost, risk, tolerance and stage-end decision.
- 2
Update the project plan
Replace high-level assumptions with actual stage performance and the latest whole-project product, milestone, resource and cost forecast.
- 3
Update the business case and benefits approach
Reflect actual costs, changed options, benefits, dis-benefits, timing, risk, affordability and post-project review needs.
- 4
Report stage end
Compare stage plan with actual and forecast, list product status, quality, issues, risk, lessons, resource performance and residual work.
- 5
Update management approaches and registers
Incorporate lessons, new context and changed controls for the next commitment.
- 6
Request next-stage authorisation
Provide the integrated decision pack, assurance findings and any conditions requiring governance.
- 7
Produce an exception plan when directed
Build a replacement plan from the actual current position, preserving history and updating the business case and risk.
Control guidance
Management products and evidence
The record may be a document, workflow item, database entry or integrated view. Give every item a purpose, owner, status, update trigger and audience; protect baselines from silent change and ensure reports trace back to source evidence.
| Management product or evidence | Control purpose |
|---|---|
| Next-stage plan | Provides detailed control and tolerance for the next commitment. |
| Updated project plan | Provides the latest whole-project forecast and stage structure. |
| Updated business case | Tests continued investment justification. |
| Stage-end report | Shows performance, products, quality, resource, issues, risk and lessons. |
| Lessons report or updated log | Transfers learning into later stages and organisational use. |
| Updated registers and initiation baseline | Maintains current control approaches and exposure. |
| Exception plan | Replaces an affected stage or project plan after approval. |
| Authorisation request | Asks governance to continue, condition, reshape or stop. |
Control guidance
Roles, decision rights and assurance
Keep direction, day-to-day management, product delivery and independent challenge distinguishable. If compatible duties are combined, map responsibilities and add an independent decision or review wherever self-authorisation, self-acceptance or self-assurance would otherwise result.
| Role or level | Core responsibility | Decision or evidence |
|---|---|---|
| Governing body | Reviews stage evidence and next commitment | Authorises next stage or exception plan |
| Business lead | Updates and owns continued justification | Recommends investment decision |
| Project manager | Prepares integrated boundary products | Requests renewed authority |
| Delivery leads | Provide product, forecast and resource evidence | Commit to feasible next work |
| User and supplier representatives | Review acceptance, benefits and feasibility | Advise stage decision |
| Project assurance and support | Challenge evidence and maintain records | Report readiness and findings |
Control guidance
Interfaces and control logic
Map incoming evidence, outgoing authority and response deadlines so products or decisions do not stall between roles. Forecast breaches move to the tolerance-setting authority; baseline impacts follow change control; weakened justification returns to the accountable business authority.
- A boundary is not simply a reporting date; it is a decision about further authority and investment.
- The next-stage plan should be detailed, while later stages remain at a justified planning horizon.
- Incomplete current-stage products need explicit disposition, not quiet migration into the next plan.
- An approved exception plan replaces the affected baseline and retains the original performance history.
| Control question | Evidence to inspect | Decision or response |
|---|---|---|
| Is the input authoritative? | Version, status, owner, approval and data date | Use, clarify or reject the input |
| Is action within delegated authority? | Plan, tolerance, budget, role and external constraints | Act locally or escalate |
| Has the activity produced a usable output? | Defined completion, assurance, decision and conditions | Pass forward or return for action |
| Has the overall forecast changed? | Integrated impact and remaining-work evidence | Update plans, business case, risks and reports |
Control guidance
Tailoring the process
A small project may hold a concise boundary review and issue one combined report and next-stage plan. A large project may require cost, schedule, commercial, technical and independent assurance inputs. Boundaries can align with release, contract, regulatory or portfolio gates when the project-control decision remains explicit. The final stage normally transitions into closure rather than another stage boundary.
Record the selected form, role mapping and evidence route in the initiation baseline. Revisit it when risk, suppliers, obligations, pace or decision lead time changes; tailoring must preserve purpose and authority even when format and frequency change.
Tailoring and readiness check
- The trigger and decision authority are explicit
- Inputs are current, approved where required and linked to their source
- Products and activities have one accountable owner
- Forecast impact covers time, cost, quality, scope, benefits and risk
- Issues, decisions and assumptions are recorded at the appropriate level
- Interfaces with the preceding and following processes are controlled
- Tailoring preserves the process purpose and required evidence
- The completion decision and any conditions have a traceable record
Control guidance
Worked application
Preventing automatic stage rollover
Situation: Most stage products are complete, but one approval is open and the next-stage team is due to start. Stakeholders suggest moving forward and 'closing the paperwork later.'
- The project manager identifies whether the missing approval blocks acceptance, a dependency or the authorised stage objective.
- Options are assessed: complete before the gate, carry as a controlled product with conditions, change the next-stage scope, or delay authorisation.
- The stage-end report makes the incomplete product and impact visible; the next-stage plan includes only the disposition governance approves.
- Governance grants conditional authorisation with a decision deadline and tolerance rather than allowing silent rollover.
Control outcome: Continuity is protected without rewriting history or allowing an unfinished baseline to disappear between stages.
Control guidance
Failure modes, recovery and common questions
| Failure mode | Consequence | Control response |
|---|---|---|
| Next stage planned too late | Resources wait and decisions are rushed | Start boundary preparation before stage completion |
| Stage report hides incomplete products | Governance authorises on false status | Use product and configuration evidence with explicit disposition |
| Business case not refreshed | Sunk cost drives continuation | Use remaining cost, current value and risk in the gate decision |
| Exception plan treated as schedule edit | Authority and history are lost | Create a replacement plan and obtain approval from the tolerance setter |
Is there a stage boundary after the final stage?
Normal final-stage work moves into project closure. Closure includes end-project evaluation and acceptance rather than a next-stage request.
Can a stage be authorised conditionally?
Yes if the governing authority understands conditions, owners, deadlines and exposure and remains within its authority.
Who prepares an exception plan?
The project manager prepares it when directed after reporting a forecast tolerance breach.
Does a new baseline erase the original variance?
No. Preserve original and revised plans and explain the decision history.