Audit-Ready Documentation & Verification
Findings mapped, dated, photographed, and tied to corrective actions you can defend standing on the floor next to the auditor.
What documentation do auditors expect from a pest program?
At minimum: a site-specific pest risk assessment, a numbered device map matching physical placement, twelve months of service and activity records, trend analysis, corrective action records with evidence of closure, applicator licensing and product documentation, and proof the program is reviewed and adjusted. Auditors are assessing the system behind the service, not just whether logs are filled in. Untracked paper logs and verbal walk-throughs generate findings because they cannot demonstrate the program is managed on a defensible schedule.
Why most corrective actions close weakly
A corrective action has three parts an auditor cares about: what caused it, what you did, and how you know it worked.
Most pest corrective actions are strong on the middle part and thin on the other two. “Increased service frequency and added four devices” documents an action. It does not establish root cause, and it does not demonstrate the condition was actually eliminated. The next audit cycle re-opens the same finding.
Detection produces evidence for the two weak parts. A canine sweep locating an active wall void establishes root cause with photographic support. A post-remediation verification sweep documents that the void is no longer active. Between them, the corrective action closes on evidence rather than assertion.
“No activity recorded” and “no activity present” are different claims
Your trend data supports the first. Only a search supports the second.
That distinction is exactly what an auditor is probing when they ask how you know a condition was resolved. A verification sweep lets you answer with a documented search rather than the absence of a capture — which is the difference between a closed finding and a repeat finding.
What our reports contain
- Numbered findings tied to named facility locations and cross-referenced to your existing device map.
- Photographic evidence at each finding, dated and location-tagged.
- Active-versus-inactive classification, so treatment scope is defensible.
- Handler confirmation status — confirmed findings and unconfirmed alerts are recorded separately and never merged.
- Prioritized corrective-action recommendations, sequenced by risk.
- Team credentials — certifying bodies and current certification status, so the finding’s provenance is documented.
- Verification sweep results where a follow-up has been performed, delivered in a format you can attach directly to your food safety management system without reformatting.
Frequently asked questions
Will an auditor accept a third-party canine detection report?
Auditors accept documented evidence from qualified parties. What makes a report credible is the same thing that makes any record credible: a named, credentialed inspector, dated findings, location specificity, photographic support, and a clear methodology. Our reports carry all of that, including certification status for the team that performed the work. Ask any vendor for a sample report before engaging.
Can you work to our existing document control format?
In most cases yes. Tell us your template and numbering conventions during the pre-deployment review.
Do you provide documentation for insurance or litigation?
We provide factual inspection reports. What they are used for afterward is your call. Tell us in advance if a report may be used in a legal or claims context so it is scoped and worded appropriately from the start.
How long should we retain detection reports?
Follow your scheme’s retention requirement for pest records — twelve months of service history is a common floor, and most facilities retain longer. Treat detection reports as part of the pest file, not as separate correspondence.
Related: Food processing facilities · Multi-site programs · back to nationwide K9 rodent detection
Need evidence, not assertions, in your next corrective action?
Tell us the finding and the standard, and we will show you what a defensible detection report looks like.