NEC delay analysis and extension of time: the complete contractor guide
- 3 days ago
- 18 min read
There is a pattern that repeats on almost every NEC project that ends in dispute. A compensation event is notified. A quotation is produced. The programme is adjusted, often several months after the event. The project manager pushes back. Negotiations drag. The completion date slips again. Eventually somebody is asked to produce a delay analysis that explains how the project ran late.
At that point, the person producing the analysis discovers something uncomfortable. The contract did not expect this kind of analysis at all. NEC was not designed to support a retrospective reconstruction of what delayed the job. It was designed to make that reconstruction unnecessary by assessing delay prospectively, one compensation event at a time, as each event occurs.
When that design is followed, extensions of time are easy. When it is not, delay analysis becomes the most expensive exercise the project will undertake. And the contractor fighting for time entitlement is almost always fighting uphill.
This article explains how delay analysis and extension of time actually work under NEC4 and NEC3. It covers the mechanism the contract expects, the mistakes that destroy time entitlement, the difference between NEC and JCT that most contractors misunderstand, and what a contractor should actually do to protect its position.
The fundamental difference from JCT
Most construction professionals in the UK have come up through JCT contracts. JCT treats delay retrospectively: something happens that delays the job, the contractor claims an extension of time, the contract administrator assesses the claim against the completion date in the contract, and the completion date is adjusted if the delay is proven to flow from a Relevant Event.
NEC does not work this way. The differences are not cosmetic. They are structural, and they change how a contractor needs to behave from day one.
Under NEC, extension of time is not a separate mechanism. It is a consequence of how compensation events are assessed. Every compensation event under clause 60.1 can carry a time impact. That time impact is assessed as part of the compensation event quotation under clause 62.2. The completion date is then adjusted by the mechanism in clause 63.5, which uses planned completion, not the contractual completion date, as the reference point.
That last point is the one contractors from a JCT background most often miss. On JCT, the completion date moves when a Relevant Event is accepted. On NEC, planned completion is the contractor's forecast of when the works will actually finish. The gap between planned completion and the completion date is terminal float, and that float belongs to the contractor. When a compensation event delays planned completion by two weeks, the completion date moves by two weeks. The terminal float is preserved, not consumed by the delay.
This is deliberately protective of the contractor. If the contractor built a two-week cushion into its programme, a compensation event does not eat that cushion. The contract recognises that the contractor earned that cushion through efficient planning, and it remains the contractor's to keep. The article on time risk allowance and terminal float in NEC covers that distinction in detail.
The second structural difference is the direction of analysis. JCT delay analysis runs backwards. Something has happened, the analyst reconstructs what caused it, and the conclusion is reached with the benefit of hindsight. NEC delay analysis is supposed to run forwards. Each compensation event is assessed at the time it occurs, using the accepted programme that existed at the moment of the event, and the analyst forecasts what the impact will be. The question is not "what happened?" but "what will happen?" from the dividing date onwards.
The third difference is that NEC is not a "wait and see" contract. Under JCT, contractors often accumulate claims and submit them towards the end of the project, when the total effect of delay is clearer. Under NEC, that approach is actively penalised. Clause 61.3 sets an eight-week time bar on compensation events that the contractor should have notified itself. If a contractor realises at month fourteen that a design issue from month six caused delay, the entitlement for that compensation event may be lost entirely. The contract is built around contemporaneous assessment, not end-of-project reconciliation.
Contractors who try to run NEC projects using JCT habits lose time entitlement almost automatically. The contract punishes late notification, rewards prospective thinking, and assumes an accepted programme that is kept current throughout the job.
The machinery of NEC delay assessment
Understanding the step-by-step mechanism matters because every step has a commercial consequence, and every step has a point at which the contractor's position can be weakened.
The sequence begins with the compensation event itself. Clause 60.1 lists the events that are compensation events. They range from project manager instructions changing the scope, to physical conditions the contractor could not reasonably have foreseen, to weather events meeting specific thresholds, to failures by the employer or others to perform obligations by the date shown in the accepted programme. That final point is important: many potential compensation events require the accepted programme to demonstrate when the employer was supposed to do something. Without that information on the programme, the clause 60.1(3) compensation event cannot be triggered.
Once an event has occurred, somebody notifies it. Clause 61.1 applies when the project manager notifies. Clause 61.3 applies when the contractor notifies, with the eight-week time bar. The distinction matters because PM-notified events do not carry the eight-week limit on the contractor, but contractor-notified events do.
The date of notification sets the dividing date. The dividing date is critical. It determines the accepted programme snapshot that will be used to assess the compensation event. Everything done before the dividing date is assessed as actual Defined Cost. Everything after is forecast. The time impact is measured from the dividing date forwards.
The contractor then provides a quotation under clause 62.2. The quotation must include any changes to the accepted programme that the compensation event requires. This is where the real delay analysis happens. The contractor is producing a forecast of what will happen, based on the accepted programme as it stood at the dividing date, incorporating the effects of the compensation event on the programme for remaining work.
The project manager has three weeks to respond under clause 62.3. They can accept the quotation, request a revised quotation with reasons, or make their own assessment under clause 64. If the project manager makes their own assessment, the contractor's position is significantly weakened. The PM's assessment stands unless formally challenged, and it is typically made using conservative assumptions that favour the employer.
The assessment uses clause 63.5 in NEC4 (clause 63.3 in NEC3): "any delay to the Completion Date is assessed as the length of time that, due to the compensation event, planned completion is later than planned completion as shown on the Accepted Programme."
Unpack that sentence carefully. The calculation is not "how much later will the job finish?" The calculation is "by how much is planned completion later than it was before the event?" The reference is the accepted programme at the dividing date. The answer becomes the adjustment to the completion date.
This is the mechanism by which extensions of time are awarded under NEC. Every time impact flows from a specific compensation event, every compensation event is assessed prospectively, and every assessment uses the accepted programme at its dividing date. There is no separate extension of time application. There is no end-of-project claim. The time entitlement is built compensation event by compensation event, in real time, throughout the project.
Why the accepted programme is the commercial anchor
The accepted programme is not just a document used to assess compensation events. It is the document that determines whether the contractor can assess compensation events at all.
If a compensation event arises and the accepted programme at the dividing date does not show the activity affected by the event, the contractor has no baseline to demonstrate the time impact. The programme cannot answer the question the contract asks: "by how much does this event push planned completion later than shown on the accepted programme?" The answer requires planned completion to be shown on the accepted programme in the first place. If it is not there, or if the programme is months out of date and no longer represents the contractor's actual plans, the question cannot be answered properly.
When the programme cannot answer the question, the project manager has grounds to make their own assessment under clause 64. The assessment uses whatever records are available, which typically means actuals rather than forecasts, and conservative assumptions rather than contractor-favourable ones. The contractor's entitlement is not lost, technically, but it is assessed by someone else using methods that rarely favour the contractor.
This is the mechanism behind a pattern that plays out on hundreds of UK construction projects every year. The contractor is entitled to time. The contract provides for that entitlement. But the programme was not in a state to demonstrate it, so the entitlement is reduced or denied. The pillar article on NEC clause 31 programme acceptance covers the mechanism by which the accepted programme is obtained and maintained in detail.
The practical implication is uncomfortable. Every contractor who wants to protect its time entitlement under NEC must maintain a current, logic-linked accepted programme throughout the project. Not because the contract demands it as an administrative burden, but because the contract cannot assess delay properly without it. The programme is the commercial anchor. Without it, the anchor drags.
The dividing date and why contractors miss its significance
The dividing date is the point in the NEC delay machinery that causes the most confusion and the most lost entitlement.
The dividing date is defined in NEC4 clause 63.1 as either the date of the project manager's instruction that caused the compensation event, the date of the employer's failure to comply with an obligation, or the date the contractor notified the compensation event, depending on the type of event. It is not the date work was delayed. It is not the date the contractor noticed an issue. It is a specific contractual date that fixes a moment in time.
At the dividing date, two things happen simultaneously. First, the accepted programme at that moment becomes the baseline for assessing the compensation event. Second, the line between actual cost and forecast cost is drawn: everything done before that date is assessed as actual, everything after is assessed as forecast.
This matters because contractors often delay their response to compensation events. A design change occurs in week eight. The contractor is too busy to deal with it immediately. By week sixteen, when the contractor finally produces a quotation, the programme that existed at the dividing date in week eight is long gone. The contractor tries to build the impact assessment against the current programme, which shows progress already lost to the design change. The analysis then has to reconstruct what planned completion would have been at the dividing date, which is harder, more disputable, and produces weaker entitlement.
The contractors who handle NEC delay analysis well treat the dividing date as a commercial anchor. When a compensation event is notified, the accepted programme at that moment is captured immediately. The impact analysis is built against that captured snapshot, not against whatever programme exists when the quotation is eventually produced. This preserves the prospective character of the analysis and keeps the entitlement in the contractor's control.
The problem is amplified when there are multiple compensation events. If three compensation events occur in a two-month period, and none of them have been properly assessed, each subsequent event has a worse baseline than the one before. The programme drifts further from the job with each unassessed event. By the time the fourth event is notified, the accepted programme may no longer represent anything useful. At that point, the contractor is no longer doing delay analysis. The contractor is doing forensic reconstruction, from a weak position, with a project manager who has every incentive to assess conservatively.
Prospective vs retrospective analysis: the hidden disagreement
The most consequential debate in NEC delay analysis is one that rarely surfaces on a live project but determines almost every dispute that ends in adjudication. When a delay analysis is eventually produced, either as part of a compensation event quotation months after the event, or as part of a dispute, should it be prospective or retrospective?
The NEC contract clearly intends prospective assessment. Clause 63.5 refers to planned completion and the accepted programme, both of which are prospective concepts. The language throughout is forward-looking. The contract assumes the analysis is done at the time of the event, when the future is still genuinely in question.
But in practice, almost every NEC delay analysis is done after the fact. The compensation event is notified late. The quotation is produced months after the dividing date. By the time the analysis is built, the actual progress of the affected activities is known, and the actual effect of the event is measurable in the project record.
When that happens, which version of reality does the analysis use? The forecast that would have existed at the dividing date, based on the accepted programme at that moment? Or the actual outcome, based on what has since occurred on site?
Adjudicators have tended to prefer prospective analysis on NEC projects, consistent with the contract's design. But where the contractor has not maintained a credible accepted programme, or where the gap between dividing date and assessment is so large that prospective analysis is no longer believable, adjudicators have been willing to use actuals. Housing Executive v Healthy Buildings remains the leading case on this point, showing that hindsight can gain ground when the prospective record has degraded.
The commercial consequence for contractors is significant. Prospective analysis tends to favour the contractor, because planned completion at the dividing date typically shows the contractor in a position where it would have finished close to, or earlier than, the completion date. Retrospective analysis tends to favour the employer, because actual records show what happened, including all the other delays that occurred, the contractor's own performance issues, and any mitigation that did or did not take place.
A contractor who maintains its accepted programme, notifies compensation events promptly, and produces quotations within the contractual timescale gets prospective analysis, which the contract was designed to provide and which tends to protect the contractor's position. A contractor who does not gets retrospective analysis, which the contract was not designed around and which tends to reduce the contractor's entitlement.
This is not a marginal concern. It is the most important commercial decision a contractor makes on an NEC project, and most contractors make it by default rather than by design.
Concurrent delay under NEC
Concurrent delay is the situation where two or more delays are running simultaneously, and at least one is the employer's risk and at least one is the contractor's risk. Under JCT, concurrent delay is extensively litigated because the extension of time assessment has to apportion cause. Under NEC, concurrent delay works differently, and the NEC approach is worth understanding because it significantly affects entitlement.
NEC4 clause 63.8 (NEC3 clause 63.6) provides that assessments are made on the basis that the contractor reacts competently and promptly to the compensation event, and that the accepted programme can be changed. But it does not explicitly address concurrent delay in the way JCT jurisprudence has developed.
The effect in practice is that NEC tends to allow time for compensation events without deducting concurrent contractor-caused delay from the assessment. If a compensation event delays planned completion by three weeks, and a contractor-caused delay would have delayed completion by two weeks anyway, the contractor may still receive three weeks of time entitlement under the compensation event. The contractor-caused delay is dealt with separately, through Disallowed Cost under Options C and D, or through the contractor absorbing the time consequence.
This is more generous to the contractor than JCT, where concurrent delay can reduce an extension of time under the principle that the contractor would have been delayed anyway. Under NEC, the compensation event entitlement is protected as a separate calculation, provided it can be properly demonstrated against the accepted programme.
The practical implication is that contractors on NEC projects should not be quick to concede that concurrent contractor-caused delay reduces their compensation event entitlement. The clause language does not support that reduction. Each compensation event stands on its own assessment against planned completion at the dividing date.
What does reduce entitlement is a failure to react competently and promptly under clause 63.8. If the contractor had the ability to mitigate the compensation event by re-sequencing work or accelerating, and failed to do so, the assessment can be reduced to reflect the mitigation that should have occurred. This is distinct from concurrent delay and is worth understanding as a separate risk.
What "reacts competently and promptly" actually requires
Clause 63.8 is short, almost casual, and carries more commercial weight than most contractors realise. The assessment of a compensation event is made on the basis that the contractor reacts competently and promptly to the event. This means the assessment assumes the contractor did what a competent contractor would do to mitigate the delay, whether or not the contractor actually did so.
If the compensation event could have been partially mitigated by bringing in an additional shift, re-sequencing a downstream activity, or accelerating a non-critical path, the assessment assumes that mitigation happened. If the contractor did not mitigate, the assessment can be reduced to reflect what the entitlement would have been if mitigation had taken place.
This creates an obligation that is not always understood. The contractor is not entitled to sit back and let a compensation event run its full course when reasonable mitigation was available. The accepted programme should show the mitigation assumed in the assessment, and the contractor should have a clear record of what mitigation was considered and either implemented or dismissed with reasons.
For contractors, the practical implication is that compensation event quotations should include a brief explanation of mitigation considered. If mitigation was not possible, the quotation should explain why. If mitigation was implemented, the quotation should show the residual delay after mitigation. This protects the contractor against later assessment reducing the entitlement on the basis of mitigation that should have occurred.
For project managers, the implication is that competent mitigation is an expectation, not a favour. The contract builds it into the assessment mechanism. A PM who accepts a quotation that shows full delay without any mitigation analysis is likely accepting an inflated assessment.
The most common delay analysis mistakes
Across the NEC projects that end in dispute, a handful of delay analysis mistakes account for most of the value at stake.
Late notification is the most common and the most expensive. Compensation events notified outside the eight-week window under clause 61.3 can lose entitlement entirely. Contractors who treat compensation event notification as something to deal with when there is time typically miss events, and the ones missed can be the ones that mattered most.
Using the wrong accepted programme is the second. Compensation event assessments built against the wrong baseline, typically a more recent programme than the one at the dividing date, produce weaker entitlement because progress already lost to the event is built into the starting position. The baseline should always be the accepted programme at the dividing date, not the current programme at the time of quotation.
Aggregating compensation events is the third. Contractors sometimes try to combine multiple compensation events into a single delay analysis covering a period of the project. This is not what the contract requires and typically weakens the contractor's position. Each compensation event has its own dividing date, its own accepted programme, and its own assessment. Aggregated analysis loses the event-by-event clarity that the contract is designed around.
Missing the terminal float mechanism is the fourth. Contractors assessing delay against the completion date rather than planned completion underuse the terminal float protection the contract provides. The completion date moves only to the extent planned completion is delayed, which preserves any terminal float the contractor built into the programme. Analysis that skips this step gives away float that belongs to the contractor.
Skipping mitigation analysis is the fifth. Quotations that show full delay without addressing clause 63.8 are vulnerable to reduction at assessment. Even a brief statement of why mitigation was not possible, or what residual delay remains after mitigation, materially strengthens the quotation.
The common thread across all five mistakes is that they flow from treating NEC delay analysis like JCT delay analysis. JCT is retrospective, claim-based, and tolerant of late submissions. NEC is prospective, event-based, and punitive about late submissions. Contractors who adapt their working practice to the NEC model make far fewer of these mistakes.
What good NEC delay practice looks like
The contractors who run NEC projects well, recover time entitlement cleanly, and settle compensation events quickly are not the ones with the most sophisticated delay analysis software. They are the ones whose practical working rhythm is built around the contract.
Early warning notification is routine and low-threshold. Clause 15 (clause 16 in NEC3) requires both parties to notify events that could affect time, cost, or quality. Contractors who use early warnings generously, as a matter of course rather than as an escalation, set the conditions for proper compensation event management later.
Compensation event notification happens promptly. Internal processes catch events as they occur, and notifications are issued within days, not weeks. The eight-week time bar under clause 61.3 is never the operative constraint.
The accepted programme is captured at every dividing date. When a compensation event is notified, the contractor records the accepted programme at that moment and preserves it as the baseline for that event's assessment. Subsequent events have their own captured baselines. The programme the contractor updates for ongoing reporting is separate from the baselines preserved for specific compensation events.
Quotations are produced within the three-week period under clause 62.3. Extensions are requested where necessary, but the default is to produce within time. Quotations include the impact programme built against the captured baseline, a brief narrative of causation, and a mitigation statement addressing clause 63.8.
Records are maintained contemporaneously. Delivery notes, timesheets, photographs, meeting notes, and correspondence are filed against the compensation event they relate to, so that if the assessment is ever challenged, the contemporaneous record supports the prospective analysis.
None of this is expensive or complicated in isolation. It is a discipline. The contractors who apply it protect their time entitlement. The contractors who do not lose it.
For specialist contractors without a dedicated planning function, specialist contractor planning support is designed specifically to maintain this discipline throughout the project, at a cost that is small relative to the commercial exposure created by a single poorly-handled compensation event.
NEC delay analysis and extension of time: the argument in short
NEC delay analysis and extension of time is not a specialised version of JCT delay analysis. It is a different mechanism, designed around different assumptions, and rewarding different contractor behaviour.
Under NEC, time is not claimed retrospectively through a consolidated extension of time application. It is built prospectively, one compensation event at a time, through the machinery of clause 62 and the assessment rule in clause 63.5. The accepted programme at each dividing date is the commercial anchor. The terminal float belongs to the contractor. The mitigation expectation is built into the assessment. The eight-week time bar is strict.
Contractors who understand this and build their working rhythm around it recover time entitlement cleanly throughout the project. Contractors who do not find themselves in a difficult position when delay accumulates, producing retrospective analysis the contract was never designed to support, from a baseline that has long since drifted from the job.
The discipline required is not large. A routine of prompt notification, captured baselines at each dividing date, quotations produced within time, and mitigation analysis included in every assessment. The commercial protection that discipline provides is the difference between recovering what the contract allows and fighting for a fraction of it from a weak position.
FAQ
What is the difference between extension of time under NEC and JCT?
Under JCT, extension of time is a separate mechanism. The contractor applies for an extension against the completion date when a Relevant Event causes delay, and the contract administrator assesses the application retrospectively. Under NEC, extension of time is not a separate mechanism. Time entitlement flows from compensation events, is assessed prospectively against planned completion at the dividing date, and is calculated event by event through the compensation event machinery. The completion date moves only by the amount planned completion is delayed, which preserves terminal float for the contractor.
What is planned completion under NEC?
Planned completion is the contractor's forecast of when the works will actually finish, as shown on the accepted programme. It is distinct from the completion date, which is the contractual obligation. The gap between planned completion and the completion date is terminal float, which belongs to the contractor. NEC delay assessments measure the effect of a compensation event on planned completion, not the completion date, and the completion date is adjusted by the same amount planned completion moves.
What is the dividing date and why does it matter for delay analysis?
The dividing date is the date fixed by clause 63.1 that determines the accepted programme snapshot used for assessing a compensation event and the line between actual and forecast cost. For contractor-notified events, the dividing date is the date of notification. For PM-notified events, it is the date of the instruction or event. The accepted programme at the dividing date is the baseline against which time impact is measured. Using a different programme, particularly a more recent one, weakens the contractor's position because progress already lost to the event is built into the starting point.
Can a compensation event be time-barred under NEC?
Yes, under clause 61.3 of NEC4 (and equivalent under NEC3). If a compensation event is one the contractor should have notified, and the contractor fails to notify within eight weeks of becoming aware of the event, the contractor loses entitlement to changes to the prices, completion date and key dates. Events that the project manager is required to notify under clause 61.1 are not time-barred on the contractor. The eight-week time bar is one of the most strictly enforced provisions in NEC and one of the most common causes of lost time entitlement.
How is concurrent delay treated under NEC?
NEC does not treat concurrent delay the way JCT does. Each compensation event is assessed against its own dividing date and accepted programme, without deducting concurrent contractor-caused delay from the entitlement. A compensation event that delays planned completion by three weeks produces three weeks of entitlement even if a contractor-caused delay would have delayed the works by two weeks anyway. The contractor-caused delay is dealt with separately, not by reducing the compensation event assessment. This is generally more favourable to contractors than the equivalent JCT treatment.
What does "reacts competently and promptly" mean under clause 63.8?
Clause 63.8 (clause 63.6 in NEC3) provides that compensation event assessments are made on the basis that the contractor reacts competently and promptly to the event. This means the assessment assumes reasonable mitigation occurred, whether or not it actually did. If the contractor could have mitigated the delay by re-sequencing, accelerating a non-critical path, or adding resource, the assessment can be reduced to reflect the mitigation that should have taken place. Contractors should include mitigation analysis in their quotations to avoid reductions at assessment.
What happens if the accepted programme is out of date when a compensation event is notified?
The contractor's position is significantly weakened. The compensation event is supposed to be assessed against the accepted programme at the dividing date. If that programme is months out of date and does not reflect progress or prior compensation events, the assessment cannot be done properly. The project manager has grounds to make their own assessment under clause 64, which typically produces a lower entitlement. The practical remedy is to keep the accepted programme current throughout the project, with revisions issued at the frequency stated in the contract data under clause 32. The pillar article on NEC clause 31 programme acceptance covers the maintenance mechanism in detail.
Should NEC delay analysis be prospective or retrospective?
The contract intends prospective analysis: each compensation event is assessed at the time it occurs, using the accepted programme at the dividing date. In practice, many assessments are done retrospectively because notifications and quotations are delayed. Adjudicators generally prefer prospective analysis on NEC projects, consistent with the contract's design, but they will use retrospective analysis where the prospective record has degraded. Contractors who maintain current programmes and notify events promptly get prospective analysis, which tends to favour their position. Contractors who do not tend to get retrospective analysis, which tends to reduce their entitlement.
Need support with NEC delay analysis on a live project?
If compensation events are accumulating without proper assessment, if the accepted programme has drifted from the live job, or if a delay analysis needs to be produced for a CE quotation or a dispute, specialist NEC programme support can keep the analysis prospective and the entitlement defensible.
Comments