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
- Assessments
Assessments
Keep each operating period, scope and safety owner clear.
OverviewMy assessments×
Safety / Incident Reporting · Assessments
New
My assessments
Assessments
| Record number | Subject | Status | Period start | Period end | Owner | |
|---|---|---|---|---|---|---|
| ASS-31442 | Draft ass-661 | Draft | 17 Oct | 19 Oct | ||
| ASS-62713 | Planned ass-867 | Planned | 25 Oct | 02 Nov | ||
| ASS-41392 | Testing ass-373 | Testing | 06 Oct | 14 Oct | ||
| ASS-34186 | Review ass-872 | Review | 19 Oct | 23 Oct | ||
| ASS-59778 | Approved ass-159 | Approved | 16 Oct | 25 Oct |
6 of 6 records
Draft ass-661Assessments · ASS-31442
DraftPeriod start17 Oct
Period end19 Oct
What you can do
Give the safety work a defined period
The Safety Manager creates an assessment for a named organization and operating unit. Its subject, period and scope statement tell the team which risks and controls are being checked. The owner holds responsibility for the assessment as testing and investigation work arrives. Planned tests provide an expected work volume; actual test records show what has been done.
An assessment should make its boundaries understandable to a new reviewer. A plant assessment covering the current quarter is a different record from an organization-wide annual review. The operating unit, period start and period end help a tester choose the right parent for a control test. An incident investigation can then be linked to the same assessment without losing its separate event date.
How the work is organized
- Scope. The Safety Manager records the organization, operating unit, owner and period.
- Testing. Control Tester adds test records against controls within the assessment.
- Review. The owner checks findings, decisions and remediation before closure.
Draft, Planned, Testing, Review, Approved, Remediation and Closed describe the assessment’s progression. Move the status when the underlying work has reached that point. For example, a failed test should lead to a finding and a named action owner, rather than moving straight from Testing to Closed. The approval date records when the assessment was accepted; the review decision record carries the independent decision detail.
What to agree during setup
Define the assessment period and who owns scope changes. Decide how the team chooses the operating unit when several sites share an organization. Set a consistent approach to planned tests, control codes and evidence references. Agree when a finding can move to retest and who checks the final assessment after remediation.
Check the handoff on an actual case
Create an assessment for one operating unit with a period that includes a recent incident. Link a control test, a finding and an investigation to it. Check that the Control Tester can see the right scope and that the Safety Manager can trace the failed result into corrective work. At review, compare planned tests with recorded results and read the decision reason before accepting the period outcome. Check that every finding cited in the review belongs to this assessment and that its owner can explain the next action.
What your team sees
- My assessments — Period work assigned to the current owner.
- Active assessments — Work in planning, testing, review or remediation.
- Assessment schedule — Start and end dates for planned work.
Follow the work through
Start with assessment and testing, then follow finding to action.
What it keeps track of
Data model- Assessments
- Period control assessments that scope risks, controls and testing
- Business units
- Sites, plants and operating units where safety work happens
- Organizations
- Employers and legal entities in scope for safety governance
- Assessment tests
- Individual control tests with sample size, exceptions and evidence
- Findings
- Control failures or gaps raised by testing
- Safety investigations
- Incident and near-miss investigations that support closing a verified corrective action
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.