Construction safety,
mapped in space and time.
SimOps maps every work area, plant item, zone and person on a live site — and flags where they're about to collide, before anyone is on the ground.
22× faster clash compute after our engine rework 82% fewer clash alerts on a live site proven at 10,000-worker scale
Running live on a major-hazard energy-from-waste site in the UK — every shift, every trade.
phantom alerts eliminated on one live site — with a deterministic proof that zero real hazards were lost.
full week-window clash recompute on that site — down from 13.3s before our engine rework (22×).
workers on the largest production site — with ~11k spatial entities and 244 permits.
automated test files; every clash-engine change gated by a parity oracle that fails on any removed hazard.
Your site, in space and time.
Not a drawing of the plan — a model of it. Every work area, plant item, zone and person carries its time window, so the site you see at 14:00 is the site that exists at 14:00.
Drag. That's tomorrow. This is what your site looks like an hour before the night shift — and the clash that exists only while two windows overlap.
Catch spatial conflicts before they happen.
A declarative rules engine checks where work areas, plant drop zones and people overlap in space and time — and ranks every clash by severity.
- Spatial and temporal rules across work areas, plant, zones and people.
- Severity-ranked red / amber so the worst conflicts rise to the top.
- Building-aware — no clashing through a wall or between floors.
Your plan, pre-filled from approved permits.
Bring your permit spreadsheet and SimOps reads it — generating the schedule, zones and contractors so the digital plan matches what was signed off.
- Import permits straight from your XLSX — config-driven for any layout.
- Entities, zones and time windows pre-filled from the approved permit.
- Every permit rests on the exact RAMS revision it was approved against — hash-frozen at submit. A later upload warns; it can never silently re-paper an approved permit.
Detection is half the job.
SimOps pushes each clash to the right person — noticeboard, notification, task — and the morning briefing writes itself from the scenes a coordinator accepts.
- A rules engine routes site events to the right seat, in-app or by email.
- Action-requiring pings become tracked tasks, not read-and-forgotten toasts.
- The report wizard ranks the day’s clash scenes and renders a branded PDF or Word doc.
Daily Coordination Report
12 scenes · 3 critical
Find it. Fix it. Prove it.
A hazard seen is worth nothing filed in a spreadsheet. SimOps runs the whole loop — report, triage, action, evidence, closure — and nothing closes until the fix is real.
Anyone on site reports a hazard in 30 seconds.
A QR poster at the gate or the site’s geofenced URL — no app, no login, no name required. Photo, a tap on the 5×5 grid, GPS evidence. HSE triage gates what the site sees.
- Anonymous by default — friction and fear both removed.
- Photo, severity tap-grid and location evidence attached at the source.
- The geofenced URL only serves on site — containment by GPS.
Excavator vs. work area
Plot 4 · cross-contractor
Crane drop zone over road
North gate · 13:00–15:00
Two gangs within 5 m
Level 2 · same window
Delivery booked — Plot 7
08:00 · 1 vehicle
Every failed check becomes an action with an owner.
Templated, versioned checklist audits — and a failed item mints a corrective Action on the spot: one accountable company, a due date, mandatory photo evidence at close-out. HSE accepts it or bounces it back, on the record.
- Versioned inspection templates — the audit you planned, every time.
- Fail → Action: one owner, one due date, no orphaned findings.
- Close-outs carry photo evidence; a rejection returns it with the rework count.
Excavator vs. work area
Plot 4 · cross-contractor
Crane drop zone over road
North gate · 13:00–15:00
Two gangs within 5 m
Level 2 · same window
Delivery booked — Plot 7
08:00 · 1 vehicle
An incident only closes when its actions are done.
The 5×5 severity matrix, the chain of events, causes pinned to Swiss-cheese barrier layers, RIDDOR accounting — and closure that is derived, not declared. A rejected fix reopens the case.
- Structured investigation: severity, event chain, barrier analysis.
- RIDDOR reportability captured as data, ready for the regulator.
- Derived closure — nobody box-ticks past an outstanding action.
Excavator vs. work area
Plot 4 · cross-contractor
Crane drop zone over road
North gate · 13:00–15:00
Two gangs within 5 m
Level 2 · same window
Delivery booked — Plot 7
08:00 · 1 vehicle
When the claim lands a year from now, the record already exists.
Everything above leaves a contemporaneous, tamper-evident trail — declared when it happened, by the people who were there.
Declare the stoppage while it's happening.
Cause, affected permits, delay vs disruption, the actual stop and resume times — countersigned or disputed on the record. Work completed is photographed day by day, and every stock movement is an append-only ledger entry.
- Concurrent delay is visible: overlapping windows on one timeline.
- Completions with photo evidence — the as-built record, kept as you build.
- The ledger answers as-of questions exactly: what was in laydown B on March 3rd.
One click. One window. One frozen pack.
Bundle a declared window — time × area × contractor — into a branded narrative PDF with 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.
- Attestation hash: the pack proves its own contents and its moment.
- Weather sections label contemporaneous observation vs later reanalysis — honestly.
- The commercial seat reads everything and touches nothing — your QS never needed edit rights.
Daily Coordination Report
12 scenes · 3 critical
One live model. Six ways to need it.
“The 8am briefing writes itself.”
Your day in SimOps HSE“Findings stop dying in spreadsheets.”
Your day in SimOps Contractors“Your crew visible. Your evidence kept.”
Your day in SimOps Site managers“The whole site, actually current.”
Your day in SimOps QS & commercial“Claims are won on records you kept at the time.”
Your day in SimOps Clients“See the site run — without asking for a report.”
Your day in SimOpsClash intelligence that respects time, not just space.
SimOps validates that work actually coexists — same shift, same place — so coordinators chase real conflicts instead of phantoms from impossible schedules.
Phantom alarms gone — provably
Time-validated coexistence eliminated 11,893 schedule-impossible alerts on one live site, with a deterministic check that zero real hazards were lost.
Hazards as data, not code
Clash rules live in the database. Tune a proximity distance or add a hazard interaction without a redeploy.
Every session in sync
WebSocket presence, live entity updates and conflict-free concurrent polygon editing keep every seat on one shared picture.
Tamper-evident records
Hash-attested evidence packs, briefing signature chains and append-only ledgers — records built to survive hostile questions.
Find out how SimOps fits your next project.
A 30-minute walkthrough on a site that looks like yours.
Want to see it on your site?
Bring your permits and a floor plan. We'll show you the clashes you're carrying today — and the report that clears them.
No install · runs in the browser · scrubbed demo data