13.1 Controlling a Stage (CS) Process: Authorizing Work & Reviewing Progress

Controlling a Stage (CS) Process: Authorizing Work & Reviewing Progress in PRINCE2 7

Practitioner Core Mandate: In the PRINCE2 methodology, a project is not delivered by executive decree or broad strategic intentions; it is delivered through rigorous, systematic, day-to-day management during delivery stages. The Controlling a Stage (CS) process represents the primary operational domain of the Project Manager. While the Project Board directs the project by exception from a strategic altitude, the Project Manager lives within the Controlling a Stage process—authorizing specialist work, tracking progress against baselined stage targets, handling operational issues, and maintaining the project's forward momentum. Understanding the precise mechanics, interfaces, and boundary controls of CS is essential for passing the PRINCE2 7 Practitioner examination.

---

1. Purpose, Objectives & Governance Context of Controlling a Stage (CS)

The Fundamental Purpose of CS

The purpose of the Controlling a Stage (CS) process is to assign work to be done, monitor such work, deal with issues, report progress to the Project Board, and take corrective actions to ensure that the management stage remains within tolerance.

Core Governance Objectives

To achieve this purpose, the Controlling a Stage process must satisfy the following objectives throughout every delivery stage:

• Focus on Deliverables: Ensure that operational attention is centered on the creation and delivery of specialist products that satisfy their defined quality specifications.
• Maintain Active Control: Keep delivery activities under continuous, proactive supervision, ensuring that risks, issues, and progress deviations are identified and managed before they threaten stage success.
• Protect Business Justification: Ensure that the stage deliverables continue to support the business outcomes outlined in the Business Case and Benefits Management Approach.
• Regulate Work Authorization: Ensure that no specialist work is commenced, modified, or delivered without formal authorization through agreed Work Packages.
• Manage Within Tolerances: Maintain delivery performance strictly within the approved stage tolerances across all seven performance targets (Cost, Time, Quality, Scope, Benefits, Risk, and Sustainability).
• Keep the Project Board Informed: Provide regular, objective, time-driven Highlight Reports to the Project Board, ensuring transparent executive oversight without encumbering board members with operational trivia.

                  THE DAY-TO-DAY DELIVERY CONTROL ENGINE

   DIRECTION (Project Board)          [Directing a Project - DP]
   ▲                             ▲                 ▲
   │ Exception Report            │ Highlight       │ Stage Boundary /
   │ (when tolerance breached)   │ Report (regular)│ Project Authorization
   │                             │                 │
   ▼                             ▼                 ▼
   MANAGEMENT (Project Manager)       [Controlling a Stage - CS]
   │                                               ▲
   │ Authorize Work Package                        │ Checkpoint Report /
   │ (defines scope, tolerances, quality)          │ Completed Work Package
   ▼                                               │
   DELIVERY (Team Manager / Specialists) [Managing Product Delivery - MP]

Operationalizing PRINCE2 Principles in CS

The Controlling a Stage process puts core PRINCE2 principles into direct operational practice:

• Manage by Exception: The Project Board delegates autonomous authority to the Project Manager to manage the stage, bounded by approved stage tolerances. As long as delivery forecasts remain within these tolerances, the Project Manager acts independently without seeking Project Board approval for routine decisions.
• Focus on Products: CS prevents teams from engaging in aimless activity. Work is packaged strictly around tangible deliverables defined by approved Product Descriptions, and work is only complete when products meet their agreed quality specifications.
• Manage by Stages: CS is executed within each discrete delivery stage. It works in partnership with Managing a Stage Boundary (SB): CS executes the stage, and as the stage nears completion, SB is invoked to plan the subsequent stage and re-assess business justification.
• Defined Roles and Responsibilities: CS enforces a clean separation of accountability. The Project Manager oversees overall stage integration and management controls, while Team Managers oversee technical execution and specialist craft.

