1. Scope and ownership
Start by stating which staff, roles, sites and record types are in scope. A result cannot be interpreted if the denominator changes between reports.
Record who owns the requirement, who maintains the staff record and which manager is expected to resolve each exception.
- The staff population and reporting date are stated
- Each requirement has a source, owner and review date
- Starters, leavers and role changes have a defined update process
2. Records, dates and evidence
Check a sample of current, due-soon, overdue and not-applicable records. Confirm that the visible status agrees with the completion date, renewal date and evidence decision.
A certificate, assessment outcome and observed sign-off prove different things. Record which evidence is required instead of treating every uploaded file as accepted proof.
- Completion and renewal dates use one agreed rule
- Required evidence is linked to the record it supports
- Missing, supplied, accepted and rejected evidence remain distinct
3. Exceptions and follow-up
A useful dashboard leads to named exceptions. Review whether managers can open the person and requirement behind each overdue, due-soon or missing-evidence item.
Keep data-quality issues separate from genuine requirement gaps. A missing role and an overdue course both need action, but not the same action.
- Every open exception has an owner or escalation route
- Managers can see the records within their permitted scope
- Closed actions keep enough context to explain what changed
4. Reports and review pack
Prepare a dated output using the same scope and filters that managers reviewed. Include known gaps and exclusions rather than presenting a clean percentage without context.
The final check is reproducibility: another authorised person should be able to open the underlying record and understand how the report was produced.
- The output states its date, scope, filters and exclusions
- Known gaps remain visible rather than being removed from the denominator
- Supporting records can be traced from the report
Questions this guide answers
Does this assessment prove compliance?
No. It helps an organisation review the completeness, ownership and traceability of its workforce records. Compliance depends on the applicable requirements, the accuracy of the records and the action taken.
Should workforce compliance readiness use one score?
A score can summarise a stated denominator, but it should never replace the exception list. Show the scope, update date, exclusions and people or requirements that need action.
How often should the assessment be repeated?
Repeat it after material changes to roles, requirements or systems and before a planned review. Ongoing exception follow-up is more useful than waiting for a fixed annual exercise.