pest_control_route_operations v1.0.0

name: pest_control_route_operations description: "Running a pest control route with the chemical record treated as part of the service: recurring service windows held by contract, product and dilution records logged per stop the way state applicator rules expect, callback and free re-service requests tracked by pest and product so patterns surface, interior access and pet instructions kept on the stop record, and route days rebuilt when callbacks cluster. Use when planning a pest route day, writing a per stop service or chemical record, logging or analysing callbacks, tracing a callback cluster to its cause, or rebuilding a route after callbacks pile up."

Pest Control Route Operations

Purpose

Run a recurring pest control route as one system: the contract window that holds each account, the stop record that proves what was applied and where, the access and pet instructions that let the next technician walk in and work, and the callback log that turns free re-services from a cost you absorb into a pattern you can read. Field service software holds addresses and invoices, and treats the chemical record as an add on. Here the chemical record is part of the service, because a state inspector, a customer with a sick pet claim, and your own callback trace all read the same record.

Workflow

1. Hold the service window by contract

• Write each account's window from its own contract: service interval, the days or dates the window allows, interior or exterior scope, the pests covered, and the callback terms, meaning which return visits are free, for which pests, and for how long after service. There is no standard industry window to borrow. If the contract does not say it, the route does not promise it.
• Build route days from windows that are actually due, in geographic clusters, the same discipline as any route trade. An account serviced early to fill a light day is an account whose next window drifts, whose product interval shortens, and whose record shows a pattern nobody chose.
• Put accounts with a recent callback, a heavy infestation on monitors, or a timed interior access window early in the day, while a same day return is still possible.
• Keep callback visits visible as callback visits on the route sheet. Folding them into a regular day without a label hides the callback rate the business needs to see.

2. Before the stop, read the stop record

The stop record is the handover. Before leaving the previous stop, read:

• Access: gate, lockbox, alarm, who must be home, and what happened last time access failed
• Pets and sensitive occupants: animals on site and where they are kept during service, fish tanks, birds, anyone who asked for notice before application
• Last service: products applied with EPA registration numbers, target pests, monitor counts, and the flag the last technician left
• Open items: callback history for this account, sanitation notes not yet confirmed fixed, exclusion work quoted but not done

A technician who learns about the indoor cat or the locked gate at the door has already lost the stop. That information lives on the record or it does not exist.

3. At the stop, work in IPM order

EPA integrated pest management runs in this order, and a route stop follows it instead of starting with the sprayer:

1. Inspect and identify. Confirm the pest from evidence, monitors, frass, webbing, or the insect itself. A misidentified pest produces a correct looking application that cannot work, and a callback nobody can explain.
2. Check the threshold. Decide whether activity crosses the level where treatment is warranted for this account and this pest. One harmless insect on a monitor is a note, not an application.
3. Prevention first. Record the conditions feeding the pest: food, water, shelter, entry gaps. Seal, remove, or report them in the record, with the customer's part stated plainly when the fix is theirs.
4. Control, least risky first. Traps, baits in placements insects reach, exclusion, and targeted application before any broad spray. Broadcast spraying is the last resort in the EPA sequence, not the default opening move.
5. Evaluate at the next visit. Monitor counts and callback history say whether the control worked. Write the comparison down instead of carrying it in memory.

4. The per stop chemical record

Fill in one record per stop, at the stop, from the label in hand. Never reconstruct it at the end of the day, because the product name and registration number exist only on that label at that moment. Fields:

• Date and time of service, technician name and license or certification number, and the supervising applicator where state rules require one
• Customer billing name and address, and the service address if different
• Target pest or pests, and the site treated, stated as rooms, areas, or structures, with the size of the area treated where the state rule asks for it
• For every product applied: brand or product name exactly as printed on the label, EPA registration number, total amount applied, and for diluted products the mixing rate plus the amount of concentrate and diluent used
• Devices used and the count of each: monitors, traps, bait stations checked, refilled, or replaced
• Application equipment type, where the state rule asks for it
• Inspection findings: pest evidence, monitor counts, sanitation and entry conditions, and what was corrected on site
• Customer instructions given: preparation done or still owed, re-entry direction from the label, pet instructions followed
• Flag for next visit: one line the next technician acts on without rereading the whole history

The field list and its sources are in references/record-fields-and-sources.md. Federal restricted use records under 7 CFR Part 110 require product name and EPA registration number, total amount, location and site, date, and applicator name and certification number, kept for two years. State structural rules usually go further and cover every application. Texas, for example, also requires the mixing rate, the device count, and the target pest, kept two years at the business premises. Use the stricter list, state or federal, for the state the work is in.

Mix math, when the label gives a rate in fluid ounces per gallon:

python3 scripts/pest_ops.py mix --finished-gal 3 --rate-oz-per-gal 1.0

finished_solution: 3.00 gal

concentrate: 3.00 fl oz

water: 2.977 gal

The rate always comes from the label for the product in hand. A rate remembered from a different product is a wrong record and possibly an illegal application.

5. Access, pets, and occupants, handled as record fields

• Pet instructions sit on the stop record, not in a text thread: animals present, where they are secured during service, who secures them, and the re-entry direction given. NPIC guidance is to remove pets, pet toys, bedding, and food and water bowls from the treatment area before application, and to keep pets away for the time on the label or until sprays have dried completely, whichever is longer.
• For foggers, all animals leave the home. For baits, record placement locations, because bait ingredients can attract pets and a customer needs to know where placements are before a dog finds one.
• Fish tanks, bird rooms, and food preparation areas get a named note on the record with the protection used, or the area is skipped and the skip is recorded with its reason. Avoid treating food preparation areas unless the label allows it.
• A failed access is a record, not a shrug: time arrived, what was locked or missing, who was contacted, and the reschedule window. Repeated access failures on one account go to the office as a contract conversation, not a fourth wasted drive.

