Every CSM-REA significant change must carry a hazard record, and every scheme rebuilds one from scratch: HAZID by HAZID, ALARP argument by ALARP argument, until the log is handed over and goes quiet. Hazlog keeps that record live, connected across schemes, and signed by your competent person.
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. No lists sold, no partners, unsubscribe with one reply.
Digital Hazard Log.New changeDraft PHLRegister
1
Describe the change, in plain English
The way you would brief it at the HAZID, not the way a form wants it
We are replacing the precast concrete parapet on Footbridge 12. Night-time possessions Tuesday and Wednesday.The bridge spans 4 tracks. The down-side wing wall was flagged in CP6 inspections 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 register, waiting for the workshop
Drafted from the change and from prior accepted schemes. Every row is advisory until a person accepts it
Ref
Hazard
Unmit.
Status
FB12-001
Falling material over live track during demolition
High
DRAFT
FB12-002
Wing-wall scour worsening under storm loading
High
DRAFT
FB12-003
Worker entering the adjacent open line during possession
High
DRAFT
FB12-004
Manual handling of precast panels at height
Med
DRAFT
9 hazards drafted, with the prior schemes they came from. The HAZID votes F×C, ALARP is argued, and a competent person signs. The system never scores and never closes a hazard.
3
A register that stays open after handover
Months later. The project is closed. The record is not
Open hazards
147
Intolerable residual
3SFAIRP
Trigger conditions live
38
Evidence traced
96%
Storm warning matched — wind threshold reached on 2 open hazardsFlagged automatically from a live weather feed. Each one waits for a competent person to accept or reject the re-review.Re-review · 2
Ref
Hazard
Residual
Status
FB12-002
Wing-wall scour worsening under storm loading
Intolerable→Tolerable
Re-review
FB12-001
Falling material over live track
Intolerable→Tolerable
Closed ✓
EC-007
Wing-wall instability, storm loading inherited from a prior scheme
Tolerable→Tolerable
Re-review
Hazards attach to the asset, not the project. The next scheme on this bridge starts from here, not from a blank workbook.
Interface concept, from our working demo. Hazlog is in build now, with UK rail partners.
This is a capacity problem wearing a paperwork costume.
Three things are true at once, and they compound.
01
The obligation recurs
A hazard record is a legal requirement under CSM-REA, overseen by the ORR and mandated through the NR/L2/RSE/100 series. It lands on every significant change, on every scheme, forever.
02
The knowledge walks out
Experienced engineers are retiring faster than they are replaced. Safety knowledge that lives in people and project spreadsheets leaves with them, and the next scheme starts from a blank workbook.
03
Capacity is the constraint
Your programme is growing and your team is not. The intent is never a smaller team. It is the same engineers spending their hours on judgement, not on assembling and re-assembling a record.
It speaks railway.
Not a generic risk tool with the word rail typed into it. Hazlog is built around the obligations your record already answers to.
CSM-REA
The risk evaluation and assessment regime your significant changes run under, overseen by the ORR
NR/L2/RSE/100
The Network Rail standard series that mandates how the hazard record is kept
ROGS 2006
The safety regulations the duty holder answers to
CDM 2015
Pre-construction information and the Health and Safety File the record feeds
HAZID & ALARP
F×C voting in the workshop, ALARP argued and evidenced, per your own matrix
SFAIRP
Residuals carried honestly, with the evidence trail that proves the position
What changes when the record is live.
A first draft from the change description. Plain language in, a structured draft out, waiting for competent-person review.
A register you can interrogate. Open hazards, high residuals, missing evidence: asked in a sentence, answered from the record.
Prior hazards resurface. On a comparable new change, accepted hazards from earlier schemes present themselves for consideration.
The record survives handover. Hazards attach to the asset, not the project, so the log persists into operation and renewal.
Nothing is accepted without a signature.
Every hazard, every residual, every closure is gated by your competent person. Hazlog 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. Nothing else, ever.