These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Safety / Incident Reporting
- Features
- Risks and Controls
Risks and Controls
Connect hazard risks to owned controls and operating units.
OverviewActive controls×
Safety / Incident Reporting · Risks and Controls
New
Active controls
Controls
| Control code | Description | Effective from | Status | Risk | Owner | |
|---|---|---|---|---|---|---|
| CC-287 | Active cnt-829 | 25 Oct | Active | RSK-2962 | ||
| CC-642 | Active cnt-420 | 07 Oct | Active | RSK-4452 | ||
| CC-104 | Active cnt-596 | 09 Oct | Active | RSK-5556 | ||
| CC-217 | Active cnt-486 | 08 Oct | Active | RSK-6081 | ||
| CC-565 | Active cnt-922 | 26 Oct | Active | RSK-4236 |
6 of 6 records
CC-287Controls · CNT-28139
ActiveDescriptionActive cnt-829
Effective from25 Oct
RiskRSK-2962
What you can do
Keep the hazard and control together
A Safety Manager records a risk against the operating unit where the hazard matters. Its title, likelihood, impact and scale version capture the assessment method being used. A control points back to that risk, identifies its owner and states when it became effective. Control status distinguishes a draft measure from one in use or one retired from use.
Suppose an operating unit identifies a vehicle movement hazard. The manager records the risk against that unit and assigns an owner. The related control describes the separation measure and its effective date. A Control Tester can record its code and reference the control in a test, then describe a failed result in a finding under the same assessment. That chain helps a reviewer understand which measure was tested, rather than reading an exception without context.
How the work is organized
- Risk ownership. The operating unit and named team member hold the hazard context.
- Control lifecycle. Draft, Active and Retired show whether a measure is current.
- Test connection. A control test references the measure and carries the observed result.
A control’s owner is separate from the person who tests it. A finding connects to both the assessment and control, so the manager can see where a gap appeared. Keep retired controls available for past findings and tests; changing current practice should not erase the older explanation. The scale version makes comparisons of likelihood and impact more understandable when the team updates its method.
What to agree during setup
Agree the meaning of likelihood and impact scores and record the scale version. Decide when a control becomes Active, how an effective date is chosen and who can retire a control. Choose control codes that a tester can reliably enter or select. Keep operating-unit ownership current when people or site responsibilities change.
Check the handoff on an actual case
Choose a hazard from one operating unit. Record its score and owner, then connect an Active control. Add a test result with an exception and raise a finding. The reviewer should be able to move from the finding back to the same control, risk and operating unit. If the control is retired later, the past test must still be interpretable through its original reference. Ask the Control Tester to compare the entered control code with the linked control before presenting that test to the reviewer.
What your team sees
- Active controls — Measures currently in use, with owner and risk context.
- Tests with exceptions — Failed tests that need attention.
Follow the work through
See assessment and testing for control checks and finding to action for exceptions.
What it keeps track of
Data model- Risks
- Hazard risks scored on an explicit likelihood and impact scale
- Controls
- Controls implemented against a risk, with ownership and effective date
- Business units
- Sites, plants and operating units where safety work happens
- Assessment tests
- Individual control tests with sample size, exceptions and evidence
- Findings
- Control failures or gaps raised by testing
- Team members
- Named people holding safety roles inside an organization
Who uses it
Permissions- Safety Manager
- , Control Tester, Independent Reviewer.
Set up Safety / Incident Reporting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.