Delay analysis basics for NEC contractors

A plain-English introduction to the main delay analysis methods and how NEC assesses time on compensation events.

Programmes and time3 min read

On this page
  1. How NEC assesses time
  2. The main retrospective methods
  3. What you need to do well
  4. Where it gets difficult

Delay analysis is the process of working out what caused a delay and how much time it is worth. It underpins extension of time claims in most forms of contract and, under NEC, the assessment of the effect of compensation events on the Completion Date.

How NEC assesses time

NEC is unusual because time on a compensation event is assessed forwards, using the Accepted Programme, at the time of the event. The change to the Completion Date is the length of time that, because of the event, planned Completion is later than planned Completion on the Accepted Programme (clause 63.5 in NEC4, 63.3 in NEC3). In NEC4 the Accepted Programme used is the one in force at the dividing date, adjusted for what has happened since its date. Float before planned Completion can absorb an event without any extra time, and the gap between planned Completion and the Completion Date stays with the Contractor. The Contractor shows this in a revised programme included with the quotation.

This means:

  • The quality of the Accepted Programme decides how well the assessment works. If there is no Accepted Programme, or the latest programme was not accepted for a reason the contract allows, the Project Manager can assess the event itself using its own view of the remaining work (64.1, 64.2).
  • Assessments are made event by event, in the order they occur.
  • Retrospective disputes happen mainly where the programme was poor, the logic was changed, or events were not notified in time.

The main retrospective methods

When a dispute does arise, analysts often use methods from the Society of Construction Law Delay and Disruption Protocol. Each has strengths and limits.

Method How it works Good for Weakness
As-planned versus as-built Compare the planned programme to what actually happened Simple, small projects Does not prove causation
Impacted as-planned Insert the delay event into the baseline Early-stage, prospective views Ignores actual progress
Time impact analysis Insert the event into the programme as it stood at the time Contemporaneous assessment, closest to how NEC works Needs good programme updates
Windows analysis Break the project into periods and analyse the critical path in each Complex projects with changing critical paths Time-consuming; needs reliable data
Collapsed as-built Remove delays from the as-built programme to see what would have happened When baseline data is poor Relies on a logic network built after the event

What you need to do well

  1. Keep every programme revision, in native format, with the data date.
  2. Keep actual dates accurate. Altering actuals retrospectively destroys the value of your records.
  3. Notify events on time. Under clause 61.3 a late notification can lose the entitlement.
  4. Record cause and effect. Link each delay to the event, the activities it hit and the date.
  5. Keep a schedule of changes between revisions.
  6. Do not change logic quietly. Explain it.

Where it gets difficult

  • Concurrent delay, where Client and Contractor risk events overlap.
  • A critical path that moves between revisions.
  • Changes to logic made with the delay in mind.
  • Float ownership disputes.
  • Accelerated or resequenced work.

These are the cases where specialist input pays for itself. A planner who has built or reviewed the programme history can often resolve in days what would otherwise take weeks of correspondence.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?