Claims are won on records you kept at the time — not the ones you reconstruct later.
Blockers with real stop/resume times, completions with photos, an append-only stock ledger — and one click bundles any declared window into an evidence pack, frozen with a content-hash attestation.
Daily Coordination Report
12 scenes · 3 critical
How the day actually runs.
- The claim
A delay claim lands for March
Six months later, someone else’s letter defines the battlefield. You open the window it names — time × area × contractor — and the record for exactly that slice is already assembled.
- The window
Blockers with the actual times
Each stoppage was declared when it happened: cause, affected permits, delay vs disruption, the real stop and resume times — countersigned by the other side, or formally disputed. Concurrent delay is simply visible: two windows, overlapping, on one timeline.
MonTueWedThuFriPlot 4 — L1Plot 4 — L2North laydownSubstation - The as-of
“What was in laydown B on March 3rd?”
Every stock movement is an append-only ledger entry, so the as-of question has an exact answer — the balance that day, derived from entries nobody could quietly edit afterwards.
RedExcavator vs. work area
Plot 4 · cross-contractor
RedCrane drop zone over road
North gate · 13:00–15:00
AmberTwo gangs within 5 m
Level 2 · same window
InfoDelivery booked — Plot 7
08:00 · 1 vehicle
- The pack
One click, one frozen bundle
The window becomes an evidence pack: a branded narrative PDF plus raw CSV and GeoJSON annexes, frozen with a content-hash attestation. “What did we hand the other side in March?” — this pack, these contents, this moment.
Daily Coordination Report
12 scenes · 3 critical
S-01S-02S-03
You've said these words before.
“We reconstruct claims across six systems, months later.”
The record was kept at the time, in one place, addressable by window — time × area × contractor — instead of excavated from emails, diaries and photos with no timestamps.
“Their lawyers call our records after-the-fact.”
Append-only entries and hash-attested packs answer the challenge structurally: the attestation proves what the bundle contained and when it was frozen.
“Concurrent delay is a shouting match.”
Overlapping blocker windows appear as overlaps on one timeline, each with its own countersignature or dispute — the argument becomes a picture.
“Delay and disruption get argued as one blob.”
Each blocker is declared as delay or disruption at the time, by the people who were there — not re-categorised to fit the claim two years on.
“As-planned vs as-built is spreadsheet archaeology.”
Issued-permit timelines are the as-planned leg, kept automatically as the site runs — the comparison baseline exists without anyone maintaining it.
“The weather data gets laughed out of the room.”
Pack weather sections label every figure as contemporaneous observation or later reanalysis — stated proudly, because honest provenance is what survives cross-examination.
A QS login that reads everything and touches nothing — sitewide records, evidence packs and exports, with no way to alter what it reads.
Your seat can
- Read the whole site across every contractor — live and back through time
- Generate evidence packs: narrative PDF, raw annexes, attestation hash
- Export the record for the claim file
- Use the audit view — who did what, when
Not this seat
- Move or edit any work — no entity mutation, full stop
- Touch permits, verdicts or any workflow — reading the record never changes it
Your QS never needed edit rights — now they don’t have them. The read-only seat is itself a credibility feature: the record’s keeper cannot be its author.
Start the record before the claim.
The pack you’ll need in two years is built from records kept today. Open the live demo and generate one — or bring a live dispute and we’ll show you the window.
No install · runs in the browser · scrubbed demo data