8-week time bar: three near-miss patterns from real projects

Clause 61.3 gives you eight weeks. Miss it, and a valid compensation event turns into money you will never see. Not because the event was wrong. Because the clock ran out while the paperwork sat in someone's inbox.

Every commercial manager on an NEC4 ECC contract knows the eight-week rule exists. Far fewer can tell you, honestly, how many events nearly slipped past it last quarter. The near-misses rarely make it into a lessons-learned deck. They should. They are where the real risk lives.

What follows is three patterns we see again and again. They are composite scenarios, built from common failure modes rather than any one project, and the figures are illustrative. The mechanics of clause 61.3, though, are exactly as they play out on site.

First, the rule in plain terms

Under NEC4 ECC clause 61.3, if you do not notify a compensation event within eight weeks of becoming aware of it, the Prices, the Completion Date and any Key Dates are not changed. The entitlement is gone.

There is one carve-out. The bar does not apply where the event arises from the Project Manager or Supervisor giving an instruction, issuing a certificate, changing an earlier decision, or correcting an assumption. In those cases the Project Manager should have notified the event under clause 61.1.

So the trap is sharpest for the events you have to notify yourself. Weather. Physical conditions. A late response. Anything the contract expects the contractor to raise. Read the full mechanics of the eight-week time bar if you want the clause-by-clause detail. The three patterns below are about how the clock actually gets missed.

Pattern one: the verbal instruction nobody wrote down

A site manager gets a call from the Project Manager's assistant. Change the drainage run around the new duct route, they say, we will sort the paperwork later. The site team does the work. Good, responsive delivery. Everyone moves on.

Nobody logs it as an instruction. Nobody notifies it. "The paperwork later" never arrives, because the person who promised it moved to another framework six weeks in.

By the time the QS spots the extra labour and plant in the cost report, ten weeks have passed. The instruction was verbal, so there is no dated record of when the contractor became aware. The commercial team is now arguing about the start date of their own eight-week window, which is a fight you do not want to be having.

The clause 61.3 mechanics. A genuine instruction is a clause 61.1 event, and in theory the Project Manager should have notified it. In practice, a verbal instruction with no written trail gives the other side room to argue it was never an instruction at all, just a conversation. Once it is reframed as a conversation, the notification duty falls back on you, and your eight weeks may already be spent.

The record-keeping fix. Every verbal instruction gets logged the same day, in the site diary, with who said it, when, and what was asked. That entry is your evidence of the date of awareness and the substance of the instruction. If the instruction should have come in writing under the contract, you confirm it back in writing and, where needed, notify it yourself rather than waiting. A contemporaneous site diary entry turns "he said, she said" into a dated fact. The near-miss becomes a non-event.

Pattern two: the weather event logged but never escalated

A junior QS records it accurately. "Concrete pour delayed two hours, heavy rain." It goes in the diary. The entry is correct, timestamped, and completely inert.

What the diary does not capture is that this was the fourth rain-affected pour that month, and that the cumulative weather was measurably worse than the contractual baseline. The individual entries look minor. The pattern across them is a notifiable compensation event.

Nobody joins the dots until the monthly review, and even then the weather sits under "site conditions" rather than "commercial actions". The eight-week window on the earliest affected days is already closing before anyone asks whether the weather beat the baseline.

The clause 61.3 mechanics. Adverse weather measured against the contract baseline is a contractor-notifiable event, which means the full eight-week bar bites. Awareness runs from when you knew, or should have known, that the weather exceeded the baseline. On a wet month, that can be much earlier than the day you finally add up the totals. Logging the rain is not the same as notifying the event, and only the notification stops the clock.

The record-keeping fix. Diary entries need to feed a running commercial view, not just a daily record. Weather days should be tagged against the baseline so the cumulative position is visible while there is still time to act, not discovered in arrears. Pair this with disciplined early warning practice so the emerging pattern is on the risk register before it becomes a claim. The fix is not more data. It is data that surfaces the commercial trigger while the window is still open.

Before you read pattern three

Both of the near-misses above turn on the same weakness. The record existed. The commercial meaning of the record did not surface in time. That gap between "it is written down somewhere" and "someone acted on it" is precisely where the eight-week bar does its damage.

This is the exact gap Gather's QS AI Agent is built to close. It reads every diary entry against the contract terms and the project baseline, flags the ones that look like compensation events, and surfaces the cumulative patterns a human scanning one day at a time will miss. It does not replace your commercial judgement. It makes sure the trigger reaches your desk while you can still notify. If the two patterns above feel familiar, a 15-minute demo will show you how it works on records like yours.

