A ready to use Excel register for tracking every compensation event from notification to implementation, with the 8 week time bar calculated automatically. Built by quantity surveyors.
A compensation event log is the register a contractor keeps of every NEC4 compensation event on a project. It records the clause 60.1 trigger, the notification date, the eight week time bar deadline, quotation status and value, so no entitlement is lost to a missed deadline.
Under NEC4 clause 61.3, a contractor who does not notify a compensation event within eight weeks of becoming aware of it loses the right to a change in the Prices or Completion Date, unless the event arises from the Project Manager or Supervisor giving an instruction, notification or certificate, or changing an earlier decision.Most CE registers fail in the same three places: the time bar date is worked out by hand, the log only records events someone remembered to notify, and the evidence sits somewhere else entirely. This template fixes the first problem and makes the second one visible.
| Field | Why it matters |
|---|---|
| CE reference and clause 60.1 trigger | Ties every entry to its contractual ground, so the PM sees entitlement not opinion |
| Date aware and notification date | The two dates the eight week time bar runs between |
| Time bar deadline (calculated) | The sheet works it out and flags anything within 14 days |
| Quotation status and value | Tracks the clause 62 cycle so quotations do not drift past their reply dates |
| Evidence reference | Points at the diary entries and records that substantiate the event |
Each column carries guidance notes in the sheet itself, with dropdown clause triggers and conditional formatting on the time bar column. The walkthrough below explains every field with a completed example.
The Excel file with automatic time bar calculation, clause 60.1 dropdowns and a worked example tab.
Download the template (.xlsx) Free download. No email needed. Yours to use and share with your team.On 4 July, the Project Manager instructs a change to the Scope under clause 60.1(1). The contractor logs it the same day as CE-014, which starts the eight week time bar at 22 August. A quotation is submitted within the three week window, the PM responds within two weeks, and the Prices and Completion Date are changed accordingly. The whole cycle is visible in one row instead of scattered across an instruction, an email thread and a quotation document nobody can find six months later.
Compare that with CE-015, a physical conditions event still sitting unquoted with seven days left on the clock. The register makes that risk visible today, not at final account.
A CE log is only as good as the records behind it. If an event never makes it into the register, the template cannot save it, and on most projects the events that get missed are exactly the ones nobody notified.
Gather's AI QS reviews your records against the NEC4 clauses and surfaces the events your team has not notified yet, before the eight week clock bars them.
See how the AI QS catches missed CEs A 30 minute call. No commitment. Bring one of your live contracts.FAQ
At minimum: a unique reference, the clause 60.1 trigger, the date your team became aware, the notification date, the calculated eight week time bar deadline, quotation status and value, and a pointer to the site records that evidence the event.
Eight weeks from becoming aware, under clause 61.3, unless the event arises from the Project Manager or Supervisor giving an instruction, notification or certificate, or changing an earlier decision.
Excel works for the register itself. What it cannot do is spot the events nobody logged, which is where most entitlement is actually lost.
Gather reads your site diaries as they come in and flags the CEs before the time bar does.
Book a demo