Managing subcontractor delay under NEC4: why every supply chain slip is two delays at once
- Feb 3
- 14 min read
Updated: 3 days ago
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
A specialist M&E subcontractor on a major utilities project misses a key date. The main contractor's commercial team logs the delay against the subcontract, issues the appropriate notices to the subcontractor under the subcontract terms, and begins building the recovery position. Three weeks later, the project manager on the head contract asks the main contractor what is being done about the delay to the upstream programme. The commercial team is taken by surprise. They have been managing the subcontract delay diligently. They have not been managing the head contract delay at all, because they did not see it as a separate event.
By the time the question is asked, the eight-week notification period under clause 61.3 of the head contract has nearly expired. The main contractor scrambles to issue a compensation event notification, but the supporting analysis takes weeks to assemble. The project manager challenges the dividing date and the link between the subcontract event and the head contract impact. The eventual entitlement is significantly less than the head contract delay would have justified if the position had been established cleanly from the start.
This pattern is one of the most damaging on NEC4 projects, and it produces a category of avoidable loss that the contractor's commercial team rarely recognises until it has happened. The cause is a structural misunderstanding that runs through the industry: contractors treat subcontractor delay as a single event with one set of consequences, when on NEC4 it is always two events running on parallel tracks.
The subcontract delay and the head contract delay are not the same thing. They have different dividing dates. They are governed by different contracts, often with materially different provisions. They produce different evidence requirements, different commercial outcomes, and different procedural risks. Most importantly, they require simultaneous administration. A contractor who runs only the subcontract process is procedurally exposed on the head contract. A contractor who runs only the head contract process loses commercial pressure on the subcontractor. The strongest contractors run both processes in parallel from the moment a delay is identified, with each process feeding evidence to the other.
This article explains why every subcontractor delay on an NEC4 project is two delays at once, what each process requires, where most contractors fail, and how to design the dual-track administration that protects both commercial positions. It is written for main contractors who recognise that subcontractor delay is not just a supply chain problem but a structural NEC4 administration challenge.
The two clocks: why the events are genuinely separate
When a subcontractor misses a key date, two contractual events have occurred. The first is a delay under the subcontract: the subcontractor has failed to meet a contractual obligation, and the main contractor has rights and procedural duties under the subcontract terms. The second is a delay under the head contract: the main contractor's ability to meet a head contract obligation has been compromised, and the main contractor must now decide whether the delay constitutes a compensation event under the head contract.
These two events are linked causally but separated procedurally. The cause of the head contract delay is the subcontract delay, but the head contract event has its own dividing date, its own notification requirements, its own quotation process, and its own assessment under clauses 63.1 to 63.10. The fact that the underlying cause is supply chain failure does not collapse the two events into one. Each runs on its own clock.
This produces several practical consequences that contractors must understand.
The dividing dates are different. The subcontract delay's dividing date is the date the subcontractor's obligation was missed or the date the relevant event occurred under the subcontract. The head contract delay's dividing date is the date the main contractor became aware that the works under the head contract would be affected, which under clause 61.3 starts the eight-week notification clock. These dates can differ by days, weeks, or in some cases months, depending on when awareness crystallised at the head contract level.
The notification obligations are different. The main contractor must notify the subcontractor under the subcontract within the subcontract's notification provisions, which vary by contract type and bespoke amendment. The main contractor must also notify the project manager under the head contract within eight weeks of the head contract awareness date. Missing either notification has consequences. Missing the head contract notification under clause 61.3 forfeits entitlement entirely on the head contract event, regardless of what is happening under the subcontract. The article on the NEC4 compensation event time bar covers the eight-week mechanism in detail.
The evidence requirements are different. The subcontract event requires evidence of the subcontractor's failure: missed milestones, communication trails, performance reports. The head contract event requires evidence of the impact on the head contract works: programme effects, mitigation considered, the cause-and-effect chain from the supply chain failure to the impact on planned completion. Some evidence overlaps. Much of it does not.
The commercial outcomes are different. The subcontract event produces remedies under the subcontract: damages, set-off, accelerated performance, ultimately termination. The head contract event produces remedies under the head contract: time extensions, cost adjustments, key date movements. The subcontract recovery and the head contract entitlement are independent positions. Recovering well under one does not guarantee recovering under the other.
This is the structural insight. Two events. Two clocks. Two evidence sets. Two commercial outcomes. Most contractors run one of these processes well and the other partially or not at all. The cumulative consequence over the life of a multi-year project is significant.
Why the dual-track problem is invisible to most contractors
The reason most contractors run only one process well is organisational, not technical. Most main contractors administer subcontracts through the commercial and procurement teams and administer head contracts through the project management and planning teams. The two functions sit in different reporting lines, attend different meetings, and use different systems.
When a subcontractor delay is identified, the immediate response is administered through the subcontract team. They issue the notices, log the failure, begin the recovery conversation. From their perspective, the matter is in hand. They are doing their job. The information reaches the head contract team eventually, often through a weekly progress meeting or a project director's report, but by then the head contract notification clock has already been running for days or weeks.
The head contract team, in turn, often assumes that subcontract management is a commercial issue rather than a head contract administration issue. They wait for the subcontract team to advise on the impact. By the time advice is received, the impact has been thought about from a subcontract recovery perspective rather than a head contract entitlement perspective, and the head contract notification window is uncomfortably narrow.
This handover gap is where most of the commercial loss occurs. Neither team is doing anything wrong individually. The dual-track requirement is invisible because the contract structure is invisible: the procedural separation between subcontract and head contract events is not signposted in either the subcontract documentation or the head contract documentation. It only becomes visible at the boundary between them, which is precisely where most contractors do not have an established process.
Recognising the dual-track requirement is the first structural fix. Once the project team accepts that every subcontractor delay produces two events, the rest of the discipline becomes operational. The article on NEC clause 32 programme revision covers the revision discipline that supports the head contract side of the dual-track approach.
What the head contract process requires
Once the dual-track recognition is in place, the head contract process needs to run on its own merit, not as an afterthought to the subcontract process.
Notification under clause 61.3 within eight weeks. The eight-week clock starts when the main contractor becomes aware that the works under the head contract are affected. This may be the same date as the subcontract awareness, but it may be later. What matters is when the main contractor identifies the consequence at the head contract level. The notification should be issued to the project manager as a separate, formal document, clearly identified as a clause 61.3 notification, with the relevant facts and an indication of the supporting analysis to follow. The notification does not need to contain a full quotation. It needs to be timely, formal, and explicit.
Programme integration. The subcontract delay must be visible in the head contract accepted programme as soon as it is identified. The compensation event fragnet showing the impact follows the principles covered in how to structure a time impact assessment under NEC4: dividing date stated, accepted programme version identified, fragnet built in isolation, impacted programme calculated, narrative explaining the cause-and-effect chain.
Mitigation that satisfies clause 63.8. The head contract assessment assumes the contractor reacts competently and promptly to any compensation event. For supply chain events, this means the main contractor has considered re-sequencing, parallel working, alternative suppliers, and any other reasonable mitigation that does not require additional cost. The mitigation statement in the quotation should describe what was considered, what was implemented, and what residual delay remains. The article on NEC programme acceleration and mitigation covers the mitigation discipline in detail.
Evidence pack designed for head contract review. The supporting evidence for the head contract event is not the same as the supporting evidence for the subcontract recovery. Head contract evidence focuses on the cause-and-effect chain at the head contract level: how the subcontract failure flowed into the works, when the impact materialised, what the main contractor did to address it. The subcontract evidence (missed milestones, performance reports, internal recovery correspondence) is supporting context, not the primary record.
Decision-ready quotation under clause 62. The quotation submitted under clause 62.2 should be acceptance-optimised in the way described in how to get NEC4 compensation event quotations agreed: cover page, assumptions register, time impact, cost build-up, evidence index, decision request. The quality of this quotation determines whether the head contract entitlement is recovered or transferred to project manager assessment under clause 64.
These five elements run independently of the subcontract process. They produce a complete head contract record that can stand on its own merits, regardless of how the subcontract recovery proceeds.
What the subcontract process requires
The subcontract process runs on its own track but feeds the head contract record at specific points. The detail of subcontract administration depends on the form of subcontract used, but the principles apply across NEC subcontracts and bespoke supply chain agreements.
Notification under the subcontract terms. Most NEC subcontracts include their own notification provisions, often mirroring the head contract eight-week period. Bespoke supply chain agreements vary widely. The main contractor must understand the specific provisions and notify the subcontractor in line with them, regardless of what is happening on the head contract side.
Recovery position established early. The subcontract recovery position is the main contractor's commercial pressure point with the subcontractor. It includes the right to set off costs, the right to instruct acceleration at the subcontractor's expense, the right to engage alternative suppliers, and ultimately the right to terminate. Establishing this position early creates options that disappear if the subcontractor is allowed to proceed without consequence.
Subcontract programme alignment. The subcontract micro-programme should be logic-linked to the head contract programme at the relevant interfaces. Without this linkage, the subcontract's own programme reporting tells a different story from the head contract programme, and the main contractor cannot demonstrate the cause-and-effect chain at either level.
Evidence retention for two purposes. The subcontract evidence (missed milestones, performance issues, recovery correspondence) supports the subcontract recovery directly. It also feeds the head contract evidence pack as supporting context. The same documents serve both purposes, but they need to be filed in a way that allows them to be used for both. A document filed only in the subcontract folder may not be retrievable when the head contract process needs it.
Recovery actions reflected in the head contract programme. When the main contractor implements recovery actions (additional resources, accelerated programme, alternative suppliers), these actions affect the head contract programme as well as the subcontract programme. The head contract programme should reflect the recovery actions as they are implemented, with the corresponding mitigation visible in the next clause 32 revision.
Where the dual tracks intersect: five operational disciplines
Running both processes in parallel requires specific operational disciplines that connect them at key points without collapsing them into one. Five disciplines protect both positions.
Single source of truth for awareness dates. When a delay is identified, the awareness date for both the subcontract event and the head contract event is logged in a shared register accessible to both teams. The subcontract team and the head contract team work from the same record of when the issue surfaced. This eliminates the most common cause of head contract notification failures.
Cross-team notification protocol. Within 48 hours of any subcontract delay being identified, a structured handover occurs between the subcontract team and the head contract team. The handover covers the awareness date, the nature of the delay, the immediate impact assessment, and the head contract notification clock. The head contract team takes ownership of the head contract event from this point.
Aligned programme reporting cadence. The subcontract micro-programme and the head contract programme update on the same data date. Subcontract progress feeds the head contract programme on the same cycle, ensuring the head contract programme always reflects current supply chain status. Without this alignment, the head contract programme drifts from reality and the compensation event assessment baseline becomes less reliable.
Joint evidence filing structure. Documents are filed in a way that supports both subcontract recovery and head contract assessment. A subcontract instruction is referenced in both the subcontract folder and the head contract evidence index, with cross-references that allow either team to find what they need quickly. The infrastructure cost is small; the procedural protection is significant.
Senior commercial oversight. A senior commercial manager owns the dual-track view across both processes. They review the position weekly, ensure both clocks are being managed, and intervene if either process is drifting. This role does not need to do the administrative work; it needs to maintain the structural awareness that is otherwise invisible.
These five disciplines are not technically demanding. They require organisational acceptance that the dual-track requirement exists and operational commitment to running both processes in parallel.
How the dual-track view changes the seven common pitfalls
Most articles on NEC subcontractor delay list pitfalls as individual operational failures: not modelling the subcontract logic, accepting "it's their problem" behaviour, blending causes, weak flow-down controls, optimistic programme behaviour, ineffective decision packs. These are real failures, but they are symptoms rather than causes. The underlying cause is the failure to recognise the dual-track structure of every subcontractor delay event under NEC4.
When the dual-track view is absent, the pitfalls are inevitable. The contractor models the subcontract scope as a single bar because they do not need detailed logic to manage the subcontract recovery, and they do not realise the head contract assessment requires that detailed logic. The contractor adopts an "it's their problem" posture because the head contract reasonable mitigation requirement is not visible to them. Causes get blended because the contractor is producing one delay narrative rather than two. Programme integrity slips because the head contract baseline is not being updated to reflect the dual-track position.
When the dual-track view is present, each of these failures becomes harder to commit. The subcontract logic is built in detail because the head contract assessment will use it. Recovery action is owned actively because clause 63.8 requires it for head contract entitlement. Causes stay separate because each event is being administered separately. Programme integrity is maintained because the head contract programme update is a procedural requirement.
The dual-track reframing therefore does not just add a discipline; it eliminates a category of failure that would otherwise be impossible to fully resolve through tactical fixes.
The bottom line
Every subcontractor delay on an NEC4 project is two delays at once. The subcontract event runs on its own clock with its own notification requirements, evidence, and commercial outcomes. The head contract event runs on a parallel clock with its own clause 61.3 notification window, its own clause 63 assessment, and its own clause 64 vulnerability. The two events are causally linked but procedurally separate.
Most contractors run only one of these processes. The subcontract event is administered through commercial and procurement functions. The head contract event is partially administered through project management, often after the head contract notification clock has already been running. The handover gap between the two functions is where most of the avoidable commercial loss occurs.
The dual-track view is the structural fix. Once the project team accepts that every subcontractor delay produces two events, the operational disciplines follow: shared awareness register, 48-hour cross-team handover, aligned programme reporting, joint evidence filing, senior commercial oversight. These are not technically demanding. They require organisational commitment to running both processes in parallel.
The pay-off compounds across the project. Head contract notifications are issued in time. Quotations are built on a current accepted programme baseline. Supporting evidence supports both subcontract recovery and head contract entitlement. Clause 64 vulnerability is reduced because the head contract process is not running on a half-administered basis. End-of-project commercial position reflects a complete record of properly handled events rather than a forensic reconstruction of partial records.
For contractors who recognise the pattern but do not yet have the dual-track discipline embedded, the structural fix is achievable in two to three months of intentional execution. The cost is modest. The benefit applies to every subcontractor delay event from the point the discipline is established, across the remaining duration of the project and into every future NEC4 project the contractor delivers.
FAQ
Why is every subcontractor delay two events under NEC4?
The subcontract delay and the head contract delay are causally linked but procedurally separate. The subcontract event has its own dividing date, notification requirements, and remedies under the subcontract. The head contract event has its own dividing date, clause 61.3 notification clock, and assessment under clauses 63.1 to 63.10. The fact that the cause is supply chain failure does not collapse the two events into one. Each runs on its own clock and requires its own administration.
What happens if the head contract notification under clause 61.3 is missed?
The main contractor's right to a change in the prices, the completion date, and any key date is forfeit on that head contract event, regardless of what is happening under the subcontract. The forfeiture is binary, not proportionate. A successful subcontract recovery does not compensate for a missed head contract notification. The article on the NEC4 compensation event time bar covers the eight-week mechanism in full.
How does the dual-track approach affect mitigation?
Under clause 63.8, the head contract assessment assumes the main contractor reacts competently and promptly. For supply chain events, this means considering re-sequencing, parallel working, alternative suppliers, and other reasonable mitigation. The subcontract recovery (instructing the subcontractor to accelerate, engaging alternatives, exercising set-off rights) is part of that mitigation. Documenting both the subcontract recovery actions and their effect on the head contract programme is what protects the head contract entitlement against reduction under clause 63.8.
Can the same evidence support both the subcontract recovery and the head contract entitlement?
Partially. Subcontract evidence (missed milestones, performance reports, recovery correspondence) directly supports the subcontract recovery and provides supporting context for the head contract event. Head contract evidence (programme impact, mitigation considered, cause-and-effect chain) is mostly distinct. Filing structures need to support both purposes. A document filed only in the subcontract folder may not be retrievable when the head contract assessment needs it.
What is the single most important structural fix on dual-track administration?
The 48-hour cross-team handover. Within 48 hours of any subcontract delay being identified, a structured handover occurs between the subcontract team and the head contract team, covering the awareness date, the nature of the delay, the immediate impact, and the head contract notification clock. The head contract team takes ownership of the head contract event from this point. This single discipline closes the handover gap that produces most of the avoidable commercial loss on subcontractor delay events.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BSc in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
Subcontractor delays turning into head contract entitlement losses?
If supply chain slips are being notified to the subcontractor but the head contract clock is being missed, if compensation event quotations are being rejected because the cause-and-effect chain cannot be demonstrated, or if the handover gap between the subcontract team and the head contract team is producing avoidable losses, specialist NEC compensation event support runs the dual-track administration that protects entitlement on both sides.
