What an auditor is actually asking for

When a reviewer asks to see pest control, the question underneath is rarely whether a technician attended. Attendance is the easiest thing in the file to prove and the least interesting. The question is whether the site can show control: that what was found was identified, managed, and resolved, and that the record holds together across a year rather than a single visit.

In practice, that breaks into three things. First, continuity. A reviewer reads the record backwards, from the most recent visit towards the start of the period, and looks for the thread: does a finding in March reappear in April with a status, or does it simply vanish? A record that loses its own findings is read as a site that loses them too.

Second, closure. Most records are good at openings — observations, recommendations, notes. Far fewer are disciplined about endings. The single most persuasive document a site can produce is a corrective action register where every line carries an owner, a priority, and a closure status. It demonstrates that the programme has a memory.

Third, proportionality. Reviewers are not impressed by volume. A thin record on a low-risk site can be a correct record. What draws attention is mismatch: heavy activity in the trend data and a quiet action register beside it, or monitoring deployed everywhere with no interpretation attached to it anywhere.

The practical test is simple, and worth running before anyone external does: pick a finding from nine months ago and follow it through the file to its close. If that walk is easy, the audit will be. If it is not, the gap is in the record, and the record is what gets reviewed.