Why Most Construction Programmes Fail — and What to Do Instead

Most construction projects start with a programme. A Gantt chart, a bar chart, a sequence of activities with durations and dependencies. It gets approved, shared with the client, and filed — and then the site gets on with the work.

Six weeks later, the programme bears no resemblance to what's actually happening on site.

Why programmes slip

Programme slippage rarely has a single cause. It accumulates:

Late design information: drawings issued after the programme assumed they'd be available
Long-lead items ordered late: procurement left until it becomes critical
Subcontractor mobilisation delays: trades who weren't ready when the programme said they needed to be
Weather and access constraints that weren't factored in at planning stage
Scope changes that weren't reflected in the programme when they were approved

Each of these individually might be manageable. Together, they compound — because construction activities are dependent on each other, and a delay in one trade cascades into the next.

The cost of a programme that nobody maintains

When the programme isn't updated regularly, nobody has an accurate picture of where the project actually stands. The superintendent doesn't know which trades are critical. The client doesn't know whether their handover date is still achievable. The head contractor doesn't know whether they're entitled to claim an extension of time — or whether they're exposed to liquidated damages.

A programme that isn't maintained doesn't protect anyone. It just creates ambiguity.

What a maintained programme looks like

An actively managed programme is updated at least fortnightly. It shows:

Actual progress against planned progress for each activity
Current critical path (which may have changed since the original programme was issued)
Forecast completion date, updated based on current progress
Any approved extensions of time and their impact on the programme
Upcoming procurement and design information requirements

The update doesn't need to be a complex re-baseline. It needs to be accurate and shared with the right people.

Recovering a slipping programme

When a programme has slipped significantly, there are three options:

Accelerate: add resources, extend working hours, or sequence trades differently to recover lost time. This costs money and needs to be approved and documented.
Re-sequence: find activities that can run in parallel rather than sequentially, reducing the overall duration without adding resources.
Revise the programme: formally acknowledge that the completion date has moved, update the programme to reflect reality, and manage client expectations accordingly.

Option 3 is the one most often avoided. It's uncomfortable. But a programme that pretends a project will finish on time when it won't doesn't serve anyone — it just delays the conversation until the problem is worse.

The role of the PM in programme management

A project manager who only looks at the programme once a month isn't managing the programme. They're reporting on it. The programme should be a live working document — reviewed at site meetings, updated after every significant event, and used to make actual decisions about resource allocation and sequencing.

If that discipline isn't there, someone needs to put it there.

Programme management is included in our Project Oversight and Full PM Partnership services. Get in touch to discuss your project.