# How to train a new tech without losing a week of productivity

> A green hire costs you two people in week one: his slow start and your best tech in the passenger seat teaching him. Here's how to close that gap fast.

Source: https://toolbagcrm.com/blog/how-to-train-a-new-tech-without-losing-productivity/
Author: The Toolbag Crew
Updated: 2026-10-25

Ride-alongs with a real plan, checklists for the stuff you're tired of explaining, small-stakes solo jobs, and job history the new guy can teach himself from.

## The first week costs you twice

A new tech shows up green. That’s fine, you knew that when you hired him. What owners forget is that the first week doesn’t cost you one slow guy. It costs you two people.

Your best tech is the one riding along explaining everything, and while he’s teaching he isn’t turning wrenches on his own jobs. So you’re down a producer and paying two wages for one truck’s worth of work. That’s the hole you’re trying to climb out of. The sooner the new guy gets to where you trust him alone, the sooner you stop bleeding.

Most shops handle this badly. They throw the kid in the deep end on day two and eat the callbacks, or they babysit him for a month and wonder why the schedule’s a wreck. There’s a road between those two.

## Ride-alongs, but with a plan

Riding along works. Sitting in the passenger seat watching does not, and there’s a real difference between the two. If your new hire spends three days quietly observing, he learned how to watch, not how to work. Put him on the ticket from day one, even if it’s the small stuff: pulling the old unit, hauling in materials, writing up the invoice while you check it. Get his hands on something.

And tell the tech he’s shadowing what you actually expect out of the week. Show him how you diagnose, then make him do the next one while you watch. Plenty of good techs are lousy teachers, mostly because nobody ever told them that teaching was the job that week. Say it out loud.

## Write down the stuff you're tired of explaining

Every shop has a list of things that go wrong the same way every time. The tech who forgets to photograph the panel before he closes it up. The one who skips the pressure test. The guy who drives off without the customer’s signature. You know your own list by heart.

So write it down once instead of explaining it fresh to every new hire. A plain checklist for each job type: what to check, what to photograph, what to hand the customer before you leave. Nobody’s babying anybody here. Airlines and surgeons run checklists for the same reason, to keep from forgetting the obvious under pressure, and a service call is plenty of pressure when you’re new.

### A starter checklist for a new tech's first solo calls

- **Confirm the job before you touch anything**: Read the ticket, confirm the address and the scope with the customer at the door. Wrong job, wrong parts, wasted trip.
- **Photograph before and after**: The panel, the unit, the work area. Covers you on warranty callbacks and shows the customer what they paid for.
- **Do the test you're tempted to skip**: Pressure test, voltage check, whatever the job calls for. The skipped test is the callback.
- **Get the signature and the payment**: Sign-off and payment before you pull out of the driveway, not a week of chasing later.

Here’s the quiet payoff: a checklist turns a vague “do good work” into something a new guy can actually follow on his own. He stops interrupting you every ten minutes to ask what’s next, because the next step is written on the ticket in front of him.

## Let them fail small

You want the new tech making his mistakes on a filter swap, not a full system install. Load his first solo runs with the low-risk, low-dollar work: maintenance calls, simple repairs, the stuff where a callback costs you an hour and an apology instead of a rework bill in the thousands.

Send him out with a phone and permission to use it. A new guy who calls you twice from a driveway is a lot cheaper than a new guy who guesses wrong because he didn’t want to look dumb. Make it clear the phone call is the right move. That one sentence saves you more rework than any lecture.

> A new guy who calls you twice from a driveway is cheaper than one who guesses wrong to avoid looking dumb.

## Where a CRM does the teaching for you

This is the part most shops miss, and it’s the one that saves you the most time. When your job history lives in one place, the new guy can look up how the last three jobs like this one went before he ever calls you. What parts got used. What the customer was quoted. Photos of how the work was left. He teaches himself off the record of work you already did.

Give a new hire access to the scheduled work and customer records they need in ToolbagCRM. Optional Job Checklists & Inspections and Documents & Photos can hold job steps and supporting files. Training certifications and employee training histories are not currently available features. Free and Founders include unlimited users. [See plan terms, plug-in slots, and payment fees.](https://toolbagcrm.com/pricing/)

None of this turns a green tech into a master in a week. Nothing does. But it gets him to useful faster, and it keeps your best producer out of the passenger seat and back in his own truck where he earns you money.

- [HVAC CRM](https://toolbagcrm.com/crm-for-hvac/)
- [Plumbing CRM](https://toolbagcrm.com/crm-for-plumbers/)
- [Electrician CRM](https://toolbagcrm.com/crm-for-electricians/)
- [Landscaping CRM](https://toolbagcrm.com/crm-for-landscapers/)
- [Finding and keeping good techs in a tight labor market](https://toolbagcrm.com/blog/finding-and-keeping-good-techs-tight-labor-market/)
- [From first call to final invoice: the ideal job workflow](https://toolbagcrm.com/blog/from-first-call-to-final-invoice-job-workflow/)
- [Founders pricing — get started](https://app.toolbagcrm.com/signup/)

## Frequently asked questions

### How long does it take to train a new field tech?

Basic competence on routine calls usually takes a few weeks; real independence on complex jobs takes months. The goal of the first week isn't mastery, it's getting the new hire to where he can run low-risk jobs alone.

### Should a new tech ride along or work solo first?

Both, in order. Start with ride-alongs where the new hire actually does part of the work instead of just watching, then move him to small solo jobs where a mistake costs an hour, not thousands.

### How do you train a new tech without slowing down your best one?

Give the trainer a clear teaching goal for the week, use written checklists so the new guy can follow steps on his own, and let past job records answer the routine questions instead of your senior tech.

### What's the fastest way to get a new hire productive?

Standardize the repeatable parts of the job with checklists and templates, and give the new tech access to your job history so he can look up how similar jobs were done before he calls for help.

## Related resources

- [Finding and keeping good techs in a tight labor market](https://toolbagcrm.com/blog/finding-and-keeping-good-techs-tight-labor-market/)

- [Getting off the tools: hiring your first office manager](https://toolbagcrm.com/blog/getting-off-the-tools-hiring-first-office-manager/)

- [From first call to final invoice: the ideal job workflow](https://toolbagcrm.com/blog/from-first-call-to-final-invoice-job-workflow/)

- [CRM for HVAC](https://toolbagcrm.com/crm-for-hvac/)

