NEC4 cl.61.3 explained: the 8-week CE notification deadline M&E contractors keep missing
Works with any UK construction contract. This guide focuses on NEC4, but Validate works with NEC4, NEC3, JCT, bespoke, or informal contracts. The audit-trail and deadline-tracking are the same regardless of contract family. See also: Construction payment disputes · Site diary app · Adjudication evidence.
Picture this. Week 3 of your fit-out. The architect issues revised riser drawings for levels 4 to 8. Your site engineer spots a containment clash with the steelwork. He flags it to the PM at the progress meeting. The PM nods and says he'll "deal with it."
Nine weeks later, your QS prices the impact and submits a CE notification. The PM's response takes 30 seconds: out of time under cl.61.3. Your claim for the redesign, abortive work, and programme impact is in serious trouble.
The scenario is made up, but the mechanism is real. The clause is brutal and mechanical. It doesn't care that your PM verbally acknowledged the problem. If you didn't notify formally within 8 weeks, you can lose the right to claim.
What cl.61.3 actually says
The clause is short. That's part of the problem: people skim it and miss what it does. Under NEC4 cl.61.3, if you don't notify a CE to the PM within 8 weeks of becoming aware, you're not entitled to a change in Prices, Completion Date, or a Key Date, unless the PM should have notified the event to you but did not.
Read that again. It doesn't say the PM can choose to reject it. It doesn't say your claim is weakened. It says you are not entitled. The contract removes your right, subject only to the exception for events the PM should have notified but did not. No discretion, no fairness test. The timebar is strict.
Key point: cl.61.3 is commonly argued to be a condition precedent. On its face it doesn't reduce your entitlement, it removes it. The position isn't fully settled, and recovery arguments can exist on the facts, but you should plan on the basis that it will be enforced.
NEC4 is designed around early warning and proactive management. The timebar is the enforcement mechanism. Other contract forms treat late notification differently, so check yours.
When does the clock start?
This is where disputes actually happen. The 8-week clock starts when you become aware the CE has happened. Not when you finish pricing it. Not when you raise it at a commercial meeting. Not when your QS gets back from holiday. When you become aware.
"Aware" is likely to be judged by what your organisation knew, not by what one person knew. If your site engineer knew about the drawing change in week 3, expect the PM to argue that your company was aware in week 3, and that the QS not finding out until week 10 is your own internal communication problem.
In practice, awareness usually starts on the day one of these happens:
- You receive a revised instruction, drawing, or specification
- You hit a physical condition on site that differs from the Site Information
- The PM or Supervisor gives an instruction that changes the Works Information
- An event occurs that you should reasonably have noticed, even if nobody told you
That last one catches people. Say there was a 2-week delay to your access because the main contractor hadn't finished the slab. Your site team was there watching it happen. The clock started when you first couldn't access the area, not when someone formally told you about the delay.
What happens when you miss the 8-week deadline
Nothing complicated. You lose the claim. The PM responds to your late notification by saying it wasn't made within the contractual period. That's the end of the conversation under cl.61.3.
If you take it to adjudication, you're on the back foot. The timebar is commonly enforced as written, and it is often argued to be a condition precedent: if you notified late, expect to be out. The position isn't fully settled, and on the right facts a recovery argument can still exist, but you should never count on one. Plan on the basis that an adjudicator won't award time or money for a CE notified outside the 8-week window, however legitimate the underlying claim. For the arguments that sometimes survive a late notification, see what happens when you miss the NEC4 CE timebar.
Say a subcontractor has a completely valid CE, a clear change to the scope of mechanical works, but notifies at week 11. An adjudicator could accept that the claim has merit and still find that the contract prevents any award. The subcontractor loses a claim that would have succeeded if they had sent a one-paragraph notification 8 weeks earlier.
The financial impact compounds fast on M&E packages. A single missed CE on a riser redesign can include abortive containment, revised builders' work drawings, extra labour for rework, and programme delay. These aren't small numbers.
The PM has notification duties too
NEC4 also puts notification duties on the PM. Where the PM should have notified an event to you, the contract treats that differently from your own failure to notify, which is why cl.61.3 carves it out. Check the exact clauses in your edition.
The kicker: the 8-week limit in cl.61.3 applies to your notification. You have 8 weeks from awareness or you risk losing the claim. That asymmetry causes disputes.
There is a counterargument, though. If the PM was aware of the event and failed to notify when they should have, the argument is that the PM can't then rely on your failure under cl.61.3. The logic: the PM had their own duty to notify and didn't, so the timebar shouldn't apply. Adjudicators may take different views, and this argument doesn't always succeed. It depends heavily on the facts. But you should know about it if you're already past the deadline.
Don't rely on this as a strategy. It's an emergency argument, not a plan.
How to track CE deadlines in practice
The fix isn't complicated. It just requires discipline. Everyone on your site team who might spot a CE needs to understand two things: what a CE looks like, and what happens if they don't report it immediately.
In practical terms:
- Train your site engineers. They don't need to know the whole contract. They need to know that any instruction, change, delay, or obstruction outside the original scope goes to your QS on the same day.
- Log everything with a date. Every instruction, every revised drawing, every verbal direction. The date you became aware is the date the clock starts. You need to prove when that was.
- Set a hard internal deadline. Your external deadline is 8 weeks. Your internal deadline should be 2. By week 2 from awareness, your CE notification should be drafted and submitted. That gives you margin and kills the "I'll do it next week" problem.
- Use a CE register with timebar tracking. Every potential CE goes into a register the day you become aware. The 8-week deadline gets calculated automatically. If you're using a spreadsheet, someone reviews it weekly.
- Never assume the PM will deal with it. Verbal acknowledgement means nothing under NEC4. The PM saying "I know about it" doesn't stop your clock. Only a written CE notification under cl.61.3 stops it.
A common pattern on M&E subcontracts: site teams focus on getting the work done. They treat commercial admin as something the office handles. But the office can't notify a CE if they don't know about it. The gap between site awareness and commercial awareness is where claims die.
Remember: A CE notification doesn't need a quotation. It just needs to identify the event. You can submit a one-liner: "We notify a compensation event arising from revised drawing issue on [date] changing containment routing on levels 4-8." That stops the clock. The quotation comes later.
Validate warns you as your notification date approaches
Validate records the date by which you need to notify, from the day you log a potential variation, and warns your office and project team when it is within three days or has passed with no notice raised.
Start free trial