New project, from the planner
Renewing 3.2 km of water main under a live A-road. Night works over 14 weeks, trenches to 2 m, valve chambers to enter, 2 subcontractors.
What the system takes from itBehind the scenesA language model turns the planner's description, or the tender scope, into the features that drive risk: the type of work, where it is, when, how deep, who is on site.In this demoScripted reading of an invented job.
Today The risk register starts from the last job's template and the planner's memory.
0
incident and near-miss reports
0
safety inspections
0
lessons learned
0
past projects
One of 1,892, written on siteBehind the scenesEvery report is read the same way: what was being done, the hazard, the outcome and the cause, each pointing to the words it came from. Photos and scanned forms are read too.In this demoThe report is invented. In a real build this ran on the contractor's own data platform, reading structured and unstructured records side by side.What it achievesFive years of reports become something you can count, compare and learn from, instead of a folder.
Night shift, lane closure on the A-road. Excavator bucket struck an unmarked low-voltage cable at 1.1 m while exposing the main. No injury. Street lighting lost for three hours. The trench was scanned at the start of the shift but not again after it was widened.
Read as
25 of 96 past projects look like this oneBehind the scenesEach past project is described by the same features as the new one. The closest are found by comparing those features, and their incidents are pulled together by risk.What it achievesThe planner starts from what actually went wrong on work like this, not from a generic template.Could go furtherWeight recent projects more heavily, and include work by the same subcontractors.
Incidents on those projects, by risk, 212 in all
Severity
Likelihood
Each risk scored, likelihood times severityBehind the scenesLikelihood comes from how often each risk happened on similar projects, per hour worked. Severity comes from the worst outcomes recorded for it. Every score opens the past incidents behind it.AssumptionInvented archive. The scoring scale is the usual five by five; a contractor's own scale drops straight in.What it achievesScores a planner can defend, because each one has evidence.
Risk register, drafted for the plannerBehind the scenesEach control is drawn from the contractor's own lessons learned and the incidents behind the score, so it names what actually worked before.What is automatedDrafting the register, the controls and the owners. The planner edits and signs; every edit is kept.Could go furtherFeed the signed register into the construction phase plan and the daily briefing.
| Risk | Score | Control, from past lessons | Owner |
|---|---|---|---|
| Striking buried services | 25 | Scan again every time the trench is widened; hand dig within 500 mm of any marked service. | Site supervisor |
| Traffic next to the work at night | 25 | Barrier, not cones, on the live side; a lookout for every night shift; speed limit agreed before start. | Traffic management lead |
| Plant moving near people | 20 | Exclusion zones marked on the ground; a banksman for every reversing move. | Plant manager |
| Trench collapse | 15 | Trench support fitted before anyone enters; daily inspection signed off. | Temporary works coordinator |
| Entering chambers and confined spaces | 15 | Permit to enter, gas test and a top person on every entry. | Site supervisor |
| Fatigue on night shifts | 12 | No more than four nights in a row; a supervisor check at 03:00. | Project manager |
0
live projects in the pack
0
pages drafted overnight
0 hours
to review it, down from 3 days (modelled)
0%
of incidents on 12 projects since fell in a flagged risk (modelled)
Month-end pack, September 2026Behind the scenesThe ledgers, cost-to-complete forecasts and safety data land in one model. The pack is built from it overnight, and a language model drafts the commentary from the numbers only.AssumptionThree days of spreadsheets cut to two hours of review is our estimate. So is the 82% of later incidents falling in flagged risks.What it achievesThe same data that scores risk before a job starts reports on it every month after.
2 projects show cost to complete up more than 5% on last month. The commentary names the lines that moved.
Risk before work starts
Water main renewal, A-road, night works
Interactive demo
Watch it run in 92 seconds, or click through at your own pace. The i buttons show what happens behind the scenes.
That was one day
212 past incidents behind one risk report
Modelled on an invented contractor. Your own archive would give the real report.