Moving tests through review
The four test statuses, why checking is separate and the reviewer permission.
Results move through four statuses. The progression exists so that no result reaches a client without a second person having looked at it.
The four statuses
| Status | Meaning | Who |
|---|---|---|
| pending | Booked, not yet tested | — |
| tested | Result recorded on the worksheet | The tester |
| checked | Verified by a second person | The checker |
| approved | Approved for issue | An approver |
Changing a status
Use the dropdown beside each test on the work request panel.
Why checking is separate
Testing and checking are deliberately different steps performed by different people. A transposed digit or a wrong container mass is invisible to the person who entered it and obvious to a second reader. The Tester and Supervisor fields on the worksheet record who did each.
Moving your own test straight from tested to approved defeats the control. Where a specification or accreditation requires independent checking, this progression is your evidence that it happened.
Report reviewer permission
Only team members with the Report reviewer permission can be selected for reviews. It is set per person in Team members under Account access — see Managing a team member. The Reviewers metric on the team register counts how many people hold it.
Tracking what is waiting
Awaiting review on the laboratory metrics counts tests that are tested but not yet approved. Work sitting here is finished but unissuable — it is the most common cause of a late report.
The Status Board breaks the same figure down by test stream.