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
- Testing and Findings
Testing and Findings
Turn sampled control results into specific findings.
OverviewFailed tests×
Safety / Incident Reporting · Testing and Findings
New
Failed tests
Assessment tests
| Control code | Tested at | Sample size | Exception count | Result | Parent | |
|---|---|---|---|---|---|---|
| CC-116 | 26 Oct | 690 | 25 | Fail | ASS-74542 | |
| CC-813 | 15 Oct | 30 | 24 | Fail | ASS-96711 | |
| CC-673 | 23 Oct | 330 | 38 | Fail | ASS-45950 | |
| CC-706 | 19 Oct | 480 | 10 | Fail | ASS-51620 | |
| CC-787 | 19 Oct | 590 | 3 | Fail | ASS-24185 |
6 of 6 records
CC-116Assessment tests · AT-17773
FailTested at26 Oct
Sample size690
Exception count25
ParentASS-74542
What you can do
Record what the test found
A Control Tester works from the scoped assessment and relevant control. Each test records when it was performed, the sample size, exception count, result and evidence reference. Pending, Pass, Fail and Inconclusive allow the team to distinguish a completed successful check from a failed or unresolved one. The control code gives a compact identifier while the reference ties the test to the actual control.
Consider a sample of access checks at a busy site. If the tester finds exceptions, the record should show both the sample and the exceptions. A Fail result directs attention to the control and assessment; the finding describes the gap in words a remediation owner can act on. A numerical exception count alone cannot explain the cause or the required response.
How the work is organized
- Test record. Sample size, exceptions, result and evidence stay with the assessment.
- Finding. Severity, opened date and description identify the control gap.
- Next state. Open, action planned, Retest and Closed show the finding’s progress.
Findings connect to an assessment and a control. The severity options are Low, Medium, High and Critical. The Safety Manager can compare those values with the operating context when assigning action. The finding should remain open until a response is planned; moving it to Retest signals that the correction is ready for independent checking.
What to agree during setup
Define how the team selects a sample and records an exception. Decide what supporting evidence belongs in the test reference and what belongs in an attachment to the parent assessment. Agree when an inconclusive test is repeated, and set the threshold for opening a finding. Document who assigns severity and who may move a finding toward retest.
Check the handoff on an actual case
Select a control with an owner and add a failed test to a scoped assessment. Open a finding that identifies the exact gap, severity and control. Assign corrective work with a due date. The Independent Reviewer should be able to follow the test into the finding and inspect the recorded evidence before a retest. If the result is Inconclusive, keep that uncertainty visible in the testing record. Ask the Safety Manager to resolve the sample question before treating it as a completed control check.
What your team sees
- Failed tests — Failed sample checks with their control and assessment.
- Open findings — Gaps awaiting action or retest.
- Findings for retest — Corrected gaps ready for independent checking.
Follow the work through
Use assessment and testing to prepare the sample and finding to action to assign the response.
What it keeps track of
Data model- Assessment tests
- Individual control tests with sample size, exceptions and evidence
- Findings
- Control failures or gaps raised by testing
- Controls
- Controls implemented against a risk, with ownership and effective date
- Assessments
- Period control assessments that scope risks, controls and testing
- Retests
- Independent retest of a finding after remediation
Who uses it
Permissions- Control Tester
- , Safety Manager, 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.