Compensation Events in NEC Contracts: A QS Guide

Ask any quantity surveyor who has spent a year on an NEC4 contract what dominates their inbox, and the answer is almost always compensation events. Under the Engineering and Construction Contract, compensation events are the only mechanism through which the Prices, the Completion Date or a Key Date can change. There is no separate route for claims, no side letter for extensions of time — if it is not processed as a compensation event, it does not happen. That single fact makes compensation events NEC process the commercial engine room of every ECC project, and mastering it is one of the fastest ways a QS can build credibility on an NEC job. Whether you trained on JCT, on bespoke amended forms, or are newly qualified and meeting NEC4 for the first time, the compensation event mechanism is the one piece of the contract you cannot afford to misunderstand.

This guide sets out how compensation events actually work in practice: what qualifies as one under the clause 60.1 list, how notification and the notorious 8-week time bar operate, what a compliant quotation needs to contain, how the Project Manager assesses and implements a compensation event, and the pitfalls that repeatedly catch out QSs moving across from JCT or from less procedurally strict forms.

Compensation events reward discipline and punish drift. The contract runs on fixed periods measured in weeks, and missing one of them can be fatal to an otherwise strong claim regardless of how clearly the Contractor was affected. Understanding the timescales is therefore not an administrative nicety — it is the difference between a properly compensated change and an entitlement that evaporates on a technicality.

By the end of this guide you will understand the four-stage life cycle of a compensation event — notification, quotation, assessment, implementation — and have a working reference for the timescales that govern each stage, along with the practical habits that keep a QS in control of their compensation event log rather than permanently reacting to it.

What Is a Compensation Event, and Why Does NEC4 Handle It This Way?

The single route to changing price and time

Under a JCT contract, a QS might process an extension of time application, a loss and expense claim, and a variation instruction as three loosely connected strands of work. NEC4 folds all of that into one mechanism. If an event listed at clause 60.1 occurs, and it is not the Contractor's fault, it is dealt with as a compensation event — covering additional cost, delay to Completion, delay to a Key Date, or all three at once, assessed together in a single quotation. There is no other contractual route to more money or more time. If an event is not a compensation event and the Contractor has not been instructed to do something outside its obligations, the Contractor bears the cost and time consequences itself. This is a deliberate consolidation. By funnelling every cost and time consequence through one procedural gateway, NEC4 avoids the parallel, sometimes contradictory, processes that traditional forms can produce when a variation, a delay event and a loss and expense claim all arise from the same underlying cause.

Prospective, not retrospective, assessment

The second defining feature is timing. Traditional contracts often assess the cost and time effect of a change after it has happened, using actual records. NEC4 compensation events are assessed prospectively wherever possible — using forecasts of the effect on Defined Cost and the accepted programme as at the dividing date, not what actually occurred. This is a deliberate design choice: it forces both parties to agree the commercial consequences of a change close to when it happens, rather than reconstructing events months later from site diaries and disputed records. For a QS, it means compensation event quotations are built on realistic forecasting skill, not just historical cost extraction, and the two disciplines require different habits.

This prospective approach also explains why the early warning system under clause 15 sits so close to compensation events in practice. A well-run Early Warning Register flags a risk before it crystallises into a compensation event, giving both parties a chance to reduce its effect through a risk reduction meeting. Under clause 61.5, if the Project Manager decides the Contractor did not give an early warning that an experienced contractor could have given, the compensation event is assessed as if it had been given on time — which usually reduces what the Contractor recovers. Treating early warnings and compensation events as two ends of the same pipeline, rather than separate processes, is one of the clearest markers of a QS who has properly internalised how NEC4 is meant to work.

The Clause 60.1 List: What Actually Triggers a Compensation Event

Clause 60.1 sets out 21 compensation events in the base ECC, and understanding their shape matters more than memorising every sub-clause number. They fall broadly into three groups.

• Project Manager or Supervisor actions — instructions changing the Works Information or Scope, instructions to stop or not start work, additional tests or inspections that show no Defect, and failing to reply to a communication within the period required by the contract.
• Client, Project Manager or Supervisor failures — not giving access to the Site by the access date, not providing something the Client is to provide by the date shown in the Accepted Programme, a breach of contract by the Client not otherwise a compensation event, and the Client changing a decision it has previously communicated.
• Supervening events largely outside either party's control — physical conditions within the Site that an experienced contractor would have judged to have such a small chance of occurring that it would have been unreasonable to plan for them, and weather measurements recorded at the stated weather station that are worse than the one-in-ten-year values stated in the Contract Data.
• Other listed events — a Plant, Materials or intended method of working being changed by an instruction issued to comply with the health and safety requirements, the discovery of an object of historical or archaeological interest, and a change in the law of the country in which the Site is located, where Secondary Option X2 applies.

