11.3 Directing Stage Transitions, Ongoing Direction & Project Closure

Directing Stage Transitions, Ongoing Direction & Project Closure in PRINCE2 7

Practitioner Core Mandate: The true test of project leadership occurs at the critical junctures of transition, uncertainty, and conclusion. In PRINCE2 7, the Project Board does not merely monitor steady progress; it is specifically constructed to make high-stakes determinations when management stages conclude, when projects veer off-course, and when final deliverables are integrated into live business operations. Mastering these decision mechanics—and distinguishing between project direction and corporate oversight—is essential for the Practitioner examination.

---

1. Directing Stage Transitions: The Gateway Decision (Authorize a Stage or Exception Plan)

In PRINCE2 7, management stages are mandatory governance break-points. A project must never drift automatically from one stage to the next. Transition across a stage boundary requires a formal decision by the Project Board within the activity Authorize a Stage or Exception Plan.

                  THE STAGE BOUNDARY DECISION GATEWAY
   
   MANAGEMENT STAGE N (Ending)              STAGE BOUNDARY GATEWAY               MANAGEMENT STAGE N+1
   
   ┌───────────────────────┐                ┌───────────────────────┐            ┌───────────────────────┐
   │  Managing a Stage     │ ──► Inputs ──► │  DIRECTING A PROJECT: │ ──► Gate ──►  Controlling a       │
   │  Boundary (SB)        │                │  Authorize a Stage or │     Pass   │  Stage (CS)           │
   │  • End Stage Report   │                │  Exception Plan       │            │  • Execute Stage N+1  │
   │  • Updated Business   │                │  (Project Board Gate) │            │    within agreed      │
   │    Case               │                └───────────┬───────────┘            │    tolerances         │
   │  • Next Stage Plan    │                            │                        └───────────────────────┘
   │  • Updated Risk Reg   │                            ▼ Gate Fail
   └───────────────────────┘                ┌───────────────────────┐
                                            │ Premature Closure /   │
                                            │ Exception Plan Demand │
                                            └───────────────────────┘

The Four-Step Evaluation Protocol

When the Project Manager submits the stage boundary artifacts produced in the Managing a Stage Boundary (SB) process, the Project Board executes a four-step evaluation protocol:

┌─────────────────────────────────────────────────────────────────────────────┐
│            PROJECT BOARD 4-STEP STAGE TRANSITION EVALUATION                 │
├─────────────────────────────────────────────────────────────────────────────┤
│ STEP 1: REVIEW THE END STAGE REPORT                                         │
│ • Compare actual performance against Stage Plan baselines across 7 targets. │
│ • Verify that all specialist products in the stage achieved quality sign-off│
│ • Review stage lessons captured in the Lessons Log.                         │
├─────────────────────────────────────────────────────────────────────────────┤
│ STEP 2: RE-VALIDATE CONTINUED BUSINESS JUSTIFICATION                        │
│ • Scrutinize the updated Business Case (NPV, ROI, payback, market demand).  │
│ • Confirm that anticipated benefits still justify forecast remaining costs. │
│ • Verify that sustainability targets (carbon, waste, social) remain viable. │
├─────────────────────────────────────────────────────────────────────────────┤
│ STEP 3: ASSESS AGGREGATED RISK EXPOSURE                                     │
│ • Evaluate the total accumulated risk profile across the entire project.    │
│ • Check whether aggregated threat exposure breaches corporate risk appetite.│
│ • Confirm that the Risk Budget remains adequate to fund planned responses.  │
├─────────────────────────────────────────────────────────────────────────────┤
│ STEP 4: APPROVE THE NEXT STAGE PLAN & SET TOLERANCES                        │
│ • Interrogate the schedule, resource allocations, and costs for next stage. │
│ • Set explicit stage tolerances across all seven performance targets.       │
│ • Formally commit funds and resources for the upcoming stage ONLY.          │
└─────────────────────────────────────────────────────────────────────────────┘

Step 1: Reviewing the End Stage Report

The Project Board evaluates the End Stage Report to assess how successfully the expiring stage was executed:

