Project reporting
Controlling a Stage
Operate the stage week by week through work authorisation, progress control, RAID management, and timely exception escalation.
What this helps you do
Make sure day-to-day delivery stays inside agreed tolerance and produces decision-ready reporting.
Use this when
- Any live stage where delivery work is in progress.
- Weekly control and sponsor reporting cycles.
- Periods of elevated risk, change pressure, or supplier uncertainty.
What good looks like
- Work is authorised with clear outcomes and ownership.
- Progress is measured against plan and tolerance, not optimism.
- Top RAID items have named actions and due dates.
- Sponsor reports contain real decisions and escalation asks.
- Forecasts are updated before tolerance failure, not after.
Minimum viable version
- Stage plan with current milestones and dependencies.
- Weekly RAID and decision review with owner actions.
- Regular highlight reporting to sponsor with explicit asks.
- Exception trigger and escalation path understood by team.
Stronger version
- Trend view on schedule, effort, and risk exposure.
- Supplier checkpoint rhythm linked to work package outcomes.
- Benefits confidence pulse in control reporting.
- Integrated change pressure and impact tracking.
Step-by-step operating flow
- Authorise work packages with output, quality, and reporting expectations.
- Collect progress and update forecast against stage tolerances.
- Review risks, issues, decisions, and changes as one control conversation.
- Resolve within authority and escalate when thresholds are threatened.
- Publish concise highlight report with action-led narrative.
- Update logs, plans, and owner actions immediately after review.
- Re-prioritise stage actions based on decision outcomes.
- Prepare evidence for boundary review as stage completion approaches.
Inputs needed
- Work package status and delivery evidence.
- Updated RAID, decision, and change items.
- Milestone forecast and variance analysis.
- Supplier updates, dependencies, and operational constraints.
Outputs produced
- Current control position for sponsor and team.
- Updated highlight report and escalation items.
- Exception report when tolerance breach is forecast.
- Actioned RAID and decision logs with accountability.
Common mistakes
- Counting activity instead of measuring control outcomes.
- Treating RAID categories as separate meetings and losing context.
- Reporting green while key decisions remain blocked.
- Escalating after tolerance breach rather than at forecast risk.
- Letting unresolved actions roll from week to week without ownership.
Tailoring notes
- Lite work can use one combined control session per week.
- Enhanced work should split operational and governance reporting where needed.
- Recovery mode should increase cadence and shorten decision lead times.
- Agile teams can feed sprint evidence into the weekly control cycle.
Related templates
Related tools
PRINCE2 mapping
Operational translation of PRINCE2 Controlling a Stage, integrating work package control, progress reporting, and exception escalation.