6. Callbacks, tracked by pest and product

A callback is any return request for a covered pest inside the contract terms, and a free re-service is the visit that answers it. Log every one, including the ones that turn out to be nothing, because the pattern only surfaces when the log is complete.

One row per callback, in a CSV or the route system, with these columns:

• date, customer_id, pest, product (the product used at the service being called back), irac_group of that product's active ingredient, area or route, days_since_service, cause_found

Fill cause_found at the callback visit, when the cause can be seen, never at intake from the customer's phone description alone. Honest cause values include: placements eaten and gone, no bait taken, competing food source, entry gap unsealed, product interval too long, misidentified pest, no activity found.

Run the tracker weekly or monthly:

python3 scripts/pest_ops.py callbacks --file callbacks.csv --min-count 3 python3 scripts/pest_ops.py rate --callbacks 14 --services 212

callback_rate: 6.60%

The tracker groups by pest plus product, pest plus IRAC group, and area plus pest, and flags any group at or above the cluster threshold. Grouping by IRAC group matters because product names hide the pattern: three different gel baits can share one mode of action, and UF/IFAS guidance on German cockroaches is to rotate baits across different IRAC groups to slow resistance and to plan for bait aversion, where a population avoids a bait outright. A cluster grouped by product alone can look like three small problems. Grouped by IRAC group it reads as one.

7. Trace a cluster before changing anything

A flagged cluster is a lead, not a verdict. Trace it in this order and write each step's result in the callback log:

1. Identification: re-inspect at least two accounts in the cluster and confirm the pest. A cluster built on a misidentification dissolves here.
2. Placement and dose: were placements eaten and gone, untouched, or missing? Eaten and gone points to amount and harborage coverage. Untouched points toward aversion or a competing food source. Missing points to placement or housekeeping.
3. Site conditions: sanitation, water, and entry points at the cluster accounts, compared against what the original stop records said. Conditions the first visit never recorded are a record problem as much as a pest problem.
4. Product history: same product, or same IRAC group, across consecutive visits at those accounts? No rotation is a finding on its own.
5. Interval and coverage: did the service interval outlast the product, or did the original service skip the harborage where activity now shows?

State the cause plainly, including when the cluster has more than one cause or the trace ends at inconclusive. Then act on the cause: rotate to a different IRAC group, change placement count or location, shorten the interval for the affected accounts, fix the site condition, or correct the stop record field that let the cause hide. Rotating the product without doing the trace is guessing with a different label.

8. Rebuild the route day when a cluster lands

• Pull the cluster accounts out of their regular slots and schedule their callback visits as one geographic block, early in a route day, with time for inspection and not only re-treatment.
• Move regular stops that no longer fit to another route day inside their contract windows. Do not shorten regular stops to absorb callback work silently. That trades a visible cluster for invisible thin service everywhere else.
• Book any mid-interval check visits the trace calls for as callback work, with their own records, until monitor counts or two clean checks say the accounts return to the regular interval. State which test you are using before the visits start.
• Singletons get stop level fixes and no route change. One callback with a seal gap is a repair note. A cluster changes the route, a singleton changes the stop.
• After the rebuilt week, rerun the tracker. A cluster that keeps growing after the fix means the trace was wrong or incomplete, and it reopens rather than closing on hope.

The full worked month, including the cluster trace, the route rebuild, and the end of month check, is in references/worked-route-month.md.

Output Contract

• A route plan returns: route days built from contract windows that are due, cluster accounts blocked together with their visit type labelled, stops moved to other days with the window check shown, and callback blocks separated from regular stops.
• A per stop record returns every field in section 4, completed at the stop, with product names and EPA registration numbers copied from the label, amounts and mixing rates stated exactly, and the next visit flag written.
• A callback report returns: total services, total callbacks, the callback rate, groups by pest plus product and by pest plus IRAC group with counts and average days since service, clusters flagged, and for each cluster the trace result and the action taken.
• A cluster trace returns the five checks in section 7, each with what was found, the cause stated plainly, and the route and product changes that follow from it.

Operating Rules

• The label is the law. Using a pesticide in a manner inconsistent with its label directions is a violation of FIFRA. The label in hand beats this skill, beats habit, and beats any prior record. Never apply a product to a site or pest its label does not cover.
• Only licensed or certified applicators, and supervised technicians where the state allows them, apply product. Know which category the stop requires before the route day is built, not at the door.
• Never invent a guarantee window, a re-entry time, a dilution rate, or a state retention period. Guarantee terms come from the account's contract, re-entry and rates come from the label, and retention comes from the state rule. When a source is not in hand, say so and get it before acting.
• Keep records for the period the state rule requires, two years in the federal restricted use rules and in the Texas and Virginia structural rules cited here, and longer where the state requires longer. Records must be producible when the state asks.
• Do not record a cause for a callback before the callback visit. Intake notes are the customer's report, labelled as such, and the cause field stays open until someone has looked.
• Photos, monitor counts, and amounts stay factual. No rounding a count down, no reusing a prior visit's photo, no recording a placement count that was not placed.
• Customer details, gate codes, alarm codes, and pet instructions stay in the route system they belong in. This skill is the method, not a place to store a customer list.
• When a customer reports a possible exposure, a sick pet, or a child in a treated area early, stop the operations work and follow the label's first aid directions and the company's incident process. The record for that stop gets completed in full, because it is the document that will be read.