Platform module Roadmap module
Risk & Impact Assessment
Hazards scored on a matrix you configure, controls that actually change the number, and treatments that become actions.
Try it
The control changes the score. Not the rule.
Score the hazard, then add the engineering control. The likelihood drops and the score drops. The verification requirement stays exactly where it was. BSLR gates verification on consequence, not on the computed score, because a fatality risk that is “unlikely” is still a fatality risk. Try it.
Reviews that chase themselves.
Review dates are owned
Every assessment carries a next-review date. Due soon appears in the owner's digest; overdue escalates up the reporting chain: same mechanics as any action.
Treatments are actions
A risk treatment is not a note in a spreadsheet column. It is a tracked action with an owner, a verifier and a due date, linked back to the assessment.
Workforce consulted, on record
Assessments record who from the crew was consulted: the ISO 45001 §5.4 evidence auditors ask for, captured at the moment it happens.
Scroll the image sideways to read it →

The register: inherent and residual side by side, consultation recorded, and a review date that escalates when it slips.
BSLR product interface · illustrative data, fictional tenant “Vantera Engineering & Contracting” · Roadmap module
Aspects & impacts, same engine.
Environmental aspects and impacts are assessed with the same matrix, the same review cycle and the same treatment mechanics: ISO 14001 §6.1.2 alongside ISO 45001 §6.1, with ISO 31000 as the method underneath. One approach your auditor sees everywhere.
Bring us the risk register you don't trust.
A walkthrough runs about thirty minutes. Bring one real assessment and score it live.