Is a spreadsheet enough to run an NEC contract?

When a spreadsheet works for tracking NEC notices and replies, how it fails, and the safeguards that make one reliable, including a simple reply date formula.

Communications and records3 min read

On this page
  1. Where it works, where it doesn't
  2. How trackers go wrong
  3. Safeguards worth adding
  4. A simple reply-date rule
  5. Signs you have outgrown it
  6. Related guides

A spreadsheet is fine for a small NEC contract if one person owns it and someone checks it every week. It starts to fail once several people edit copies, several contracts share one tracker, or you need to prove what was sent and when. The contract does not care which tool you use. It cares that replies are on time and on record.

Where it works, where it doesn't

Situation Verdict
One small contract, few events, one administrator Fine
A short-form contract with light process Fine
A mid-size contract with several commercial staff Workable with discipline
Several contracts in one file Risky: periods differ and formulas get copied wrongly
Main contract and subcontracts linked together Risky: links between files break
Both sides need one live view Weak: copies drift
A dispute or audit is likely Weak on its own: a typed date is not proof it happened

How trackers go wrong

  • Wrong reply formula. One week is hard-coded into every row, so a Z clause (an extra condition the Client adds) or a subcontract's longer period is missed.
  • Overwritten rows. A filter was on, a paste crossed hidden lines, and nobody noticed for months.
  • No one is chased. A date in a cell reminds nobody. If the owner is on leave, the sheet just sits.
  • Status means different things. To one person "closed" means implemented, to another it means rejected.
  • Evidence lives elsewhere. The notice is in someone's mailbox, and when they leave, the link leaves too.
  • Totals drift. The value in the tracker stops matching the latest payment certificate.

Safeguards worth adding

  1. One file, one place, one named owner. No emailed copies.
  2. A settings tab holding the actual periods for your contract, with every date formula reading from it.
  3. Drop-down lists for status and event type, with a note on what each status means.
  4. Locked formula columns, so only input cells can be typed in.
  5. An "action needed" column that flags what is overdue or due within seven days, sorted first each week.
  6. A link in every row to the project folder, not a personal inbox.
  7. A dated, read-only copy saved every month.
  8. A monthly check against the other side's list and the payment certificate.

A simple reply-date rule

Reply date equals start date plus the period in weeks times seven, unless an agreed extension date is entered, in which case use that. Flag the row when no reply is recorded and today is within seven days of the date. With invented dates: a quotation sent on 10 June with two weeks allowed is due a reply on 24 June, flagged from 17 June. This counts calendar weeks, so check your contract for anything different, and read tracking periods for reply. Keep the date you became aware of a compensation event (the contract's term for something that can change your price or dates) in its own column so the eight-week check under clause 61.3 runs the same way.

Signs you have outgrown it

  • A reply was missed because the owner was away.
  • You had to work out which of two copies was right.
  • Someone spends a day each month reconciling it.
  • A senior manager asked for a view across contracts and it took a week.
  • You cannot quickly show when a notice was sent and who received it.

Whatever tool you choose, the routine matters more than the tool.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?