Reading clause 60.1 correctly

Two habits keep QSs out of trouble here. First, the Contract Data can add or remove events — a project may include additional Z clause compensation events, or the Client may have amended the standard list, so always check the Contract Data against the printed clause before assuming the standard 60.1 list applies unmodified. Second, several events depend on a comparison against a baseline the Contractor set at Contract Date — the Accepted Programme, the Contractor's assumed physical conditions, the stated weather data — so a QS building a compensation event case needs that original baseline evidence close at hand, not reconstructed after the fact.

Notification: The 8-Week Time Bar and Why It Is Absolute

Who notifies, and when

Where the Project Manager or Supervisor causes the event — for example, by issuing an instruction — the Project Manager notifies the Contractor of the compensation event under clause 61.1, generally at the same time as giving the instruction. Where the Contractor identifies an event the Project Manager has not notified, the Contractor must notify it under clause 61.3, and this is where the 8-week time bar bites: notification must happen within eight weeks of the Contractor becoming aware that the event has happened. Miss that window and, under clause 61.3, the Contractor loses its entitlement to a change in the Prices, the Completion Date or a Key Date — unless the Project Manager should have notified the event itself but did not.

"Becoming aware" is an objective test

The clock starts running from when a reasonable contractor, exercising reasonable diligence in the Contractor's position, would have known the event had happened — not from when someone happened to mention it in a progress meeting or a site diary note. A verbal reference is not a notification; clause 61.3 requires a separate, written communication that clearly identifies the matter as a compensation event. Because the time bar is binary rather than discretionary, the Project Manager has no scope to waive a late notification on the basis that the delay was minor or the Contractor's case looks strong — the entitlement is either preserved or it is gone.

Quotations: Building and Submitting a Compliant Assessment

Once the Project Manager confirms an event is a compensation event, or instructs the Contractor to submit quotations under clause 61.2, the Contractor has three weeks under clause 62.3 to provide one or more quotations, unless a longer period is agreed. A compliant quotation is not a single lump-sum figure — it must include proposed changes to the Prices, any delay to the Completion Date and any Key Dates, and, where the event affects the programme, a revised programme showing the effect. Clause 63 sets the assessment basis: changes to the Prices are assessed as the change in Defined Cost the Contractor forecasts will result, plus the applicable Fee percentage, using the shorter of the period to the next assessment date or the period the event affects.

A strong quotation is built the same way regardless of the underlying event: it links the cause clearly back to a clause 60.1 trigger, it shows the Defined Cost build-up by cost component rather than a single number, it demonstrates the time effect through a properly updated programme rather than an assertion, and it is submitted inside the three-week window or with an agreed extension recorded in writing. Quotations that arrive late, or that bundle several unrelated events into one submission, invite the Project Manager to reject them or fall back on its own assessment under clause 64 — which rarely favours the Contractor.

Project Manager Assessment and Implementation

When the PM makes its own assessment

Clause 64.1 gives the Project Manager the right to assess a compensation event itself in specific circumstances: if the Contractor has not submitted a quotation in time, if the Contractor's programme does not comply with the requirements of the contract, if the Project Manager considers the Contractor's forecast Defined Cost or time is not realistic, or if a first quotation has already been considered and rejected. A PM's own assessment tends to be more conservative than a well-supported Contractor quotation, since it is built on the Project Manager's own view of the compliant programme and Defined Cost rather than the Contractor's live cost records — another reason to submit clean, timely, well-evidenced quotations wherever possible.

Implementation changes the contract, not just the accounts

Once a compensation event is accepted or assessed, clause 65.2 makes the change effective: the Prices, the Completion Date and any Key Dates are changed, and this is treated as final unless the assessment is later shown to have been based on incorrect information available to the assessing party at the time. Because implementation also updates the Accepted Programme baseline going forward, every subsequent compensation event assessment is measured against a moving target — which is exactly why keeping the compensation event log and the programme reconciled to each other, event by event, matters so much more on NEC4 than on contracts where variations and delay are dealt with separately.

Where the compensation event affects more than one activity or cost centre, the Project Manager and Contractor should also agree how the assessment interacts with the existing target or activity schedule, since a compensation event that is assessed in isolation from the rest of the cost model can distort the pain/gain position on Option C and D contracts. Keeping a running reconciliation between implemented compensation events and the current forecast total of the Prices is good practice on every main option, not just the target-cost ones.

Common QS Pitfalls With Compensation Events

