Prevention: NEC's version of force majeure (clause 60.1(19))

What counts as a prevention event, why it is hard to prove, and how time and money are assessed when something outside both parties' control stops you.

Compensation events and change3 min read

On this page
  1. In plain English
  2. All four tests must be met
  3. Evidence
  4. Worked example
  5. How it is assessed
  6. What people get wrong
  7. Related guides

Prevention under clause 60.1(19) covers a rare event that was beyond both sides' control and so improbable at the Contract Date that pricing it would have been unreasonable for an experienced contractor, where it stops you finishing the works or finishing by the date on the Accepted Programme. It is NEC's answer to force majeure, with one big difference: it is priced, so you get time and money, not time alone.

It applies in NEC3 and NEC4. NEC4 specifies the whole of the works. Clause 19.1 separately covers the Project Manager's actions when it happens.

In plain English

It is the last resort. If any other event on the list fits, use that one. Prevention is for a sudden, major outside happening that no other entry covers, and the tests are deliberately tough.

All four tests must be met

Test What fails it
It stops completion, either overall or by the planned date Extra cost or a short interruption that float absorbs
Neither side could have prevented it A problem you could have avoided by acting differently
It was very unlikely at the Contract Date Ordinary commercial or construction risks
No other compensation event covers it Weather, ground and Client faults, which each have their own entry

Typical things that fail: a subcontractor going insolvent, price rises and shortages, weather that narrowly misses the weather test, and bad ground that misses the physical conditions test. Each event is a judgement on its own facts. Do not rely on someone saying it worked on another job.

Evidence

  • Independent records of the event, such as authority notices or road closure orders.
  • Why neither side could have prevented it.
  • How likely it looked when the contract was signed, drawing on the Site Information, local history and your tender risk register.
  • Programme logic showing it truly stops planned Completion.
  • What you did to limit the effect.

Worked example

A fictional river bridge strengthening job on Option C. A landslip closes the only access road, which is outside the Site, for ten weeks. The only alternative is a ferry crossing taking two weeks to arrange. Steel deliveries are on the critical path, so you can no longer meet the planned date.

You notify, citing 60.1(19). The Project Manager agrees it qualifies and, under clause 19.1, tells you to arrange the ferry and carry on with other work. Ferry hire and extra handling cost £90,000, redeployed plant over the two weeks costs £24,000, and two weeks of time-related cost is £36,000. That is £150,000 before the Fee.

If a longer second road had stayed open, deliveries would have continued and the stopped-completion test would fail. The extra mileage would be yours.

How it is assessed

Because you raise it, the eight-week bar in clause 61.3 applies, and the date you notify is the dividing date. Because these events are uncertain, assumptions under clause 61.6 are common, with corrections later. Clause 63.9 assumes you react competently and promptly, and reasonable workaround costs count if properly incurred.

Where the forecast delay passes thirteen weeks, clause 91.7 allows termination (reason R21). In the ECC that is the Client's right. Check your own wording and amendments.

What people get wrong

  • Expecting time without money. Readers from other forms assume relief only. Here the normal assessment applies, which is why the bar is high.
  • Trying it first. Rule out every other entry before you get to this one.
  • Using hindsight. Last year's events do not settle what was foreseeable at tender.
  • Ignoring Z clauses. Amendments can change or remove the entry.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?