Event-Driven vs. Time-Driven Controls in CS

Delivery stage control operates on two distinct mechanisms:

---

2. The Eight Activities of Controlling a Stage (CS)

PRINCE2 7 table 16.1 names eight activities (16.4.1 to 16.4.8). They fall into three operational cycles — managing work packages, monitoring and reporting stage progress, and handling issues and risks — but learn the eight official names, because the syllabus tests activities, inputs, and outputs directly:

┌─────────────────────────────────────────────────────────────────────────────┐
│                THE 8 ACTIVITIES OF CONTROLLING A STAGE (CS)                 │
├─────────────────────────────────────────────────────────────────────────────┤
│ CYCLE 1 — MANAGING WORK PACKAGES:                                           │
│    16.4.1 AUTHORIZE A WORK PACKAGE (formal delegation to a team manager;    │
│           creates/amends/approves the work package description)             │
│    16.4.2 EVALUATE WORK PACKAGE STATUS (reads checkpoint reports and team   │
│           plans; updates the project log and stage plan)                    │
│    16.4.3 RECEIVE COMPLETED WORK PACKAGE (quality sign-off and acceptance)  │
├─────────────────────────────────────────────────────────────────────────────┤
│ CYCLE 2 — MONITORING & REPORTING STAGE PROGRESS:                            │
│    16.4.4 EVALUATE STAGE STATUS (variance tracking across the 7 targets;    │
│           may trigger managing a stage boundary or directing a project)     │
│    16.4.8 REPORT HIGHLIGHTS (a highlight report for each reporting period)  │
├─────────────────────────────────────────────────────────────────────────────┤
│ CYCLE 3 — HANDLING ISSUES & RISKS (detailed in section 13.3):               │
│    16.4.5 CAPTURE ISSUES AND RISKS (project log; issue reports if required) │
│    16.4.6 TAKE CORRECTIVE ACTION (adjustments within stage tolerances)      │
│    16.4.7 ESCALATE ISSUES AND RISKS (exception report to the project board) │
└─────────────────────────────────────────────────────────────────────────────┘

[!EXAM WATCHPOINT: 'REVIEW' BECAME 'EVALUATE'] The 6th Edition activities review work package status and review the stage status are named evaluate work package status and evaluate stage status in PRINCE2 7. The eighth activity, report highlights, is numbered 16.4.8 in the manual even though it belongs to the monitoring cycle.

---

3. Authorizing a Work Package (16.4.1): The Formal Governance Contract

The Work Package as a Constitutional Boundary

A fundamental rule of PRINCE2 is that specialist teams cannot commence work on any product without an authorized Work Package. The Work Package is not a casual verbal instruction or an informal Jira ticket; it is the formal operational contract between the Project Manager and the Team Manager (or specialist team).

┌─────────────────────────────────────────────────────────────────────────────┐
│        THE SEVEN HEADINGS OF A PRINCE2 7 WORK PACKAGE DESCRIPTION (A15)     │
├─────────────────────────────────────────────────────────────────────────────┤
│ 1. DESCRIPTION OF WORK TO BE DONE                                           │
│    A statement of work and the associated WORK BREAKDOWN STRUCTURE.         │
│ 2. TEAM MANAGER OR PERSON AUTHORIZED                                        │
│    The named team manager or individual responsible for the work package.   │
│ 3. PRODUCT DESCRIPTIONS                                                     │
│    The product descriptions associated with this work package.              │
│ 4. TECHNIQUES AND PROCEDURES                                                │
│    Requirements for HOW the work is to be done: standards, tools, methods,  │
│    health and safety mandates, digital platforms.                           │
│ 5. CHANGE CONTROL REQUIREMENTS                                              │
│    Arrangements for control of the project and product baselines that fall  │
│    within the scope of this work package.                                   │
│ 6. CONSTRAINTS                                                              │
│    Restrictions or limits on the work — authorized work hours, safety and   │
│    security measures, budget caps, freeze windows.                          │
│ 7. MONITORING, CONTROL, AND REPORTING                                       │
│    How the work package will be monitored, controlled, and reported:        │
│    work package tolerances, checkpoint report format and frequency, and     │
│    the escalation thresholds back to the project manager.                   │
└─────────────────────────────────────────────────────────────────────────────┘

