NEWRecognition module — recognise hard work and the people going above and beyond
AgencyOptixRecruitment software

Checks & records

What is a compliance file?

A compliance file is the set of records an agency holds for a worker evidencing that they were entitled and qualified to do the work they were placed in — checks, qualifications, references and agreed terms.

compliance file — diagram A compliance file is the set of records an agency holds for a worker evidencing that they were entitled and qualified to do the work they were placed in — checks, qualifications, references and agreed terms. Right to work DBS check References Qualifications Expiry tracking Client audit
Compliance file, shown among the checks in a compliance file.
Use this diagram+

Free to use on your own site, in training material or in a handout, as long as the credit link stays on it. Paste this where you want the diagram to appear.

<figure>
  <img src="https://agencyoptix.co.uk/glossary/compliance-file/diagram.svg" alt="compliance file — diagram from AgencyOptix" width="880" height="620" loading="lazy">
  <figcaption>
    <a href="https://agencyoptix.co.uk/glossary/compliance-file">What is a compliance file?</a> — diagram by
    <a href="https://agencyoptix.co.uk">AgencyOptix</a>
  </figcaption>
</figure>

Its value is entirely in when it was built. A file assembled before placement demonstrates that the checks informed the decision; the same documents gathered afterwards demonstrate only that they exist.

Client audits are the usual forcing function, and they tend to sample. A firm with ninety-five per cent of files complete will still fail an audit that happens to pull three of the incomplete five per cent.

Documents expire at different rates, which is what makes a file a live object rather than an archive. A file complete at placement can be non-compliant three months later without anything having been removed from it.

What goes wrong in practice

  • Files completed retrospectively when an audit is announced.
  • Expiry dates held in the document rather than in a system that raises them.
  • Documents stored without recording who verified them and when.
  • No single view of which files are currently short of what, so gaps are found by sampling rather than by looking.