NEC Clause 60 Compensation Events: How the Mechanism Works and Where It Fails
The compensation event mechanism is the commercial heart of NEC contracts. It is the system through which the Contractor recovers time and cost for events that are not at the Contractor's risk under the contract. Everything about how NEC projects perform commercially, from programme management to cash flow to dispute frequency, flows through Clause 60. A QS who understands the mechanism fully, and who reviews it carefully at tender stage and manages it actively on the live project, is in a fundamentally stronger commercial position than one who treats it as an administrative process.
This guide covers what Clause 60 requires, why the exhaustive list structure is commercially significant, how the eight-week notification deadline operates as a condition precedent, and how Z clauses remove entitlements that the standard form provides.
What Clause 60 Requires
Clause 60 of the NEC4 Engineering and Construction Contract defines the events that constitute compensation events. A compensation event is an event that entitles the Contractor to an adjustment to the Prices and the Completion Date, or both, depending on its effect.
The mechanism works as follows. When a compensation event occurs, either the Project Manager notifies the Contractor under Clause 61.1, or the Contractor notifies the Project Manager under Clause 61.3. The Contractor then submits a quotation under Clause 62, setting out the proposed adjustment to the Prices and the Completion Date. The Project Manager either accepts the quotation, instructs a revised quotation, or makes their own assessment under Clause 64. The agreed or assessed quotation then becomes the adjustment to the contract.
The critical feature of this mechanism, compared to the FIDIC claims procedure, is that it is forward-looking in design. NEC expects compensation events to be identified and assessed as close as possible to the time the event occurs, using forecasts of cost and time impact rather than retrospective records of what actually happened. Clause 63 requires the assessment to be based on the assumptions that the Contractor reacts competently and promptly, and that any Employer risk event that has already occurred is taken into account at the time of assessment.
This design principle has commercial consequences. A Contractor who notifies compensation events promptly, submits quotations based on reasonable forecasts, and manages the Clause 62 and 64 assessment procedure actively will realise time and cost recovery close to the time the events occur. A Contractor who allows compensation events to accumulate, delays notification, or fails to follow the procedure will find that retrospective recovery is limited by the condition precedent nature of the notification requirement and by the difficulty of retrospective programme analysis.
The Exhaustive List Under Clause 60.1
The most commercially significant feature of Clause 60 is that the list of qualifying compensation events in Clause 60.1 is exhaustive. Unlike FIDIC, where the Contractor has broader entitlements to claim under multiple provisions, NEC provides that only the events listed in Clause 60.1 give rise to compensation event entitlement. If an event occurs that causes delay or cost but does not fall within any of the Clause 60.1 categories, and has not been added by a Z clause, there is no compensation event and no entitlement to a Prices or Completion Date adjustment.
The events listed in Clause 60.1 of NEC4 include the following categories, among others.
The Project Manager gives an instruction that changes the Scope. This is the primary variation mechanism: any instruction that changes what the Contractor is required to do is a variation. The instruction triggers the quotation and assessment procedure under Clauses 62 and 64.
The Employer does not allow the Contractor access to part of the Site by the access date stated in the Contract Data. Access dates are part of the programme and the contract data. Failure to provide access on time is a compensation event that affects both time and cost.
The Project Manager does not reply to a communication within the period required by the contract. This category exists because NEC is designed to operate through active Project Manager engagement. Failure to respond is treated as a compensation event because it prevents the Contractor from proceeding with informed agreement.
A physical condition is encountered that an experienced Contractor would have judged as having a sufficiently low probability of occurring that it would not have been allowed for. This is the ground conditions compensation event, which is one of the most commercially significant provisions on civil engineering and infrastructure projects. It transfers the risk of genuinely unforeseeable ground conditions from the Contractor to the Employer.
Weather measurement recorded within a stated interval is more adverse than the weather data included in the Contract Data. The weather compensation event is calibrated against the agreed weather data, not against actual historical records. Events that exceed the Contract Data reference are compensation events; events within the reference are at the Contractor's risk.
The Project Manager or Supervisor gives an instruction or changes a decision when neither is required by the contract. This category prevents the Project Manager from directing the Contractor's activities outside the contract's instruction mechanism without triggering a compensation event.
The Scope is found to contain an ambiguity or inconsistency and the Project Manager gives an instruction to resolve it. Where the Scope is ambiguous, the risk of that ambiguity sits with the Employer: resolving it is a compensation event.
These are not the complete list: Clause 60.1 includes further categories, and the active management of which events fall within each category is a live commercial question on most NEC projects.
How the 8-Week Notification Deadline Works
Clause 61.3 provides that if the Contractor does not notify a compensation event within eight weeks of becoming aware of the event, the Contractor is not entitled to a change in the Prices or Completion Date arising from that event. This is a condition precedent. The legal consequence of missing the eight-week deadline is the loss of entitlement, regardless of whether the underlying compensation event was genuine and regardless of the quantum of the time or cost impact.
The eight-week clock starts when the Contractor becomes aware of the event, not when the impact becomes fully visible. A Project Manager instruction issued in week one of the project may cause delay that does not manifest as a programme impact until week ten. The eight-week notification clock started in week one, when the instruction was given. A Contractor who waits until the impact is visible before notifying has missed the deadline on the instruction itself, even if the delay impact is only apparent later.
This timing structure creates a management requirement that is different from FIDIC. Under FIDIC Clause 20, the notice clock runs from awareness of the event, typically the instruction or the occurrence of the condition. Under NEC Clause 61.3, the same principle applies. The practical implication is that the commercial team must track instructions, access failures, weather exceedances, and ground condition encounters contemporaneously, and must notify each one within eight weeks, rather than accumulating events and notifying them in batches.
The Project Manager also has an obligation under Clause 61.1 to notify compensation events that arise from their own instructions or actions. If the Project Manager fails to notify an event that is a compensation event, and the Contractor also fails to notify within eight weeks, the Contractor loses the entitlement. Both parties carry a responsibility for timely identification and notification.
Clause 61.4 provides that if the Project Manager decides that an event notified by the Contractor is not a compensation event, the Project Manager notifies the Contractor accordingly. The Contractor can challenge that decision, but the notification timeline continues to run from the original event, not from the Project Manager's rejection. A Contractor who notifies within eight weeks and then disputes the Project Manager's rejection is in a defensible position. A Contractor who misses the eight-week window and then argues that the event should have been notified by the Project Manager is in a much weaker one.
How Z Clauses Modify the Compensation Event List
Z clauses are Employer-drafted additions and amendments to the standard NEC conditions. They are the primary mechanism through which the risk allocation of the standard Clause 60.1 list is changed. The commercial significance of Z clause modifications to Clause 60 is high: removing a Clause 60.1 event transfers the risk of that event category entirely to the Contractor, with no compensation event entitlement and no Prices or Completion Date adjustment if the event occurs.
The most commercially significant Z clause modification in practice is the removal of the physical conditions event. On contracts where the Employer removes this event from the Clause 60.1 list, the Contractor bears the full risk of unforeseeable ground conditions, regardless of how adverse they are or how low the probability of encountering them was at the time of tender. On civil engineering, infrastructure, and remediation projects where ground conditions carry material uncertainty, this removal is one of the most significant risk transfer mechanisms in the contract.
The second most common removal is the weather compensation event. Removing this event places all weather risk on the Contractor, including weather that genuinely exceeds the historical reference data in the Contract Data. On projects with exposed sites or long programme durations, this removal can represent a material unpriced risk if it is not identified at tender.
Z clauses also sometimes restrict the Project Manager communication event, which covers the compensation event arising from the Project Manager's failure to reply within the required period. Restricting or removing this event reduces the commercial consequence of Project Manager delay in responding to Contractor submissions.
Other Z clause modifications include: adding notification conditions that go beyond the eight-week requirement, such as requiring the notice to include preliminary cost and time estimates; narrowing the scope of what counts as a change to the Scope under Clause 60.1(1); and introducing requirements for Contractor consent before certain categories of event can be treated as compensation events.
For a detailed treatment of Z clause risk patterns across NEC contracts, including how AI identifies Z clause modifications and their downstream effect on the compensation event mechanism, see the guide to NEC contract review and how AI spots hidden risk.
How AI Reviews NEC Clause 60 Modifications
AI review of Clause 60 identifies every modification to the standard compensation event list and the notification procedure, and explains the commercial consequence of each modification.
For Z clause modifications to the Clause 60.1 list, AI identifies which events have been removed or restricted, and which events have been added. The analysis confirms what risk categories remain at the Employer's risk under the modified contract, and which categories have been transferred to the Contractor by Z clause amendment.
For the notification procedure, AI identifies any Z clause modifications to the eight-week period, any additional notification requirements, and any conditions imposed on the content of compensation event notifications. It flags provisions that could make it easier for the Project Manager to reject a notification on procedural grounds, increasing the risk that a legitimate compensation event entitlement is lost.
AI also reads the compensation event provisions alongside the programme provisions to assess the interaction between Key Dates and the compensation event mechanism. Where the contract includes Key Dates with separate liability under Clause 25.3, and the compensation event list has been restricted by Z clauses, the Contractor's ability to claim for events that delay Key Dates is more limited than the standard form would provide.
For the complete framework of how AI handles NEC, FIDIC, JCT, and AIA contract review from initial upload to structured risk report, see the complete guide to AI construction contract review.
Frequently Asked Questions
What are NEC Clause 60 compensation events?
Compensation events under NEC Clause 60 are the events that entitle the Contractor to an adjustment to the Prices, the Completion Date, or both. The list in Clause 60.1 is exhaustive: only the events on that list give rise to compensation event entitlement. Key categories include Project Manager instructions changing the Scope, Employer failure to provide access by the access date, Project Manager failure to reply to communications within the required period, unforeseeable physical conditions, adverse weather beyond the Contract Data reference, and ambiguity or inconsistency in the Scope. If an event occurs that does not fall within Clause 60.1, and has not been added by a Z clause, there is no compensation event and no entitlement to time or cost recovery.
What is the notification deadline for NEC compensation events?
Under Clause 61.3, the Contractor must notify a compensation event within eight weeks of becoming aware of the event. This is a condition precedent: failure to notify within eight weeks extinguishes the entitlement to a Prices or Completion Date adjustment, regardless of whether the underlying event was a genuine compensation event. The eight-week clock runs from awareness of the event, not from when the impact becomes quantifiable. The Project Manager has a parallel obligation under Clause 61.1 to notify events arising from their own instructions.
Can Z clauses remove NEC compensation events?
Yes. Z clauses are Employer-drafted amendments to the NEC conditions and can remove specific events from the Clause 60.1 list. The most commonly removed events are the physical conditions event and the weather event. Removing the physical conditions event transfers the full risk of unforeseeable ground conditions to the Contractor. Removing the weather event places all weather risk on the Contractor regardless of how adverse conditions are compared to the Contract Data reference. Both removals are common on public sector infrastructure contracts and should be identified and commercially assessed before signing.
What is the difference between NEC3 and NEC4 compensation events?
The structure of Clause 60 is similar across NEC3 and NEC4, but there are differences in the specific events listed and in the drafting of the notification and assessment procedures. NEC4 tightened some of the compensation event assessment procedures under Clauses 62 to 65, and updated the programme provisions under Clauses 31 and 32 in ways that affect how compensation event time impacts are assessed against the Accepted Programme. The fundamental principle, an exhaustive list with an eight-week condition precedent notification requirement, is the same in both editions. Confirming which edition applies is the first step in any NEC contract review, because the specific clause references and drafting differences between editions matter when managing the compensation event procedure on a live project.
What happens if the Project Manager rejects a compensation event notification?
Under Clause 61.4, if the Project Manager decides that the notified event is not a compensation event, the Project Manager notifies the Contractor of that decision. The Contractor can challenge the decision through the dispute resolution procedure: under NEC4, this means the Senior Representative tier and then adjudication. The notification timeline continues to run from the original event: the Contractor's position is protected by having given notice within eight weeks, and the dispute is about whether the event qualifies, not about whether notice was given in time. A Contractor who misses the eight-week window and then argues that the Project Manager should have notified the event under Clause 61.1 is in a weaker position, because the Contractor's own eight-week obligation is not removed by the Project Manager's failure to notify.
Lexilio is the construction commercial intelligence platform for FIDIC, NEC, JCT, and AIA contracts.
