The onboarding playbook: get a new field tech productive in weeks, not months

Walk into most HVAC, roofing, or restoration shops and ask how a new technician learns the job. The answer is almost always the same: "He rides with one of the senior guys until he's ready." It sounds reasonable. It is also the slowest and most expensive way to train a human being.

Here is what it actually costs you. Your senior tech, the one who runs clean diagnostics and upsells without being pushy, is now driving at half speed because he is explaining every step. Two people are in one truck doing one person's work. Call it a month of that, sometimes three, and you are paying two wages for one output while your best closer is off the board.

The second cost is quieter and worse. The new hire inherits whatever that particular senior tech does, good habits and bad. If your guy skips the combustion analysis because he "can tell by the flame," so will the new one. If he never photographs the panel before he starts, neither will the rookie. You are not training to your standard. You are cloning one person, quirks included, and you have no idea which quirks you just copied.

Most owners cannot tell you when a new tech is "ready" because they never defined it. Ready is a feeling their lead hand has on a Tuesday. That is why the timeline drifts. If the finish line keeps moving, the race never ends.

So draw the line first. Productive is not "shows up and is pleasant." Productive is a specific, written list of jobs this person can run solo, to your standard, without calling the office twice an hour. For a residential HVAC tech, week-three productive might look like:

• Complete a maintenance call start to finish, including the combustion analysis and the photos, without supervision.
• Diagnose a no-heat call on the two furnace brands you install most, and know when to escalate instead of guess.
• Write up the work order so the office can invoice it without chasing him for details.
• Talk a homeowner through a repair-versus-replace decision without over-promising.

For a roofer it is a different set of jobs, for a restoration tech different again, but the principle holds. You name the competencies, in writing, before the person starts. Now "ready" is not a vibe. It is a checklist somebody can sign.

This is the part almost everyone skips, and it is the whole game. The reason onboarding takes months is that the knowledge a new tech needs is not written down anywhere. It lives in the heads of three or four long-tenured people, and it comes out only when the rookie happens to hit the situation that jogs it loose. That is a terrible way to transfer knowledge, because it is random. You are waiting for the job to teach the lesson instead of teaching it on purpose.

The fix is to codify it. Not a policy binder nobody opens. A working Business Playbook that captures the operational intelligence your veterans carry around in their heads. In the trades that means the unglamorous, high-value specifics:

• Which supply house stocks what, who to call for a same-day part, and which counter guy actually picks up the phone.
• How you photograph a job so the office and the customer both have what they need, before, during, and after.
• The three equipment brands you see most and the two failure modes that account for half your service calls on each.
• Exactly how a work order gets filled out, because a sloppy one is a delayed invoice, and a delayed invoice is your cash flow.
• What "done" looks like on site: the walkthrough, the cleanup, the sign-off, the review ask.

This is Codified Operational Intelligence, and it is the difference between a business that trains people and a business that hopes people absorb things. When it is written down, a new tech does not need to catch your best installer on a good day. He reads it, he practises it, and your veteran gets to stay on billable work.

Once you have the playbook, the temptation is to dump all of it on the new person during week one. Do not. Nobody retains forty procedures in five days. Sequence it by what they will actually touch first.

A simple order that works across most field-service trades:

• Days 1–2: Safety, the truck, the tools, and the software. Where everything lives, how to clock in, how to log a job. Boring, foundational, non-negotiable.
• Days 3–5: Shadow on real calls, but with a job. The new hire runs the checklist while the lead runs the work. They are not watching, they are documenting against the standard you wrote.
• Week 2: Flip it. The new tech runs the call, the lead watches and coaches. Same checklist, roles reversed. This is where weeks-not-months gets won or lost.

The point of the sequence is that your senior person's time is spent coaching against a written standard, not narrating from scratch. That is a far smaller ask, which means you can afford to have your good people do it well.

The last piece is how you close it out. Not "I think he's good now." A competency sign-off, where a lead initials each item on the list once they have watched the new tech do it solo and to standard.

If nobody will put their initials next to "can run a no-heat call unsupervised," then the answer is no, and you have just found the exact gap to coach next week.

That sounds bureaucratic. It is the opposite. It is the fastest way to know precisely where someone is, so you stop guessing and start closing specific gaps. It also protects you. When a job goes sideways six months later, you are not relying on memory about what the tech was or was not trained on. It is on the sheet.

One more benefit worth naming. Every time you onboard someone against a written playbook, you find the holes in the playbook. The new person asks the question your veterans stopped asking a decade ago, and you improve the document. Onboarding stops being a cost you absorb and becomes the thing that keeps your operating system honest.

None of this requires a training department. It requires deciding that the knowledge running your business should live in the business, not just in the three people who might retire, quit, or take a Friday off. If you want to see how much of your operation is codified versus still riding around in a few people's trucks, that is worth measuring before your next hire, not after.