It was a Tuesday in March. My new hire's third day. I had blocked the morning to rebuild a quoting workflow, and by 9:40 a.m. I had answered eleven questions: where the gate code lives, which invoice template, is this a callback or a new job, does the customer get a text before or after. None of the questions were unreasonable. Every one of them had an answer that existed somewhere — in my head, in a Slack thread, in a folder nobody had opened since 2023. That morning is why I rebuilt the employee onboarding process for small business teams around a simple rule: the new person learns from the system, not from the owner.
Shadowing feels like training. It is not. Shadowing is the owner reading their own operating manual out loud, one question at a time, at random. It costs you your week, it produces no artifact, and it means the second hire costs exactly as much as the first. What follows is the version I run now — pre-boarding, week one, weeks two and three, and a day-30 certification — with the caveats I only learned by getting them wrong.
The shadowing math nobody runs
Do this on paper before you hire anyone. A typical field or admin hire, trained by shadowing, pulls the owner out of position for roughly 15 to 25 hours across the first two weeks — not in blocks, but in eight-minute interruptions, which is worse. Interrupted hours don't just disappear; they take the surrounding hour with them.
Then run it forward. If your onboarding lives in your head, hire number three costs the same 20 hours as hire number one. If it lives in checklists, hire number three costs your operations lead about four hours of review. That is the whole argument. Onboarding is not an HR ritual — it is the point where your documented processes either exist or get exposed as missing.
Here is the uncomfortable diagnostic: if you cannot onboard someone without being present, you do not have an onboarding problem. You have an undocumented business. The new hire is just the first person to notice.
If this sounds like your week, see how owners hand this off.
Day Zero: the block you finish before they walk in
Every onboarding I have watched fail in week one failed in the week before. The new hire showed up, and nothing was ready — no login, no vehicle assignment, no first job on the schedule — so the owner improvised, and improvisation is just shadowing with extra steps.
Day Zero is a fixed checklist, run by whoever owns hiring, finished before the start date. Three lanes:
Compliance (do not improvise this lane)
- Form I-9. Section 1 is completed by the employee no later than their first day of work for pay; you complete Section 2 within three business days. Pull the current Form I-9 from USCIS — the 08/01/2023 edition expires 05/31/2027 — rather than the PDF in your onboarding folder from two years ago.
- E-Verify, if your state requires it. Florida requires it for private employers with 25 or more employees, Tennessee at 35, Arizona for everyone. If you are growing past a threshold, the obligation attaches the moment you cross it.
- State new-hire report. Federal law requires reporting every new hire to your state directory within 20 days of hire; some states are tighter. The federal Office of Child Support Services publishes each state's rules. Put it on the checklist with a named owner — payroll platforms often file it, but "often" is not a control.
- W-4, state withholding, workers' comp class code, and direct deposit. The class code matters more than owners think: misclassifying a helper as clerical shows up as a nasty audit adjustment at policy renewal.
Access
Login to your field service platform (Jobber, Housecall Pro, ServiceTitan — whichever runs your jobs), with the correct role and permission set, not an admin seat handed out because it was faster. Mobile app installed and logged in. Time-tracking app installed. Shared phone number or extension routed. Fuel card, keys, gate codes, and any customer-portal access.
The first two weeks of work, already scheduled
This is the step most owners skip. Before the start date, put the actual jobs on the calendar: which job on Day 1, which on Day 2, who they ride with, which day they run their first solo call. If the schedule is blank on Day 1, you will fill it with yourself.
Days 1–5: one system, one checklist, one supervised job
Week one is not about culture decks. It is about producing one complete, correct unit of work — a finished job, a closed ticket, a clean invoice — under supervision that is scheduled rather than ambient.
The structure I use:
- Day 1, morning: safety and the non-negotiables. Hazard Communication training under OSHA's standard (29 CFR 1910.1200) is required at the time of initial assignment — before they handle the chemicals, not after — and OSHA expects it delivered in a language and vocabulary the worker actually understands. Cover incident reporting the same morning: a work-related fatality is reportable to OSHA within 8 hours, an amputation, in-patient hospitalization, or loss of an eye within 24. A five-person crew still owns those clocks.
- Day 1, afternoon: the job lifecycle, on one page. Not the whole business. One diagram: how a lead becomes a scheduled job becomes a completed job becomes a paid invoice. If you have already mapped your repeatable path from lead to paid, this is a fifteen-minute conversation instead of a two-hour one.
- Days 2–3: ride-along with a peer, not with you. The peer carries the checklist. The new hire's job is to watch the checklist get used — that is the actual lesson.
- Days 4–5: they run the checklist, the peer watches. Roles flip. The peer's only job is to note where the checklist was ambiguous.
Capture the ambiguity in writing, the same day. Every question the new hire asks in week one is a defect report against your documentation. I keep a running list titled "questions week one" and turn each line into a checklist step by Friday. Do that for three hires and your onboarding stops needing you. If you have never written a procedure that survives contact with a real employee, start with the fill-in SOP format — one page, trigger, steps, done-condition — and resist the urge to write a manual.
Days 6–15: reps against a scorecard, not a shadow
Week two is where owners relapse. The instinct is to keep hovering because the work is not yet perfect. Replace hovering with two mechanisms.
First, a defined scope of independence. Write down which job types they can run alone starting Day 6 — usually the highest-frequency, lowest-variance ones: a standard service call, a routine maintenance visit, a straightforward install. Everything outside that list stays paired. This is far better than a vague "use your judgment," which just routes judgment calls to your phone.
Second, an inspection point that is not you watching. Photos on the job record. A three-item post-job checklist. A customer follow-up text 24 hours later. This is ordinary quality control built into the workflow, and its side effect is that it makes supervision asynchronous — you review at 4:30 p.m. instead of interrupting your own day at 10:15 a.m.
Set the escalation rule explicitly, because the default is "call the owner":
- Question about a procedure → check the SOP, then ask the peer trainer.
- Question about a price or scope change on-site → dispatcher or ops lead, who has authority to approve up to a stated threshold.
- Safety, injury, property damage, or an angry customer → owner, immediately, no filter.
Three lanes, written on a card. Most of the eleven questions from my Tuesday morning belonged in lane one.
Days 16–30: certification, and what you are actually testing
End the onboarding period with a specific event, not a vibe. I use a certification checklist — 10 to 15 line items the new hire must demonstrate, initialed by their trainer, reviewed by me in under thirty minutes.
For a field role, a real one looks like:
- Completes a job record with before/after photos and correct line items, unassisted, three times running.
- Collects payment on-site and closes the invoice same-day.
- Handles a scope change correctly: stops, calls dispatch, gets written approval before proceeding.
- Passes a spot-check on chemical handling and PPE.
- Explains the callback policy to a customer in their own words.
- Arrives inside the arrival window on 90% of jobs across the two weeks.
Notice what is being tested. Not "is the work good" — is the person following the system that makes the work good. Those are different things, and only the second one scales. A talented tech who improvises is a future rework problem; a solid tech who runs the checklist is the foundation of a business that holds together when you step out.
What is the fastest way to get a new hire productive in a small service business?
Give them a written checklist for the highest-frequency job type, a named peer trainer, and a scheduled first two weeks of real work — before their start date. Productivity comes from removing ambiguity, not from adding supervision. A new hire with a clear checklist and a defined escalation path typically runs a standard job unaccompanied by the end of week two. A new hire trained by shadowing takes longer and produces no reusable training material, so the next hire costs the same again.
The caveats I only learned the hard way
Do not onboard into an undocumented process and call the checklist "good enough." I once handed a new admin a half-finished collections procedure and told her to "ask if anything's unclear." Everything was unclear. She asked constantly, which was correct, and I resented it, which was not. Before the start date, either the procedure exists or you admit you are teaching it live and block the calendar honestly.
The peer trainer needs to be chosen, briefed, and compensated with time. Your best tech is not automatically your best trainer, and assigning training on top of a full schedule guarantees it gets skipped. Take jobs off the trainer's board for the ride-along days. If you don't, you have quietly punished your best person for being good.
Onboarding for an office or ops role is a different animal. Field roles certify on repeatable job execution; ops roles certify on judgment and exception handling, which takes closer to 60 to 90 days. If your first non-field hire is on the horizon, the sequencing question deserves its own treatment — I wrote about what to hand off first and how to onboard that role separately, because handing an ops hire a field checklist teaches them nothing about the decisions they were hired to make.
Day 30 is a two-way review. Ask three questions and write down the answers: What was confusing that shouldn't have been? What did you expect that turned out differently? What did we tell you that turned out not to be true? The third question stings and is the most useful. New hires see your operation with fresh eyes for about six weeks, and then they acclimate to the dysfunction like everyone else.
Turnover in the first 90 days is almost never a hiring mistake. It is usually an onboarding vacuum — the person never got clear on what "good" looked like, so they guessed, guessed wrong, got corrected, and left. That pattern belongs to the broader question of why turnover is rarely a hiring problem.
Where onboarding meets the rest of the back office
Onboarding is the seam where your operating discipline gets tested by an outsider. It touches payroll setup and worker classification, so your books have to be current. It touches scheduling and dispatch, so your job workflow has to be real. It touches customer communication, so somebody has to have decided what the automated texts say. A well-run back office — clean books, a website that actually explains the service, and a few sensible automations behind the scenes — is what makes onboarding a checklist instead of an event.
At Turnkey Services, the pattern we see across small service businesses is consistent: the owners who onboard well are not better managers of people. They are better managers of documentation. The system teaches; the owner reviews.
Start with one job type. Write the checklist. Hire the next person into it. Then fix the checklist with what they ask you in week one, and hire the person after that into a better version. That is the whole compounding mechanism, and it is available to you starting today. If you're not sure which process to write first, the sequencing question has a practical answer — and it is usually the process your next hire will touch on their first morning.
Frequently asked questions
How long should onboarding take at a small service business?
Plan 30 days to certification for a field role and 60 to 90 days for an operations or admin role. Day 30 is when the person can run standard, high-frequency work unaccompanied against a documented checklist — not when they are fully seasoned. Judgment on edge cases keeps developing for months after.
What paperwork do I legally have to complete for a new employee?
At minimum: Form I-9 (employee Section 1 by their first day of work for pay, employer Section 2 within three business days), Form W-4 plus any state withholding form, a state new-hire report filed within 20 days of hire, workers' compensation with the correct class code, and E-Verify if your state requires it at your headcount. OSHA-required safety training attaches at initial assignment, before the work begins.
Can I onboard without any written SOPs?
You can, but each hire will cost you the same 15 to 25 hours of interrupted owner time and produce nothing reusable. The practical shortcut is to document only your highest-frequency job type before the start date, then let the new hire's week-one questions write the rest of the documentation.
Should I train a new hire myself or assign a peer trainer?
Assign a peer for day-to-day training and reserve yourself for a Day 1 orientation and a Day 30 review. Owner-led shadowing builds dependency on you specifically. Take jobs off the peer trainer's schedule so training isn't unpaid overtime on top of a full board.
What do I do if someone is still asking constant questions at day 30?
Log the questions for a week before deciding. Clustered around one process means the documentation is at fault — fix the checklist. Scattered across every process suggests a role fit issue, but confirm it with a written record rather than a feeling. Many day-30 'bad hires' are documentation failures wearing a person's name.