Records Win Disputes: Building the Evidence Pack Before You Need It

Every construction law update ends the same way: keep good records. It is the most repeated and least operationalised advice in the industry. Repeated, because it is genuinely how disputes are decided — White Constructions Pty Ltd v PBS Holdings Pty Ltd [2019] NSWSC 1166 turned on a site diary that didn't say what the claimant needed; the referees in Santos v Fluor [2025] QSC 184 rewarded the delay analysis grounded in contemporaneous records; the disruption expert in Civil Mining & Construction Pty Ltd v Wiggins Island Coal Export Terminal Pty Ltd [2017] QSC 85 was criticised for a baseline his records couldn't honestly support. And least operationalised, because "good records" is not a specification. This is the specification.

Why contemporaneity is the whole game

Tribunals trust documents made when nobody knew there would be a dispute, and discount everything reconstructed afterwards. A delay narrative assembled two years later from memory is advocacy; a diary entry made the day the crane stood down is evidence. The legal doctrines we write about elsewhere — common-sense causation, measured mile baselines, time-bar compliance, prolongation cost proof — all collapse to the same operational question: what did you write down at the time?

The discipline pays even when nothing goes wrong. Projects with real records settle claims faster and cheaper because there is less to argue about. The evidence pack is not dispute preparation; it is commercial infrastructure.

The site diary, specified

A diary that says "wet day, reduced works" loses claims. A diary worth keeping captures, daily, in a consistent structure:

• Labour: each crew/subcontractor, headcount, location, the activity actually worked — and where crews were idle or relocated, why, in plain words ("D&B gang stood down — awaiting RFI 114 response, moved to Level 3 fitout").
• Plant: items on site, working or standing, and the reason for standing time.
• Progress: activities started, progressed (with measurable quantity where possible), completed.
• Events: instructions received (by whom, from whom, oral or written), access or information constraints, inspections, test results, incidents, visitors.
• Conditions: weather and its actual effect ("rain 10am–2pm; concrete pour deferred; excavation continued").

Two rules make it forensic-grade. First, the reason is the record — idle time without its cause proves nothing. Second, consistency beats eloquence — the same fields, every day, signed and dated, in a system that timestamps entries and prevents retrospective editing.

The registers that preserve entitlement

Around the diary sit five registers, each a one-page live document:

1. Notice register — every contractual notice issued and received: clause, trigger date, deadline, service method, response due. The defence against every time-bar trap we have written about, reviewed weekly.
2. Delay event register — each delay event as it emerges: cause, ownership (principal-risk, contractor-risk, neutral), affected activities, linked notices, status. This is what makes concurrency arguments winnable.
3. Variation register — directions (written and oral, with the confirmation request issued for oral ones), pricing status, approval status. After Kaloriziko v Calibre [2025] NSWCA 259, also track which "approved" values remain provisional "on account".
4. RFI/information register — what was asked, when, answered when, and what work waited on it.
5. Daywork/resource records for disputed or changed work, signed daily where the contract allows.

Programme and photo discipline

The programme is statused honestly each month — actual starts, actual finishes, genuine percent-complete — and archived, every cycle, unedited. A contemporaneous record of what was driving completion each month is the raw material of every credible delay method; a baseline updated only when claims loom is an exhibit for the other side. Photos and video: dated, located, systematic (same vantage points weekly, plus event-driven capture), stored against the work breakdown — not scattered across personal phones that leave when the engineer does.

Cost records complete the pack: cost codes that can isolate time-related preliminaries by period and disruption by work front. Prolongation and measured-mile claims are built from exactly this granularity, and fail without it.

What this means in practice

1. Specify it, assign it, audit it. A one-page records standard per project: the diary fields, the registers, the photo protocol, the programme cycle — with named owners and a monthly ten-minute audit. Systems fail at the level of ownership, not intention.
2. Write reasons, not just facts. Train site staff that every idle resource, every resequencing, every deferred activity gets its cause recorded in plain English the same day. This single habit converts a diary from logbook to evidence.
3. Capture the oral instructions. The recurring entitlement-killer is the oral direction acted on and never confirmed. Standing rule: every oral instruction is confirmed in writing within 24 hours, and logged.
4. Archive immutably. Monthly programme files, diary exports, photo sets — snapshotted and locked. The value of contemporaneous records is destroyed by any suggestion of after-the-fact editing.
5. Run a quarterly "claim-readiness" pass. Pick one live issue and dry-run it: could we prove this delay path, this disruption, this variation entitlement from the records as they stand today? The gaps you find are cheap to fix now and unfixable later.

Key takeaways

• Disputes are decided on records made at the time; reconstructed narratives are discounted (White Constructions; Santos v Fluor).
• A forensic-grade site diary records labour, plant, progress, events and conditions — with the reason for every idle hour.
• Five live registers — notices, delay events, variations, RFIs, daywork — convert daily records into preserved entitlement.
• Honest monthly programme statusing and immutable archiving are what make any delay analysis method possible later.
• Treat the evidence pack as commercial infrastructure with named owners and audits — not as dispute preparation.

This article is general information only and is not legal advice. For advice on a specific contract or dispute, seek legal counsel or contact Sumit Consulting for commercial and claims advisory support.