Monitors Show Zero but Customer Still Sees Pests: Reading In-Spec Decision Tree

Why this matters

A monitor station showing zero catch over a 14- or 30-day period is supposed to be evidence the property is clean. When the customer is still reporting sightings, the technician is caught between two conflicting reads of the same property: the instrument says no activity, the human says yes activity. Resolving that conflict is not optional. If you side with the monitors and tell the customer there is nothing there, you lose the account when they see the next bug. If you side with the customer and re-treat aggressively, you train them to demand re-treatment on any sighting and you burn product on a property that may not need it.

This pattern is the in-spec reading problem. The reading itself is technically valid; the conclusion the reading is being asked to support is what is wrong. The fix is to read the monitors for what they actually measure, and to treat customer sightings as data that supplements rather than contradicts.

What a monitor actually measures

A sticky monitor, glue board, or pheromone trap measures one thing: pests that came into physical contact with that specific surface during the deployment window. It does not measure:

• Pests that did not cross that specific square foot of floor or wall.
• Pests in zones the monitor was not placed in.
• Pests using harborages or travel routes that bypass the monitor location.
• Population density across the property as a whole.
• Pest species that do not interact with the monitor's attractant (pheromone traps are species-specific).
• Activity outside the deployment window (a 14-day catch zero does not mean activity in day 15-30 will be zero).

So a zero catch is consistent with a clean property AND with several other states: a property with active pests outside the monitor coverage area, a property with active pests of a different species than the pheromone targets, or a property where the monitors are placed where the pests do not travel.

What customer sightings actually report

A customer sighting reports: this specific individual was seen at this specific location and time by this specific person. It is high-confidence evidence of presence and low-confidence evidence of population density. One sighting could be:

• A genuine residual population that monitors missed because the pest was not crossing the monitor location.
• A reintroduction (one bug that came in with groceries, with the dog, on a visitor's bag) that does not represent an established infestation.
• A misidentification (carpet beetles called bed bugs, drain flies called fruit flies, paper wasps called something else).
• An occasional invader that bypassed exterior treatment and entered through a single entry point.
• An ongoing low-level activity that the customer notices because they have been primed to look after the previous infestation.

The customer is not wrong about seeing a bug. The disagreement is about what that sighting means for the program.

The decision tree

Run this when the monitor-vs-sighting conflict arises. Stop at the first match.

1. Customer sighting was the same species being monitored AND in a different room than monitors were placed? Monitors are reading correctly for their location, not for the property. Action: relocate or add monitors to the sighting zone. Re-evaluate at next interval.

2. Customer sighting was a different species than what the monitors target (pheromone-specific trap missed a non-target species)? Monitors are reading correctly for the target species. Action: identify the actual sighted species, add appropriate monitors or inspect for that species directly.

3. Customer sighting was the same species AND in the same zone as monitors AND monitors are clean for 14-plus days? Two scenarios are possible: low-density residual activity that did not cross the monitor surface, or reintroduction. Action: inspect for fresh evidence (feces, shed skins, fresh activity signs) in the sighting zone. If fresh evidence is present, treat as low-density residual; intensify monitoring. If no fresh evidence beyond the single sighting, treat as occasional invader and document.

4. Customer sighting was in a zone the program never covered (basement, garage, exterior under a deck)? Scope question, not a monitor question. Action: ask whether the customer wants to expand scope. Do not push expansion if the sighting was a one-off occasional invader; do explain that monitors only report on covered zones.

5. Monitors are reading zero but inspection finds fresh evidence (fresh feces, fresh kill, fresh shed skins, fresh damage)? Monitors are placed wrong. Action: relocate monitors to where the fresh evidence is. The instrument is misconfigured for the property.

6. Monitors are reading zero, no fresh evidence on inspection, customer sighting is documented but isolated (one bug, identifiable as the target species)? Most likely an occasional invader. Action: document, explain to customer, do not re-treat the whole property. Add a single monitor near the entry point if a likely entry can be identified.

Why monitors miss real activity

Five common reasons a clean monitor sits next to a real infestation:

• Wrong placement. Sticky monitors work for pests that crawl across floors and along walls. They miss pests that travel in voids, on ceilings, or in furniture. Bed bugs traveling on a headboard never see a monitor on the floor.
• Wrong species coverage. Pheromone traps for stored product moths do not catch beetles. Pheromone traps for German cockroaches do not catch American cockroaches.
• Wrong height. Crawling-pest monitors need to be at the floor-wall junction. A monitor on a counter catches almost nothing because few crawling pests travel mid-cabinet.
• Wrong duration. A pheromone lure that has been deployed for 60 days when its rated life is 30 days has lost the attractant. Same monitor reads zero because no pests are attracted, not because no pests are present.
• Wrong scope. The property has 12 rooms and 3 monitors. The 9 monitor-free rooms can house an entire infestation invisible to the program.

For each of these, the fix is the placement, the species coverage, the schedule, or the scope, not the customer.

Reading the customer's report

The customer report itself contains diagnostic information. Useful questions:

References

1. NPMA technical resources on monitor placement, IPM thresholds, and sighting-based vs monitor-based action thresholds.
2. EPA FIFRA and 40 CFR Part 156 - labeling requirements; re-treatment decisions must comply with the product label's maximum application intervals.
3. University Extension entomology publications on insect monitoring and threshold-based pest management (e.g., Cornell IPM Program, Purdue Urban Entomology, University of Kentucky Entomology) covering monitor sensitivity, species-specific lure life, and the interpretation of zero catches.