The auditor wants twenty random loads from March
An audit is booked. The auditor sends a list: temperature records for a sample of loads, calibration certificates for probes and recorders, trailer cleaning records, pest control reports, driver training records, unit service history and your procedures.
The quality manager spends the next fortnight collecting. Some records are in the telematics portal, some in a folder on the shared drive, some in the workshop office, some in the training provider's system and some on paper. On the day, the auditor picks another five loads at random and the scramble starts again.
Why evidence is so hard to gather
The records are created by different people in different systems for their own purposes. Nobody designed them to be pulled together, so every audit rebuilds the same pack by hand.
- Temperature records live in telematics or store monitoring systems.
- Calibration and service certificates arrive as PDFs by email.
- Cleaning and pest control records are on paper at each site.
- Training records are in spreadsheets or a training provider's portal.
- Procedures exist in several versions on a shared drive.
What audit preparation costs
Weeks of the quality manager's time, several times a year, spent on collection rather than improvement. Gaps found during preparation, too late to fix properly. Findings raised because a record could not be produced on the day, even though the work was done.
Audit outcomes can affect contracts, so the pressure lands on a small number of people who already have full jobs.
How we build an evidence library
- We connect to the systems that create records where they allow it: reefer telematics, cold store monitoring, the driver app, the maintenance system.
- Documents that arrive by email, such as calibration certificates and service reports, are forwarded to a mailbox, read and filed against the right asset and date.
- Paper records at sites, such as cleaning schedules, are replaced by simple checklists on a phone, or photographed and filed until they are.
- Every record is tagged by type, site, vehicle or asset, customer and date, and procedures are held with version history.
- Expiry dates, such as calibration due, are tracked and alerted before they lapse.
- For an audit, the quality manager selects the period and record types, or picks the auditor's sample, and a pack is assembled as a single indexed file.
| Record type | Collected from |
|---|---|
| Load temperature records | Telematics and store monitoring |
| Calibration and service | Certificates filed by email |
| Cleaning and pest control | Phone checklists or photographed sheets |
| Training | Training records or provider exports |
| Procedures | Controlled documents with versions |
We do not tell you what a standard or customer requires. Your quality team sets that, and the library holds the records they decide are needed.
What audit week looks like after
The quality manager checks the library rather than building it from scratch. Gaps, such as an expired calibration, were flagged weeks ago. The auditor's random sample is produced on screen during the audit.
Between audits, the library is also where the operations team finds records for customer queries, so the effort pays off all year.
Is audit preparation taking over your quality manager's life?
- Every audit starts with weeks of record gathering.
- Records are spread across several systems and paper files.
- Expired calibrations or missing records are found during preparation.
- Random samples on audit day cause a scramble.
- Procedures exist in several versions.