Walk the site without leaving the cabin — and prove it ran right.
The live map at 07:00 shows who’s already in. Permits move through both gates, findings become actions that actually close — and the record of how your site was run writes itself down daily, while it runs.
How the day actually runs.
- 07:00
The site, live
Presence shows who’s already signed in and looking. Every crew, plant item, delivery and work window sits on one current map — the picture you used to assemble from four phone calls.
- 09:20
Both gates moving
Permit requests flow endorsement → issue with named issuer appointments. You watch the board move without being the person every request waits on.
- 11:45
The programme, against reality
The Work home’s Reality view holds the site up against the master programme: issued permits aggregated into a contractor × place × day matrix. When the P6 says level 3 and the site says level 5, you know before the progress meeting does.
- 13:40
“Did anyone actually fix that?”
The actions band answers it: close-outs arrive with photo evidence and get accepted or bounced on the record. Open means open, closed means fixed.
- 17:30
The day writes itself down
The site diary has filled its own cells — weather, labour, the permits that ran — and the round’s answers are in, attributed and append-only. At the deadline a sweep publishes Revision A: an immutable PDF, in the client’s inbox by morning. No one stayed late to write it.
You've said these words before.
“The wall plan is three days old.”
The map is the model, not a printout of it. Scrub to any hour — tonight’s shift, Thursday’s lift — and see what the site will actually be doing.
“I’m the bottleneck for every decision.”
Seats and gates distribute the work: coordinators endorse, HSE signs verdicts, contractors run their own crews. You see all of it move without touching each piece.
“Did anyone actually fix that?”
Closure is earned, not declared — actions close on accepted photo evidence, incidents close only when their actions are done. The question stops needing to be asked.
“The site diary gets written at 7pm from memory.”
The diary fills itself from the platform’s own record and asks people only what it can’t know — during the day, from their phones. It publishes on schedule by a sweep, not a button, and corrections are issued as revisions, never edits.
“When the client asks how the site was run, it’s anecdotes.”
It’s an audit trail: permits, verdicts, stoppages, completions, day by day — topped by an immutable daily diary that lands in the client’s inbox every morning. Retire the monthly deck.
The deputy-admin: everything the site runs on, minus a deliberately short list — admin governance and irreversible deletion.
Your seat can
- The full coordination surface — entities, exports, reports
- Both permit gates, with named issuer appointments
- The full H&S band — triage, verdicts, inspections, RAMS lanes
- Author the site’s inspection templates: the audit regime is yours to set
- Read the Work home’s Reality view: the contractor × place × day matrix against your programme
- Hold the site diary’s write band, and the audit view of who did what, when
Not this seat
- Author admin governance — the admin-only site settings and notification rules stay with the site’s admins, and only an admin can mint an admin
- Delete irreversibly — the record survives everyone, including you
One seat that sees the whole machine without being able to quietly rewire it — that’s the point.
See your whole site in one window.
Open the live demo and walk it from the cabin — or bring a floor plan and this month’s permit sheet, and we’ll show you your own site running.
No install · runs in the browser · scrubbed demo data