> [!EXAM WATCHPOINT: THE 6th EDITION HEADINGS ARE GONE]
> 'Development interfaces', 'operations and maintenance interfaces', 'problem handling and escalation', and 'hand-over procedures' were separate Work Package headings in the 6th Edition. PRINCE2 7 consolidates the work package description into the seven headings above — interfaces sit under *techniques and procedures* or *constraints*, and escalation sits under *monitoring, control, and reporting*. Tolerances are still agreed for the work package; they are recorded under the monitoring, control, and reporting heading rather than as a heading of their own.

Authorizing the Work Package

When authorizing a Work Package, the Project Manager must:

1. Verify Baseline Alignment: Ensure the work required matches the approved Stage Plan and aligns with the Project Initiation Documentation (PID).
2. Review Available Resources: Confirm that required resources, personnel, and commercial supplier agreements are in place.
3. Allocate Tolerances: Assign realistic, sub-allocated tolerances to the Work Package (e.g., ±3 days, ±$5,000, max 2.5 tonnes carbon). The PM must never allocate the entire stage tolerance to a single Work Package, as this would leave zero buffer for other package deviations.
4. Define Reporting Tempos: Agree on the frequency and format of Checkpoint Reports (e.g., weekly written reports, bi-weekly virtual checkpoint reviews).
5. Secure Team Manager Agreement: Ensure the Team Manager formally accepts the Work Package, confirming that the technical requirements are achievable within the stated constraints.

---

4. Evaluating Work Package Status (16.4.2) & Reading Checkpoint Reports

Once work is underway, the Project Manager does not stand over specialists' shoulders or attend internal daily technical scrums. Instead, the PM maintains control through the activity Review Work Package status.

Scrutinizing the Checkpoint Report

The primary input to this activity is the Checkpoint Report, produced periodically by the Team Manager within the Managing Product Delivery (MP) process:

• Progress Completed: Products completed and quality-tested during the reporting period.
• Work in Progress: Deliverables currently being developed and percentage of effort expended.
• Quality Activities Conducted: Tests, reviews, inspections, and audits completed during the period, along with any identified defects.
• Issues & Risks Encountered: Technical hurdles, team-level risks, or supply chain frictions managed or needing PM awareness.
• Forecast for Next Period: Products scheduled to be started or completed in the upcoming checkpoint window.
• Tolerance Consumption: Team Manager's forecast of whether Work Package tolerances (cost, schedule, quality, sustainability) remain safe.

Project Manager Analysis

The Project Manager evaluates the Checkpoint Report against the Stage Plan:

• Is actual progress tracking in accordance with the planned schedule?
• Is the burn rate of labor and materials within the stage budget?
• Are quality review results passing, or is excessive rework eroding stage schedule contingency?
• Are secondary risks emerging from technical implementation?

If the Checkpoint Report indicates that Work Package tolerances are threatened, the PM immediately collaborates with the Team Manager to explore corrective adjustments, or prepares to escalate if the breach will impact the wider Stage Plan.

---

5. Receiving a Completed Work Package (16.4.3): Quality Assurance & Acceptance

