Six months behind is a difficult number to hear. It's also, in most cases, a recoverable position — provided the first moves are the right ones. The instinct in a lot of project teams is to react to the headline: add resource, demand a new programme, or start assigning blame. None of those things help until you understand what's actually driving the delay.
Get the real position first, not the summary
Progress reports tend to compress a complicated picture into a single RAG status or a headline percentage. That's useful for a board pack. It's not useful for deciding what to do next. Before anything else, you need the actual current programme, the baseline it's being measured against, and a clear view of what's on the critical path versus what merely looks bad.
Separate critical path delay from noise
Not every late activity is affecting completion. Some delay is absorbed by float. Some is genuinely driving the end date. Time spent early on distinguishing the two is rarely wasted — it stops you fixing the wrong thing loudly while the real cause continues unaddressed.
Work out who actually knows what's happening
On most delayed projects, different people hold different pieces of the picture — the site team, the design team, the contractor's planner, the client's own project manager. Six months of delay usually has more than one contributing cause, and reconciling those different accounts is often where the real diagnosis starts.
Decide what needs deciding this week
Not every issue needs solving immediately, but some do. Separating the decisions that are genuinely time-critical from the ones that can wait a fortnight keeps the recovery effort focused rather than diffuse.
Get the records straight now
Whatever the eventual outcome — recovery, a negotiated extension of time, or something more contentious — contemporary records matter. If they're incomplete or inconsistent, that's worth knowing and addressing early, not discovering six months further on.
The first move that matters most
The most useful first step is usually an honest, independent diagnosis: what's actually causing the delay, who's right about what, and what the programme is genuinely saying. Everything else — recovery planning, contractual position, resourcing decisions — follows from getting that right first.
This is the core of construction project recovery — establishing the real position before committing to a plan.
This article offers general guidance based on common patterns in construction project delivery. It is not project-specific or legal advice, and every project is different. If you're facing a specific situation, the details matter — talk it through directly.