Pattern three: the scope creep the site team quietly absorbed

This one is the most expensive and the hardest to spot, because it looks like everything is going well.

The design firms up as the job progresses. Details get added. The specification tightens in a dozen small ways that never arrive as a single, obvious instruction. The site team, proud of keeping pace, absorbs each small change without flagging it. No fuss, no delay, no notification.

Twelve weeks later the QS is reconciling cost against the target and cannot make the numbers meet. The extra work is real and it was done well. But it drifted in as a series of unnotified changes, and the eight-week window on the earliest ones has long since closed.

The clause 61.3 mechanics. Where the changes are genuine Project Manager instructions or changed decisions, the 61.1 duty helps you. Where they arrived informally, absorbed by a helpful site team without a written instruction, you are back in contractor-notification territory and the bar applies. Death by a thousand small changes is still death. Each absorbed change is a separate event with its own eight-week clock, and most of them are already stopped by the time anyone adds them up.

The record-keeping fix. The site team needs a frictionless way to flag "this is different from what we priced" the moment it happens, without stopping work or filling in a form. Every deviation from the priced scope gets captured at source, dated, and routed to the commercial team the same week. That way scope creep shows up as a live list of potential events, each with its window still open, rather than a reconciliation shock at final account. Structured, contemporaneous records are the difference between recovering the work and gifting it.

What the three patterns have in common

None of these near-misses was caused by a weak entitlement. Every underlying event was valid. Every one nearly died on a technicality of timing.

The common failure is not laziness and it is not incompetence. It is that the commercial significance of a record surfaces too late, usually at the monthly review or, worse, at final account. By then the eight-week windows on the earliest events have already closed, notice periods have expired, and the negotiating position has evaporated.

The habit that catches all three is the same. Capture at source, date everything, and make the commercial trigger visible while the window is still open. The clause does not forgive good intentions. It only responds to notification.

Frequently asked questions

What is the 8-week time bar under NEC4?

The 8-week time bar is the rule in NEC4 ECC clause 61.3 that a contractor must notify a compensation event within eight weeks of becoming aware of it. Miss the deadline and the Prices, Completion Date and Key Dates are not changed, so the right to additional time or money is lost, regardless of how valid the underlying event was.

Does the 8-week time bar apply to every compensation event?

No. The bar does not apply where the event arises from the Project Manager or Supervisor giving an instruction, issuing a certificate, changing an earlier decision, or correcting an assumption, because the Project Manager should notify those events under clause 61.1. The bar bites hardest on events the contractor must notify itself, such as adverse weather or physical conditions.

When does the 8-week clock start?

The clock starts when the contractor became aware, or should reasonably have become aware, of the event. For a single instruction that is straightforward. For a cumulative event like adverse weather beating the baseline, awareness can start well before the totals are added up at a monthly review, which is why the deadline is often closer than teams expect.

How do good site records prevent a time-barred compensation event?

Contemporaneous records fix the date of awareness and the substance of each event while the eight-week window is still open. A dated site diary entry for a verbal instruction, weather logged against the baseline, and scope deviations captured at source all turn a late reconciliation shock into a live list of notifiable events. The record only helps if its commercial meaning reaches the QS in time to notify.

Can software help catch compensation events before the time bar?

Yes. An AI QS agent reads every diary entry against the contract and baseline, flags likely compensation events, and surfaces cumulative patterns a person reviewing one day at a time will miss. Gather's QS AI Agent is built to get the trigger to the commercial team while the eight-week window is still open, rather than at final account.

The bottom line

The eight-week time bar rarely catches people on the events they are watching. It catches them on the verbal instruction nobody wrote down, the weather that looked minor day by day, and the scope that a good site team quietly absorbed. Valid entitlement, lost to timing.

The fix is not heroic. It is a record captured at source, dated, and read for its commercial meaning while there is still time to act. Do that consistently and clause 61.3 stops being a threat and becomes a routine you barely notice.

If your team is reviewing diaries a month behind, you are already inside somebody's eight-week window. See how the QS AI Agent surfaces compensation events in time to notify.

Source: Gather Insights, the AI-powered site diary and commercial record management platform for UK construction. The near-miss patterns in this article are anonymised composite scenarios for illustration and do not describe any single named project or customer.