A checklist is the list of checks a tester works through to test a control: "Guard fitted?", "Guard undamaged?", "Last inspection within 12 months?".
Where checklists come from
Data pack controls come with a default checklist. Use it as it is, or copy it and make it your own.
Your own controls need a checklist you write.
Open a control's checklist with the Checklist button on the unit screen, the testing panels or Control Criticality.
Kinds of check
Kind | Answered with |
|---|---|
Yes / No | Pass, Fail or N/A. |
Reading | A value, with an optional unit and range. Outside the range suggests Fail. |
Photo | A photo or other evidence is the answer. |
Note | Free text for the next tester. Never scored. |
The suggested % is the share of checks passed, ignoring N/A. A check can be marked critical: failing it pulls the suggested result down hard, whatever else passed.
Versions
Checklists are versioned. Each test uses the version that was current when it started, so later edits never change an old result. Strengthening a test after a failure means making a new version.
Notes for next time
When a test finds a weakness in the checklist itself ("we didn't check the spare guard"), the tester can add a note for next time. It shows on the checklist until someone makes a new version.