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
- Investigations
Investigations
Record an incident or near miss and prepare it for independent review.
OverviewCompleted investigations×
Safety / Incident Reporting · Investigations
New
Completed investigations
Safety investigations
| Status | Site | Occurred at | Decision at | Parent | |
|---|---|---|---|---|---|
| Completed | STE-763 | 12 Oct | 16 Oct | ASS-67417 | |
| Completed | STE-498 | 14 Oct | 18 Oct | ASS-63796 | |
| Completed | STE-258 | 07 Oct | 15 Oct | ASS-99896 | |
| Completed | STE-156 | 27 Oct | 03 Nov | ASS-35581 | |
| Completed | STE-693 | 13 Oct | 22 Oct | ASS-56169 |
6 of 6 records
STE-763Safety investigations · SI-22018
CompletedOccurred at12 Oct
Decision at16 Oct
ParentASS-67417
What you can do
Put the event in context
An Investigator opens an investigation for an incident or near miss and connects it to the relevant assessment and organization. Record the site and occurrence date while the details are fresh. The severity rank and corrective action description help the reviewer understand what happened and what response is being considered. The assessment connects this account to the period, operating unit and controls under review.
Suppose a near miss occurs at a plant entrance. The Investigator records the site, occurrence date and observed hazard, then checks which assessment covers that operating unit. A control test under the same assessment may reveal an exception, and the finding gives the action owner a specific gap to address. Keep the original event account clear even as the response develops.
How the work is organized
- Draft account. The Investigator records site, occurrence and the proposed corrective action before submission.
- Submitted review. The Independent Reviewer sees the source revision and supporting evidence before deciding.
- Recorded outcome. The decision and subsequent status show whether the investigation can be completed.
An investigation may move from Draft to Submitted, Approved, Rejected or Completed. Those states should describe the actual decision reached, rather than a desired finish date. A rejected investigation needs a reason and a corrected account before another review. A decision belongs to the assessment and identifies the examined revision; compare both before using it for this investigation. The reviewer should be able to find the related assessment, action evidence and retest when assessing the submitted version.
What to agree during setup
Agree who may submit the investigation and who serves as Independent Reviewer. Define the team’s meaning of severity rank and where supporting evidence belongs. Choose a consistent way to identify sites so an incident can be compared with the operating unit on its parent assessment. Confirm what a completed investigation means in the organization’s operating practice.
Check the handoff on an actual case
Take a real near miss through a draft account, finding, action and retest. The Investigator should see the current status; the reviewer should see the same site, occurrence and revision that were submitted. Record a Return or Reject decision with a reason when the evidence is insufficient. After an accepted decision, compare the investigation with the finding’s action evidence and passing retest before marking it complete.
What your team sees
- Investigations awaiting review — Submitted incidents ready for an independent decision.
- Investigation board — Working incident accounts grouped by status.
- Completed investigations — Closed accounts with a recorded decision date.
Follow the work through
Use incident review for the decision handoff and action verification for the finding response under the same assessment.
What it keeps track of
Data model- Safety investigations
- Incident and near-miss investigations that support closing a verified corrective action
- Assessments
- Period control assessments that scope risks, controls and testing
- Corrective actions
- Remediation work assigned to a finding owner
- Review decisions
- Independent reviewer outcomes recorded against a source revision
- Record attachments
- Files supporting tests, investigations and decisions
Who uses it
Permissions- Investigator
- , Independent Reviewer, Safety Manager.
Set up Safety / Incident Reporting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.