Manuall Trade Library Run your shop on Manuall

Counts Meet Threshold But Complaint Persists Reading-In-Spec Decision Tree

Troubleshooting Diagnostics Updated Jun 19, 2026 ยท Pest Control

Why this matters

A commercial account where sticky-trap counts have dropped below the contracted threshold, fruit-fly cards read clean, and the rodent stations show no take, but the customer keeps calling: this is the classic "in-spec but unhappy" scenario. Treating it as a chemistry problem leads to over-application, label violations, and a rotating tech roster. Treating it as a customer-management problem alone ignores the real possibility that the monitoring program is sampling the wrong space. The decision tree below sorts the call into the right bucket fast and protects both the account and the technician's program from drift.

Step 1: Confirm the counts are real

Before defending the program, audit it. Pull the last three service reports and re-walk the building with the customer's complaint locations specifically in mind.

  • Are the monitors actually where the contract says they are? Equipment migrates. A glue board kicked behind a pallet for six weeks reads zero by default.
  • Are the monitors fresh? A glue board past its service life loses tack; a pheromone lure past its rotation date stops attracting.
  • Is the count methodology the same tech to tech? One tech counts adults only, another counts all life stages, the chart looks like a victory but the underlying biology has not changed.

If the audit shows the program is not measuring what it claims to measure, the in-spec reading is an artifact. Fix the program before fixing the chemistry.

Step 2: Match the complaint to the monitor coverage

The customer is reporting sightings in a specific area. Are the monitors covering that area?

A bakery whose monitors are in the dry-storage room but whose complaint is on the proofing-room floor has a sampling gap, not an in-spec performance. A medical office whose monitors are in the basement utility chase but whose complaint is in the third-floor break-room kitchen has a sampling gap. The reading is in-spec for the sampled space; the complaint space is uninstrumented.

The fix is to extend the monitoring grid, not to escalate chemistry. Add monitors to the complaint area, baseline for two service intervals, and judge from real data.

Step 3: Match the pest sighted to the pest measured

A drain-fly monitoring program reads zero. The customer reports flying insects. Are they actually drain flies?

Phorid flies, fungus gnats, fruit flies, and drain flies all look small and dark to a stressed receptionist. A program tuned to the wrong target species will read in-spec while a different species runs unimpeded. Ask the customer to capture a specimen in a clear cup with a damp paper towel and identify before responding. The wrong target species explains a striking share of "in-spec but complaint" calls.

Step 4: Check for time-of-day or shift mismatch

Monitors integrate over the full service interval; complaints are point-in-time. A monitor that reads three German roaches over thirty days can still produce a dramatic sighting at 2:30 AM when the night-shift cook turns on the dish pit lights.

  • When does the customer see the pest?
  • When does the tech service the account?
  • When was the building constructed, last remodeled, or last had refrigeration replaced?

A monitor on the day-shift floor that reads in-spec tells you nothing about night-shift activity in a different room with different conditions. The fix is to expand the monitoring window: add a remote-readable device, place a monitor in the night-shift area, or schedule a single after-hours inspection.

Step 5: Distinguish active pressure from imported pressure

A monitor that reads zero week after week and then suddenly reads three is usually showing imported pressure: a new delivery, a new employee bag, a returning food shipment, a piece of used equipment.

If the spike is isolated to a single monitor near a receiving door, the program is working as designed; the customer's complaint is about inbound logistics, not about the pest-control program. Document the source, advise the customer on inbound inspection of pallets and packaging, and resist the urge to broadcast-treat.

Step 6: Honest conversation about expectations

Sometimes the program is correct, the counts are correct, the sightings are real, and the customer's expectation is zero-tolerance in a building that the IPM threshold treats as acceptable at low levels.

  • Restate the contracted threshold in plain language.
  • Show the trended count chart from the last six services.
  • Explain what is realistic, what is achievable with additional sealing or sanitation work, and what is not achievable at any application rate that the label allows.

This conversation is uncomfortable, but it is the one that prevents the slow slide into label violation. A technician who keeps escalating chemistry to chase a zero-tolerance expectation eventually applies off-label and loses both the account and the license.

Pesticide application above labeled rates or frequencies to satisfy a customer complaint is a federal violation under FIFRA, regardless of customer pressure. When the monitoring data says in-spec, the appropriate response is more monitoring, better sanitation, structural correction, or a frank scope conversation, not heavier chemistry.

Decision tree summary

  1. Are the monitors placed, fresh, and counted consistently? If no, fix the program first.
  2. Are the monitors covering the complaint area? If no, extend coverage and rebaseline.
  3. Is the pest reported the pest measured? If no, identify the actual species.
  4. Is the sighting happening outside the sampled window? If yes, expand the window.
  5. Is the activity isolated and inbound? If yes, address logistics, not the building.
  6. Is the customer's tolerance below the IPM threshold? If yes, have the scope conversation.

Run the call through these six gates in order. Most "in-spec but complaint" calls resolve at gate two or three.

References

Related articles