Knowledge Hub

Late and exposed: Weather risk after the Completion Date

17 November 2026

Dr Stuart Kings

NEC4 Drafter & Co-author

PhD, MRICS, MCIPS, BSc (Hons)

Construction workers looking at wind turbines
5 minutes read

Under NEC4, weather after the Completion Date is never a compensation event. That makes programme control and timely compensation events a weather risk issue as much as a commercial one.

 

A line in the calendar

Clause 60.1(13) only applies to weather recorded before the Completion Date for the whole of the works. After that date, no measurement, however extreme, can be a compensation event.

At Sypro’s Knowledge Hub webinar on 10 November, Dr Stuart Kings, one of the nine drafters of NEC4, put it bluntly: “as soon as they are late on the project, and they are past the completion date… then any bad weather, no matter how bad, is all contractor risk. So that’s quite profound when you think that through.”

 

Why the rule exists

The logic is straightforward. If the contractor had completed on time, it would not have been on site when the weather arrived. Weather encountered during a period of culpable delay is a consequence of that delay, and the contract places it with the party responsible.

That is fair as far as it goes. The difficulty lies in the phrase “completion date”. Under NEC4, the Completion Date is not fixed at the outset. It moves as compensation events are implemented. The date that decides who carries the weather risk is only as accurate as the contract administration behind it.

 

The hidden link to compensation events

Consider a contractor that has suffered several genuine compensation events: a change to the Scope, late access, a physical condition. Each should move the Completion Date. If those compensation events are notified late, quoted slowly or left unimplemented, the Completion Date stays where it was on paper.

Now a severe storm arrives. On the contractor’s view, the works are still within time once the outstanding compensation events are counted. On the contract record, the Completion Date has passed. Until the compensation events are implemented, the parties are arguing about weather risk with no agreed baseline. That is how a weather event becomes a dispute.

This is not a theoretical concern. Stuart reminded the webinar that NEC4 assesses time and money together under a single compensation event, precisely so that time is not left to a global extension of time argument at the end of the job. That system only works if the compensation events move through the process on time.

 

Timescales are the protection

NEC4 sets clear periods. The Project Manager has one week to reply to a notified compensation event. The contractor has three weeks to submit a quotation. The Project Manager then has two weeks to reply. All of these periods can be extended by agreement between the Project Manager and the contractor, without needing the client or anyone more senior.

Stuart’s view of those deadlines was simple: “If the contract didn’t have timescales in, we’d put things off till tomorrow, wouldn’t we? It’s human nature.” The timescales and the remedies for missing them exist to keep the Completion Date current. When they slip, both parties lose sight of where the risk sits.

 

Programme discipline matters too

The Accepted Programme is the other half of the picture. A programme that reflects the implemented compensation events, realistic weather allowances and the current planned completion gives both parties a clear view of the exposure. A programme that is months out of date leaves weather risk to be argued after the event.

Weather allowances deserve particular care. A contractor carries the risk of weather up to the 1 in 10 year value, so its programme should show realistic weather working days for each season. When a compensation event is instructed during the contract, the same allowance applies to the new work. A sensible Project Manager will expect to see it in the quotation, and Stuart was clear that the Project Manager “needs to respect that”. Where the allowance is missing, the contractor has quietly accepted risk it cannot recover. Where it is present and agreed, both parties know exactly how the weather has been treated, and the Completion Date that results is one both can rely on.

 

What both parties should take from this

Contractors should treat late compensation events as a weather risk. Every unimplemented compensation event is time that does not yet protect them. Notify within eight weeks, quote within three weeks or agree an extension, and press for implementation.

Project Managers should recognise that delayed replies have consequences beyond the compensation event in question. A Completion Date that is wrong on paper invites an argument about every subsequent weather event.

Both should hold regular reviews of open compensation events, weekly or fortnightly when numbers are high, so that the Completion Date always reflects the real position.

 

The real lesson

The weather clause looks like a technical rule about meteorology. In practice, its sharpest edge is administrative. The party that keeps its compensation events moving and its Completion Date current knows exactly where weather risk sits. The party that does not is exposed to every storm.

 

Sources

Pinsent Masons, Navigating weather conditions in Hong Kong SAR NEC4 contracts (March 2025), which also summarises the standard NEC4 ECC weather test. https://www.pinsentmasons.com/out-law/analysis/nec-risk-allocation-for-weather-events

CECA, NEC Bulletin No. 48: Assessing weather delays under NEC contracts (December 2024). https://ceca.co.uk/wp-content/uploads/2024/12/CECA-NEC-Bulletin-Nr-48-Assessing-weather-delays-under-NEC-contracts-December-2024.pdf

Speaker quotes: Dr Stuart Kings, Sypro Knowledge Hub webinar, 10 November 2026.

Meet the author Dr Stuart Kings

NEC4 Drafter & Co-author

PhD, MRICS, MCIPS, BSc (Hons)
View Profile
Share

Get started now with Sypro