In this guide 6 sections
Technician productivity in pest control is set by route design, training and pay structure long before it is set by how hard anyone works. Give each new technician a named trainer, a written method and thirty supervised jobs, then pay only on jobs that close without a repeat complaint.
Productivity as a routing problem
One technician completes four jobs a day and another completes seven, and the first assumption is usually effort when a manager first reads the weekly sheet. More often the cause is the route. Seven jobs inside one housing layout and four jobs scattered across the city are different working days, and the second technician may be working harder for a worse number.
Before judging anyone’s performance, measure travel time as a share of the working day, because a badly built route can keep a technician on the road for three hours. Motivation does not give those hours back.
Cluster jobs by area and by weekday. Reschedule a postponed treatment into the area it belongs to, not into whichever slot happens to be free, and each technician may gain a visit a day.
The first ninety days
Many technicians who quit do so in their first three months, often because they were sent out alone before they were ready and then blamed for the complaints. Nobody taught them the method.
Give every recruit a named trainer, not a rota of whoever is free that week, and keep that trainer until sign-off on each service. Add a written method for each service sold, plus a fixed number of supervised jobs before solo work: thirty suits routine residential visits, and termite work needs more.
Record each technician’s sign-offs. A technician certified for cockroach and bed bug work but not for anti-termite treatment should never appear as available for a termite job in the scheduler.
Pay tied to quality
A per-job incentive with no quality gate produces exactly what it rewards: more jobs, done faster, with thinner application and more callbacks inside the warranty period. The bill arrives a month later as unpaid repeat visits that nobody traces back to the pay structure and gets blamed on the customer.
Pay the incentive on jobs completed and closed without a repeat complaint inside the warranty window, because that single condition changes behaviour on site more than any instruction does. Keep the rule simple.
Publish the measure and its source. Technicians then see their own numbers the day after the job instead of at a quarterly review, and most pay disputes turn out to be disputes about record keeping.
The monsoon and the seasonal peak
Pest control demand swings with the seasons, and the usual response is to hire a crowd for the peak and lose them in the trough. Training never ends and experience never accumulates.
A better shape is a smaller permanent team kept busy all year on annual maintenance contracts, with a known list of trained part-time technicians to cover the peak. Recurring contract revenue pays for that permanent headcount through the quiet months when one-off call-outs dry up, which spares the owner a choice between idle technicians and layoffs.
Keep the peak list warm between seasons. A technician trained last year who can be called back outweighs a new hire in peak week, and staying in touch costs almost nothing.
The records behind all of this
None of this works from memory. It needs work order history for travel and completion times, a certification list for scheduling, and complaint records tied to the job and the person who did it.
Each is an ordinary field. Most operators cannot run this approach because the data sits on paper and is never assembled, not because it is hard to collect.
Start with two numbers per technician. Completion time and warranty complaints, taken over three months, settle most arguments about who is productive before anyone has to raise their voice.
Ninety day technician onboarding plan
A week by week plan for a new technician. It lists which services they shadow and how many supervised jobs come before sign-off. It also shows what the trainer records, and when they may be scheduled alone for each service sold.
Open a blank worksheet to printQuestions owners ask
How many supervised jobs before a technician works alone?
Around thirty for routine residential services, and considerably more for anti-termite and fumigation work, where a mistake is expensive and slow to surface. The number matters less than sign-off by a named trainer against a written method, and a signature beats a calendar date every time.
Should technicians be paid per job?
Only with a quality condition attached. A per-job incentive with no warranty gate produces faster, thinner treatments and more callbacks, so tie the incentive to jobs closed without a repeat complaint inside warranty.
How do we stop an untrained technician being scheduled for a job they cannot do?
Hold certifications in the scheduler, not a file. If the system knows a technician is not signed off for termite work, that job cannot be assigned to them, which is more reliable than a supervisor remembering.