All posts

New Hire Onboarding Checklist for Service Businesses

9 min read

Onboard a new crew member in four stages: paperwork and compliance before day one, systems and gear on day one, shadowing and job-site standards through week one, and a 30-day check-in to confirm the hire is working. Write the checklist once and run it the same way every time. CRMb adds new members to a shared roster with one join code, so a new tech is on the schedule and their hours flow into job labor cost from their first shift.

Most service businesses hire the way they estimate before they build a price book: from memory, under pressure, differently every time. The new tech shows up, nobody has their gear, nobody told them which truck, and they spend the first morning watching someone else work.

That first week sets the habits you will live with for years. A checklist is the cheapest fix in the business.


Why onboarding is a cost-control problem

A new hire is not productive on day one, and that is fine. What matters is how long the ramp takes and what it costs you while it runs.

Three costs hide in a sloppy onboarding:

  • Lost billable hours. Both the new hire's and the person babysitting them. Two people on a one-person job is real labor cost on that job.
  • Rework and callbacks. A tech who was never shown your standard gets it wrong once, and you pay to go back. Callback costs are some of the most expensive hours you will ever run.
  • Turnover. People quit early jobs that felt chaotic. Replacing a hire means paying the ramp twice.

The goal is not to make onboarding elaborate. It is to make it the same every time, so ramp time shrinks and the hire knows what "good" looks like before they are alone on a site.


Stage 1: Before day one

Everything in this stage should be done before the new hire arrives. If they show up and the first hour is forms, you have already told them how the company runs.

  • Employment paperwork. Offer letter signed, tax withholding forms, direct deposit details, and I-9 or local equivalent work authorization. Check the requirements for your state or province; they vary.
  • Payroll setup. Pay rate, pay type (hourly or salary), pay period, and overtime rules entered before the first shift, so the first check is right. A wrong first paycheck is a bad first impression that takes months to undo.
  • Licenses and certifications. Collect and file copies, with expiry dates. Trade licenses, driver's license, and any certification your insurance requires.
  • Insurance and emergency contacts. Workers' comp notification, benefits enrollment if you offer them, and an emergency contact on file.
  • Gear ordered. Uniform, PPE, tools, keys, fuel card. Order these when the offer is accepted, not the night before.
  • First-week schedule built. Which jobs, with whom, starting when and where. Send it before day one so nobody is guessing about the 7 a.m. meet point.

A short welcome message the week before, with start time, address, what to bring, and who to ask for, costs you five minutes and removes most first-day friction.


Stage 2: Day one

Day one is orientation and access. Keep the classroom part short and get them on a real job in the afternoon if you can.

TaskWhy it matters
Walk the shop or yardWhere tools, stock, and paperwork live
Introduce the crewNames, roles, who to call for what
Safety briefingPPE rules, site hazards, incident reporting
Vehicle assignmentWhich truck, fuel policy, inspection routine
Systems accessTime tracking, schedule, job details on their phone
Review expectationsStart times, breaks, how to report a problem

The systems piece is where onboarding usually stalls. A new tech needs three things on their phone before their first shift: how to punch in, where they are working, and what the job actually is.

In CRMb, an owner or manager adds the new member to the team roster and shares one join code. The same roster and join code work for Punch, the time-tracking app, so setting them up once covers both: their schedule, the job site, and their punch clock. Their punched hours then feed straight into that job's labor cost, so the new hire's ramp shows up in your margin numbers instead of disappearing into a spreadsheet.


Stage 3: Week one

Week one is shadowing, standards, and small amounts of real responsibility. The pattern that works is watch, assist, do with supervision, do alone.

Pair them deliberately. Put the new hire with your most consistent tech, not necessarily the fastest one. Speed is easy to teach later; habits are not. Your best worker is not always your best trainer, so pick for patience and standards.

Teach the job-site standard explicitly. What a finished job looks like, how the site is left, what gets photographed, what gets confirmed with the customer before leaving. Do not assume the last employer's standard matches yours. A job-site walkthrough checklist makes this concrete.