One of the most dangerous points in any project is the premature handover of deliverables. The activity Receive completed Work Packages enforces rigorous quality verification before any work is formally recognized as done.

                    WORK PACKAGE RECEIPT & ACCEPTANCE GATEWAY
   
   [Team Manager / Specialists]           [Project Manager in CS]
   ┌───────────────────────────┐         ┌───────────────────────────────┐
   │ 1. Complete specialist    │         │ 4. Inspect Quality Register:  │
   │    development work       │         │    • Verify quality reviews   │
   └─────────────┬─────────────┘         │    • Verify defect sign-offs  │
                 │                       └───────────────┬───────────────┘
                 ▼                                       │
   ┌───────────────────────────┐                         ▼
   │ 2. Execute quality tests  │         ┌───────────────────────────────┐
   │    per Product Description│         │ 5. Verify Product Approvals:  │
   └─────────────┬─────────────┘         │    • Designated approvers     │
                 │                       │      have formally signed off │
                 ▼                       └───────────────┬───────────────┘
   ┌───────────────────────────┐                         │
   │ 3. Notify PM:             │                         ▼
   │    "Work Package complete"│────────►┌───────────────────────────────┐
   └───────────────────────────┘         │ 6. Update Stage Plan actuals  │
                                         │    & notify Team Manager of   │
                                         │    formal package closure     │
                                         └───────────────────────────────┘

The Mandatory Verification Steps

A Project Manager cannot mark a Work Package as complete simply because a Team Manager declares that work is finished. The PM must execute three non-negotiable checks:

1. Audit the Quality Register: Verify that all quality activities specified in the Product Descriptions (e.g., peer reviews, automated regression tests, stress tests, user acceptance walkthroughs) have been performed and recorded as completed.
2. Verify Formal Product Approval: Ensure that the specific roles named in the Product Description's 'Quality method' and 'Approvals' sections (e.g., Senior User representatives, external safety regulators, architectural leads) have formally signed off on the products. A developer or Team Manager cannot approve their own product unless explicitly designated in the Product Description.
3. Confirm Handover & Configuration Baseline: Ensure that the products have undergone formal handover according to the Work Package instructions (e.g., code merged to master branch, physical assets delivered to warehouse custody, operational documentation archived). Once confirmed, the PM updates the Stage Plan with actual completion dates and formally closes the Work Package.

---

6. Evaluating Stage Status (16.4.4): Continuous Performance Monitoring

While reviewing individual Work Packages gives the PM tactical visibility, the PM must continuously synthesize this data into an integrated view of overall stage health through the activity Review the stage status.

Continuous Tracking Across All Seven Performance Targets

In PRINCE2 7, stage status is not judged solely by time and money. The Project Manager must continuously monitor variance across all seven project performance targets:

Horizon Scanning and Early Warning

Reviewing stage status is fundamentally forward-looking. The Project Manager is not merely recording historical actuals; the PM is forecasting future trajectory:

• "If Team B continues at their current velocity, will they breach their 10-day tolerance window in three weeks?"
• "If raw material prices rise by another 3%, will the stage cost tolerance be exceeded before the final Work Package is authorized?"

If the PM forecasts that delivery will remain within stage tolerances, the PM takes corrective action internally as needed. If the forecast indicates that an approved stage tolerance will be breached, the PM's autonomy ends, triggering the creation of an Exception Report.

---

7. Reporting Highlights (16.4.8): Project Executive Communication with the Project Board

Under the principle of Manage by Exception, the Project Board does not hold routine weekly progress meetings. Instead, the Project Manager keeps the board informed through regular, time-driven Highlight Reports produced in the activity Report highlights.

┌─────────────────────────────────────────────────────────────────────────────┐
│                     STRUCTURE OF A HIGHLIGHT REPORT                         │
├─────────────────────────────────────────────────────────────────────────────┤
│ 1. REPORT METADATA: Project ID, Stage number, reporting period, author (PM).│
│ 2. EXECUTIVE STAGE SUMMARY: High-level narrative of stage health (RAG status)│
│ 3. TOLERANCE CONSUMPTION: Current variance & forecast against 7 targets:    │
│    • Cost, Time, Quality, Scope, Benefits, Risk, and Sustainability.        │
│ 4. PRODUCTS COMPLETED IN PERIOD: Deliverables approved and signed off.      │
│ 5. PRODUCTS IN PROGRESS: Deliverables underway and percentage completion.   │
│ 6. PRODUCTS SCHEDULED FOR NEXT PERIOD: Forward outlook for upcoming period. │
│ 7. KEY RISKS & ISSUES: High-severity threats, opportunities, and open RFCs. │
│ 8. LESSONS IDENTIFIED: Practical insights captured in period.               │
│ 9. BUDGET STATUS: Spend-to-date, commitments, and contingency utilization.  │
└─────────────────────────────────────────────────────────────────────────────┘

