Construction Programme Basics: Reading the Critical Path
Many delays are not caused by site productivity, but by late information and approvals that sit on critical path activities. Knowing where float does and does not exist is essential.
Separate milestone dates from activity logic
Milestones are useful for reporting, but they do not explain risk. Activity-level logic shows what must happen first, what can overlap, and where delays are absorbable.
Track information release dates as programme drivers
A drawing issued one week late can postpone multiple trades. Programmes should include information release points and approval windows as first-class tasks.
When design release is managed as part of the programme, procurement and installation remain aligned.
Watch handover pathways from mid-project onward
Commissioning, statutory sign-off, and O&M compilation often begin too late. Embedding these items early protects completion and occupation dates.
- Plan witness testing windows before commissioning starts.
- Set document handover requirements in every subcontract.
- Review partial completion zones for phased access where possible.
Key takeaway
Programme reliability comes from dependency discipline, not optimistic durations. The critical path should guide decision priority every week.