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.
- Labor Law Compliance
- Features
- Retests and review
Retests and review
Record independent results and reviewer decisions
OverviewRetest results×
Labor Law Compliance · Retests and review
New
Retest results
Retests
| Finding | Reviewer | Tested at | Result | Evidence | |
|---|---|---|---|---|---|
| FND-7999 | 14 Oct | Pass | EVD-678 | ||
| FND-8265 | 05 Oct | Fail | EVD-555 | ||
| FND-2772 | 19 Oct | Inconclusive | EVD-551 | ||
| FND-9073 | 24 Oct | Pass | EVD-655 | ||
| FND-3002 | 10 Oct | Fail | EVD-856 |
6 of 6 records
EVD-678Retests · RTS-47848
PassFindingFND-7999
Tested at14 Oct
What you can do
Retests and review in the working cycle
Review decisions and retests answer different questions. A review decision records whether an assessment revision is approved, rejected or returned, with a reviewer, decision date and reason. A retest checks whether work on a finding has changed the observed result. Both need enough context for another person to understand what was examined and what remains open.
When an assessment reaches review, the Compliance Manager presents its tests, findings and attachments. The reviewer records the source revision and decision. If information needs correction, a return or rejection keeps that decision visible. An approval belongs to the reviewed revision. A later change should come back through review rather than silently inheriting the earlier judgment.
After a Remediation Owner submits evidence, the Retest Reviewer tests the finding independently. They record the test date, result and evidence on the retest. A failed or inconclusive result directs the team back to the finding and action. A passing result supports verification, while the Compliance Manager remains responsible for the broader assessment closure decision. For example, an updated time-record process may be documented by the owner, then sampled again by a separate reviewer before the finding is closed.
How the work is organized
- Revision decision. Keep the source revision, reviewer, reason and decision on the assessment.
- Independent check. Record the retest against the original finding and its corrective evidence.
- Closure context. Read decisions and retests together before closing the assessment.
What to agree during setup
Agree who may review an assessment revision and who is independent enough to retest an action. Set the evidence needed for approval and what a returned decision asks the owner to change. Define when a passing retest is sufficient to verify an action and when the finding needs another step. Keep the review reason specific to the case.
Check the handoff on an actual case
Use an assessment with a finding and a submitted action. Have one reviewer decide the assessment revision and another person perform the retest. Return a revision once, then check that the later approval refers to the revision actually reviewed. Enter an inconclusive retest and confirm the team can still see the unresolved issue. Finish with a passing result and review the full trail.
What your team sees
- Retest results — Dated retest results with reviewer and finding.
- Assessment review inbox — Assessment revisions awaiting a decision.
- Actions awaiting verification — Submitted corrective actions awaiting verification.
Follow the work through
Follow the related process, review the data model and agree implementation steps with the team.
What it keeps track of
Data model- Retests
- Independent retest of a remediated finding.
- Review decisions
- Independent reviewer decisions on submitted revisions.
- Findings
- Test exceptions raised as findings for remediation.
- Corrective actions
- Assigned remediation work with due dates and evidence.
- Assessments
- Wage-hour, OSHA and classification assessments with scope and lifecycle.
Who uses it
Permissions- Retest Reviewer
- , Compliance Manager, Legal Reviewer.
Set up Labor Law Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.