Training a new technician: your growth ceiling is what you can build, not what you can hire

The four rings

The most useful way to structure this is to define what a technician can do unsupervised, and expand that outward deliberately.

Ring 1 — safety, vehicle and company. Before any customer contact: safety procedures, tool handling, vehicle and equipment care, paperwork, the software, how to call for help. Days, not weeks, and completed before anyone rides anywhere.

Ring 2 — assist. The technician works alongside someone with defined responsibilities of their own, not as an observer. Specific tasks they perform while the lead handles the rest. The distinction matters enormously: watching produces very little, and doing a defined part produces competence.

Ring 3 — supervised solo. They run the call, with the lead present but hands-off, stepping in only when asked or when something goes wrong. Uncomfortable for both, and the ring where most of the actual learning happens.

Ring 4 — independent, by job type. The critical insight here is that independence is not a single switch. A technician may be fully independent on maintenance and diagnostics while still requiring support on installations. Define the ring per job type, write it down, and dispatch accordingly.

Managing a new technician's schedule against a written list of what they are cleared for is the single practice that separates companies that build technicians from companies that hope.

The competency list, verified rather than assumed

The mechanism that makes the rings real is a list of specific, testable competencies — not topics, but tasks with an observable standard.

"Understands refrigeration" is a topic. "Can recover, evacuate and charge a system to specification without assistance, and explain the readings" is a competency. The second can be signed off; the first cannot.

Four rules make the list work. Each item is verified by someone watching it done, not by a conversation. Each has a date and a name attached. The list is visible to the technician, so they know what they are working toward rather than waiting to be told they are ready. And nothing is signed off early to be encouraging — an item signed off before it is true creates a dispatch decision that will fail in a customer's home.

Choosing and paying the mentor

Two mistakes are near-universal. The first is assigning the best technician, who is frequently the worst teacher — high skill often correlates with having found it easy, which is precisely the wrong experience for explaining it. Look instead for patience, willingness to be interrupted, and the habit of explaining why rather than only what.

The second is not paying for it. A mentor on production-based pay loses money every time they slow down to teach, and no amount of encouragement overcomes that arithmetic. Pay for mentoring explicitly — a stipend for the period, a bonus when the apprentice reaches defined competency, or a protected reduction in their own targets during the training window. Companies that add this line typically find that mentoring quality improves immediately, because it becomes work rather than an imposition.

The part that is harder to teach

Technical skill is the easier half. What separates a technician customers request from one they tolerate is a set of behaviors that rarely appear in any training plan.

Explaining a problem in language a homeowner understands, without condescension and without jargon. Delivering bad news — that the repair is not worth doing, that the estimate was optimistic — clearly and early rather than at the end. Handling a customer who is angry about something that happened before the technician arrived. Knowing when to stop working and call the office. And the small physical courtesies that customers notice more than any technical explanation: shoe covers, cleaning up, not leaving the gate open.

These are teachable, and the method is different: they are learned by watching them done well, then doing them while someone listens, then being given specific feedback afterward. A mentor who debriefs for five minutes after each call — what went well, what to say differently — produces this faster than any classroom.

The ramp, and when a new technician pays for himself

Owners routinely underestimate this timeline and then panic in month three. A realistic ramp for a genuinely new technician runs four to eight months to full productivity, with negative contribution for the first two or three.

Knowing that in advance changes two decisions. It changes hiring timing — you hire ahead of the demand, not in response to it, because a technician hired in April is not productive for the summer. And it changes how you evaluate progress: month-three revenue is not a signal of anything, while competency sign-offs at month three are.

It also argues for hiring in pairs where cash flow permits. Two apprentices can practice on each other, compare notes, and the second one costs less to train than the first because the material has already been organized.

Two years, measured

A plumbing company with eight technicians, roughly $3.1 million in revenue, in a market where experienced hires had become unavailable.

Starting point. Hired experienced when possible; otherwise a new person rode along informally for a month. Of the last six technicians hired, four had left within eight months. Callback rate among technicians with under a year of tenure was 17%.

What changed. The company built a written competency list of 84 items across four rings, with sign-off required by a named lead. It designated two mentors — not its two best technicians, deliberately — and paid a stipend plus a completion bonus. It stopped dispatching new technicians to any job type they were not cleared for. And it added a five-minute post-call debrief as a required part of the mentor's day.

Two years later. Seven technicians hired, six still with the company. Callback rate among technicians under a year fell from 17% to 6.1%. Time to full productivity fell from an estimated nine months to 5.5 months, measured by revenue per technician-day reaching the company average.

The financial effect was largest where it was least visible. The company estimated it avoided roughly $118,000 in turnover cost over the two years, and the reduction in early-tenure callbacks recovered about 240 technician-hours annually — nearly a third of a full-time position, recovered from work that had been done twice.

Hiring for trainability instead of experience

Once a company accepts that it will build technicians rather than buy them, the hiring criteria change completely — and most job postings have not caught up.

A posting that asks for five years of experience is competing for a person who does not exist in sufficient numbers, and who, if found, arrives with habits from another company that may or may not match yours. A posting that asks for the traits that predict success in training is competing in a much larger pool.

