A construction programme shows how work was planned to proceed: its activities, sequence, durations, dependencies and milestones. It can help identify when planned completion may have moved, but it cannot establish on its own what happened on site, what caused a delay or whether the contract grants an extension of time or compensation. Those questions require the programme to be tested against project records, actual progress, planning assumptions and the contract.
What a programme can—and cannot—show
A logic-linked programme represents a plan, not a complete record of the project. Its network can show which sequences of work were expected to govern planned completion and how a modeled change might affect that date. But the result depends on the network logic, activity durations, status date, progress information and assumptions being credible.
That distinction matters in a delay dispute. A programme may be accepted, updated or presented as the project’s critical-path schedule; none of those facts alone proves that its logic reflected the work actually performed or that a particular event delayed completion. The Society of Construction Law (SCL) Protocol advises analysts conducting time-slice analysis to check that historical programme components reflect actual progress and that future sequences and durations are reasonable, realistic, achievable and logically linked. See the SCL Delay and Disruption Protocol, second edition.
A critical path is therefore a conclusion drawn from a network and its inputs—not a verdict about responsibility. The programme can help frame a cause-and-effect question, but dated evidence is needed to establish what occurred and whether it affected the work that governed completion.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Why the critical path needs to be tested
Logic and durations shape the answer
Dependencies determine which activities can proceed in parallel and which must wait for others. If the logic is incomplete, unrealistic or inconsistent with the construction method, the calculated critical path may not represent the way the project could actually be delivered. Durations matter too: an optimistic duration can make a sequence appear achievable on paper while concealing the time needed for the work.
Progress and assumptions can change over time
As work proceeds, actual starts and finishes, remaining durations, new activities and revised forecasts can alter the path to completion. An analysis should distinguish what was known at the time from what became clear later, and identify which programme version and status date it uses. An update is evidence of a forecast at a point in time; it is not automatically proof of actual progress or cause.
Risk and productivity affect whether a plan is credible
The Office of Rail and Road’s inquiry into the May 2018 timetable disruption found that Network Rail’s planning did not accurately estimate actual construction risks and did not sufficiently account for historical productivity. It also described replanning becoming overly optimistic as timescales compressed. The inquiry is a specific example, not proof that every programme has the same weakness. It illustrates why planned durations and recovery assumptions should be assessed against project conditions and relevant performance evidence. Read the ORR inquiry findings.
Safety and sequencing assumptions belong in that assessment as well. In UK construction guidance, the Health and Safety Executive says hazards should be considered when estimating costs and preparing the programme of work, with suitable allowances made. Its guidance also describes project-management arrangements and the planning, management, monitoring and coordination roles of the principal designer and principal contractor under the UK CDM context. This is relevant to how work is planned, not a rule deciding delay entitlement. HSE: Planning for construction work.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What different delay-analysis methods are designed to do
Delay-analysis methods differ in when they assess the critical path, whether they model effects prospectively or examine them retrospectively, and what records they need. The SCL Protocol describes the approaches below; none is universally best. Choice depends on the question being asked, the project’s changing critical path and the reliability of the available baseline, updates, progress records and as-built information.
| Method | Orientation and critical-path treatment | Key evidence and limitation |
|---|---|---|
| Impacted as-planned | Prospective: inserts modeled delay-event sub-networks into a logic-linked baseline to assess their predicted effects. | Needs a suitable baseline and credible assumptions about the modeled events. It assesses modeled effects rather than reconstructing actual progress. |
| Time-slice or windows analysis | Examines the project in periods, using updates or progress information to assess the contemporaneous critical path and critical delay in each period. | Needs reliable updates or progress information and records to investigate possible causes. The Protocol advises checking historical progress and whether future logic and durations are realistic. |
| As-planned versus as-built windows | Compares planned and actual progress within framed periods. | Can be useful where baseline or update reliability is in question, but the analyst still needs to explain how criticality was determined. |
| Retrospective longest path | Retrospective: develops or verifies an as-built programme, then traces the longest continuous path backward from actual completion. | Needs a sufficiently reliable as-built programme. The Protocol notes that this method has more limited capacity to recognize changes in the critical path over time. |
| Collapsed as-built | Retrospective: models selected delay events out of a logic-linked as-built programme to assess their effects. | Depends on the reliability of the as-built network and the events selected and modeled. |
For a method comparison, ask whether the analysis is prospective or retrospective; how and when it determines criticality; what baseline, updates, progress records or as-built information it relies on; and whether the project’s critical path changed. Those choices affect what the analysis can answer and how confidently its conclusions can be checked. The SCL Protocol’s detailed descriptions are in its second edition.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use project records to test the programme narrative
Contemporaneous records help distinguish planned activity from work actually carried out, and a forecast from an outcome. They can also help investigate why progress differed from the plan. A useful review draws on dated records relevant to the activities and period in dispute, rather than relying on a programme diagram in isolation.
A public Imperial War Museum fit-out tender specification illustrates the kinds of information a project may require. Its specified progress reporting includes activities started and completed, actual dates, remaining durations, additional activities and assumptions, forecast completion, slippage or advance against contractual dates, comparison of actual and programmed work, outstanding information, resources, weather, variations, instructions and requests for information. These are requirements in that tender document—not a universal contractual checklist. See the Imperial War Museum Age of Terror fit-out tender attachment.
Best Value
![Express Schedule Free Employee Scheduling Software [PC/Mac Download]](https://m.media-amazon.com/images/I/41yvuCFIVfS._SL160_.jpg)
- Simple shift planning via an easy drag & drop interface
- Add time-off, sick leave, break entries and holidays
- Email schedules directly to your employees
- Progress evidence: dated activity starts and finishes, progress updates, remaining durations and records of work added or changed.
- Forecast and comparison: forecasts, slippage or advance, and comparisons between programmed and actual work.
- Potential causes and constraints: instructions, variations, requests for information, outstanding information, resources and weather records where relevant.
- Planning basis: the assumptions and durations used, and whether they reflect known risks, site conditions and achievable sequencing.
The precise records available and required depend on the project and its contractual arrangements. The point is to use evidence that can test the programme’s dates, logic and assumptions—and to keep the source and timing of each record clear.
The programme is not the contract’s answer to entitlement
The SCL Delay and Disruption Protocol is professional guidance on extensions of time and compensation for delay and disruption. Its second edition was published in February 2017, supersedes the first edition and Rider 1, and is described by the Society as guidance focused on the UK construction market, particularly the English-law position. It is a reference framework, not legislation, a judgment or an amendment to a project contract. SCL: Delay and Disruption Protocol.
A programme and delay analysis can inform a project’s account of timing and cause; they do not, by themselves, determine whether a party has a contractual entitlement. That requires the actual contract and applicable law to be considered. For a particular project, the relevant provisions may include those governing programmes, notices, extensions of time, concurrency and compensation. A general article cannot determine how those terms apply to a specific dispute.
For public project reviews, NISTA’s Gate 2 Review: Delivery Strategy guidance says: “The Programme/Project should demonstrate that it is controlling its schedule, and the impact of delays on benefits and cost.” That is a government review expectation, not a statement of every construction contract’s terms. The guidance also addresses objectives, assumptions, constraints, activities, milestones and baselining at business-case stages. NISTA Gate 2 Review: Delivery Strategy.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
