Commercial Pest Control Log Book Template (Excel)

A commercial account does not just buy treatments, it buys a binder. Somebody walks the site, opens the folder on the shelf, and expects to find what is out there, what has been caught in it, what anyone saw between visits, what went down, and who signed for it. This is that binder as one Excel workbook: seven tabs, blank, no signup, no email wall. Download it, keep one workbook per site, and fill it in Excel, Google Sheets, or LibreOffice, or print the tabs and fill them by hand on the route.

The device number is the spine

Everything else in the binder is an argument about a device number, so number them once and never renumber. The Device map tab is the register: device number, type, zone, a location description that matches your drawn site map, interior or exterior, and the date it went in. From then on a device check is a number plus a status code, a corrective action is a zone plus an owner, and anyone reading the binder cold can follow a catch back to a spot on the floor.

Six codes carry the Device checks tab: OK for in place with no activity, A for activity or a catch with the count written in, S for serviced or re-baited, M for missing, D for damaged or replaced, and I for inaccessible at the time of service. They are the workbook’s own convention, printed on the Read me tab so the person auditing the binder reads the same key the technician wrote from. Laying the exterior stations out in the first place is a different job, done once, with the bait station spacing calculator.

This is the site binder, not your application log

Two records get confused constantly, so the tabs keep them apart. The pesticide application log worksheet is the applicator’s own record of what was sprayed, where, when, and at what rate. The log book is the customer’s copy of the program: what is installed, what was found, what staff reported, what was applied on their floor, and what still needs fixing. The Products applied tab overlaps the two on purpose, because a site that cannot see the EPA registration number and the label REI for its own building is not being told enough. Both remain free-text cells. Nothing here validates a registration number, looks up a label, or times a re-entry interval, because the label governs the rate, the placement, and the REI every time.

The Sightings log is the tab that earns its keep between visits. A shift lead who saw three small flies by a floor drain on Tuesday has nowhere to put that fact unless the binder gives them a line, and by Friday the technician gets a shrug instead of a location. Give staff the page and the visit starts with evidence.

What the schemes and the state actually decide

Third-party audit schemes and your state’s pesticide rules set what a site must keep and for how long. They differ by scheme, by state, and by site type, and they change, so this workbook deliberately reproduces none of them and asserts no scheme’s requirements. What it does is give you the records a commercial account is normally built around, laid out so an inspector can read them: device register, checks, sightings, products, corrective actions, sign-off. Read your own scheme’s current standard and your state’s rules, then add whatever they call for.

Corrective actions are the tab most operators skip and then wish they had. A gap under a dock door, standing water by a drain, cardboard stored against a wall: none of those are yours to fix, and all of them are yours to raise. One row, one owner, one target date, one verification line, and the conversation about why activity keeps coming back has evidence behind it.

Where it sits in the visit

The binder is the record of the program, not the program itself. The program document is the IPM plan, which names the pests, the thresholds, the monitoring schedule, and the approved materials the log book then evidences visit by visit, in the sense of integrated pest management the EPA sets out: thresholds first, monitoring and identification second, prevention third, and control chosen least-risky first. The paperwork around a single visit lives elsewhere: the pest control work order template is the job ticket the technician carries in, and the pest control service report generator is the leave-behind the customer reads on the way out. Nothing you do on this page is saved to Fieldwynn: the workbook is a static file, and the only copy is the one you download.