Planning advice for contractors

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 window, its own assessment, and its own clause 64 vulnerability. Most contractors run one of these processes diligently and the other partially or not at all.

NEC did not arrive fully formed. It evolved as a deliberate response to the failures of the contracts that preceded it, and every clause in the current NEC4 suite carries the imprint of a specific problem that JCT and ICE could not solve. The history is not background to contemporary NEC practice. It is the explanation of why the controls matter, what the contract was designed to prevent, and how contractors who understand the evolution administer the contract more effectivel

Every contractor running an NEC4 contract loses some compensation event entitlement that the contract would otherwise have delivered. The amount lost is not random. It is the predictable consequence of seven specific failure modes that recur across contractor types, contract sizes and sectors. Each is preventable through operational discipline.