Standard forms
NEC: early warnings and compensation events
NEC manages forward and prices as it goes. Run well it is the most transparent delay machinery in mainstream contracting. Run late it is the least forgiving.
- Jurisdiction
- United Kingdom and international
- Law and editions as at
- 3 August 2026
- Last reviewed
- 3 August 2026
- Editorial status
- Editorial draft, not yet independently reviewed
One mechanism, not two
A compensation event adjusts time and money together, assessed when it arises rather than argued at the end. The quotation prices the effect on cost, built from Defined Cost plus the Fee, and the effect on time, shown against the Accepted Programme.
The notification window
Contract text For events the contractor should have noticed, the standard NEC4 form gives a fixed period from becoming aware to notify the compensation event, drafted as a bar rather than a discretion. Both the money and the time for that event can be lost. The period is a favourite target of amendment, and the only number that matters is the one in the executed contract.
Early warnings are not notifications
The early warning is a management tool on a shared register, and it is separate from the compensation event process. Raising one does not notify a compensation event and does not stop the window running. Teams conflate them constantly and lose entitlements in perfectly good faith.
The link between them is subtler: failing to give an early warning that an experienced contractor could have given may mean the event is later assessed as if the warning had been given, which usually means assessed less generously.
The Accepted Programme
Every assessment is measured against the live, agreed picture of sequence, float and method that NEC expects to be updated and re-accepted throughout the job. A current programme makes delay measurable. A stale one weakens both parties at once, because there is nothing credible to measure against. Keeping it current is the precondition for the whole mechanism working.
Where it goes wrong
- The window treated as guidance in a form where it is a bar.
- Early warnings mistaken for notifications while the clock runs.
- Quotations built without programme evidence, inviting the Project Manager’s own assessment.
- An Accepted Programme months out of date when the largest event of the job lands.
Where the record comes in
Every mechanism on this page turns on evidence: what happened, what was known and when. A record built as the job happens is worth more than any argument assembled afterwards. Construction Metric keeps that record automatically, from the messages, photographs and voice notes a site team already sends.
Built by AI Metric
The analysis on this site is only as fast as the evidence behind it. AI Metric builds bespoke systems for consultancies, contractors and claims teams: document and correspondence triage, event registers assembled from the project record, programme and cost reconciliation, and drafting support that always cites the document it came from. Built for review by your own experts, never to replace their judgement.
Do not overread this page
NEC text is the copyright of its publisher and none is reproduced here. Z clauses routinely change the event list, the periods and the risk allocation.
General explanation of how contract mechanisms, analysis methods and legal principles generally work. It is not legal or contractual advice, not an opinion on any project, and no standard-form contract wording is reproduced anywhere on this site. Standard forms are routinely amended, so every default described here, including every time period, can be different on your project. Your executed contract, as amended, and the governing law and forum always control. Deadlines may already be running: if an event has occurred, preserve your position and take qualified advice.