HVAC Tech Onboarding & Training: The First 90 Days

A new tech's first 90 days decide whether they become an asset or a costly write-off — and most shops leave it to chance. Hand someone the keys with no system and you get predictable results: callbacks because they don't know your standards, unhappy customers who see your name on rushed work, and a hire who quits because they felt lost and unsupported. After all the effort to recruit them, that's an expensive way to lose them. Onboarding is how you protect the investment.

Why onboarding is worth the effort

• Retention. People quit most in the first few months, and the number one reason is feeling unsupported and unsure. A structured start dramatically improves the odds they stay.
• Quality & brand. Your new tech represents your company in customers' homes on day one. Onboarding makes sure they represent it well — fewer callbacks, better reviews.
• Speed to productivity. A clear plan gets a tech billable and confident faster than trial and error.
• It's cheaper than turnover. Replacing a tech costs thousands in recruiting, lost productivity, and callbacks (see the loaded-cost math in the hire & keep guide). Onboarding is the cheap insurance.

The first-90-days plan

Before day 1

Nothing says "you don't matter" like a chaotic first day. Have it ready: paperwork done, truck/tools/uniform/phone assigned, first-week schedule set, and the team told a new person is starting. A smooth arrival sets the tone.

Week 1 — orient and pair

• Company standards and values — how you treat customers, what "done right" looks like, the cleanup standard.
• How you do a job — your job checklist, customer script, and process (your SOPs — below).
• Software and pricing — your field service software and flat-rate pricebook, so they quote and document consistently.
• Safety and compliance — including required certifications; anyone handling refrigerant must hold the EPA Section 608 Technician Certification.
• Ride-along with a senior tech or lead — the fastest way to transfer how your shop actually works.

Weeks 2–4 — shadow to supervised solo

Ramp deliberately: shadowing → running calls with a mentor nearby → solo calls with QA on their work. Introduce your option presentation and membership process gradually once the basics are solid — don't dump everything at once.

30 / 60 / 90-day check-ins

Sit down at 30, 60, and 90 days for structured, two-way feedback. Catch problems while they're small, reinforce what's going well, and confirm the fit. New techs who get regular check-ins feel supported — and supported techs stay.

Standardize how you do the work (SOPs)

You can't onboard consistently to a process that only lives in your head. Write down how a job gets done — arrival, diagnosis, customer communication, pricing, cleanup, follow-up — so every tech delivers the same experience. These SOPs are the backbone of onboarding and the thing that lets you scale without quality falling apart. Start with your most common jobs and build from there.

Keep training after 90 days

Onboarding rolls into ongoing development, which is one of your strongest retention tools:

• Certifications — support EPA 608, NATE, and manufacturer training; pay for it and tie it to your pay ladder.
• Regular tech meetings and ride-alongs to share knowledge and keep standards sharp.
• A clear growth path — helper to tech to lead — so people can see a future with you.

Assign a mentor

Pair every new hire with a patient, respected senior tech as their go-to. It accelerates learning, transmits your culture, and gives the new person someone to ask the "dumb" questions without fear. Choose the mentor for attitude, not just skill.

Common mistakes

• Sink-or-swim — keys and a truck on day one with no plan.
• No documented process — every tech freelances, quality varies.
• No mentor — the new hire has nowhere to turn.
• No check-ins — problems fester until the tech quits or gets fired.
• Overwhelming week 1 — dumping everything at once instead of ramping.
• No ongoing training — skills and motivation stagnate.
• Skipping culture — technical training without your standards and values produces a tech who does the work but not the way you'd want.