How long should onboarding take for a field technician?

Plan a structured 30 days minimum: ride-alongs in week one, supervised calls in weeks two and three, and a gradual move to solo work in week four. The formal decision point comes at 90 days, but the first 30 set the trajectory. A tech thrown into a truck alone on day two is not onboarded, just deployed.

What should a field tech do in their first week?

Ride along with your best tech, not whoever had room in the truck. Week one is for learning how your company runs a call: your software, your pricing, how you talk to customers, what a finished job looks like. Add the paperwork, truck assignment, and uniforms on day one so the week is about the work, not the forms.

When should a new tech start running calls alone?

When they have demonstrated your call process on real jobs with someone watching, usually in week four for an experienced tech and much later for a green hire. The trigger should be demonstrated skills, not a date on a calendar or a busy dispatch board. Sending someone solo early to cover demand is how thirty-day quits happen.

Who should be responsible for onboarding a new technician?

One named person, agreed before the start date: usually a lead tech or field supervisor who is measured on the new hire's progress. When onboarding belongs to "everyone," it belongs to no one, and the new hire spends their first month guessing. The owner can set the plan, but the day-to-day belongs to one accountable person.

Why do new field techs quit in the first month?

Almost never over pay. They quit because the job did not match the posting, nobody was assigned to them, expectations were vague, or they were pushed into solo calls before they were ready and got burned on one. All four are onboarding failures, and all four are cheaper to fix than replacing the hire, which SHRM pegs at 90-200% of salary all-in.

How to onboard a field tech: what a good first 30 days looks like

What should the first 30 days look like for a new field tech?

A good first 30 days is a written, week-by-week plan: paperwork and setup done before day one, week one riding with your best tech, weeks two and three running supervised calls with daily debriefs, and week four easing into solo work with a formal 30-day review at the end. One named person owns the plan, check-ins happen on a schedule instead of in passing, and the new hire always knows what "good" looks like this week and what comes next. That's it. It fits on one page, and it beats the "here's your truck, call me if you're stuck" approach that quietly loses good techs before they ever get invested.

This article is the concrete plan. The reasoning behind it lives in three pieces we've already written: why retention starts on day one, why consistency beats program complexity, and why the first 90 days decide more than you think. Read those for the why. This is the what.

Before day one: don't waste the first morning on forms

Everything that can happen before the start date should. That means:

Offer letter, tax forms, and direct deposit done electronically the week before
Truck assigned, stocked, and cleaned. A new tech reads a filthy hand-me-down truck as a message
Uniforms ordered in their size, not "we'll get those sorted"
Logins created: dispatch software, pricebook, email, GPS
A start-day text the Friday before: where to park, who meets them, what time, what to bring

Then tell the team. Not a mass email — actually tell your lead tech who is starting, what their background is, and who owns their first month. A new hire who walks in to find nobody expected them has learned everything they need to know about how the company runs.

Pick the owner now. One lead tech or field supervisor is accountable for this hire's first 30 days, and they knew it before they agreed to it. Everything below is that person's checklist.

Week 1: ride-alongs with your best tech

The first week is observation, and who they observe matters more than anything else you decide this month. New hires calibrate to the first tech they ride with. Put them with your best — best habits, best customer manner, best paperwork — not with whoever happened to have room in the truck, and definitely not with your cynic.

What week one should cover:

Day 1: Shop tour, meet the team, truck walkthrough, software basics. One sit-down with the owner or manager: why the company exists, what "good" means here, what the first 30 days look like. Thirty minutes, not a seminar.
Days 2-5: Full ride-along days. The new tech watches complete calls end to end: the greeting, the diagnosis, the options conversation, the payment, the photos and notes. By Thursday they're doing pieces of the call — running the diagnosis while the senior tech watches, writing up the ticket — with the safety net still in place.
Every day: A ten-minute end-of-day debrief with their onboarding owner. What did you see, what surprised you, what questions do you have. Scheduled, not "if we get a minute."

By Friday of week one, the new hire should be able to answer: who do I go to when I'm stuck, what does a finished call look like here, and how does this company want me to talk to customers.