• Target Variance Analysis: Did actual costs, timescales, quality metrics, scope delivery, benefit milestones, and sustainability targets remain within authorized tolerances?
• Product Approval Audit: Have all deliverables scheduled for the stage received formal quality sign-off against their approved Product Descriptions? No stage should be signed off if uncompleted deliverables are quietly left unrecorded.
• Lessons Review: What went well, what went poorly, and what process adaptations should be mandated for subsequent stages?

Step 2: Validating Continued Business Justification

A project is not a runaway train; it is a financial investment. The Project Board re-interrogates the updated Business Case:

• Incurred historical expenditures are sunk costs and must be ignored when evaluating future viability.
• The Board asks: Do the forecast remaining costs and risks still justify the anticipated future benefits?
• If an external market shift, technological obsolescence, or regulatory change has destroyed viability, the Board must halt the project immediately.

Step 3: Assessing Aggregated Risk Exposure

Evaluating risks in isolation is a primary cause of governance failure. The Project Board looks at aggregated risk:

• While ten individual risks might each have a "Low" rating, their combined, compounding probability and impact could pose an existential threat to the organization.
• The Board checks the updated Risk Register, verifies that secondary risks introduced by recent changes are addressed, and confirms that the project's overall risk profile remains within the organization's risk appetite.

Step 4: Approving the Next Stage Plan and Allocating Tolerances

• The Board reviews the Stage Plan for the upcoming stage produced by the Project Manager in SB.
• It commits the financial expenditure, staffing, equipment, and supplier resources for that stage only.
• The Board delegates explicit Stage Tolerances across all seven targets (Cost, Time, Quality, Scope, Benefits, Risk, Sustainability), defining the operational boundaries within which the Project Manager must deliver.

---

2. Providing Ongoing Direction & Managing Off-Track Projects

While stage transitions are periodic and planned, Ongoing Direction is an ongoing, responsive activity executed whenever events require Project Board intervention.

                       AD HOC DIRECTION ESCALATION PATHWAY

   [Controlling a Stage (CS)]
   Project Manager forecasts a breach of Stage Tolerance
             │
             ▼
   [Create EXCEPTION REPORT]
   Details deviation, cause, impact across 7 targets, options, and recommendation
             │
             ▼
   ┌────────────────────────────────────────────────────────┐
   │       DIRECTING A PROJECT: GIVE AD HOC DIRECTION       │
   │                (Project Board Review)                  │
   └───────────────────────────┬────────────────────────────┘
                               │
        ┌──────────────────────┼──────────────────────┐
        ▼                      ▼                      ▼
   [ADJUST TOLERANCES]  [REQUEST EXCEPTION PLAN] [DIRECT PREMATURE CLOSURE]
   Board absorbs        PM instructed to enter   Viability lost; PM told
   variance; project    SB process and draft     to initiate Closing a
   continues under CS   Exception Plan           Project (CP) immediately

Triggers for Ongoing Direction

1. Receipt of Highlight Reports: Periodic, time-driven summaries from the Project Manager detailing progress, milestone achievements, current risk/issue status, and tolerance health.
2. Receipt of Exception Reports: Event-driven escalations submitted when the Project Manager forecasts that the stage (or project) will breach one or more authorized tolerances.
3. Requests for Advice or Support: Informal or formal queries from the Project Manager seeking guidance on political friction, commercial disputes, or supplier negotiations.
4. External Strategic Shifts: Notifications from the business layer regarding organizational restructuring, budgetary cutbacks, or statutory regulatory amendments.

Project Board Decision Pathways During Exceptions

When an Exception Report arrives, the Project Board has four distinct options:

