Community supermarket cleaning supervisor - pest control and records SOP; daily prevention folded into the cleaning route, monthly third-party service with a complete service ticket, numbered bait stations mapped, and one inspection folder assembled in a fixed order

You are the cleaning supervisor of a community
supermarket. Pest problems are a heavyweight
item in fresh-food store inspections. Write an
archivable pest-control SOP built around
"prevention" and "records" - inspections test
the system, not the sightings.

Five parts:

1. Daily prevention (fold into the existing
cleaning route)
- At open, confirm door sweeps / air curtains
  are in place and running
- Trash room cleared daily, nothing overnight;
  cardboard and junk never stacked against
  walls overnight
- Floor drains and sewer openings flushed and
  checked daily (tighter loop around deli and
  fresh-prep areas)

2. Monthly treatment (third-party service)
- Service visits by a licensed pest-control
  operator (PCO); the store never buys
  chemicals and sprays them itself - self-
  spraying a food facility is a contamination
  risk, and inspectors do not accept self-spray
  logs anyway
- Every visit must yield a service ticket:
  chemicals used / areas treated / station
  count / technician signature - anything
  missing gets completed on the spot before
  filing; a ticket backfilled later reads fake
  at a glance
- Service frequency per contract; flag the
  manager one month before renewal

3. Bait-station management
- Every station numbered, mapped on one sheet
  (A4 map posted in the office; numbering
  matches the physical station labels)
- Monthly activity check: stations with take
  get a tick on the check sheet - the same
  zone triggered two months running means the
  PCO adds density there
- Damaged or moved stations replaced or
  restored the same week, noted on the sheet

4. Fly-trap (ILT) management
- Placement: inside of entrances, never
  directly above food-prep surfaces
- Glue boards swapped by soil level (over half
  the surface covered = swap); UV tubes
  replaced per the tube's rated life (per the
  manufacturer's sheet)
- Both logged: date / location / what was
  replaced

5. Inspection folder (one folder, contents in
exactly this order)
Pest-control contract / all service tickets /
bait-station map and monthly check sheets /
fly-trap change log / staff pest-awareness
training sign-in sheets (twice yearly)
When an inspector arrives, hand over the folder
- nothing assembled on the spot, nothing
explained away

Escalation (any one found, executed same day):
- Live rodent, or heavy insect activity in the
  fresh area: seal visible holes immediately,
  notify the manager, call the PCO for an
  urgent same-day visit, and cover or isolate
  food in that zone
- A live rodent is the single heaviest finding
  in an inspection - overreact on purpose

Constraints:
- No "keep the store clean" filler; every line
  is an action + a frequency + a record carrier
- Chemicals left on site by the PCO: locked,
  off the floor, away from food - storage
  location and custodian named in the SOP
- Written to be printed and executed as-is; no
  background, no rationale sections

Why it is written this way

The core insight of this SOP: a pest inspection is an audit of the file, not of the floor. Inspectors flip through service tickets, station maps, and check sheets - a folder assembled in a fixed order beats a pest-free night, and the reverse is brutal: a spotless floor with records pieced together that morning falls apart at the second follow-up question. "In exactly this order" is where the whole SOP lands.

Banning store-bought spray marks a trap small and mid-size operators step in: hiring a PCO feels expensive, so someone buys an aerosol and sends the cleaner around. In a food facility that carries contamination risk, and inspectors reject self-spray logs - all of the risk, none of the credit. This line is deliberately absolute.

Bait stations with "numbering + map + monthly activity check" are where pest prevention earns its keep: a station is not furniture for the inspector, it is a sensor. Take at one station means rodent activity in that zone; two consecutive months in the same zone should trigger added service density. A station without monthly checks is just a plastic box.

The live-rodent escalation is its own block, hard-limited to same-day, because it is both the heaviest finding in an inspection grading and the only one with no remedy window: a missing ticket can be issued later; a rodent an inspector saw cannot be unseen. The action density in that block (seal, report, urgent call, isolate) is intentional - that moment leaves no time to invent steps, which is exactly what an SOP is for.

Variables