On an NEC4 project, your daily records aren't admin. They're the contemporaneous evidence the entire commercial position rests on. You're not a commercial party the way the Project Manager is. But the records you create are read, months later, to decide who pays for what.
A foreman or engineer writing "access delayed 3 hours, waiting for the Client's rep to clear the area" is describing a compensation event. They almost never know that. Under clause 60.1, there are 19 categories of compensation event, from physical conditions under 60.1(12) to a Client or Project Manager instruction under 60.1(1). The trigger for many of them shows up first in a site record, written by someone who has no idea they've just documented an entitlement.
And the clock is already running. Under clause 61.3, the Contractor must notify a compensation event within eight weeks of becoming aware of it. Miss that window and the entitlement is gone, however legitimate it was. The engineer's record is frequently the first evidence that the eight-week clock has started. A record that captures the cause, the date, and the impact gives the commercial team something to act on. A record that says "delayed, weather" gives them nothing.
There's a second mechanism worth knowing. Under clause 15.1, early warnings require both parties to notify matters that could increase cost, delay completion, or impair performance, as soon as they become aware of them. Site engineers are usually the first to see these coming. An engineer who flags these into the record promptly feeds the early warning process, and that early warning often protects the commercial position even when the formal compensation event notice ends up late.
So when AI prompts you to add the causal chain to a diary entry, it isn't being fussy. It's capturing the evidence that, under clauses 60.1, 61.3, and 15.1, decides whether the project recovers tens or hundreds of thousands of pounds it's genuinely owed. Your job is to build it; the AI's job is to nudge you towards building it well.
Worked example: how one diary entry held a £62,000 entitlement together£28M · NEC4 Option C · Yorkshire
On a £28M NEC4 Option C highways improvement package in Yorkshire (started January 2025), a site engineer was carrying out drainage works in the verge. On 14 March 2025, the gang hit an unrecorded live utility duct that wasn't on any of the issued service drawings. Work stopped while the utility was traced and protected.
The engineer used an AI-assisted diary tool that evening. His first dictated note was short: "Drainage stopped, found a cable, lost most of the afternoon." The tool prompted him for the detail. By the time he finished, the entry recorded: the time the obstruction was found (13:20), the duration of the stoppage (3 hours 40 minutes), the gang and plant stood down (a four-person drainage gang plus a 13-tonne excavator), the fact that the utility wasn't shown on service drawing rev C, and a photo of the exposed duct, geotagged and dated. He also flagged it as a potential early warning.
When the QS reviewed records the following month, that entry mapped cleanly to a physical conditions compensation event under clause 60.1(12). Because the engineer had logged the discovery date of 14 March 2025, the team could see the eight-week notification window under clause 61.3 closed on 9 May 2025, and they notified in good time. The early warning flag meant the Project Manager had been told promptly too.
Stoppage duration3h 40m
Gang and plant stood down4-person gang + excavator
Notification windowClosed 9 May 2025
Assessed value of the event£62,000
Lesson: the work found the money. AI made sure the work was recorded in a way the commercial team could use before the window closed.
.webp)
