What happens when you miss the NEC4 CE timebar, and can you recover?
Works with any UK construction contract. This guide focuses on NEC4, but Validate works with NEC4, NEC3, JCT, bespoke, or informal contracts. Deadline tracking and audit-trail discipline applies regardless of contract family. See also: Construction payment disputes · Adjudication evidence · Site diary app.
You've just reviewed your CE register and found 3 compensation events notified after the 8-week deadline under cl.61.3. Combined value: north of £100,000. Your site team knew about the events when they happened, but the notifications didn't get submitted in time. The PM hasn't said anything yet. When they do, you know what's coming.
This is the moment many M&E subs panic. The first question is usually the same: is there anything we can do?
The honest answer: the default position under NEC4 is brutal. Miss the timebar, lose the claim. But there is nuance. There are circumstances where a late-notified CE might still be recoverable. Arguments are made in adjudication, but none are guaranteed, and adjudication decisions are not published precedent. All depend on the facts. But if you've already missed a deadline, you need to know your options.
What cl.61.3 provides
Start with what the contract actually says. No point building arguments on a misunderstanding of the clause.
NEC4 cl.61.3 provides that if you don't notify a CE within 8 weeks of becoming aware, the Prices, Completion Date and any Key Date are not changed, unless the PM should have notified the event to you but did not. The language is mandatory rather than permissive. Check the wording in your own edition and any amendments.
This is commonly argued to be a condition precedent. Notification within 8 weeks is a prerequisite to entitlement. If the condition isn't met, the entitlement doesn't arise, and the adjudicator isn't exercising discretion.
The baseline: If you notified outside the 8-week window and the PM rejects it on timebar grounds, the default is no entitlement. The arguments below are exceptions, not the rule.
Can you argue you didn't know?
The 8-week clock starts when you become "aware" the event has happened. This creates a potential argument. If you can demonstrate you genuinely weren't aware until a later date, you can argue the clock started later than the PM thinks. Your notification may actually be in time.
This argument has limits. Expect awareness to be judged by what your organisation knew, not by what one person on the commercial team knew. If your site foreman witnessed the event but didn't tell the commercial team, the PM is likely to argue that the Contractor was aware.
There are genuine scenarios where awareness is delayed:
- Latent conditions. If the CE relates to physical conditions that differ from the Site Information, you might not grasp the full extent until investigation. You became aware when the investigation revealed the discrepancy, not when you first started digging.
- Cumulative impact. Some CEs only become apparent through cumulative effect on the programme. A series of small instructions, none individually significant, might collectively constitute a CE. Awareness didn't crystallise until the cumulative impact became clear.
- Information withheld by the PM. The PM issued a revised drawing but didn't send it to you. You discovered the change on site weeks later. Your awareness date is when you received or discovered the information, not when the PM issued it internally.
The strength of a "delayed awareness" argument depends on evidence. If you can show a paper trail proving when you first learned about the event, and that date is within 8 weeks of your notification, you have a viable argument. If you're relying on people's recollections, it's much weaker.
The PM's own notification duty
This is the argument most often raised. NEC4 puts notification duties on the PM as well, and cl.61.3 itself carves out the case where the PM should have notified the event to you but did not. Check the exact clauses in your contract.
The argument: if the PM was aware of the CE (because they issued the instruction that caused it) and failed to notify when they should have, the PM shouldn't be allowed to rely on your failure under cl.61.3. The PM had their own duty and didn't act on it. Allowing the PM to benefit from their own breach would be inequitable.
Some adjudicators may agree. NEC4 sets out notification duties for both parties. When the PM issues an instruction that's clearly a CE, then waits silently for your 8-week window to expire, an adjudicator may hold that the PM can't rely on the timebar.
Important caveat: This doesn't always succeed. Some adjudicators take a stricter view: the Contractor's duty to notify and the PM's duty to notify are separate obligations, and the PM's failure doesn't relieve you of the timebar. Don't treat this as a certainty.
The argument is strongest when the PM clearly knew about the event because they caused it, had an obvious duty to notify, and failed. It's weaker when the event was something the PM might not have known about, like a physical condition found during installation.
What to do if you've already missed a deadline
If you've found CEs that were notified late, here's a practical approach:
1. Assess the awareness date carefully. Go through your records: site diaries, emails, meeting minutes, drawing transmittals. Pin down exactly when your organisation first knew about each event. Don't assume the PM's version of the awareness date is correct. They may be arguing for an earlier date than the evidence supports.
2. Check whether the PM had their own duty to notify. For each late CE, ask: did the PM know about it? Did they cause it by issuing an instruction? Did they notify when they should have? If they knew and didn't notify, document that failure. It's your strongest recovery argument.
3. Check your subcontract amendments. Some bespoke NEC4 subcontracts modify the timebar through Z-clauses or option statements, which can change the 8 weeks or how strictly the bar is applied. Check your actual contract documents. The answer might be in a Z-clause you haven't read.
4. Notify anyway. Even past the 8 weeks, submit the CE notification. State the facts. Explain when you became aware. Make the arguments you have. The PM may accept it. If they don't, you've created a record you can take to adjudication. Not notifying at all guarantees you get nothing.
5. Get specialist advice early. If the value at stake is significant, and on M&E packages it usually is, get advice from someone who knows NEC4 adjudication before you decide your approach. How you frame the notification and the evidence you assemble will determine whether recovery has any chance.
How to make sure it never happens again
The best strategy for missed timebars is preventing them. Prevention is straightforward:
- Every potential CE goes into your register on the day of awareness. Not next week. That day. With the 8-week deadline auto-calculated.
- Set internal deadlines at 2 weeks, not 8. Target notification within 2 weeks of awareness. That gives you 6 weeks of buffer. Enough margin for holidays, sickness, and the normal chaos of site life.
- Make notification someone's specific responsibility. Not "the commercial team." A named person who reviews the register weekly. Someone accountable for getting every CE notified within the internal deadline.
- Train your site team on what a CE looks like. A common cause of missed timebars: the site team didn't recognise the event as a potential CE and didn't report it to the commercial team. A short training session at project start helps.
- Use automated alerts. Software or a calendar reminder. You need something that tells you when a deadline is approaching. Relying on memory is not a system.
Every missed timebar is money you've earned but can't recover. On an M&E subcontract with many CEs over the project, missing even a few can badly hurt your margin. The 8-week deadline isn't forgiving, but it is predictable. With the right process, there's no reason to miss one.
Keep your own notification date in front of you
Validate records the 56 day notification date for a variation you log, and warns your office and project team when it is within three days, or has passed with no notice raised.
Start free trial