Customer Cleaned Up Evidence Before Inspection: DIY-Induced Decision Tree
Why this matters
A customer calls reporting activity. By the time the technician arrives, the kitchen has been scrubbed, the basement floor has been swept, the droppings are in the trash, the dead roaches have been flushed, the smear marks on the wall have been wiped, and the chewed cereal box is gone. The customer is embarrassed, or they wanted the place tidy for the visit, or they thought cleaning was the right first step. Whatever the motive, the inspector now cannot see the freshness, the location, the volume, or in many cases the species of the activity that prompted the call.
This is one of the most under-discussed DIY-induced faults in residential pest work. It does not break the chemistry, it does not create a compliance issue, and the customer rarely thinks they did anything wrong. But it strips the inspection of the primary data the technician needs to scope, price, and target a treatment. The wrong response is to either guess or to lecture. The right response is a structured recovery of what evidence remains, plus a controlled monitoring window that lets the property tell the technician what the customer cannot.
What gets lost when evidence is cleaned
Each evidence category answers a different inspection question. When the category is gone, the question is open.
- Droppings. Species identification (mouse vs rat vs cockroach vs bat vs squirrel), volume of activity, freshness, travel routes, harborage location.
- Smear and rub marks. Travel paths along walls and beams. Long-term repeated use of a route.
- Frass and shed skins. Cockroach and bed bug species identification, life stage distribution, population maturity.
- Dead specimens. Species ID, life stage, recent kill (relevant to recent treatment work elsewhere on the property).
- Damaged packaging or chewed material. Active feeding sites, source pressure direction.
- Visible nests, runs, or harborage. Direct sightings, breeding evidence.
- Odor. Active vs historical activity, dead animal location.
When the customer cleans, the technician loses some or all of these. The reported pest type may be wrong. The reported severity may be wrong. The location of the source may be entirely unknown.
The decision tree
Run on first inspection of a cleaned property. Stop at the first match.
Ask the customer directly: "Before I walked in, did you clean, vacuum, sweep, or throw out anything related to what you saw?" The phrasing matters. Customers will deny "cleaning evidence" but will admit "tidying up before you came." If yes, GO TO recovery path. If no but the property looks suspiciously evidence-free given the call description, treat as cleaned for inspection purposes and continue on recovery path.
Recovery path step one: ask what specifically was cleaned and from where. Most customers can describe what they removed if asked specifically ("I swept the pantry floor, I threw out a box of cereal, I wiped the wall behind the trash can"). Map these locations on the inspection notes. These are now the highest-probability inspection zones.
Recovery path step two: ask whether anything was kept that the technician can see. A bagged dropping sample, a photo of the activity, a dead specimen kept "to show you." Many customers do save a sample even after cleaning, especially if they took a photo with their phone. The photo alone is often enough to confirm species and freshness.
Recovery path step three: re-inspect the cleaned zones for residual signs. Cleaning by a homeowner is rarely thorough. Look for: droppings in cabinet corners and behind appliances, smear marks the rag did not reach (under cabinets, behind baseboards, on door jambs), frass in cabinet hinges and drawer tracks, gnaw marks on wood and plastic that cannot be wiped away, grease and oil residue on rodent runways. Ten minutes of focused inspection in the customer's stated cleaning zone usually recovers enough evidence to identify species and severity.
Recovery path step four: place monitor stations in the cleaned zones. Glue boards for rodents in the runways the customer described. Sticky traps for cockroaches in cabinet voids near the cleaned area. Activity monitors for ants on the travel paths. These will catch within hours to days and give the technician the data the cleaned property is no longer providing visually.
Decision point: is enough recovered to confidently identify the target species and severity? If yes, proceed with treatment as normal, with a note in the file that initial inspection was on a cleaned property and species ID is monitor-confirmed rather than droppings-confirmed.
If not enough recovered, schedule a monitor-only first visit. Place monitors, set a date for a follow-up inspection at day 3-5, brief the customer on no further cleaning until the follow-up. Treatment waits until species and source are confirmed. This is a difficult conversation with a customer who is paying for action, but treating without knowing the target burns product on the wrong species at the wrong location.
The conversation with the customer
Most customers who clean do it from embarrassment or from wanting to be a good host. Lecturing them about evidence destruction reads as blame. The framing that works:
Template: "Before I walked in, did you tidy up at all? I am asking because what I look at to identify the pest is the same stuff you cleaned. If you have a photo on your phone, or kept a sample, that helps a lot. If you can show me where you swept or wiped, I will look there first. For the next call, leave everything where it is and I will take care of the cleanup as part of the service."
This frames the request as practical rather than corrective. It also gives the customer a script for next time without making them feel bad about this time.
Why this matters for program quality
Routes with a high proportion of cleaned-before-arrival properties show worse first-time-fix rates and higher callback volumes than routes with intact-evidence inspections. The data the technician collects on a clean property is monitoring data over days, not direct observation in minutes. That extra time gap is real. The fix is on the intake side, not the inspection side: scheduling staff should brief customers at booking that the technician needs to see what they saw, and that no cleaning is needed before the visit. Building that into the intake script catches the problem before it reaches the property and the technician.
References
- NPMA technical resources on inspection methodology and integrated pest management (IPM) data collection.
- UC IPM published guidance on monitoring and species identification under field conditions.
- CDC public guidance on rodent dropping handling and household cleaning timing.