Frequency and Channel Alignment

The timing, frequency, and distribution of Highlight Reports are baselined in the Communication Management Approach during project initiation:

• In fast-moving, high-risk software projects, Highlight Reports may be delivered weekly via digital dashboards.
• In multi-year civil infrastructure projects, Highlight Reports may be distributed monthly in formal written documentation.
• The Highlight Report enables the Project Board to execute its oversight duty in Directing a Project (DP)—specifically the activity Reviewing progress—without interfering in daily execution.

---

8. The Operational Interface: Controlling a Stage (CS) vs. Managing Product Delivery (MP)

A core conceptual distinction in PRINCE2 is the sharp boundary between project management and specialist production:

---

9. Practical Scenario Evaluations

Scenario A: The Micro-Managing PM Bypass

On a cloud transformation project, the Project Manager bypasses the software engineering Team Manager and begins assigning user stories directly to individual developers during morning standups. When a senior database engineer encounters performance bottlenecks, the PM re-allocates two frontend developers to assist, altering the team's sprint backlog. The Team Manager complains to the Senior Supplier that project governance has broken down.

Practitioner Evaluation:

• Governance Flaw: The Project Manager has violated the operational boundary of Controlling a Stage and invaded Managing Product Delivery.
• Consequences: The PM has compromised the Team Manager's accountability. By assigning tasks directly, the PM invalidates the agreed Work Package, renders the Team Plan meaningless, and destroys the Team Manager's ability to manage technical quality and team velocity. If the Work Package slips, the Team Manager can legitimately argue that the PM's meddling caused the failure.
• Correct PRINCE2 Action: In CS, the Project Manager manages through the Team Manager using authorized Work Packages. The PM defines what products must be delivered, when, and to what quality, but leaves how the specialist team organizes internal assignments to the Team Manager. If technical adjustments are required, the PM discusses them with the Team Manager, who adjusts the internal team workflow.

Scenario B: Premature Work Package Sign-Off

During a commercial office fit-out, the electrical contractor finishes installing backup diesel generators. The contractor's Team Manager submits a completion notice to the PM. Under pressure to meet the stage end milestone, the PM immediately signs off the Work Package as complete and updates the Stage Plan. Two weeks later, building inspectors discover that mandatory municipal emissions tests and load-bearing vibration certifications were never conducted, requiring walls to be dismantled at a cost of $75,000.

Practitioner Evaluation:

• Governance Flaw: The Project Manager committed a critical procedural failure during the activity Receive completed Work Packages.
• Consequences: By taking the contractor's word without verifying quality documentation, the PM accepted non-conforming products into the project baseline, exposing the organization to severe financial and regulatory penalties.
• Correct PRINCE2 Action: Before receiving any Work Package, the PM must inspect the Quality Register to verify that all quality activities specified in the Product Description have been completed. Furthermore, the PM must confirm that the designated approvers (in this case, municipal safety inspectors and the structural engineer) have signed their formal approvals. Only after formal quality verification is documented can the Work Package be closed.

Scenario C: Filtered Highlight Reporting Trap

On an automated logistics warehouse installation, a mechanical conveyor subsystem experiences severe sensor calibration failures, consuming 80% of the stage time tolerance and 60% of the cost contingency. The PM knows the Project Board is sensitive to bad news. In the bi-weekly Highlight Report, the PM reports the stage RAG status as 'Green', omits mention of the sensor failures, and states that 'minor technical calibrations are progressing normally', intending to recover the schedule during the final testing phase.

