Skip to content

The early warnings should have been raised and weren't

The contract wanted them, the register is empty, and the events happened anyway.

01The change happens
02Put in writing
03Recorded as it runs
04Valued
05Applied and paid
You are here: The risks arrived unannounced and the register shows it.

What's happening?

NEC is built around the early warning: the matter that could affect price, time or quality, notified as soon as either party becomes aware, so it can be managed while managing is still cheap. On this job the register is empty. The events happened anyway, they always do, and the file now says every problem arrived unannounced.

The consequences run through the assessments. Where an early warning should have been given and was not, the event can be assessed as if it had been, as if the risk had been flagged and managed early, which is rarely the cheaper version for the side that stayed silent. And beyond the arithmetic sits the record itself: when the account is argued, a file of raised-and-answered warnings reads as a job managed in good faith, and an empty register reads as one side keeping its problems to itself.

The register cannot be backdated and should not be. It can be started: the live risks on the job raised now, recorded and answered in the contract's format, so the next event lands on a job that flags its problems while they can still be shared.

The solution

Start the register with the next risk, not the last one.

If you would rather it were done for you, NEC Compensation Event Review is the service that does it.