• Option 1: Adjust Stage Tolerances (Increase Leeway): If the variance is modest and the Project Board has sufficient surplus tolerance within its own overall Project Tolerances, the Board can simply expand the stage tolerance and instruct the PM to continue managing under the current Stage Plan.
• Option 2: Request an Exception Plan: If the deviation requires significant replanning, rescheduling, or deliverable modification, the Board instructs the Project Manager to produce an Exception Plan (via the Managing a Stage Boundary process). The Exception Plan replaces the current Stage Plan from the point of failure to the end of the stage.
• Option 3: Escalate to the business layer: If resolving the exception would cause the overall Project Tolerances (set by the business layer) to be breached, the Project Board cannot authorize the solution alone. It must escalate the Exception Report to the business layer for additional funding, time, or scope relief.
• Option 4: Direct Premature Closure: If the exception reveals that business justification is destroyed, the solution is unaffordable, or strategic priorities have shifted, the Board orders immediate project termination.

The Philosophy of Premature Closure

On the Practitioner exam, candidates must understand that premature closure is not an admission of failure:

• Recognizing that an initiative is no longer viable and terminating it cleanly is a mark of superior corporate stewardship.
• Abandoning a doomed project prevents the squandering of organizational capital on products that will deliver no value.
• Even when terminated early, the project must still follow an orderly closure process through Closing a Project (CP) to recover assets, terminate contracts, capture lessons, and salvage useful deliverables.

---

3. Authorizing Project Closure: Operational Handover & Benefits Realization

The final gateway in the project lifecycle occurs when the Project Manager completes the activities of Closing a Project (CP) and requests authorization from the Project Board to close the project.

┌─────────────────────────────────────────────────────────────────────────────┐
│            PROJECT BOARD ACTIONS IN AUTHORIZING PROJECT CLOSURE             │
├─────────────────────────────────────────────────────────────────────────────┤
│ 1. VERIFY OPERATIONAL ACCEPTANCE & PRODUCT HANDOVER                         │
│    • Confirm specialist products meet final acceptance criteria.            │
│    • Verify that operational, maintenance, and support teams have signed    │
│      formal handover certificates and taken custody of deliverables.        │
├─────────────────────────────────────────────────────────────────────────────┤
│ 2. REVIEW THE END PROJECT REPORT                                            │
│    • Evaluate actual performance against the original baseline PID.         │
│    • Scrutinize final cost, duration, quality, scope, and sustainability.   │
│    • Review follow-on action recommendations and residual operational risks.│
├─────────────────────────────────────────────────────────────────────────────┤
│ 3. REVIEW AND DISTRIBUTE THE LESSONS REPORT                                 │
│    • Evaluate the comprehensive Lessons Report submitted by the PM.         │
│    • Authorize transmission to corporate knowledge management repositories. │
├─────────────────────────────────────────────────────────────────────────────┤
│ 4. HAND OVER THE BENEFITS MANAGEMENT APPROACH                               │
│    • Transfer the updated Benefits Management Approach to the business     │
│      layer for post-project benefits tracking during operations.            │
├─────────────────────────────────────────────────────────────────────────────┤
│ 5. FORMALLY DISSOLVE THE PROJECT & RELEASE RESOURCES                        │
│    • Issue formal notice of project closure to the business layer.        │
│    • Reassign team members, demobilize suppliers, and close project budgets.│
└─────────────────────────────────────────────────────────────────────────────┘

The Critical Handover of Benefits Management

A major focus of PRINCE2 7 is that most business benefits are realized post-project, long after the project team has disbanded:

• While the project delivers products (capabilities), the business uses those products to achieve outcomes and realize financial and operational benefits.
• Because the Project Manager and Project Management Team are disbanded upon closure, they cannot measure post-project benefits.
• Therefore, during Authorize project closure, the Project Board reviews the updated Benefits Management Approach and formally transfers custodial ownership to the business layer.
• the business layer holds the operational managers (and former Senior User representatives) accountable for conducting post-project benefits reviews in live operations.

---

4. Corporate Governance vs. Project Board Direction

A frequent source of exam confusion is distinguishing between the responsibilities of the business layer and the Project Board:

---

5. Practical Scenario Evaluations

Scenario A: The Blind Stage Rollover

A telecommunications company is building a nationwide fiber network. At the end of Stage 2, the Project Manager submits the End Stage Report showing that Stage 2 was completed on time and within budget. The PM also submits the Stage Plan for Stage 3. However, during the stage boundary, a new national environmental tax is passed that triples the excavation cost of laying fiber in Stage 3, turning a projected £4 million net profit into a £2 million net loss. The Project Board rapidly approves the Stage 3 Plan because 'Stage 2 was delivered flawlessly.'

