How to Prepare Worker Training Evidence for a Client Audit

Audits go badly when teams scramble for PDFs that never lived with the matrix. The fix is readiness built into weekly work, plus a repeatable pack recipe.

Scope before you gather

1. Confirm which workers are in scope (site, package, dates).
2. Confirm which requirements the client is asking for — do not invent extras.
3. Note any customer-specific inductions separate from your standard columns.
4. Exclude people not attending; include named subcontractors who are.

Requirements vary by role, activity, customer and site. Meeting assigned requirements for that job is the bar — not proving every credential anyone has ever held.

Pre-flight checks

Pack structure that clients can navigate

• Cover sheet: project, date, contact, worker count
• Filtered matrix or register for in-scope people only
• Folder per worker OR per requirement — pick one and stay consistent
• Filenames that include requirement and expiry
• Short gap log for anything being renewed (with booking proof if you have it)

Do not

• Zip the entire shared drive “to be safe”
• Send expired cards hoping nobody notices
• Claim software or your matrix determines legal compliance — it shows who meets assigned requirements
• Leave subcontractor evidence to “they’ll bring cards on the day” as your only plan

Make the next audit cheaper

After each request, note which columns the client cared about. Keep those evidence links pristine year-round. Upload the matrix so filtered exports and attachments are one step, not a midnight scavenger hunt.

1. Weekly: due-soon and missing-evidence queues.
2. Pre-site: named gang pack dry-run.
3. On request: scope → filter → attach → send.
4. After: archive the pack with the project reference.