HAZLOG.ai Join the waitlist
For UK rail · launching 2027

The hazard log that stays open.

The asset carries its own safety knowledge. Live, queryable, bound to the asset at its real location, and signed by your competent person.

HAZLOG.ai New changeDraft logMapAsset watchSample scheme, for illustration
1
Describe the change, in plain English
The way you would brief it at the HAZID, not the way a form wants it
CSM-REA change description · Footbridge 12 parapet replacement
We are replacing the precast concrete parapet on Footbridge 12. Night-time possessions Tuesday and Wednesday. The bridge spans four tracks. The down-side wing wall was flagged at the last exam for scour after heavy rainfall.
Draft the hazard log

Nothing else to fill in. The record starts where your knowledge already is.

2
A draft log, carried forward, not conjured
It reads what already exists: Health and Safety Files, prior schemes' logs, this asset's own history, similar assets at similar locations. Watch it gather
RefHazardCarried fromStatus
FB12-001Falling material over live track during demolitionPrior scheme on this lineDRAFT
FB12-002Wing-wall scour worsening under storm loadingThis asset's inspection historyDRAFT
FB12-003Worker entering the adjacent open line in possessionGeneric record, possession workingDRAFT
FB12-004Manual handling of precast panels at heightYour change descriptionDRAFT

The HAZID still votes F×C. ALARP is still argued. A competent person still signs. The draft changes where the workshop starts, never what it decides.

3
Hazards live on the asset, at its real location
Each asset carries its record as a digital perimeter. Real weather tests the declared conditions. Drag the front, or keep scrolling
Amber warning, wind and rain, crossing the patch. Four assets, each carrying its own live record. Sample patch, Sussex. Not live data.
4
The project closed months ago. The asset did not.
What the designer declared keeps acting for whoever is accountable now
Embankment, Brighton Main Line. Rainfall threshold met. The scour hazard accepted at design is re-opened for review; the route asset engineer holds the decision on a line speed restriction.
Re-review
Wing wall, East Croydon. Wind threshold met on a residual carried from a scheme that closed years ago. The maintainer it belongs to now is the one notified.
Re-review
Footbridge 12. Residuals carried into the Health and Safety File, still live. The next scheme on this bridge starts from here, not from a blank workbook.
Carried

Line speed, closures, timetable, monitoring: the decisions stay human. The record's job is to make sure the knowledge is standing next to the person who has to make them.

01 · Describe the changeBrief it the way you would at the HAZID.

02 · The draft gathersCarried forward from what already exists. Every entry traceable.

03 · Real weather tests the recordTwo assets re-open for review. Two do not. Nothing lands in an inbox.

04 · Alive after handoverThe knowledge stands next to whoever is accountable now.

What a designer knows at design time does not survive to the people accountable years later.

Design assumptions, accepted residual risks, declared service lives: written into documents, archived at handover, and in practice never read again. Three things follow, and they compound.

  1. The accountability moves. The knowledge does not.

    At handover the accountable party changes. What the designer accepted, and why, stays behind in an archive nobody machine-reads. The person now carrying the risk inherits the asset without its reasoning.

  2. The record cannot see the world.

    A storm, a heatwave, a scour warning. The log holds hazards whose conditions are being tested by real events, and notices none of them. Nothing in a static spreadsheet can evaluate itself against what is actually happening.

  3. Every scheme starts from scratch.

    Each new project on the same asset begins the hazard work again. What the last scheme accepted, argued and signed is re-derived instead of inherited, on every scheme, forever.

It speaks railway.

Not a generic risk tool with the word rail typed into it. HAZLOG.ai is built around the obligations your record already answers to.

  • CSM-REAThe risk evaluation and assessment regime your significant changes run under, overseen by the ORR
  • NR/L2/RSE/100The Network Rail standard series that mandates how the hazard record is kept
  • ROGS 2006The safety regulations the duty holder answers to
  • CDM 2015Pre-construction information and the Health and Safety File the record feeds
  • HAZID and ALARPF×C voting in the workshop, ALARP argued and evidenced, per your own matrix
  • SFAIRPResiduals carried honestly, with the evidence trail that proves the position

The effect is physical, not administrative.

  • Line speed reduced around a compromised embankment, because the log knew which hazard a rainfall warning was testing.
  • A station closed ahead of flooding, not after it, because the declared condition met a live forecast.
  • A timetable adjusted ahead of extreme heat, on the sections whose assets actually carry the susceptibility.
  • Monitoring deployed to the specific assets a warning affects, rather than a patch-wide email nobody can act on.

The decisions stay human. The knowledge arrives in time to make them.

Nothing is accepted without a signature.

Every hazard, every residual, every closure is gated by your competent person. HAZLOG.ai changes the effort, not the accountability. The record stays yours, and so does the judgement. Early access starts with UK rail teams, in 2027.

You are on the list. We will write when early access opens for UK rail teams. Nothing else, ever.

That did not go through. Try again in a minute, or email bill.guo@automatex.uk and we will add you by hand.

Your email is used for one thing: telling you about HAZLOG.ai. No lists sold, no partners, unsubscribe with one reply.