Should you throw a new technician straight onto flat-rate work and let them figure out your shop, or slow down and walk them through everything first? That is the question almost every shop owner faces the Monday a new hire shows up, and getting it wrong is expensive. Roughly half of technician turnover happens inside the first 90 days, and replacing a tech who quits at week six costs you the recruiting time, the ramp-up wages, and the productivity of whoever had to babysit them.
Here is the plain answer: neither extreme works. Sink-or-swim burns out good people, and hand-holding for a month drains your bays. A structured first 90 days that front-loads clarity and backs off as competence grows is what actually keeps a technician. Below is how to decide what that looks like in your shop.
The three onboarding paths, and where each one fails
Most shops fall into one of three approaches by default, not by choice.
Sink-or-swim. You hand the new tech a work order, point at a bay, and see what happens. Cheap on paper. The problem is comebacks. A tech who does not know your inspection standards, your parts vendors, or your labor guide will produce rework, and rework at your door costs far more than a slow first week. One shop I know put a lateral hire on brake jobs day one, ate three comebacks in two weeks, and lost the customer relationships behind them.
Full hand-holding. The owner or lead tech shadows the new hire on every job for two to three weeks. Quality is high, but you have effectively pulled two techs off billable work. At a $145 effective labor rate, a lead tech shadowing for 60 hours is over $8,000 in lost production before the new person turns a single profitable hour.
Structured ramp. Clear standards on paper, a named mentor for questions, and a schedule that starts with straightforward jobs and widens over 90 days. More setup up front, far less waste after week one.
The structured ramp wins for almost every 2-to-6-bay shop. The tradeoff is that it forces you to write down how your shop actually runs, which most owners have never done.
The criteria that decide your version
Not every new tech needs the same runway. Use three factors.
Experience level. A 15-year master tech needs orientation, not training. Give them your standards, your systems, and a mentor to ask, then get out of the way by day three. A second-year tech or apprentice needs a genuine 90-day ramp with checkpoints.
Your systems maturity. If your shop still runs on a whiteboard and paper tickets, onboarding is slower because knowledge lives in your head. When your process lives in software, a new tech can see the flow of work themselves. This is one of the quiet wins covered in our breakdown of what a paper system actually costs you every month: the cost is not just your time, it is every new hire who has to interrupt you to ask what is next.
Bay pressure. If you are slammed, you cannot afford a lead tech shadowing for two weeks. Lean on written standards and short daily check-ins instead. If you have a slower stretch, invest more mentor time up front.
A 90-day framework you can copy
Here is a version most shops can adapt.
Days 1 to 7: standards and systems
No flat-rate pressure this week. The new tech learns your digital inspection standard, your vendor list, your labor guide, and how your job board works. Assign a mentor for questions and set the expectation that asking is fine. End the week with two or three real jobs the tech owns start to finish, checked before delivery.
Days 8 to 30: supervised volume
Widen the work. The tech carries a real load but every ticket gets a quality check before it leaves. Track comebacks honestly. A realistic target is fewer than one comeback per 25 jobs by day 30. Meet weekly for 15 minutes: what is slowing them down, what tools or info are missing.
Days 31 to 90: independence with checkpoints
Pull back the checks to spot audits. Start reviewing their productivity numbers together, not to micromanage but to show them where their hours go. This is also when pay conversations get real, so make sure your comp plan was clear before day one. If you are weighing structures, our comparison of flat-rate versus hourly pay lays out how each affects a new tech’s first months.
Why systems beat willpower here
The single biggest onboarding drag is a new tech who cannot see the work. When jobs, statuses, and assignments live on one screen instead of in your head, a day-one hire stops interrupting you every twenty minutes. That visibility is the same reason shops report faster ramp times after moving off paper, and it is a real line item in the return-on-investment math for shop software. If you are still deciding whether a platform fits your shop, the side-by-side comparison is a straightforward place to start.
A structured 90 days is not about being soft. It is about protecting the money you already spent to hire someone, and giving them a real reason to still be at your shop in month four.
Frequently Asked Questions
How long should onboarding a new technician take? Plan for a full 90 days, front-loaded. The first week is standards and systems with no flat-rate pressure, the first month is supervised volume, and the back half is independence with spot checks. Experienced master techs can compress the early weeks, but do not skip the systems orientation.
Should I put a new tech on flat rate right away? No. Starting a new hire on flat rate in week one punishes them for not yet knowing your shop, which drives comebacks and early quits. Ease into it over the first 30 days, and make sure the pay structure was explained clearly before they accepted the job.
How do I onboard a tech without pulling my lead tech off billable work? Write your standards down and let your systems carry the load. When your job board, inspection process, and vendor list live in software a new tech can see, your lead answers occasional questions instead of shadowing every job, which keeps both people productive.