The Safety Requirements Register ensures a requirement only ever gets a row once a person explicitly confirms a candidate the Applicability Engine proposed — never inserted automatically.
Intelligence
Safety Requirements Register
The confirmed-requirement record a human creates by approving an Applicability Engine candidate.
Available
Overview
The Safety Requirements Register only ever gains a row when a human explicitly confirms a candidate the Applicability Engine proposed. Nothing here is ever inserted automatically.
Every confirmed requirement keeps a permanent record of why it exists, so that justification survives even if circumstances later change. Confirmed Safety Requirements are retained in SafetyOps with their justification, confirmation history and source context, and can be reviewed through the Company Compliance Profile.
Why it matters
'Why does SafetyOps say we need this?' is a question every safety manager will eventually ask. The Register exists so that question always has a real, permanent, attributable answer.
Benefits
Never automatic
A row only exists because a human explicitly confirmed it.
Permanently attributable
Confirmation is mandatory and can't silently disappear if a user account is later removed.
Versioned, not edited
Superseding a requirement creates a new version — the original record is never altered in place.
Workflow
- The Applicability Engine proposes a candidate topic.
- A human (owner or administrator) reviews it and explicitly confirms.
- A permanent, attributed Safety Requirement record is created, snapshotting exactly why.
- If circumstances change, the requirement is superseded by a new version — never silently edited.
Interface
A dedicated interface for this module already exists in the SafetyOps application.
Frequently asked questions
Is the Safety Requirements Register live today?
Yes. Confirmed Safety Requirements are retained in SafetyOps and reviewed through the Company Compliance Profile, reached from Company Setup.