A pest control service log is not about pests; it is about proof. "We've never had pests" is a claim nobody can check, and a health inspector is trained not to take claims. "We monitor — here are twelve months of weekly checks, contractor reports, and receipts for every fix" is a record the inspector can read in thirty seconds, and it is the difference between the pest conversation ending and the pest conversation starting.
The log has two parts, and both matter: the weekly self-checks your own crew does (Part A) and the block you fill at every contractor visit (Part B).
Part A — the weekly self-check (five minutes, before the contractor ever comes)
One row per week, on one sheet taped inside a cabinet near the back door:
- Sightings and signs. What was actually seen, where, and when. "Nothing observed" written honestly every week is worth more than a page of perfect weeks that suddenly stops.
- Trap and station status. The numbered stations on the floor plan: intact, baited, sprung, missing. A missing station is a work order.
- Harborage. The cardboard stack behind the prep line, the mop head stored wet, the gap under the back door sweep. Pests are a habitat problem before they are a bug problem.
- What was done right then. Harborage removed, trap reset, bin re-lidded — the same-hour fix is the heart of the log.
- Initials. A real person. Accountability is what makes it a log instead of a poster.
Part B — the contractor visit block (filled at hand-off, never from memory)
Date, tech name and license number — the license line is what the inspector looks for first. Stations serviced plus the bait map updated — numbered stations on a current floor plan, not the map from 2023. Product used plus the EPA registration number — every chemical gets its number, or the visit is a liability instead of a defense. Findings, corrective actions, and the next scheduled visit.
Why it reads as a defense
When the inspector asks about pests, the binder opens to: twelve months of weekly rows, signed; contractor reports with license and EPA numbers; the receipts for the door sweep and the bin lids; and the correction trail for the two incidents the year before — both closed. That binder reads as management. A folder of contractor invoices with nothing around them reads as spending.
Worked example
Two mouse droppings behind the dish pit, week 33. Row written same hour: location, count, harborage found (a cardboard tower), action (tower removed, two traps set, gaps sealed under the dish line), initials. Contractor's quarterly visit lands week 35 — the tech confirms the seal, resets the map, EPA number on file. The inspector in week 41 reads the trail in thirty seconds. The counterfactual: the same two droppings found by the inspector, with no row, no map and no receipts, is the conversation where kitchens get closed.
Full sheet, plus the equipment downtime log and the maintenance work order that pest findings feed into, on the page itself.
Kits — the paid tools behind the free advice:
- The First 30 Minutes — free incident quick-start checklist
- Ops Starter Kit — incident response for small teams — $14
- Ops Starter Kit Vol. 2 — advanced incident response & communications — $27
- Ops Mega Bundle — all 5 kits in one download — $49
Code HIVE-LAUNCH30 takes 30% off any kit at checkout.
Top comments (0)