Proving completion to auditors without screenshots

An auditor walks into HQ and asks for completion records on harassment-prevention training for the last 12 months across all 80 locations. The wrong answer is "give us a week, we will pull it together." The right answer is to filter the dashboard, export the report, hand it over before the auditor's coffee gets cold. The screenshot model — where you ask managers for proof and paste images into a Word document — does not survive a real audit. Build the system right and audit prep becomes a query, not a project. ## What an auditor actually wants Auditors want four things, and they want them in this order: roster, assignment, completion, evidence. **Roster.** Who was employed at each location during the audit window? This comes from your HRIS, not your training system. The training system has to match the HRIS — every active employee in scope at the time has a record. Gaps in the roster mean gaps in the audit. **Assignment.** What training was each employee required to complete? This is where most franchises fall apart. If the assignment was "food safety training, sometime," you have no audit trail. The assignment must be a specific course, with a specific deadline, attached to a specific employee. The platform records when it was assigned and by whom. **Completion.** Did the employee finish the course before the deadline? Pass / fail / overdue, with a timestamp. Not "the manager confirmed they did it" — the platform's own record of the employee's interaction. **Evidence.** Can the auditor see the underlying data on demand? Module-by-module progress, knowledge-check answers, the timestamp of every action. Not a screenshot. The actual platform record, exportable. If any of those four breaks down, the audit finding is on you — not on the training vendor. ## Why screenshots fail A manager screenshots their LMS view and emails it to HQ. HQ pastes it into a Word document. The auditor opens the doc and sees an image. Three problems: 1. **Not authoritative.** A screenshot can be edited, cropped, taken on the wrong day. It is hearsay, not record. 2. **Not queryable.** The auditor cannot ask follow-up questions of an image. "Show me only employees overdue past 30 days" requires a real query. 3. **Not scalable.** At 80 locations and 12 months of training, you are pasting hundreds of images into a Word document. That is not an audit response, it is a hostage situation. The screenshot model is what you do when your underlying system cannot produce a real report. The fix is the underlying system. ## The audit-ready record A training record that survives an audit has these fields, per employee per assignment: - Employee ID, location, role, start date, end date (if applicable) - Course name, course version, content owner (HQ or franchisee) - Assignment date, assignment author, deadline - Completion timestamp, pass/fail, score - Module-level progress (which modules viewed, which knowledge checks attempted) - Refresher schedule and next-due date All of these are filterable. An auditor asks "show me everyone at site 12 who completed harassment-prevention in Q3," you filter and export. The export is a CSV or PDF report with the data the auditor can verify. Aristotl's record schema includes all of these by default — no consultant configuration to add audit fields, no schema migration to support filtering. The record is the record. ## The data-retention question Auditors care about retention. Most regulatory regimes require training records be kept for a defined period — typically 3 to 7 years. Your platform must store records for that long, not delete them when an employee leaves. The retention policy must be documented and enforced. Aristotl is EU-hosted and GDPR-aligned, with retention policies you can configure per content type. Compliance training records can stay 7 years; ad-hoc training can roll off in 12 months. The right defaults are pre-configured; you adjust if your jurisdiction requires longer. ## What this means for the training team The training team's audit prep used to be a multi-week project. With a real record, it is a one-hour exercise: the auditor sends the scope, the team filters the dashboard, the export goes over. The hours saved go back into the work that actually moves completion rates — building better courses, intervening on slipping locations, running refresher cycles. Audit becomes a query, not a project.

Ready to put this into practice?