Cover the paperwork path. How a work order arrives, what they record on it, how materials used get noted, and what happens when the customer asks for something outside the scope. That last one matters: an untrained tech saying yes to extra work is a change order you never got paid for.

Set the customer-facing rules. How to introduce themselves, what to say about pricing (usually: nothing, refer it to the office), and how to handle a complaint on site. A new tech quoting a price off the cuff can cost you the margin on the whole job.

Check in daily, briefly. Two minutes at the end of each shift. What went well, what was confusing, what they need tomorrow. Small corrections in week one prevent entrenched habits in month three.


Stage 4: 30, 60, and 90 days

Ramp does not end when the first week does. Set three checkpoints and actually hold them.

  • 30 days. Are they safe, on time, and doing the work to standard? This is the honest point to correct fit. Most problems visible at 30 days do not resolve on their own.
  • 60 days. Are they working independently on routine jobs? Compare their hours on a job type against your estimate for that job type. A tech consistently running long on the same work needs training, not pressure.
  • 90 days. Full productivity review. Pay review if you promised one. Confirm certifications, tools, and any gaps worth closing.

The 60-day comparison is where onboarding meets job costing. If you track labor hours per job against what you estimated, a new hire's ramp is measurable instead of a feeling. You will see the gap close, and you will know when it stops closing.


The mistakes that cost the most

  • Onboarding by osmosis. "Follow Dave around for a week" is not a plan. Dave has his own job and his own shortcuts, some of which you would not approve.
  • Skipping the safety briefing because they are experienced. Experience elsewhere is not knowledge of your sites, your equipment, or your incident process.
  • Getting the first paycheck wrong. Nothing erodes trust faster. Enter pay rate, type, and overtime rules before the first shift.
  • No written standard. If "done right" lives only in the owner's head, every hire learns a different version of it.
  • Delaying systems access. A tech who cannot punch in or see the schedule on day one learns that the systems are optional. That habit is very hard to reverse.

Frequently Asked Questions

What should be on a new hire onboarding checklist for a service business?

Four stages: pre-start paperwork (tax forms, work authorization, direct deposit, licenses, insurance, gear ordered), day-one setup (safety briefing, vehicle, crew introductions, systems access), week-one training (shadowing, job-site standards, work orders, customer-facing rules), and check-ins at 30, 60, and 90 days. Writing it down is what makes it repeatable.

How long should onboarding a field technician take?

Plan on a first day of orientation, a first week of shadowing and supervised work, and roughly 30 to 90 days to full productivity depending on trade complexity. Simple recurring work like cleaning or lawn maintenance ramps in weeks; licensed trades with diagnostic work take longer. Measure it by comparing their hours per job type against your estimates.

What paperwork do I need before a new employee starts?

Signed offer, tax withholding forms, work authorization documentation, direct deposit details, emergency contact, and copies of any licenses or certifications with expiry dates. Requirements vary by state and country, so confirm the current list for your jurisdiction rather than reusing an old file, and keep records where you can find them at audit time.

How do I get a new crew member set up on scheduling and time tracking?

Add them to your team roster and give them a single join code, then confirm on day one that they can punch in and see their assigned job site on their own phone. In CRMb, the roster and join code are shared with the Punch time-tracking app, so one setup covers scheduling, job sites, and the punch clock, and their hours flow into job labor cost.

How do I know if a new hire is working out?

Check at 30, 60, and 90 days against specific signals: safety and punctuality first, then independence on routine jobs, then hours per job type compared to your estimates. A new tech running long on the same job type after 60 days needs training or a different role. Job costing turns "how are they doing" into a number you can act on.


Getting started with CRMb

Write your checklist this week, before the next hire. Four stages, a page each at most, and run it the same way every time. The version that exists beats the perfect one you keep meaning to write.

CRMb puts your roster, schedule, job sites, quotes, invoicing, and inventory in one place on Mac, iPad, and the web, with crew hours from Punch flowing into every job's labor cost. Start your 14-day free trial and get your next hire on the schedule the day they start.

More from the blog