New Technician Onboarding: First 30 Days Plan 2026

TL;DR

The first month decides whether a new technician becomes a long-term asset or a short-term cost. As of September 2026 the pattern most small service owners describe is still the same: a new hire is thrown onto a full solo route in week one, runs late, misses things, collects a callback and a rough review, and quietly starts looking for another job. That is not usually a hiring problem. It is a scheduling problem.

This is a new technician onboarding schedule for the first 30 days: ride-alongs, lighter job loads, which job types to hand over first, the shadow-then-lead progression, check-ins, and when to put a new tech on the online booking calendar. It picks up where hiring ends. For the hiring side itself — where to find techs and how to evaluate them — see our hiring a technician guide.

Why onboarding is a scheduling problem

A new tech's first weeks are shaped more by the calendar than by any training manual. Which jobs they get, how many, how much time each one is given, and who is nearby when something goes wrong — that is all scheduling.

Get it wrong in either direction and it costs you. Overload a new tech and they rush, make mistakes, and lose confidence. Underload them for too long and they get bored, feel untrusted, and still are not productive by month two. The goal is a steady ramp: enough challenge to learn, enough support to succeed.

There is a cost side to be honest about. A tech on a ride-along is a paid employee generating no separate revenue, and their trainer runs slower than usual. That investment only pays off if it produces a tech who stays and performs. A structured month is how you protect it.

Before day one: set up the tech in your systems

Onboarding starts before the tech arrives. A new hire who spends their first morning waiting for logins has already learned something about how you run the business.

• Create their account and role. Give them access that fits a technician, not an admin. At the Pro tier, staff roles (Owner, Admin, Tech) keep a new tech focused on their own jobs. Starter and Pro plans add staff seats at $25/mo each.
• Set their working hours on the calendar so conflict detection and availability reflect reality from day one. Our scheduling overview covers working hours and time blocks.
• Load their tools and truck inventory, so the first solo jobs do not fail for want of a part.
• Walk through the mobile app they will use in the field. In Tech Mode that means the daily schedule, one-tap status updates, navigation, photos, notes, and signatures.

Week one: ride-alongs

The first week is for watching. The new tech rides with an experienced tech and does not run jobs on their own.

What they should be learning is less about technique — you hired them for that — and more about how your business does things. How your techs greet customers. What your pricing conversation sounds like. How you document a job. What your quality standard looks like on a finished install. Where the supply house is and which parts you keep on the truck.

Schedule it on the calendar, not informally. Put the new tech on the trainer's jobs as a second person, the same way you would schedule a two-tech crew. That keeps the calendar honest and makes the trainer's longer job times visible. Our guide to two-technician crew jobs covers how to schedule paired work.

Pick the trainer carefully. Your best tech is not always your best trainer. You want someone who is good, patient, explains their reasoning out loud, and represents the way you want the job done.

Give the trainer a lighter day. A tech who is teaching is slower. Budget roughly one fewer job for the trainer during ride-along days, or you will get a rushed lesson and a late schedule.

Week two: shadowing, with the roles reversed

In week two, the new tech does the work while the experienced tech watches and steps in when needed. This is the most valuable week of the month, because it is where you find out what the new hire actually knows.

Watch for the gaps that do not show up in an interview: how they talk to customers, how thorough their diagnosis is, whether they document the job, whether they clean up. Correct things in the moment, quietly, in a way that does not undermine them in front of the customer.

Keep these jobs on the simpler end, and keep job times padded. The point is to build good habits at a pace where they can actually form.

Week three: leading simple jobs solo

Week three is the first time the new tech runs jobs on their own. The key is choosing which jobs, and how many.

Start with the most repeatable job types. Every trade has jobs with a predictable scope and a low risk of surprise: routine maintenance visits, standard installs, simple service calls. Those are the first solo jobs. Save the rest for later.

Run a light load. Roughly half of a normal day is a reasonable starting point for the first solo week, with generous time on each job. Say an experienced tech runs five or six jobs a day — a new tech might run two or three, spaced so a slow job does not cascade into a late afternoon. Our guide to technician capacity planning goes deeper on how many jobs a day is realistic.

Keep backup within reach. Schedule the new tech's solo jobs near an experienced tech's route where you can, so help is a short drive away if they get stuck. That one decision prevents most first-week disasters.

Review every job that week. Look at the photos, notes, and outcomes for each solo job. It is the fastest way to catch a habit before it sets.

