Notifying a compensation event before it happens
You can notify an event you expect, not just one that has happened. When to do it, when to send an early warning instead, and the knock-on effects.
On this page
You can see an event coming, such as access that will be late, and you want to know if you have to wait for it to actually happen before notifying.
The short answer
No. Clause 61.3 covers an event you expect as well as one that has already occurred, as long as you genuinely believe it is coming and the Project Manager has not already notified it. How firm your facts are decides whether you should. If you only fear something might go wrong, send an early warning, not a notice.
What to do, step by step
- State the facts behind your expectation. A utility's letter saying it cannot attend until August is a fact. "We are concerned" is not.
- Name the event. Give the clause and the Accepted Programme date you expect to miss.
- Keep it on its own page. Clause 13.7 wants a notification kept separate from other correspondence.
- Diary the answer. It is due in one week under clause 61.4, or two in the NEC4 subcontract. If none comes, you can use the failure route.
- Notify again if the event turns out different. If your notice described four weeks' delay in one area and the real problem is elsewhere, send a second notice.
Which message to send:
| What you know | Send |
|---|---|
| Something might go wrong, cause unclear | Early warning only |
| It is now expected and would be a listed event | Early warning and notification, separately |
| It has already occurred | Notify immediately, as the time limit is live |
| The Project Manager has already notified it | Respond to that |
Effects you might not expect
- Dividing date. For events not from a Project Manager communication, it is the notification date (clause 63.1). Everything after is a forecast.
- Programme. Delay is measured on whichever Accepted Programme is current that day, so an early notice may fix an earlier one.
- Uncertainty. Where effects cannot be forecast, the Project Manager may set assumptions (clause 61.6). A wrong one can be corrected later as an event of its own.
- Reply. An event that has not happened and is not expected is one ground for a "no" under clause 61.4, so show your evidence of expectation.
On the clock, NEC4 starts the eight weeks when you become aware the event has happened, so one you merely expect has not started it. NEC3 is worded more loosely and can be read as starting earlier. Under NEC3, play safe and count from the day you first saw it coming.
What to record
- The evidence that the event is coming, ideally in writing from someone else.
- The programme date at risk.
- Your notice and the Project Manager's reply.
- Any change in the facts afterwards.
What not to do
- Do not use a notice for a vague worry.
- Do not assume an early warning covers notification.
- Do not withdraw your notice if the Project Manager says "deal with it by early warning first".
- Do not ignore the clock once the event actually happens.
When to get help
A commercial manager can judge whether your evidence is firm enough. Ask a planner to forecast the effect, because an early notice makes the whole quotation a forecast.
Example
The Accepted Programme gives you the east wing on 8 September. On 12 August the Client emails that the occupier will stay until 6 October. You send an early warning and a separate notice under 60.1(2) the same afternoon, with the email attached. The quotation covers redeploying the joiners to the west wing and the four weeks that planned Completion moves. If the occupier leaves early, the assessment is not revised for that alone, unless the Project Manager set an assumption and later corrects it under clause 61.6.
A reply of "too early, come back when it happens" does not stop you notifying again later. Watch the clock from that moment.
Related guides
- Can a compensation event be notified without an early warning?
- Does an early warning count as notifying?
- Late access to site
- Quoting when facts are unknown
This guide is general information, not legal advice. Check it against your contract.