Practitioner Evaluation:

• Governance Flaw: The Project Board failed in its primary duty under Authorize a Stage or Exception Plan: re-validating Continued Business Justification.
• Systemic Consequence: Achieving past stage milestones does not guarantee future viability. By ignoring the environmental tax and failing to interrogate the updated Business Case, the Board committed £6 million of delivery capital to an unviable investment.
• Correct PRINCE2 Governance: The Project Board must scrutinize the updated Business Case. Because viability is eliminated, the Board must reject the Stage 3 Plan, instruct the PM to assess alternative routing options or sustainability concessions, and direct premature closure if profitability cannot be restored.

Scenario B: The Sunk-Cost Fallacy and Exception Plan Refusal

On a software platform rewrite, the project has already spent £3 million across three stages. During Stage 4, a major architecture failure occurs. The Project Manager submits an Exception Report showing that finishing the platform will require an additional £1.5 million, while a newly launched commercial cloud service could provide identical functionality for £200,000 annually. The Project Executive rejects premature closure, stating: 'We have already invested £3 million into this software; we cannot afford to throw that money away. We must approve the Exception Plan and finish building our own system.'

Practitioner Evaluation:

• Governance Flaw: The Project Executive has fallen victim to the sunk-cost fallacy. In PRINCE2, past money spent is completely irrelevant to forward-looking business decisions.
• Correct PRINCE2 Governance: The Board must compare future investment against future return. Spending £1.5 million of additional capital to build a redundant asset when a superior £200,000 solution exists is commercially irresponsible. The Project Board should reject the Exception Plan and direct premature closure, salvaging reusable code components and transitioning to the cloud solution.

Scenario C: The Disowned Benefits Trap at Closure

During project closure of a renewable solar farm, the Project Board approves the End Project Report and immediately dissolves. The Senior User assumes the Project Manager will return in 12 months to measure electricity generation revenues. The Project Manager leaves the organization, and no operational department is tasked with monitoring the solar inverters. Three years later, corporate auditors discover that inverter degradation reduced energy output by 35%, but no one noticed because benefits were never tracked.

Practitioner Evaluation:

• Governance Flaw: The Project Board abdicated its responsibility during Authorize project closure regarding the Benefits Management Approach.
• Correct PRINCE2 Governance: Project Managers are released upon project closure and do not measure post-project benefits. The Project Board must update the Benefits Management Approach, verify that operational metrics are baselined, and formally transfer custodial ownership to the business layer, ensuring operational managers are assigned to measure benefits throughout the product's operational lifecycle.

---

6. Practitioner Exam Pitfalls & Governance Traps

• Trap 1: Assuming the Project Board Drafts Exception Plans: When an Exception Report is approved, the Project Board never drafts the Exception Plan; the Project Board directs the Project Manager to produce the Exception Plan within the Managing a Stage Boundary (SB) process.
• Trap 2: Believing the Project Manager Authorizes Premature Closure: A Project Manager can recommend premature closure in an Exception Report, but only the Project Board holds the legal and organizational authority to direct and authorize premature closure.
• Trap 3: Handing Over Benefits Tracking to the Project Manager at Closure: Any exam answer suggesting that the Project Manager tracks post-project benefits is incorrect. The Project Manager role ceases to exist when the project is dissolved. Ownership transfers to the business layer or designated operational managers.
• Trap 4: Conflating Project Tolerances with Stage Tolerances: If an exception can be resolved within Project Tolerances, the Project Board can approve an Exception Plan. If resolving the exception would breach Project Tolerances, the Board must escalate to the business layer.
• Trap 5: Skipping the Closing Process for Terminated Projects: When a project is closed prematurely, the team does not simply walk away. The Project Manager must execute the Closing a Project (CP) process to conduct an orderly shutdown, salvage deliverables, document lessons, and secure closure authorization from the Board.