Most compensation event disputes on NEC4 projects trace back to a handful of recurring, avoidable mistakes rather than genuinely difficult points of interpretation. Recognising them early, and building them into a standard compensation event checklist, does more to protect a Contractor's entitlement than any amount of after-the-fact argument once a dispute has already crystallised.

• Treating the 8-week time bar as a soft deadline. Clause 61.3 is binary. Diarise the date of awareness the moment a potential event surfaces, not the date someone gets around to writing it up.
• Notifying verbally and assuming it counts. A comment in a progress meeting or an email that does not clearly flag the matter as a compensation event will not satisfy clause 61.3 if it is later challenged.
• Letting the Early Warning Register and the compensation event log run as separate systems. Under clause 61.5, a missed early warning can reduce what the Contractor recovers, so the two logs should always be read together.
• Submitting a single lump-sum figure instead of a proper Defined Cost build-up. Quotations without a transparent cost and time breakdown are far easier for a Project Manager to reject or replace with its own assessment.
• Missing the three-week quotation window without agreeing an extension in writing first. Clause 62.5 allows the period to be extended by agreement — but only if that agreement is actually recorded before the deadline passes.
• Failing to update the programme alongside the quotation. A time effect that is asserted but not demonstrated on a compliant, accepted programme rarely survives scrutiny.
• Losing track of deemed acceptance dates. When a Project Manager overruns its reply period, the quotation is deemed accepted under clause 62.6 — QSs who track these dates proactively can bank favourable outcomes that would otherwise be missed.

Frequently Asked Questions

What is a compensation event in an NEC contract?

A compensation event is an event listed at clause 60.1 of the NEC4 Engineering and Construction Contract that entitles the Contractor to a change in the Prices, the Completion Date, or a Key Date. It is the only mechanism under NEC4 for changing price or time — there is no separate claims or extension of time process.

How long does a Contractor have to notify a compensation event?

Under clause 61.3, the Contractor must notify the Project Manager within eight weeks of becoming aware that the event has happened. If the Contractor misses this window, it loses its entitlement to a change in the Prices, Completion Date or Key Dates, unless the Project Manager should have notified the event itself but did not.

What happens if the Project Manager does not respond to a compensation event quotation?

If the Project Manager does not respond within its two-week reply period under clause 62.6, the Contractor's quotation is treated as having been accepted. This deemed acceptance mechanism was introduced in NEC4 to keep both parties working to fixed timescales.

How long does the Contractor have to submit a compensation event quotation?

Under clause 62.3, the Contractor has three weeks from being instructed to submit a quotation, unless a longer period has been agreed with the Project Manager and recorded in writing. The quotation must cover changes to the Prices, the Completion Date, any Key Dates, and a revised programme where relevant.

Can a Project Manager assess a compensation event itself?

Yes. Under clause 64.1, the Project Manager can make its own assessment if the Contractor fails to submit a quotation in time, if the Contractor's programme does not comply with the contract, if the forecast Defined Cost or time is considered unrealistic, or after a first quotation has already been rejected.

What is the difference between an early warning and a compensation event?

An early warning under clause 15 flags a risk that could affect cost, time or performance before it has happened, giving both parties a chance to reduce its effect. A compensation event is the formal mechanism that actually changes the Prices and dates once a qualifying event under clause 60.1 has occurred. Failing to give an early warning that should have been given can reduce a related compensation event's assessment under clause 61.5.

Are weather and ground conditions always compensation events under NEC4?

Not automatically. Weather is only a compensation event if measurements recorded at the stated weather station are worse than the one-in-ten-year values stated in the Contract Data. Physical conditions are only a compensation event if an experienced contractor would have judged the chance of encountering them so small that planning for them would have been unreasonable, measured against the information in the Site Information.

Final Thoughts

Compensation events look intimidating on first encounter because NEC4 compresses claims, variations and extensions of time into one procedurally strict process rather than three looser ones. In practice, the discipline required is straightforward once it becomes habit: notify early, notify in writing, build quotations on a transparent Defined Cost and programme basis, and track every deadline as if it were absolute — because under clause 61.3 it is.

QSs who treat the compensation event log, the Early Warning Register and the Accepted Programme as three views of the same live risk picture, rather than three separate admin tasks, tend to spend far less time firefighting disputes and far more time managing the commercial position proactively. That shift in mindset, more than any single clause, is what separates confident NEC4 practice from a QS permanently one deadline behind.

Want the full picture? Want the full NEC4 picture?

This compensation events guide sits alongside our wider NEC coverage — read our NEC Contract Explained: A Beginner's Guide for QSs for the full suite context, and NEC vs JCT Contracts Explained if you are comparing forms before your next project starts.