Four signals matter more than trade experience. Mechanical curiosity — evidence that this person takes things apart, fixes what breaks at home, understands how something works because they wanted to. Comfort in strangers' homes, which sounds trivial and is not: a large share of this work is being calm and respectful in someone's private space while they watch. Tolerance for being bad at something, since the first six months involve daily incompetence in front of an audience. And a real reason to be in the trades, because the ones who chose it stay and the ones who ended up in it drift out.

Two practical sources are consistently underused. Adjacent hands-on trades — auto repair, appliance work, maintenance, even kitchen work — produce people who already understand tools, schedules and physical days. And the second-career hire in their thirties often outperforms the twenty-year-old, because the decision was deliberate and the customer-facing maturity is already there.

One caution worth stating plainly: hiring for trainability only works if the training exists. Hiring inexperienced people into an informal ride-along is worse than hiring experienced ones, not better.

Five mistakes in training technicians

• Treating the ride-along as a program. It is a random sample of jobs with no verification attached.
• Assigning your best technician as mentor by default. Skill and teaching ability are different, and one does not imply the other.
• Not paying for mentoring. On production pay, teaching costs the mentor money, and the behavior follows the incentive.
• Signing off competencies to be encouraging. The consequence lands in a customer's home, not in a file.
• Expecting productivity at month three. Panicking on the wrong timeline is how companies fire people who were about to become good.

The numbers to watch

Five metrics tell you whether training is working. Time to full productivity, defined as revenue per technician-day reaching the company average, which is the master measure. Callback rate segmented by tenure, because a company-wide average hides exactly the problem you are trying to fix. Retention at six and twelve months, since most departures happen early and usually because the person felt lost rather than underpaid. Competency completion rate against plan, which is the leading indicator — it moves months before the revenue does. And mentor output during training periods, watched deliberately, because if your mentors are quietly paying for the program out of their own paychecks, the program will stop working the moment nobody is looking.

Frequently asked questions

Why does the ride-along fail as technician training?

It fails consistently, for reasons that have nothing to do with either person involved. The mentor is measured on his own output, so every minute spent explaining costs him money and puts him behind. He was hired for skill rather than teaching, and being excellent at something is not the same as being able to transmit it. The new technician sees whatever jobs happen to come in that week, which is a random sample rather than a curriculum. And nobody is checking what was actually absorbed — at the end of three weeks, the only evidence is that the new person was present. Ride-alongs are useful, but they are not a training program. The difference is that a program specifies what must be learned, in what order, and verified how, with someone accountable for confirming each item was demonstrated rather than discussed.

How should a new technician's training be structured?

Around what they can do unsupervised, expanding outward through four rings. Ring one is safety, vehicle and company — safety procedures, tool handling, equipment care, paperwork, the software and how to call for help — completed in days, before anyone rides anywhere. Ring two is assist, where the technician works alongside a lead with defined responsibilities of their own rather than as an observer, because watching produces very little and doing a defined part produces competence. Ring three is supervised solo, where they run the call with the lead present but hands-off, which is uncomfortable for both and where most of the actual learning happens. Ring four is independent by job type, and the critical insight is that independence is not a single switch: someone may be fully independent on maintenance and diagnostics while still needing support on installations.

How long until a new technician becomes profitable?

A realistic ramp for a genuinely new technician runs four to eight months to full productivity, with negative contribution for the first two or three — and owners routinely underestimate this and then panic in month three. Knowing the timeline in advance changes two decisions. It changes hiring timing, because you hire ahead of demand rather than in response to it: a technician hired in April is not productive for the summer. And it changes how progress is evaluated, since month-three revenue is not a signal of anything while competency sign-offs at month three are. It also argues for hiring in pairs where cash flow permits, because two apprentices can practice on each other and compare notes, and the second one costs less to train than the first since the material has already been organized.

Who should mentor a new technician?

Not your best technician by default, which is the near-universal mistake. High skill often correlates with having found the work easy, which is precisely the wrong experience for explaining it to someone who does not. Look instead for patience, willingness to be interrupted, and the habit of explaining why rather than only what. The second mistake is not paying for it: a mentor on production-based pay loses money every time they slow down to teach, and no amount of encouragement overcomes that arithmetic. Pay for mentoring explicitly — a stipend for the period, a bonus when the apprentice reaches defined competency, or a protected reduction in the mentor's own targets during the training window. Companies that add this line typically find mentoring quality improves immediately, because it becomes work rather than an imposition.

Should I hire inexperienced people for technician roles?

Yes, if the training exists — and that condition is not optional, because hiring inexperienced people into an informal ride-along is worse than hiring experienced ones, not better. Once you accept that you will build technicians rather than buy them, the hiring criteria change. Four signals matter more than trade experience: mechanical curiosity, meaning evidence that this person takes things apart and fixes what breaks at home; comfort in strangers' homes, which sounds trivial and is not, since much of the work is being calm and respectful in someone's private space while they watch; tolerance for being bad at something, because the first six months involve daily incompetence in front of an audience; and a real reason to be in the trades. Two underused sources are adjacent hands-on trades and second-career hires in their thirties, whose customer-facing maturity is already there.