Reading a construction programme: the five dates that matter
A construction programme can run to hundreds of lines. For a client, only a handful of dates really tell you whether the project is on track.
The first time a client is handed a construction programme, the reaction is usually the same: a polite nod, and a quiet decision never to open the file again. A detailed programme can run to several hundred activities, and reading it line by line is not your job.
But you do need to hold the contractor to account on time, and for that you only need to watch a few things. Here is where to look.
1. Practical completion
This is the date the building is finished and you can use it. Everything else on the programme exists to serve this date, so it is the first one to find and the one to protect. If it moves, you want to know immediately, and you want to know why.
2. The start on site
Obvious, but worth stating: until the contractor is genuinely mobilised — hoarding up, welfare in, first works underway — the programme is a forecast, not a record. A start date that keeps quietly slipping is often the first honest signal that something upstream is not ready.
3. The long-lead items
Every project has a few elements that take a long time to procure: a curtain-walling package, lifts, switchgear, anything bespoke. These need ordering weeks or months before they are installed. A good programme shows the order dates, not just the installation dates. If an order date passes without the order being placed, the installation date is already at risk, whatever the bar chart still says.
4. Your own decision dates
A programme does not only place obligations on the contractor. It usually assumes the client will make certain decisions — finishes, layouts, sign-offs — by certain dates. These are easy to miss, because they are your dates, not the contractor’s.
A late client decision is one of the most common, and most avoidable, causes of delay. Find your dates on the programme and treat them as deadlines.
5. The critical path
Not every delay matters equally. Some activities have slack; others sit on the “critical path”, where any slippage pushes completion back day for day. You do not need to trace the critical path yourself — that is what your project manager is for — but you should ask, at each progress meeting, one question: are we still on the critical path, and has it moved?
What this looks like in practice
A useful progress report turns the full programme back into those few numbers: the completion date, whether it has changed since last month, and the one or two issues threatening it. If your reporting does not do that, ask for it.
We build programmes to be managed, not admired — and we report against them in language you can act on. Get in touch if that is what your project is missing.