Can you claim for bad weather under NEC?

Bad weather is a compensation event only if the recorded figures beat the one-in-ten-year test. How to check, what to log, and what stays with you.

Compensation events and changeScenario3 min read

On this page
  1. The short answer
  2. What to do, step by step
  3. What to record
  4. What not to do
  5. When to get help
  6. Example
  7. Related guides

It has been a dreadful few weeks on site, the team wants to claim, and you want to know whether the contract allows it. Sometimes it does, but not for the reason people expect.

The short answer

Judge it by the numbers, not by how bad it felt. Weather is a compensation event under clause 60.1(13) only when a measurement for a calendar month, taken before the Completion Date at the place named in the Contract Data (the part of the contract where project specific details are filled in), is shown by the weather data to be rarer than once in ten years. Anything short of that is your risk, however long it lasted.

What to do, step by step

  1. Open Contract Data part one and find the weather entries: which measurements, which place, who supplies the figures and which past records apply.
  2. Establish the one-in-ten level for each month and each measurement. If the contract doesn't state it, agree it with the Project Manager.
  3. Give an early warning now. Weeks of weather threatening Completion are worth warning about under clause 15.1, whatever the final test shows.
  4. Compare each month's figure as it arrives. If one passes, notify the event. The limit is eight weeks from becoming aware it has happened (clause 61.3; seven under the NEC4 Engineering and Construction Subcontract), and you may notify an event you expect to happen.
  5. Log daily effects: what was stopped, why, and what you did instead.
  6. If nothing passes, stop spending time on a claim and recover on the programme instead.

What to record

  • The weather supplier's monthly figures for the named place
  • Your daily records of lost or changed working
  • Plant standing, and any work moved to other areas
  • Dated early warnings and meeting notes

What not to do

  • Do not use your own site rain gauge or thermometer as the test. The named source decides.
  • Do not add two part-months together. The test is one calendar month at a time.
  • Do not claim the whole lost period. Only the excess over the one-in-ten level is taken into account.
  • Do not treat the prevention event (clause 60.1(19)) as a fallback for a near-miss month. It covers only what is not another compensation event.
  • Do not assume your subcontractors share your protection. A main contract weather test does not help them unless their own terms and data line up.

When to get help

A planner and a commercial manager should translate any excess into lost working time with a method the Project Manager can follow, particularly where the measure is a total (such as millimetres of rain) rather than a count of days. Take advice if the Client disputes the source data.

If no measurement passes, the outcome depends on your Option. Under A and B you carry cost and time. Under C and D the cost goes through the target-cost share and neither target nor date moves. Under E the Client pays the cost and the date stays put.

Example

A highways resurfacing job on Option A. Contract Data names days of ground frost as the measure.

Month Frost days recorded One-in-ten level Excess
December 15 17 None
January 21 19 2 days

It felt like seven weeks of frost, but only two days exceed the threshold. The Contractor shows those two days stopped paving and moved planned Completion by two days. At an invented £5,000 a day for standing plant and site team, the Prices rise by £10,000 plus Fee and the Completion Date moves by two days. Everything else was a risk the Contractor priced.

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

Was this useful?