Tell the right progress story

What you will understand

• Match progress reports to their sender, recipient and decision.
• Distinguish time-driven controls from event-driven controls.
• Recognise the limits of dashboard data and apply useful lessons.

The idea

Imagine opening a project dashboard covered in green indicators while the main supplier quietly expects a six-week delay. A progress practice should make that contradiction visible. Its job is to connect evidence about completed work and remaining work with the decisions needed to keep the project under control. Activity alone is not proof of useful achievement.

Start with an agreed reference point: a plan, its performance targets and the tolerances granted by the next management level. Compare actual achievement with that reference and update the forecast. Money already spent and tasks already started matter, but neither tells you whether the required products will be accepted or whether the remaining investment is worthwhile. Progress information must support both performance control and continued business justification.

A checkpoint report carries team-level progress to the project manager. Its frequency and format are agreed in the work package arrangements. A highlight report carries the project manager’s stage-level summary to the project board. These are time-driven controls because an agreed interval triggers them. A report can be a conversation supported by records or a digital view; its management purpose matters more than its file format.

An event-driven control responds to something happening. Examples include authorising a work package, reaching a stage boundary, preparing closure and responding to a forecast tolerance breach. An exception report explains a forecast breach to the board and supports its decision. It should not wait for the next routine highlight report. An end stage report supports a stage-end decision; an end project report supports the review of the whole project.

Decide where the data comes from, who owns it, when it was updated and what it means. A dashboard showing hours booked may say little about accepted products. An automated percentage may conceal unresolved defects or unsupported estimates. Useful digital controls preserve access permissions, meaningful definitions and traceable evidence. A green status cannot replace a named person’s responsibility to assess the forecast and act on uncertainty.

Learning is also part of control. Capture a useful observation when it occurs, identify its implications and change an approach when justified. Waiting until closure can waste an opportunity to improve the current stage. A lessons log supports continuing capture; a lessons report shares selected lessons with an audience that can use them. A collection of anecdotes has limited value until someone decides what to do differently.

Reports connect management levels

Points to remember

• Checkpoint: team manager to project manager; highlight: project manager to board.
• Time-driven and event-driven describe triggers, not paper versus digital formats.
• Progress combines actual evidence, forecasts, tolerance checks and action.

Your takeaway

Choose progress information by its decision, level and trigger. Verify the evidence behind the colour, and use reports and lessons to support timely action.