How do you onboard a new HVAC or plumbing tech in the first 90 days?

Onboarding starts the day your offer is accepted, not the first shift.

Two tracks run in parallel before day one: the paperwork with federal deadlines, and the physical setup that lets a new tech produce in week one instead of watching.

Send the offer letter first, with the start date, the pay and the schedule in writing, so the first conversation at your shop is about work, not terms.

The federal paperwork has fixed deadlines.

The IRS's guidance for hiring employees says to get a signed Form W-4 from each new employee when they start work, effective with the first wage payment.

Form I-9 is separate and universal: every U.S. employer must complete it for every person they hire in the United States.

Section 2 — the document-review step — is due within three business days of the hire, and for a job lasting fewer than three business days the I-9 steps must all be done at the time of hire.

Print the current forms from the issuing agencies rather than reusing the copy from your last hire.

Two more filings follow the start date.

Federal law requires employers to report new and rehired employees to the state within 20 days of hire, and some states require sooner — your state's registry sets the deadline that actually applies to you.

Workers' compensation coverage and unemployment-insurance registration are state-by-state as well; our research did not pin down each state's trigger, so confirm yours with your state before day one.

E-Verify is the piece shops most often leave out.

It is a free online service that checks an employee's Form I-9 information against government records.

If your company bids federal work carrying the FAR E-Verify clause, the contract requires you to enroll within 30 calendar days of award and, within 90 days of enrolling, to E-Verify all new hires within 3 business days of hire.

Whether your state requires private employers to use E-Verify is a state-law question our research did not cover — check with your state rather than assuming it is optional.

The physical track matters just as much to the first 90 days.

Assign the truck or settle the ride plan, pull a baseline of tools and parts, and stage the uniform and safety gear so nothing is borrowed on day one.

Build the first week's calendar before the tech walks in — who they ride with, which shop days are scheduled — and share it with them in advance, so the first morning has a shape.

A checklist only works if one person owns it.

In most shops the office manager or bookkeeper runs the paperwork items and the service manager runs the field items; split it however your company does, but keep every item in one shared document so nothing rides on memory.

The consolidated first-90-days version to print is at the end of this page — these are the day-one items:

• W-4 signed and payroll set up, with the first pay date explained before the tech's first weekend
• Form I-9 completed, with the Section 2 document review inside the three-business-day window
• New-hire report to your state calendared against its deadline
• Truck assigned or ride plan settled; tools, parts baseline and safety gear issued and counted
• Uniform and phone issued
• Field-service software, parts-procurement and timekeeping logins working
• Safety orientation on the calendar
• Crew introductions done, and the first week's ride-along schedule handed over

Two habits make the list stick.

First, give the tech a copy — an onboarding checklist the new hire can see becomes a to-do list they help finish.

Second, anything not finished by end of day one gets an owner and a date, not a shrug.

Day one stays at the shop.

Paperwork, payroll, the walk-through of the building and the yard, crew introductions, safety orientation, and the logins from the checklist.

Finish the I-9 before the first truck rolls — the document-review window is three business days from the hire, and the first week goes by fast.

The rest of week one belongs to ride-alongs.

Put the new tech with your strongest senior techs — the ones whose paperwork you never have to fix — not whoever has the spare seat.

What the tech is watching for: how your company documents a job, how the senior tech prices parts and options, how they treat the customer's home, and when they call the office instead of improvising.

What the new tech does: navigate, take notes, hand tools, and write up each ticket in your software for the senior tech to check.

Close the week with a debrief at the shop: what the tech saw, what surprised them, what your company does differently from wherever they worked before.

A tech hired from another shop unlearns old habits faster when the differences are named out loud in week one.

Set the second week's ride-alongs before the debrief ends, and name one person — usually the service manager — as the point of contact for every question in between.

There is no fixed date.

A tech runs the first solo call when the readiness signs are there, and those signs come from the ride-alongs: they document jobs the way your company does without prompting, they handle customers in a way you would repeat, they complete trade tasks to standard, and they call the office at the moments a senior tech would.

When you can point to those behaviors on real calls, the tech is ready; when you cannot, another week of ride-alongs is cheaper than a comeback.

Separate the two things a hire brings: the licence and the process.

A licence says what a board — a state's, or a city's or county's where licensing is local — allows the tech to do; it says nothing about how your company prices, documents and schedules the work.

A journeyman recruited from another shop may need less trade supervision than a helper but exactly as much process onboarding, so judge readiness on your process, not on the licence alone.

Structure the first solo call rather than hoping it goes well.

Pick a routine job you watched the tech handle on a ride-along.

Keep a senior tech one text away, and tell the tech exactly that.

Debrief the same day — what the ticket looks like, what the customer said, what the tech would do differently — and build solo volume gradually from there.

The 30-day check-in is a friction audit.

Is the paperwork finished and filed?

Does the tech have every tool, part and login the job needs?

What did the ride-alongs surface that the shop has not fixed — a missing ladder rack, a parts-procurement step that dead-ends at a person who is never in?

Logistics problems found at 30 days cost an afternoon; found at 90, they have already cost you calls.

The 60-day check-in is the first performance conversation.

Review the tech's solo work: documentation quality, customer feedback, and the callback signal if your shop tracks one.

Ask which job types fit them and which do not — the answer changes what you dispatch them to, and it often surfaces a strength the interview never showed.

The 90-day check-in is the full review.

Production against what you expected when you wrote the job posting — be concrete about the number you had in mind.

Where the tech grows next: which certifications, which job types, what the pay plan says about how they get there.

And if you hired the tech into a probationary period, this is usually the decision point your policy defines — make it deliberately, and put the outcome in writing.

Document every check-in, in the tech's file, every time.

A 90-day onboarding plan ends when a tech produces without oversight; the sourcing, screening and pay decisions that put them in your truck are covered in our guide to hiring HVAC and plumbing techs.

This page is employer career and business information, not legal advice. Hiring-paperwork deadlines and E-Verify duties are federal; state registration and E-Verify requirements vary, so confirm the rules that apply to your company with the issuing agencies or an employment attorney before you act.