Week 2: they run the call, someone else drives

Flip the ride-along. The new tech now runs supervised calls — they lead, the senior tech shadows and only steps in when needed. Start with straightforward work: maintenance visits, simple diagnostics, warranty calls. The point is not to test their technical ceiling; it's to let them practice your process where mistakes are cheap.

Two things to hold firm on:

Debrief after every call, not every day. Two minutes in the truck: what went well, what you'd do differently. Feedback within minutes of the work is worth ten times the same feedback on Friday.
Resist the dispatch board. This is the week you'll be tempted to pull the shadow off and send the new tech alone because the board is full. Every operator faces this. The ones with low turnover don't blink. Replacing a tech who washes out costs 50-60% of their salary in direct costs and 90-200% all-in, per SHRM — no single busy Tuesday is worth that.

End of week two: a 30-minute sit-down check-in. Not a hallway "how's it going." What's working, what's not, what do you need. Write down the answers.

Week 3: widen the work, shrink the net

Same structure, harder calls. Mix in the work that actually defines the job: the no-cool call at 4pm, the water heater swap, the panel that doesn't match the drawing. The shadow tech's job shifts from watching everything to spot-checking the moments that matter — diagnosis, the options conversation, the final walkthrough.

This is also the week to verify the boring-but-critical stuff, because bad habits set now last for years:

Are their tickets, photos, and notes complete without prompting?
Are they quoting from the pricebook or freelancing?
Do callbacks on their work look normal or high?
How do customers respond to them? Read the reviews and ask the office staff.

If something's off, week three is when you say so, plainly and privately. A tech who hears honest correction in week three trusts the praise in week six. A tech who hears nothing assumes nobody's watching, and nobody staying long works for a company where nobody's watching.

Week 4: solo calls, with a floor under them

Now they run calls alone — but sequenced, not dumped. Early in the week, solo calls picked for confidence: maintenance, straightforward service, repeat customers. Later in the week, the normal board. All month, one standing rule: calling for help is free. The new tech needs to hear, explicitly, that phoning the lead from a driveway is what good techs do here, not a mark against them. Shops that punish the question get techs who guess, and guessed diagnoses come back as callbacks and reviews.

Keep the daily ten-minute debrief through the end of the month. It's the cheapest early-warning system you will ever run.

Day 30: the review both sides deserve

Close the month with a real 30-day review. Thirty minutes, calendar-scheduled, two agendas:

Yours: where they are against the plan, what they've done well (specifically), what needs work (specifically), and what weeks five through twelve look like — because day 30 is a checkpoint, not the finish line. The 90-day mark is where the real mutual decision happens.

Theirs: does the job match what they were sold? What's confusing? What does the company do that makes their job harder? New hires see your broken processes with fresh eyes exactly once. Take notes.

Then keep the check-ins going — weekly through 90 days. The cadence can loosen after that. The habit shouldn't.

The one-page version

Week 0: paperwork, truck, logins, team told, owner named. Week 1: ride-alongs with your best tech, daily debriefs. Week 2: supervised calls, easy board, per-call feedback. Week 3: harder calls, verify the paperwork habits, honest correction. Week 4: sequenced solo work, help is free. Day 30: real review, both directions. If your plan doesn't fit on a page, it isn't a plan yet — it's an intention.

None of this requires software, an LMS, or an HR department. It requires deciding it matters and running it the same way for every hire. And it starts before the hire: an onboarding plan can't save a mismatched hire, which is why the job posting has to tell the truth about the work — see our plumber job description template for what that looks like. It matters double for green hires and apprentices, who wash out at rates that should alarm anyone building a bench — we dug into the actual numbers in apprenticeship completion rates.

At HireAligned we run recruiting for HVAC, plumbing, and home-services companies, and the pattern is consistent: the shops that keep techs aren't the ones paying the most, they're the ones where the first month is deliberate. We handle the pipeline so the right person shows up; a plan like this one is how you keep them. If the pipeline side is the part you're missing, that's what done-for-you is.