Reporting schedule status to the client
In the client meeting, what was observed on site turns into a decision. For the programme this means it is not enough to print the current plan and put it on the table. Site management has to explain what it means.
Schedule status is not a snapshot
A bar chart shows where the tasks stand. It does not answer the questions the client actually has: are we holding the handover date? Where are we losing time, and can it be recovered? What happens if a decision takes another two weeks?
The gap between depiction and statement is site management’s real contribution to this agenda item. Showing only the plan leaves the interpretation to the audience – at the risk that each party reads something different into it.
What schedule status covers
It has proved useful to go through the same points at every meeting. That makes changes visible over time and stops a topic from quietly disappearing:
- Current progress against the agreed state.
- Critical milestones – met, at risk or moved.
- Existing delays, with cause and extent.
- Impending shifts, before they have occurred.
- Client decisions that are pending and affect the programme.
- Effects of variation orders on the sequence.
- Occupancy and handover dates.
- Acceptance and pre-acceptance as dates in their own right.
Decisions are tasks with a duration
The point most often missing in practice: a pending client decision affects the programme just as a delivery period does. If a sample approval or an award is resolved three weeks later than planned, the dependent work shifts accordingly – except that this delay appears on no bar, because it sits before the task.
Every pending decision therefore comes with a statement of when it has to be taken for the sequence to hold. This does not move responsibility for the programme onto the client – it only makes it visible before it turns into a question.
Report early, while it is still steerable
With dates, openness pays. A delay named early can still be absorbed by rearranging the sequence or bringing work forward. The same delay, reported only once it touches the handover date, allows nothing but expensive answers – acceleration measures or a postponement.
A client meeting should therefore not learn of a scheduling problem only when it is no longer steerable. That is less a matter of openness than of preparation: an impending delay becomes visible only if the plan has been kept up to date between meetings.
In Menira the current state can be exported print-ready for the meeting – with the critical path highlighted and the milestones the discussion will turn on anyway.