A commercial manager we spoke to at a Tier 1 civils contractor caught a Compensation Event on the Thursday before its notification deadline expired. The dispute would have run into seven figures. What saved it was that a partner happened to be reading through the previous month's meeting minutes for an unrelated reason and noticed a discussion that should have triggered a notice on the Monday five weeks earlier.
That is not a story about a heroic partner. It is a story about a spreadsheet.
The register was in a shared spreadsheet. The eight-week Compensation Event clock in NEC4 clause 61.3 was tracked by a column of dates the QS was supposed to update. The QS had updated it correctly. The row for that specific event had never been added, because the discussion in the meeting had not been flagged as a CE trigger by the person taking minutes. A single omission at the intake, five weeks earlier, would have cost the firm the right to claim.
The rule under NEC is one of the plainest in the standard form. Under clause 61.3 a Compensation Event not notified inside eight weeks is lost outright. The claim is time-barred. The engineering merits do not matter. The reason for the delay does not matter. The counterparty's own contribution to the delay does not matter. The passage of time is what defeats the right.
The clocks that matter
NEC4 runs on clocks. Two of them do the load-bearing work.
The first is the Early Warning clock. Under clause 16.1 either party is obliged to notify the other as soon as they become aware of a matter that could increase the total of prices, delay Completion, delay a Key Date, or impair the performance of the works. The obligation is joint. If either party knows, either party must notify. If either party fails to notify a matter they knew about, and a Compensation Event later arises from it, the Project Manager can reduce the assessment on the ground that the risk-reduction meeting the Early Warning would have triggered was denied.
The second is the Compensation Event decision clock. Under clause 61.3 the Contractor has eight weeks from becoming aware of an event to notify it as a Compensation Event. Miss the eight weeks and the right is lost. Under clause 62.3 the Project Manager then has three weeks (extendable by agreement) to respond. The response is one of four things and the four are exhaustive. Silence is not one of them.
Every contract in a Tier 1 portfolio is running those clocks in parallel. Fifty active contracts, three to eight Compensation Events per contract at any given time, twelve to twenty Early Warnings open at any given time. That is the exposure. The mechanism that keeps it defensible is a register of when each clock started, when it will expire, and what has been done about it.
The mechanism is manual
The mechanism, on almost every contract we have looked at, is a spreadsheet. Sometimes it is a document control system with a spreadsheet bolted on top of it. Sometimes it is Excel and Outlook reminders. Occasionally it is a bespoke database that was built in the mid-2000s and has not been meaningfully updated since.
The failure modes are consistent across the sample:
A column that has to be updated. The eight-week deadline is stored as an "expiry date" field that somebody has to compute at creation time and re-check on read. When the notification date is corrected (which happens, because the notification date is often established retroactively when the paperwork is filed), the expiry date does not automatically move. A stale field is worse than no field. The spreadsheet reads green on a row that is actually red.
A row that was never added. The trigger event happened in a meeting or a site visit or an inspector's report. The person who was there did not flag it. The notice register was not the first place anyone thought of when they were writing up the minutes. Five weeks later the discussion resurfaces and by then the intake is late.
A person who has to remember. The CE decision clock is on the Project Manager, not the Contractor, but the pattern is the same. The PM has three weeks to respond after the Contractor's quotation. The response is a specific one of four options. If the PM misses the three weeks and does not extend, the treatment under NEC is complicated and adjudicators disagree about it, and the contract is now uncertain in a way that no one wanted.
A record that can be edited. When a claim reaches adjudication, the Adjudicator asks for the contemporaneous record. The contemporaneous record is the sequence of who did what and when, kept as the work happened. If the record is a spreadsheet, the last-modified timestamp is at the file level, not the row level. There is no honest answer to "when was this entry added". The other side's counsel will not accept the register as evidence, and the reconstruction happens under discovery, which is exactly the time when it is hardest to do.
Each failure mode compounds the last. The register does not know its own state. The state cannot be defended in adjudication. The claim is lost or reduced, not because the merits were bad, but because the record could not carry them.
What Zeno is doing differently
Zeno is Nuviax's NEC4 contract intelligence engine. It is built around four ideas, each of which closes one of the failure modes above.
Clocks are derived, not stored. The state of a notice is computed from the contract dates at read time. There is no expiry column that someone has to update. When a notification date is corrected in the underlying record, the derived status changes on the next read. Nothing goes stale because nothing is stored.
Notices are auto-numbered, cited, and stamped. Every notice created in Zeno takes its reference from the contract identifier, its number from the next unused slot on the contract's register, its clause from the NEC section that governs it, and its timestamp from the write. The commercial manager reviews the entry rather than composing it, and the register maintains itself.
The log is append-only. Every action, every change, every response, every decision, every attachment, is a new entry with a timestamp. Nothing is edited. The Adjudicator asks for the contemporaneous record and the log is the record. It was written as the work happened, not reconstructed at review.
The board is portfolio-wide. The commercial lead opens one board that spans every contract, every contractor, and every employer, sorted by exposure. The overdue row is where the eye lands first. The Fenland flood scheme sitting at plus twenty-six days is visible next to the A66 River Eden Viaduct at minus eight. One view instead of eleven spreadsheets.
The animation on the Zeno product page shows the mechanism at a fraction of the actual speed. A row ticks down a day at a time, then goes overdue. That is the whole product story. The calendar is what defeats you if you are not watching. Zeno is the software that is watching.
Where Zeno sits
Signet, our AI code compliance product for buildings, proves a building's design meets the code before it is built. Zeno proves the delivery met the contract while it is being built. Same DNA. Evidenced, dated, defensible to a third party. Applied either side of the ground-breaking.
Underneath both, the platform layer is the same. Intelligence Fabric for orchestration and retrieval. AI Guardrails for policy and access control. AI Gateway for model routing and cost control. The audit story that runs on a Signet submission is the same audit story that runs on a Zeno notice register.
If your team runs a portfolio of NEC4 contracts and the notice register is a spreadsheet somebody has to remember to update, tell us the contract that keeps you up. We will run it live and show you the clock board and the append-only record. An architecture review takes ninety minutes and produces a written findings document your commercial lead and your general counsel can read together.