The Commercial Pest Sighting Log
Why this matters
On a commercial account, the tech is on site a few hours a month and the staff are there every day. The sighting log is how the other twenty-nine days reach the tech. Kept well, it shows a roach problem starting at the dish machine a week before it reaches the line, and it shows an auditor that the program responds to what the facility sees. Kept badly, it is a page of "saw bug" with no location and no response, and an auditor reads every unanswered entry as a program that is not working. This card owns the log itself: what goes on it, how staff fill it, how the tech closes each entry, and what an auditor looks for. The audit standards are in Commercial Food-Handling Facility Audit Requirements (AIB, SQF, BRC).
The log page
SIGHTING LOG Riverside Grill map rev 3 page 4
date time loc pest ct by
----- ----- ----- -------------- --- -----
10/02 21:40 K-04 roach, adult 1 M.R.
10/05 06:15 S-02 mouse, live 1 D.K.
10/06 22:10 K-04 roach, nymphs 2 M.R.
10/07 13:30 ??? "bugs" - T.L.
10/08 14:05 D-01 flies 5 D.K.
TECH RESPONSES, visit 10/09 init
10/02 + 10/06 K-04: dish machine base, live JL
roaches in wall gap; treated per label;
monitors added K-04a, K-04b
10/05 S-02: trap S-02 one capture; receiving JL
door sweep gap 3/8 in, mgr notified
10/07 ???: no location; staff shown map; JL
no evidence found on walk-through
10/08 D-01: dumpster door propped open, JL
mgr notified; fly light checked
What each column is for
Date and time. Time matters more than staff think. German cockroaches are mostly active at night, so a daytime roach sighting points to a heavy population or a disturbed harborage. A mouse at 06:15 near receiving suggests it came in overnight. Time also lets the tech match a sighting to a delivery, a deep clean or a pest of the season.
Location code. The single most important column. The code matches the device map posted on site (K for kitchen, S for storage, D for dock or dumpster, numbered by device or zone). A code puts the sighting on the same grid as the monitors and traps, so a sighting at K-04 sits beside the sticky monitor at K-04. "Kitchen" is not a location; "by the dish machine" is better; "K-04" is what the log needs. Keep the posted map at the same revision as the log header, and replace both when devices move.
Pest and count. What and how many, in the staff member's words if they do not know the species ("small brown roach", "mouse"). Count is honest even when it is approximate ("5 flies") and it lets the tech compare against the account's thresholds. See related: IPM Action Thresholds for an Account.
Reported by. Initials, so the tech can ask the person who saw it. A staff member who logs often and clearly is the best monitor on the account.
Tech response and initials. Every entry gets one, on the next visit at the latest, and sooner for anything the service agreement calls urgent. A response states what the tech did (inspected where, found what, did what, per which label or agreement) or why nothing was done (no evidence on walk-through, outside the scope). An entry with no response is the gap an auditor finds first.
How staff fill it
Post the log and the map in one place, usually by the back office or the manager's desk, and train every shift on four rules:
- Log it when you see it, not at the end of the shift from memory.
- Use the map code. If unsure, write the nearest equipment and ask the manager to add the code.
- Keep the pest if you can. A dead roach on a piece of clear tape on the page, or a photo on the manager's phone, tells the tech the species in seconds. A cockroach crushed and thrown away tells him nothing.
- Call for urgent ones. Rodents in a food prep or storage area, or anything the agreement lists as urgent, get a call to the service office the same day, not just a log line.
Where staff go wrong. "Bugs" with no location (the 10/07 entry above). Pest entries copied from the previous week to look busy. Sightings only logged in the days before an audit. Each of these is a training issue, and the tech's response to it goes in the log so the auditor sees it was handled.
How the tech reviews it every visit
Read every entry since the last visit before you touch a device. The log tells you where to start. In the example, two of five entries are at K-04 within four days, so K-04 is the first stop, not the last.
Group by location, then by pest. Repeated entries at one code are a harborage or an entry point; scattered single entries across the building are more often a sign of staff alertness than of an infestation. Compare against the monitor data at the same codes. See related: How to Place and Read Sticky Monitors in a Kitchen.
Respond to each entry, even the ones that lead nowhere. The 10/07 "bugs" entry got a walk-through and a training note; the response proves the program looked.
Write the response in the log and on the service report. The log stays on site; the service report goes to the account and the office. Each should reference the other so a reader can tie a sighting to the visit that answered it. See related: Pesticide Application Record and State Reporting for what the application part of the record must carry.
Worked example: reading a week at Riverside Grill
The log page above covers 10/02 to 10/08, and the tech visits on 10/09.
K-04, two entries, three roaches. One adult on 10/02 at 21:40, two nymphs on 10/06 at 22:10, both at the dish machine. Nymphs mean breeding nearby; two sightings in four days at the same code mean a harborage, not a stray from a delivery. The sticky monitor at K-04 had caught four roaches since the last visit, against one in the visit before. The tech inspects the dish machine base, finds live roaches in a gap where the machine's frame meets the wall, and treats per the product label with a crack-and-crevice placement suited to a food area. He adds two monitors (K-04a and K-04b) to map the spread and notes the gap for the manager as a sealing item.
S-02, one mouse. One live mouse at 06:15 in dry storage. Trap S-02 has a capture. The receiving door's sweep has a 3/8 inch gap at one end; a mouse can pass about 1/4 inch, so that gap is an entry. The tech records it and notifies the manager; exclusion materials are in Rodent Exclusion Materials and Opening Sizes.
The unlocated entry. No code, no count, no species. A walk-through finds nothing. The response is a training note, which is all the entry supports.
D-01, flies. Five flies at the dock, and the dumpster door was found propped open. A sanitation and building item for the manager, and the fly light at the dock was checked.
After the visit. On 10/11 at 23:00, M.R. logs another adult roach at K-04. That is one entry, one roach, two days after treatment. Whether it is an expected survivor or a sign the harborage is wider than treated is what the new K-04a and K-04b monitors will answer on the next visit, and the account's thresholds set when a sighting count at K-04 triggers an extra visit before the scheduled one.
What the auditor sees. Five entries before the visit, every one answered with initials in four responses (the two K-04 entries answered together), a pattern at K-04 noticed and acted on, three building and sanitation items (the K-04 wall gap, the receiving door sweep, the propped dumpster door) passed to management with dates. One entry after the visit, awaiting the next one. That is a log that works.
When the log and the monitors disagree
The log and the devices measure the same pests two different ways, and a disagreement between them is information.
Sightings rising, monitors quiet. Staff keep logging roaches at a code where the sticky monitor catches nothing. Either the monitor is in the wrong spot (on an open floor rather than against the wall the roaches travel, or replaced so recently it has not had time), or staff are seeing the pests somewhere the map code does not quite describe. Ask the person who logged it to point to the exact spot, then move or add a monitor there.
Monitors catching, log empty. The monitor at a code catches steadily and nobody logs anything. Usually that means the activity is at night when nobody is there to see it, which is normal for cockroaches and rodents, or that staff have stopped using the log. Check the dates on the last few entries. A log whose last entry is from the previous audit is a staff engagement problem, and the response goes to the manager in writing.
Both rising together. The clearest signal there is, and the one the account's thresholds are written to catch.
What an auditor reads for
Auditors under the common food-safety schemes look for closure (every entry answered), timeliness (answered by the next visit or sooner for urgent items), patterns acted on (repeat codes lead to inspection and action), consistency between the log, the device data and the service reports, and management follow-through on building and sanitation items the tech raised. An empty log for six months is not reassuring; it reads as a log nobody uses. Ask the manager to keep the log active and to show it to every new hire.
Keep the old pages
Retain completed log pages for as long as the account's audit scheme or contract requires, and at least through the next audit, filed with the service reports for the same period. A missing page is the same as a missing response.
References
- See related: Commercial Food-Handling Facility Audit Requirements (AIB, SQF, BRC)
- See related: IPM Action Thresholds for an Account
- See related: How to Place and Read Sticky Monitors in a Kitchen
- See related: Pesticide Application Record and State Reporting
- See related: Rodent Exclusion Materials and Opening Sizes