Project controls

An update should change the conversation.

Progress reporting becomes useful when it helps the team decide what to do next.

2 MIN READ
FIELD NOTES / ILLUSTRATIVELAST REVIEWCURRENT FORECASTDecision needed

Establish what actually happened

Use a clear data date and reconcile actual starts, finishes and remaining work with the field. Record the source of material changes. An update should provide a consistent account of the project’s status before it offers conclusions.

Explain the forecast movement

A changed completion date needs an explanation. Review the driving path, changed relationships, remaining durations and procurement commitments. Distinguish progress effects from adjustments to the plan so the team can understand what moved the forecast.

A good update helps the project team act before the next one.

Turn the review into action

Identify the decisions that can still influence upcoming work. Focus the report on the workface, approvals, materials and handovers that the team must address. Give each priority an owner and a required decision date.

Keep the narrative readable

A useful narrative connects the current status to the next period. Explain what changed, which milestones moved and what the project team needs to do. Detailed schedule data should support that explanation rather than replace it.

TRY THIS ON YOUR NEXT REVIEW
  • Reconcile progress at a clear data date.
  • Explain forecast movement.
  • Assign an owner to each next decision.

This article is general planning commentary. Project requirements and engagement methods are defined for each assignment.

Keep exploring

Where to next? Follow the loop.

Let’s put a better plan behind your next project.

Start a conversation