Project Delivery · Project Control Methods
Controlling a Project Stage
Stage control is the project manager's day-to-day operating process. It translates an authorised stage plan into work packages, receives evidence from delivery, integrates product, schedule, cost, quality, risk and issue status, corrects deviations inside tolerance and raises an exception when the forecast can no longer be delivered within delegated authority.
Executive summary
What this guide enables
Stage control is the project manager's day-to-day operating process. It translates an authorised stage plan into work packages, receives evidence from delivery, integrates product, schedule, cost, quality, risk and issue status, corrects deviations inside tolerance and raises an exception when the forecast can no longer be delivered within delegated authority.
Learning outcomes
- Explain the purpose and lifecycle position of controlling a project stage.
- 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 assign work, monitor it, deal with issues, report progress and take corrective action so the management stage remains within tolerance. It keeps attention on the requested and received products while shielding the governing body from routine detail unless a decision or forecast exception requires direction.
Lifecycle position: This process operates throughout each delivery stage and may be used in initiation for the management products being created there. The project manager is central, coordinating with delivery leads, support, assurance and governance. The process runs as repeated control cycles rather than one sequential pass.
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 authorised
The governing body approves the stage plan, tolerance and any conditions.
Work ready for authorisation
Product definitions, resources, dependencies and package constraints are sufficiently clear.
Checkpoint or product event
Delivery evidence, completed work, issue, risk or decision enters the stage-control cycle.
Forecast or boundary event
Corrective action, exception escalation or stage-boundary preparation is required.
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
Authorise a work package
Agree products, criteria, constraints, resources, reporting, tolerance, quality, issue and handover arrangements with the delivery lead.
- 2
Review work-package status
Use checkpoints and source evidence to assess product status, remaining work, quality, risk, issues and forecast.
- 3
Receive completed work packages
Confirm products are approved, records complete, configuration current and open items have authorised disposition.
- 4
Review stage status
Integrate work packages, cost, schedule, quality, scope, benefits, risk, issues, resources and business-case signals against the stage plan.
- 5
Report highlights
Provide the governing body with concise time-driven information about achievements, forecast, exposure, corrective action and decisions.
- 6
Capture and examine issues and risks
Classify, assess and route new information through the defined risk and issue procedures.
- 7
Escalate issues and risks
Raise an issue or exception when impact or forecast exceeds the project manager's stage authority.
- 8
Take corrective action
Authorise proportionate changes to work or sequence inside tolerance, update records and verify effectiveness.
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 |
|---|---|
| Work package | Authorises creation and delivery of defined products. |
| Checkpoint report | Provides delivery-level product and forecast status. |
| Highlight report | Provides governance with stage health and forecast at an agreed frequency. |
| Issue and exception reports | Provide impact, options and recommendation for event-driven decisions. |
| Updated stage plan and registers | Maintain current actual, forecast, risk, issue, quality and lesson status. |
| Approved products and records | Evidence work-package completion and release dependencies. |
| Corrective action record | Shows local management action, owner, due date and effectiveness. |
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 | Sets stage tolerance and receives highlights or exceptions | Provides direction when requested |
| Project manager | Owns stage control and integrates evidence | Authorises work and correction inside tolerance |
| Delivery lead | Accepts packages, manages team work and forecasts | Raises deviations and delivers approved products |
| Project assurance | Reviews business, user and supplier control | Reports independent findings |
| Project support | Maintains plans, registers, configuration and reports | Provides controlled information |
| Product approvers | Review and approve product versions | Provide quality and acceptance evidence |
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 delivery team should receive work through an agreed package, even when the project manager also leads delivery.
- Stage status must integrate all work packages and remaining dependencies, not average their reported percentages.
- Highlight reports are time-driven; exception reports are event-driven and should not wait for the next report date.
- Corrective action cannot change an approved baseline without the authorised issue and change route.
| 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
On a small project, work packages can be concise and checkpoints may be direct conversations followed by a controlled status update. On a large stage, package authorisation and reporting may be automated, with discipline leads and integrated controls. Reporting frequency can vary by package. The project manager should preserve one integrated stage forecast even when delivery systems differ.
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
Managing a threatened package tolerance
Situation: A delivery lead forecasts that a component will exceed its work-package time tolerance, but resequencing could keep the overall stage within tolerance.
- The delivery lead raises the forecast promptly with remaining-work and dependency evidence.
- The project manager assesses the integrated stage, quality, resource, cost and risk impact rather than automatically escalating to governance.
- A corrective resequencing action and revised package agreement are authorised within stage tolerance; affected teams and configuration records are updated.
- The next checkpoint tests recovery. An exception trigger is retained if the stage forecast deteriorates beyond delegated authority.
Control outcome: The issue is escalated one level to the person who can act, while governance remains undisturbed unless its stage tolerance is threatened.
Control guidance
Failure modes, recovery and common questions
| Failure mode | Consequence | Control response |
|---|---|---|
| Unauthorised informal work | Scope, resource and acceptance drift | Create or update a work package before work continues |
| Historic status only | Problems are reported after recovery time is lost | Require remaining-work and forecast evidence |
| Correction changes baseline silently | Plans and products lose traceability | Use issue and change control |
| Every variance goes to governance | Delegation collapses | Use measurable package and stage tolerances |
Can stage control be used during initiation?
Yes for authorising and monitoring the management products created in the initiation stage.
Who accepts a completed work package?
The project manager confirms package completion after required product approvals; final product acceptance may belong to another authority.
What belongs in a highlight report?
Achievements, next period, integrated forecast, significant exposure, correction and decisions—not all task detail.
When does corrective action become change?
When it alters an approved product, stage or project baseline or exceeds delegated authority.