Follow-Up and Re-Treatment Protocol SOP

Purpose

Define the standard operating procedure for follow-up visits and re-treatments when pests persist or recur after initial treatment. The follow-up discipline is the single biggest difference between commodity pest control and professional pest control. Most pest infestations are not eliminated in a single visit - eggs hatch, pupae emerge, new individuals find their way in from adjacent properties. Companies that handle the follow-up well retain customers and build referral pipelines; companies that leave after a single visit are forever chasing new customers to replace the ones who churned.

Scope

Applies to:

• Every initial treatment visit
• Every customer reporting continued pest activity after treatment
• Every recurring-service customer between scheduled visits
• All pest categories: insects, rodents, wildlife (within scope of the company's license)

Responsibilities

• Service technician identifies the need for follow-up at the initial visit
• Office schedules the follow-up appointment
• Customer communicates pest activity between visits
• Owner / GM reviews repeat callback patterns

Initial visit - set the follow-up expectation

At every initial pest treatment visit:

1. Identify the pest accurately
2. Treat the pest with the appropriate product and approach
3. Set expectations for what the customer will observe:

• When activity should decline
• Whether some activity is expected initially (pupal emergence, etc.)
• What "success" looks like at the 2-week and 4-week marks

1. Document the initial findings with photos
2. Schedule the follow-up before leaving the property

The customer who's been told "watch for ____ over the next 14 days, then we'll come back" is a customer who's not surprised when the followup happens. The customer who hasn't been prepared often interprets normal post-treatment activity as failure.

Standard follow-up windows by pest

These are starting points. Individual customer situations may require more frequent visits.

Follow-up visit procedure

Step 1: Review the customer file

Before the visit:

1. Read the initial treatment notes
2. Review the photos from the initial visit
3. Note the products used, application areas, dilution rates
4. Note the expectations set with the customer

Step 2: Customer interview

On arrival:

1. "How has it been since the initial visit?"
2. "What activity have you noticed?"
3. "Anything specific you want me to look at?"

Listen carefully. The customer's description of post-treatment activity is the diagnostic.

Step 3: Inspection

1. Walk the property focusing on the originally-treated areas
2. Check sticky monitors, traps, bait stations
3. Look for evidence of continued activity:

• New droppings (rodents)
• Live insects
• New mud tubes (termites)
• Active trails (ants)
• New damage

1. Note any new infestations or activity in previously-untreated areas

Step 4: Documentation

1. Photo the current state
2. Compare against initial-visit photos
3. Document any pest still observed
4. Note the area's response to treatment

Step 5: Decision tree

After inspection:

Step 6: Re-treatment (if needed)

1. Identify what's different from the initial treatment
2. Adjust the approach:

• Different product (resistance issue)
• Different application method
• Targeting missed areas
• Higher concentration within label allowance

1. Apply re-treatment
2. Document the change

Step 7: Customer communication

1. Show the customer what you observed
2. Explain the action taken
3. Schedule the next follow-up
4. Provide written documentation of the visit

Step 8: Update the customer file

1. Visit notes
2. Photos
3. Products applied
4. Next visit date

What's NOT a callback

Some post-treatment activity is normal:

• Dead insects appearing for days after treatment: bait took effect; clean up but no re-treatment needed
• Fleas emerging from pupae for 2-4 weeks after treatment: expected
• Cluster flies appearing in warm weather mid-winter: the colony is dying; vacuum visible flies
• Ant trails to previously-treated bait: the bait is working as intended; let it continue

Educate the customer rather than re-treating prematurely.

What IS a callback

Some signs require return:

• New live insects/rodents in numbers
• New mud tubes (termite)
• Pest activity in previously-untreated areas (expansion)
• Customer reports of new bites or stings
• Increased activity above pre-treatment baseline

These get same-week response.

The "warranty / re-treatment" promise

Most pest control companies offer a re-treatment guarantee:

• If pests are observed within X days/months of treatment, return at no charge
• Typical period: 30 days for general pest control, 90 days for termite, ongoing for contract customers

This is not a money-back guarantee - it's a re-treatment guarantee. The customer gets additional service, not a refund. Most issues resolve with one follow-up; severe persistent issues may require multiple.

Pattern recognition

The office should track:

• Callback rate per technician
• Callback rate per pest type
• Recurring problem properties

A technician with rising callback rates needs coaching. A pest type with rising callbacks may need a product change. A property with recurring problems may need source elimination beyond standard treatment.

When the customer calls back outside the scheduled follow-up

If a customer calls reporting continued activity before the scheduled follow-up:

1. Take the call seriously and take it on the phone. Do not route it to "we will see you at the scheduled visit" before you know what they are seeing. A customer who feels dismissed at this call is the one who cancels.
2. Get specifics before deciding anything. What did they see, how many, which room, what time of day, and how does it compare to before the treatment. "A few dead ones in the kitchen" and "live roaches on the counter at noon" are different calls with different answers.
3. Sort it against the two lists above. If it is expected post-treatment activity (dead insects, flea emergence, ants working a bait), explain what is happening and why it is the treatment working. Set the date they should expect it to stop, and note the call on the account.
4. If it is a real callback, schedule inside the same week and say so on the call. Same-week response is the standard, and hitting it is most of what the customer is judging.
5. Pull the original ticket before the tech goes back. What was treated, with what, where, what conditions were documented, and what the customer was asked to do. The tech should arrive knowing the history, not re-interviewing from scratch.
6. Treat the return as a diagnostic visit, not a repeat application. Re-inspect, re-read the monitors, and find what the first visit missed: wrong species, missed harborage, an untreated adjacent unit, a customer-side condition, a source outside the treated area, or resistance. Applying the same product to the same places is how a callback becomes three callbacks.
7. Log it as a callback in the system, against the technician and the pest type, even when it is a five-minute education call. The pattern data above is only as good as the logging discipline.
8. Do not charge for it inside the guarantee period. Do note in the record when the cause was a customer-side condition, so a pattern of free returns on an uncorrected condition becomes a conversation about the condition rather than a permanent cost.
9. Reset expectations for the rest of the program. Confirm the next scheduled visit, what the customer should watch for, and what they should call about immediately versus note for the next visit.

References

• IPM (Integrated Pest Management) principles
• NPMA (National Pest Management Association) Service Excellence Standards
• State pesticide regulatory requirements for service documentation
• Manuall internal: Integrated Pest Management, Quarterly Residential Pest Service SOP, Customer Complaint Resolution