Week four: building toward a normal load

By the fourth week, a tech who has passed the earlier stages should be ramping up — more jobs per day and a wider range of job types. The target is not a full load by day 30 for everyone. The target is a tech who is clearly on track.

Add job types one at a time. If the tech has nailed routine maintenance, add standard repairs. Hold back the hardest work — emergency calls, complex diagnostics, commercial accounts, and known difficult customers — until the tech has a solid run of clean jobs behind them.

The 30-day plan at a glance

Here is the whole month on one page.

Every stage ends with a sign-off, not a date. A tech who is ready early can move early. A tech who needs more time gets more time. The calendar serves the plan, not the other way around.

Check-ins: short, frequent, and specific

Check-ins are how you find problems while they are still small.

Daily in the first two weeks. Five minutes at the end of the day. What went well, what felt hard, anything that surprised them.

Weekly after that. A slightly longer conversation covering the week's jobs, any callbacks or complaints, tool and parts gaps, and whether they are ready for the next stage.

Use the job record, not just memory. A good end-of-day closeout — final statuses, photos, notes, payment outcome — gives you something concrete to review with the new tech. The routine is in our technician end-of-day closeout checklist, and it is worth teaching in week one.

Ask the trainer too. The experienced tech who rode along sees things the new hire will not mention.

When to put a new tech on the online booking calendar

This is the decision that most often goes wrong, because it happens by default rather than on purpose.

An online booking portal shows customers real available time slots based on technician schedules and working hours. The moment a new tech's schedule is open and bookable, a customer can book any job type you offer straight into a rookie's first free slot — including the complex job you meant to keep away from them.

So keep the new tech's schedule dispatcher-controlled for the first month. The office assigns their jobs deliberately, matching each one to where the tech is in the ramp. Only when the tech is running the job types customers can book, solo and without frequent callbacks, should their availability flow into online booking.

When you do open it up, watch the first few weeks of customer-booked jobs on that tech's calendar and pull back if the mix is too hard. Online booking is included from the Starter plan, and our guide on how to get your team to adopt an online booking system covers the rollout side.

What to measure by day 30

At the end of the month, look at a few simple signals:

• Callbacks on the new tech's solo jobs compared with your team norm.
• Job times — are they settling toward normal, or still running well over?
• Documentation quality — photos, notes, and payment status on every job.
• Customer feedback and reviews on their jobs.
• The tech's own confidence, which you will hear in the check-ins.

None of these need to be perfect by day 30. They need to be trending the right way. A tech on a clear upward trend after a month is a hire that worked.

If you need a sense of the broader labor market for your trade while you plan hiring and pay, the Bureau of Labor Statistics Occupational Outlook Handbook is a good neutral reference.

Frequently asked questions

How should I schedule a new technician's first 30 days?

Schedule the first month in stages — a week of ride-alongs, a week of shadowing where the new tech does the work under supervision, a week of leading simple jobs solo with backup, and a final week building toward a normal load. Each stage should have a clear sign-off before the next one starts.

How many jobs a day should a new technician run?

Start well below your experienced techs and build up. A reasonable pattern is roughly half a normal load in the first solo week, rising toward a full load by the end of the month, adjusted to how the tech is actually performing rather than to the calendar alone.

What jobs should a new technician do first?

Start with the most repeatable, lowest-risk job types — routine maintenance, standard installs, and simple service calls with a predictable scope. Save emergency calls, complex diagnostics, commercial accounts, and difficult customers until the tech has proven the basics.

How much does GetTimePad cost?

GetTimePad is $79/mo Starter for one staff member, $199/mo Pro for up to five staff, and $499/mo Agency for unlimited staff. Extra staff seats on Starter and Pro are $25/mo each, which is how most shops add a new hire. Tech Mode and staff roles land at Pro. Annual billing gives you two months free. See /pricing.

When should a new technician appear on the online booking calendar?

Only after they are running the job types customers can book, solo and without frequent callbacks. Until then, keep their schedule dispatcher-controlled so the office decides exactly which jobs they get, rather than letting a customer book a complex job into a rookie's open slot.

What should a new technician's check-ins cover?

Check-ins should cover what went well, which jobs felt difficult, any callbacks or complaints, tool and parts gaps, and whether the tech is ready for the next stage. Keep them short and frequent in the first weeks — daily at first, then weekly — so problems surface while they are still small.