New Tech Onboarding: The 2-Week Training System That Actually Works
Stop throwing new hires on a truck and hoping. The day-by-day 2-week plan: the pre-day-1 packet, shadow shifts that teach, the truck-stocking checklist, the first-solo sign-off test, and the 30-day check that catches bad habits before they fossilize.
Part of the Leveraged Owner 8-system framework
Monday morning, 7:30. Your new tech is standing in the shop holding a coffee, looking at a truck he's never driven, tools he's never inventoried, and a first job he's never seen — and your lead tech is already backing out of the yard. So you hand him a stack of work orders, point at the truck, and say "ride with Mike today, you'll figure it out." He does not figure it out. He guesses. And three weeks later you're re-running his callbacks and wondering why "good help is so hard to find."
Why most onboarding dies in the first 72 hours
Most contractors don't have a training problem — they have a day-one-through-fourteen problem. The pattern is always the same: hire on Friday, throw them in a truck on Monday, and call the chaos "sink or swim." The techs who sink were never trained. The techs who swim learned by making your customers the test audience.
The fix isn't a longer training period. It's a planned one. Two weeks is enough if every day has a job: day 1 absorbs the paperwork and the culture, days 2–5 build hands under supervision, days 6–10 run supervised solo jobs with same-day debriefs, and day 10 ends with a scored sign-off. After that, the 30-day check keeps standards from drifting.
Onboarding sits inside the bigger machine: hiring, dispatch, follow-up, and reputation all connect, which is why the full picture is the 8-system framework for home-service businesses. This post is the deep dive on the training piece.
Before day 1: the new-hire packet
The new tech's first impression of your company happens before the first shift. If day 1 starts with "we don't have your uniforms yet," you've told them exactly how organized you are. Get this done before they walk in:
- Truck assigned and stocked to the standard list. Not "the spare truck." A truck stocked to the same checklist below that every tech carries. A new hire's first week should never include discovering what's missing mid-job.
- Uniforms, badge, and business cards. Two shirts minimum on day 1. The customer-facing identity is part of the job from the first knock.
- Access sorted: shop key or code, fuel card with the PIN, phone or tablet login for the CRM (your customer relationship management software — where jobs, customer history, and notes live), and the company messaging channel.
- The paperwork in one sitting: W-4, I-9, handbook signature, pay schedule, and the 30-60-90 expectations sheet (see the 30-day check below). Day 1, done in the first hour, not dragged across the week.
- A named trainer. One specific person — a lead tech — who owns the new hire for the next two weeks. Not "whoever's free." One name, written down, introduced on day 1.
The takeaway: a prepared day 1 tells the hire the company has standards. An improvised day 1 tells them standards are optional.
Week 1: shadow shifts and the ride-along rules
Week 1 has one goal: the new tech learns how your company does the work, not how they did it at the last shop. Structure each day:
- Day 1 — Orientation, not jobs. Paperwork, shop tour, the CRM walkthrough, truck inventory walkthrough, and a 30-minute sit-down with you: how we treat customers, what "done" looks like, and the one standard you're proudest of. Then they ride along and observe only.
- Days 2–3 — Observe and document. Ride with the lead tech. The rule: after each job the new hire explains it back — what was wrong, what was fixed, what parts were used. Watching without explaining is sightseeing.
- Day 4 — Hands under eyes. The new hire does the work while the lead tech watches and corrects in real time — corrections are about your SOPs (standard operating procedures, the written step-by-step way each task gets done), not about general trade skill.
- Day 5 — The first half-job. A simple, well-defined job the new hire runs mostly alone with the lead tech on site. Debrief for 15 minutes after: what went right, what was slow, what was skipped.
Customer intro script — new tech, first week:
"Hi [Customer First Name], I'm [Tech First Name] with [Business Name]. I'm training with [Lead Tech Name] this week — he's the one with all the answers, I'm the one doing the work. We'll have you taken care of in about [Time Estimate]."
Example: an HVAC shop owner pairs every new installer with his lead tech for the full first week — no solo dispatching, no exceptions — and the lead tech signs whether the hire is ready for week 2 or repeats week 1. Repeat is not punishment; it's cheaper than callbacks.
The takeaway: shadow shifts work only when the hire has to explain the work back. Passive riding produces passive techs.
The truck-stocking checklist
Every tech carries the same truck. No exceptions, no "his truck is different." Stocking is an SOP, not a preference. Your list will be trade-specific, but every list needs these five categories, verified on day 1 and re-checked monthly:
- Top 20 parts for your most common jobs. Pull your CRM's last 90 days of job history and list the parts actually used. Those are the truck. Everything else is a warehouse trip that eats your schedule.
- Full tool set, photographed. The complete kit for the trade, checked against a photo inventory the new hire keeps on their phone. Missing tool = reported same day, replaced that week.
- Consumables at par levels. Fuses, connectors, filters, screws, tape, caulk — with written minimum quantities. Restocking happens before the bin is empty, not after.
- Customer-facing kit: shoe covers, drop cloths, invoice forms or tablet, the review-request QR card, business cards, and the "we're on our way" script.
- Safety gear: glasses, gloves, masks, lockout tags, fire extinguisher with a current date. Non-negotiable and checked, not assumed.
The takeaway: a standardized truck means a new tech's third week looks like their tenth — same parts, same tools, same speed. The truck is training that never sleeps.
Week 2: supervised solo to the first-solo sign-off
Week 2 the training wheels come off in stages. The new hire takes real jobs from dispatch, but every job gets a same-day debrief with the trainer — 10 minutes, three questions: What did you find? What did you do? What would you do differently?
"On my way" text template (send before every job):
"Hi [Customer First Name], this is [Tech First Name] with [Business Name] — I'm on my way and should be there around [ETA]. Please reply here if anything changes. Reply STOP to opt out of texts."
Before you send automated business texts like this, note the compliance basics: A2P 10DLC registration is required (application programming interface-to-person texting over 10-digit long codes — 1–7 day approval, ~$15–$20 one-time); include opt-out language in the first text; observe TCPA quiet hours (no marketing texts before 8am or after 9pm in the recipient's local time). This is general information, not legal advice.
The takeaway: week 2 is supervised independence — real jobs, real customers, real debriefs. The debrief is the training; the job is the test.
The first-solo sign-off (the test that matters)
End of day 10, the trainer signs off or the hire repeats. This is a scored sign-off, not a gut feeling. The new tech must demonstrate all of these:
- Runs a complete job alone — diagnosis through cleanup — with no callbacks on their week-2 work so far.
- CRM entries are complete: job notes written so another tech could read them, photos attached, invoice closed same day. If the notes are empty, the job didn't happen.
- The customer intro and "on my way" text happen every time. The trainer spot-checks two jobs. Scripted customer communication isn't optional — it's the brand.
- The review ask, done right. The tech knows the 30-second ask and delivers it before leaving: "If the work looks good, the review link I'll text you takes 30 seconds — and if anything isn't right, tell me now so I can fix it today." Never pay for or incentivize reviews in ways that violate Google policy; never filter unhappy customers before the review ask (review gating) — it violates Google's policy.
- Truck still stocked to standard. Re-inventory against the checklist. If parts are missing or unreported after two weeks, the habit is already wrong.
of consumers read reviews (BrightLocal 2026). That's why the review ask is part of the sign-off, not a "when you get around to it" — a tech who can't ask for reviews in week 2 won't start in week 20.
The takeaway: the sign-off is the moment training becomes a standard. A signed checklist is something you can enforce in month 3. A memory of "I think he's fine" is not.
The 30-day performance check (stop bad habits before they fossilize)
Whatever a tech does in their first 30 days becomes their permanent method. The 30-day check is a 30-minute sit-down with you and the trainer, scored against the numbers — not a vibe conversation:
- Callback rate under 3%. Callbacks in month 1 are a training signal. Pull the number, name the jobs, fix the pattern.
- CRM compliance at 100%. Every job has notes, photos, and a same-day close. Spot-check five jobs together in the meeting.
- Review-request rate. Every completed job should generate a review request. The CRM log shows whether the ask actually happened.
- On-time rate and truck standard. Arriving when the text said, truck still matching the stocking checklist. These are the two habits that drift first.
- One coaching item. Pick the single biggest gap and set a 30-day goal with a date. One item, written down. This is the 30-60-90 plan in action: day 30 reviewed, day 60 expectations reset, day 90 independence confirmed.
If the numbers aren't there at day 30, extend training with a specific written plan — not a vague warning. If they aren't there at day 60, you have your answer: the system worked, the fit didn't. A bad hire caught at day 60 costs you a month. A bad hire kept for a year costs you your reputation, one customer at a time.
The takeaway: day 30 is the last cheap moment to correct course. After that, every bad habit is a re-training project instead of a conversation.
Mistakes that turn good hires into callbacks
- Training by whoever's available. Rotating trainers teach rotating standards. One named trainer, two weeks, signed sign-off.
- Skipping the truck inventory. An unstocked truck teaches the new hire that improvisation is the system. It isn't.
- No written SOPs to train from. If the procedure lives in your lead tech's head, it can't be taught consistently — and it leaves when he does.
- Signing off on a gut feeling. "He seems ready" is how week-2 problems become month-6 patterns. The scored sign-off exists so you don't have to trust your memory.
- Treating day 30 as a formality. The 30-day check with no numbers is a coffee chat. With numbers, it's the highest-leverage meeting of the hire's first quarter.
Related guides in this series
Onboarding is one piece of building a team that runs without you. Get the office side right with First CSR Hire: Systems to Have in Place Before You Hire, and see where trained people fit into the bigger escape with Owner-Operator to CEO: Systems to Step Off the Truck.
Get System 1 free: the complete Missed-Call Safety Net
The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Good training starts with enough work to train on — stop losing the calls first.
Get the AI Automation Starter Pack — $27, one-time: https://leveragedowner.com/starter-pack/
The done-for-you version
This post is part of the Leveraged Owner 8-system framework — the done-for-you version with the full setup guides, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems.
Stats sourced as labeled: BrightLocal 2026 (97% read reviews) — directionally useful, always measure your own numbers.