Built by safety engineers, for safety engineers
Bring your log across from Excel, CSV or DOORS. Every cause links to the controls that answer it, and every change is reviewed by a second person before it counts.
50% off with code FORGEDSAFE at checkout.
Keep your whole hazard log in one place, with every hazard linked to its causes, its controls and the requirements behind them. Bring it in from Excel, CSV or DOORS and your agent repairs the links. A second person approves every change.
Try it: one risk from the sample railway. Open a cause or a control, follow the links, then switch to Edit mode.
The demo uses a fictional railway, the Mystical-Mountain Steam Train, and runs entirely in your browser: nothing is saved or sent.
Key barrier states drawn from the findings of the Cullen Inquiry (2001); some barrier detail added for demonstration. Hover any cause, barrier, or consequence for detail. Greyed, crossed barriers were absent or rejected before the event.
A SPAD occurs when a train passes a stop signal without authority — one of the classic precursors of rail collision. The causes span engineering, environment, and human performance; most SPADs end as near misses, which is exactly why weak signals accumulate quietly in the data until the barriers align against you. SPADs drove three major UK accidents in a decade: Purley (1989), Southall (1997), and Ladbroke Grove (1999).
This bow-tie summarises a real accident: 31 lives were lost at Ladbroke Grove. The inquiry found the gaps were visible beforehand — 8 SPADs at signal SN109 in six years with no effective corrective action; signal-sighting committees never convened around Paddington since 1994 despite two audits; and ATP rejected on cost-benefit grounds after being recommended following Clapham Junction (1988). Diagram simplified from the public findings, for education.
This is the purpose of SafeForge — we help you forge Safe Systems.