7.1 Controlling a Stage (CS) Process
Key Takeaways
- Controlling a Stage (CS) is the day-to-day management process executed by the Project Manager during delivery stages.
- Work is delegated to Team Managers using Work Packages, which establish clear tolerances, constraints, and quality requirements.
- Progress is monitored via Checkpoint Reports from Team Managers and summarized to the Project Board via Highlight Reports.
- The Project Manager handles day-to-day issues and risks within authorized stage tolerances; breaches require an Exception Report.
- CS operates as a continuous management loop: Authorize Work Package → Monitor Progress → Review Stage Status → Report → Take Corrective Action / Escalate.
7.1 Controlling a Stage (CS) Process
Exam Focus: Controlling a Stage (CS) represents the operational engine room of a PRINCE2 project. It describes the day-to-day work of the Project Manager during every delivery management stage. Candidates must understand the sequence of CS activities, how Work Packages are authorized and controlled, how progress is reported, and the precise escalation boundary between the Project Manager and the Project Board.
Purpose and Scope of Controlling a Stage
The purpose of Controlling a Stage (CS) is to assign work to be done, monitor that work, deal with issues, report progress to the Project Board, and take corrective actions to ensure that the management stage remains within agreed tolerances.
CS is executed by the Project Manager for every delivery stage of the project. It is not used by the Project Board (who operate under Directing a Project) nor by the Team Manager (who operate under Managing Product Delivery). While principles of control apply during the Initiation Stage, formal CS process execution specifically governs delivery management stages after the Project Board authorizes project execution.
+-----------------------------------------------------------------------------+
| DIRECTING A PROJECT (Project Board) |
+-----------------------------------------------------------------------------+
^ Directives & Exception Decisions | Authorizations & Tolerances
| v
+-----------------------------------------------------------------------------+
| CONTROLLING A STAGE (Project Manager) |
| [Authorize WP] -> [Monitor Progress] -> [Review Status] -> [Take Action] |
+-----------------------------------------------------------------------------+
^ Checkpoint Reports & Products | Work Packages & Tolerances
| v
+-----------------------------------------------------------------------------+
| MANAGING PRODUCT DELIVERY (Team Manager) |
+-----------------------------------------------------------------------------+
Key Objectives of the CS Process
The Project Manager performs CS to achieve several critical governance objectives:
- Controlled Delegation: Focus attention on delivering management stage products in accordance with agreed Work Packages.
- Proactive Monitoring: Maintain control through regular Checkpoint Reports and progress reviews to detect variances early.
- Active Risk & Issue Management: Keep risks and issues under continuous evaluation and control using the Risk Register and Issue Register.
- Business Case Alignment: Ensure that the stage forecast remains aligned with the Business Case and project objectives.
- Transparent Reporting: Provide regular Highlight Reports to the Project Board to maintain executive visibility.
- Boundary Compliance: Take corrective action within agreed stage tolerances, and promptly escalate forecast breaches via Exception Reports.
The Cyclic Engine of Controlling a Stage
CS is not a linear, one-time process; it is an iterative management loop that runs continuously throughout the stage. The process consists of eight interconnected activities grouped into four operational phases:
1. Work Package Cycle (Delegation & Receipt)
- Authorizing a Work Package: The Project Manager formally agrees the scope, constraints, quality criteria, reporting frequencies, and tolerances of a Work Package with the Team Manager.
- Reviewing Work Package Status: The PM evaluates Checkpoint Reports from the Team Manager to verify progress against the Work Package agreement.
- Receiving Completed Work Packages: When products are completed and quality checked, the PM verifies formal acceptance criteria before closing the Work Package.
2. Monitoring & Progress Evaluation
- Reviewing Stage Status: The PM collates completed work and remaining effort to assess whether the management stage is on track regarding time, cost, quality, scope, benefits, and risk.
- Capturing and Examining Project Issues and Risks: New risks, change requests, or off-specifications are logged in the Daily Log, Issue Register, or Risk Register and evaluated for overall impact.
3. Reporting & Escalation
- Reporting Highlights: The PM compiles regular Highlight Reports to communicate stage progress, completed Work Packages, and upcoming milestones to the Project Board.
- Escalating Issues and Risks: If an issue or risk is forecast to exceed authorized stage tolerances, the PM prepares an Exception Report for the Project Board.
4. Corrective Action
- Taking Corrective Action: The PM implements internal remedies or adjustment actions (such as reallocating stage contingency resources) provided the stage tolerances are not breached.
Deep Dive: Management Products in CS
| Management Product | Author / Maintainer | Primary Recipient | Core Purpose & Contents |
|---|---|---|---|
| Work Package | Project Manager | Team Manager | Formal agreement defining product scope, quality criteria, constraints, interfaces, tolerances, and Checkpoint reporting frequency. |
| Checkpoint Report | Team Manager | Project Manager | Periodic progress update detailing Work Package performance, quality checks completed, and short-term forecast. |
| Highlight Report | Project Manager | Project Board | Summary report providing stage progress, budget/schedule status, key risks, issues, and next period's planned activities. |
| Issue Report | Project Manager / Logged by Any | Project Manager / Project Board | Detailed description and impact analysis of a specific project issue (Request for Change, Off-Specification, or Problem/Concern). |
| Exception Report | Project Manager | Project Board | Formal notification detailing a forecast breach of stage or project tolerances, analyzing options, and recommending a way forward. |
Work Package Structure and Dynamics
A Work Package is the foundational mechanism for delegating work from the managing level (Project Manager) to the delivering level (Team Manager). It prevents micro-management by establishing clear boundaries within which the Team Manager operates independently.
Essential Elements of a Work Package:
- Product Descriptions: Clear specification of the products to be produced, including quality criteria and quality method.
- Development Interfaces: Technical, physical, or organizational dependencies that must be managed.
- Tolerances: Specific time, cost, scope, and quality tolerances assigned to the Team Manager for this Work Package.
- Reporting Requirements: Frequency and format of Checkpoint Reports (e.g., weekly written report or bi-weekly meeting).
- Approval & Acceptance: Named individuals responsible for inspecting products and signing off final acceptance.
+-----------------------------------------------------------------------------+
| WORK PACKAGE CONTAINER |
| +-----------------------+ +--------------------------------------------+ |
| | Product Description | | Work Package Tolerances (Time/Cost/Quality)| |
| +-----------------------+ +--------------------------------------------+ |
| +-----------------------+ +--------------------------------------------+ |
| | Quality & Acceptance | | Reporting Frequency (Checkpoint Schedule) | |
| +-----------------------+ +--------------------------------------------+ |
+-----------------------------------------------------------------------------+
Managing Tolerances and Escalation in CS
One of PRINCE2's core principles is Manage by Exception. In CS, the Project Manager operates within stage tolerances set by the Project Board during Directing a Project (DP).
Tolerance Escalation Workflow:
- Detection: During stage status review, the PM identifies that a stage parameter (e.g., cost or schedule) is forecast to exceed tolerance.
- Analysis: The PM investigates root causes and formulates viable corrective options.
- Exception Report: The PM writes an Exception Report detailing the breach, options analysis, and recommended action, and submits it immediately to the Project Board.
- Board Decision: The Project Board reviews the Exception Report and either provides advice, approves corrective action, or instructs the PM to invoke Managing a Stage Boundary (SB) to draft an Exception Plan.
Critical Exam Rule: The PM must escalate as soon as a tolerance breach is forecast, not after the breach has already occurred! Waiting until the tolerance is actually exceeded before reporting is a major project management failure in PRINCE2.
Roles and Responsibilities in CS
- Project Board: Reviews Highlight Reports, receives Exception Reports, provides guidance, and approves major change requests that exceed PM authority.
- Project Manager: Executes the entire CS process—authorizes Work Packages, monitors progress, captures issues/risks, writes Highlight/Exception Reports, and takes corrective action within tolerances.
- Team Manager: Receives Work Packages, provides Checkpoint Reports, escalates team-level issues to the PM, and delivers accepted products.
- Project Assurance: Verifies that Work Packages are correctly authorized, products meet quality standards, and stage status reporting is accurate and objective.
- Project Support: Maintains registers (Issue Register, Risk Register, Quality Register) and assists in compiling status metrics.
Exam Tips & Common Distractor Patterns
- Who authorizes Work Packages? Always the Project Manager. The Project Board authorizes stages (in DP), while the PM authorizes Work Packages (in CS).
- Is CS executed in every stage? CS is used in every delivery stage. During the Initiation Stage, initiation activities are controlled under IP/DP, but CS is the standard process for delivery management stages.
- Highlight Report vs. Checkpoint Report: Checkpoint Reports flow from Team Manager to Project Manager. Highlight Reports flow from Project Manager to Project Board. Do not confuse their direction or audience!
- Corrective Action vs. Exception: If the corrective action keeps the stage within tolerance, the PM acts directly. If the action requires exceeding stage tolerance, the PM cannot act unilaterally—they must submit an Exception Report.
Who is responsible for authorizing a Work Package in the Controlling a Stage process?
What should the Project Manager do immediately upon forecasting that stage cost tolerances will be exceeded?
Which progress report is produced by the Team Manager and sent to the Project Manager?