Practitioner Evaluation:

• Governance Flaw: The Project Manager has breached the fundamental governance obligation of Report highlights and violated the Manage by Exception principle.
• Consequences: The Project Board is deprived of accurate, objective information regarding tolerance consumption. By concealing the reality, the PM prevents the Board from exercising its executive oversight. When the remaining 20% of tolerance is consumed two weeks later, the Board is blindsided by a sudden crisis that could have been mitigated earlier.
• Correct PRINCE2 Action: The Highlight Report must provide an honest, objective summary of stage status, including actual tolerance consumption, open issues, and realistic forecasts. Transparency is non-negotiable; highlighting risks and tolerance erosion early allows the Project Board to provide ongoing direction or prepare contingency reserves before an outright exception occurs.

---

10. Responsibilities in CS: The RACI Chart and Practice Application

Table 16.2 — RACI for controlling a stage

¹ business related · ³ supplier related · ⁴ within work package tolerance

Key: A Accountable · R Responsible · C Consulted · I Informed. The business layer has no entries in this table at all.

Reading the chart

• The project executive is Accountable for most of CS even though it is the project manager's process. Accountability for the stage never leaves the board; the project manager holds delegated responsibility within tolerance.
• Receive completed work package is the exception: the project manager is Accountable and the team manager is Responsible. That reflects the handback direction — the team completes and returns, the project manager answers for whether it is genuinely complete.
• The manual's own tailoring note matters here. Section 16.5.2 says the project manager is responsible for creating all new management products in this process but may delegate tasks while retaining responsibility — the example given is relying on a team manager or specialist to draft the technical content of a work package description while the project manager ensures it is defined, reviewed, and assured well enough to meet the stage plan. An exam option that calls such delegation a governance breach is wrong.
• Collaboration, not command. Section 16.5.1 states the relationship between project manager, project support, and team managers should be collaborative: the project manager is facilitating, not assigning tasks, in order to improve ownership.

How the practices are applied in CS (table 16.3)

The plans practice supplies the stage plan against which status is evaluated and the work package descriptions being authorized; quality supplies the product descriptions whose quality activities are recorded in the quality register before a work package can be received; risk and issues run continuously through capture, corrective action, and escalation; progress produces the highlight reports and the exception reports; business case is checked whenever an issue threatens justification; organizing governs who may authorize and receive work.

---

11. Practitioner Exam Pitfalls & Governance Traps

• Trap 1: Confusing Checkpoint Reports with Highlight Reports: Checkpoint Reports are produced by the Team Manager for the Project Manager in Managing Product Delivery. Highlight Reports are produced by the Project Manager for the Project Board in Controlling a Stage. Never confuse the sender, recipient, or process of these two reports.
• Trap 2: Marking a Work Package Complete Without Product Approval Sign-off: A Work Package is not complete when coding, manufacturing, or construction finishes. It is complete only when all quality activities in the Quality Register are executed and the products are signed off by the approvers designated in the Product Description.
• Trap 3: Directing Specialist Team Members Directly: The Project Manager does not manage individual craftspeople or developers when a Team Manager is appointed. The PM interfaces exclusively with the Team Manager via Work Packages.
• Trap 4: Assuming the Project Manager Authorizes Stage Plans in CS: The Project Manager never authorizes Stage Plans. Stage Plans are authorized exclusively by the Project Board under Directing a Project (DP). In CS, the PM merely executes and monitors the stage against the previously approved plan.
• Trap 5: Concealing Variances within Highlight Reports: Highlight Reports must reflect objective reality. Candidates are frequently tested on scenarios where a PM attempts to 'smooth over' negative variances. In PRINCE2, concealing tolerance consumption or falsifying RAG status is a major governance breach.