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
- Review and Evidence
Review and Evidence
Keep reviewer outcomes and supporting evidence traceable.
OverviewReview decisions×
Safety / Incident Reporting · Review and Evidence
New
Review decisions
Review decisions
| Source revision | Decision | Decided at | Reason | Parent | Reviewer | |
|---|---|---|---|---|---|---|
| 840 | Approve | 05 Oct | Approve rd-736 | ASS-19863 | ||
| 290 | Return | 11 Oct | Reject rd-783 | ASS-83834 | ||
| 650 | Approve | 19 Oct | Return rd-225 | ASS-40065 | ||
| 880 | Return | 10 Oct | Approve rd-228 | ASS-90700 | ||
| 280 | Approve | 20 Oct | Reject rd-379 | ASS-50536 |
6 of 6 records
Approve rd-736Review decisions · RD-40203
ApproveSource revision840
Decided at05 Oct
ParentASS-19863
What you can do
Make the decision explainable
The Independent Reviewer records an outcome under the assessment with the examined source revision. Match the assessment and revision to the investigation before using that decision. Approve, Reject and Return are distinct decisions, each with a date, reason and reviewer. A returned case asks for correction; a rejected one records an adverse decision. The original source revision matters because the team must know which version was examined.
Evidence files can be attached to the assessment with a title, upload date, evidence type, visibility and uploader. Internal and Shared visibility help the team choose who should receive the material. Keep the file tied to the assessment that contains the tests, findings and investigation it supports. An attachment title should identify the case and purpose clearly enough for another reviewer to find it.
How the work is organized
- Attachment. The file and upload details provide the supporting record.
- Decision. The reviewer records an outcome and reason against a revision.
- Receipt. An operation receipt records the action, expected revision and actual result state.
Operation receipts can be Pending, Completed, Failed or needs review. They record the result of a guarded operation and give the team a place to inspect uncertain effects. A completed receipt should be read alongside the decision, retest and investigation status. The receipt is evidence of an operation result; it does not replace a professional judgment about the underlying safety case.
If a reviewer returns a case, keep the reason available to the Investigator while the record is corrected. The next decision should identify the revision it actually examined, so the team can distinguish the earlier concern from the later accepted account.
What to agree during setup
Set a rule for evidence titles and visibility. Choose the people allowed to upload Shared material and who may make review decisions. Agree when a changed source requires another review. Decide which failed or uncertain operation receipts need human attention and who investigates them. Retain the reason for Return or Reject so the next submission answers the specific concern.
Check the handoff on an actual case
Submit a near-miss investigation under an assessment with an evidence file attached to that assessment. The Independent Reviewer inspects the version and records a Return decision with a reason if the site evidence is incomplete. After correction, compare the new revision and record a new decision. Check the receipt’s result state before treating the operation as finished. The Safety Manager can then read the investigation, review and action records as one traceable case.
What your team sees
- Review decisions — Dated outcomes with reviewer and reason.
- Investigations awaiting review — Submitted cases ready for decision.
Follow the work through
Use incident review for decisions and action verification for the final evidence check.
What it keeps track of
Data model- Review decisions
- Independent reviewer outcomes recorded against a source revision
- Record attachments
- Files supporting tests, investigations and decisions
- Operation receipts
- Durable record of each guarded operation and its actual result state
- Retests
- Independent retest of a finding after remediation
- Assessments
- Period control assessments that scope risks, controls and testing
- Safety investigations
- Incident and near-miss investigations that support closing a verified corrective action
Who uses it
Permissions- Independent Reviewer
- , Safety Manager, Investigator, Admin.
Set up Safety / Incident Reporting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.