Every owner asks this eventually, usually when a route needs covering and there is a half-trained person sitting in the office.
The honest answer is that it is the wrong question, and the reason it is the wrong question is the most useful thing in this article. But before that, there is a mistake almost everybody makes at the very start, and it decides everything that follows.
Most companies train for the license. That is the first error.
Somebody gets hired. They go through HR, the paperwork, the handbook. Then the training starts, and in most companies the entire focus of that training is passing the state licensing exam.
I do the opposite.
Train them to your business. Your policies. Your procedures. Your protocols. What your customers actually need and what they will ask for. Do that properly and the license exam passes itself, because you have taught them the material in the context they will use it in rather than in the context of a test.
Train for the exam and you get somebody who can pass the exam. That is all you have proven and it is not much.
Field training does not come after. It runs alongside.
This is where most training plans are built wrong. Classroom first, then field. A block of one, then a block of the other.
It should be happening at the same time, and the first part of it does not need a customer at all.
Start on your own property. Put a B&G in their hands and let them spray water. Let them service bait stations around your own yard using the handheld, so the device and the software stop being a thing they have read about. Ladders. Safety. Where a device goes and why it goes there rather than eighteen inches to the left.
None of that requires a paying account, and all of it is field training. Doing it early means the first time they are in front of a customer, the equipment is not the thing they are thinking about.
Then the real field work, and the roles reverse
Now you go out.
And here is the part that most companies get backwards. On a proper field visit the new technician works and you watch. Not the other way round.
The usual version has the trainer doing the job while the new person follows, watches, and carries things. At the end of three weeks of that you have somebody who has seen the job done well many times and has never once done it themselves.
You are out there for two reasons, and neither of them is to demonstrate.
To watch them interact with the customer. How they handle the conversation at the door, what they do when someone is annoyed, what they say when they do not know the answer.
To watch them make decisions. Specifically, to watch them adapt. You spent the classroom time describing situations. The field is where you find out whether any of that turned into judgment, or whether it stayed a list of facts.
A person who can recite the biology and then freezes in an unfamiliar basement has not learned the thing you thought you taught.
A ride-along log proves nothing on its own
“He rode with Dave for three weeks” is a statement about a schedule.
It says somebody sat in a truck for fifteen days. It does not say what they can do at the end of it, and it is the same weak proof as an attendance sheet with a signature on the bottom.
If you cannot say what a person is now able to do without help, the three weeks were a duration, not a training program.
So what ends it?
Not a date. Not a number of accounts.
Once they have been out enough times that you have seen them handle real situations, you build the list. Specific check-offs and milestones, written down, running out over the following months and years.
That list is where the career path starts, and it is a whole subject of its own that I am not going to try to compress into a few paragraphs here. What matters for this article is that the list exists and that it is written before you need it, because a milestone invented on the day somebody asks for a raise is not a milestone.
Letting them out is not the end of training
Here is the answer to the question at the top.
There is no point at which enough field training has happened. You do not finish. You change the interval.
Once a technician is out on their own, competency checks continue on a schedule. What I use:
Year one, at six months and at nine months.
Year two, at three months, six months and twelve months.
Year three, at six months.
Notice that year two is heavier than year one. That is deliberate and it is the opposite of what most companies do. Year one gets all the attention because the person is new and visibly needs help. Year two is when the habits set, and it is when quiet drift starts, and almost nobody is watching by then.
What that schedule is actually building
Three things, and only one of them is knowledge.
Retention. You are finding out what has survived and topping up what has not, before it costs you an account.
Trust. Yours, in them. Not a feeling, evidence. You know what they can do because you checked, recently.
And theirs. A technician who has been checked and passed knows they can do the job. That confidence is worth as much as the competence, because a technician who is unsure of themselves avoids the difficult account, and the difficult account is the one that cancels.
And then you grow them
Once someone is genuinely competent at the work you hired them for, the question changes.
What other pests can they learn? What other services could they carry? Where else in the business could they be useful, and what would they actually enjoy?
That is not a nice-to-have. It is the alternative to watching a good technician get bored in year three and take everything you invested to the company down the road.
Where to start
Take whoever you trained most recently and answer two questions on paper.
What can they do now, unaided, that they could not do when they started? And when is the next time anybody is scheduled to check?
If the first answer is vague and the second is never, you do not have a training program. You have an onboarding period, and they are not the same thing.
Dominique Sauvage, ACE, PCQI, founder of Sequoia Quality Solutions. He speaks and writes on technician development, retention, and audit-ready quality programs. More at sqs-usa.com/speaking.