How to Onboard a New Office Admin in 30 Days

You hired someone to take the office off your plate. Three weeks in you are answering more questions than before, your evening goes on redoing their work, and a quiet voice is asking whether it would be faster to do it yourself. That voice is right about today and wrong about the year. The fix is not training harder. It is changing the order you hand things over in.

The short answer

Onboard in four waves over roughly six weeks. Days 1 to 10 the admin owns the phone and intake. Days 11 to 20 the schedule and dispatch. Days 21 to 35 money coming in. Money going out is split between two people permanently and never handed over whole. Before any of it, write the job down on one page, because a role that was never defined cannot be delegated, only leaked.

Why this fails in trade businesses specifically

The failure mode is not laziness on either side. It is a math error the owner makes on day three.

A contractor on r/Contractor described it precisely. Running a shop with two in management and six hourly, they hired for the role and then found: "We struggled giving her direction and setting her up for success. Didn't have the time to spend to teach her how to do certain things in QBO and other programs when you could just do it yourself in a couple minutes." That is the trap in one sentence. Teaching a task costs 30 to 45 minutes once. Doing it yourself costs two minutes. On day three, doing it yourself wins. Over a year, a two-minute task done fifteen times a week is twenty-six hours you never got back, and the admin still cannot do it.

The second error is expecting a gain in week one. Another operator in the same thread put the honest version well: "Having the expectation that a new hire is at first a setback before they become a multiplier is a challenge for sure." You are going to be slower for three to four weeks. If you do not plan for that dip, you will abort the handover somewhere around day ten, which is the exact point where the investment is at its most sunk and its least returned.

The third error is scope. Two office managers in that thread, one in the US and one in the UK, independently described the same ending: they left, and were replaced by more than one person. "After I left they hired two full-time replacements and someone else to do the social media." Role creep in a small office is invisible on any given day, because every task that lands looks small. It is only visible in aggregate, which is what the one page is for.

Before day one: the one page

Write four paths down before the new admin walks in. Not a policy manual. Four paths, on one page:

1. How a phone call becomes a booked job.
2. How a booked job becomes a scheduled job with the right person on it.
3. How a finished job becomes an invoice.
4. How an unpaid invoice gets chased, and by whom, and on what day.

If you cannot write those four in an hour, that is the finding, and it is worth more than the hour cost. It means the process exists only as your judgment, and judgment cannot be handed over in week one at any speed. Our breakdown of whether to hire office help or buy software makes the case for fixing that before the hire, not after.

Then list what the role is not. In a shop under twenty people the admin will be offered estimating, marketing, HR, safety paperwork, supplier accounts and social media inside a year. Some of that is right. All of it is not.

Hand the job over in four waves

Order the handover by what it costs when it goes wrong, not by what is on your desk today.

The instinct is the reverse: hand over the paperwork first and keep the phone, because the phone is the customer relationship. That is backwards. Paperwork done wrong is annoying. A phone that rings out while you are under a sink is the only one of these that loses money the moment it happens.

Wave 1, days 1 to 10: the phone

Give the phone a script per service type, not one general script. A solo plumber on r/Plumbing who systemized before hiring described exactly this setup: "one admin intake checklist per service (blocked drains, leaks, etc.)", structured questions to identify the issue and book correctly, and a hard rule that "admin does not diagnose or quote fixed prices over the phone."

That last rule deserves the most drill time in week one. When a new office admin at a plumbing company asked r/Plumbing what would make the techs' lives easier, the answer came fast: "don't let customers price shop. If they ask how much it will be, let them know that a technician needs to take a look to give them an accurate price." An admin who guesses either names a price low enough to lose margin you cannot recover on site, or high enough that the caller shops it. That is a script failure, not a training failure.

The second thing to drill is the job note. The most common complaint field techs have about dispatch is a note with nothing in it. As one plumber put it: "I often get dispatched jobs that just say 'leak' in the job notes and that can be a bit frustrating." Another spelled out what a useful note contains: whether the pipe is underground or under the house, the type and size if the customer knows it, and whether there is a cleanout. Get that and the tech makes one supply house trip instead of two.

Third, verify the address out loud. "Double check address with customer. I've been sent to so many wrong houses because people mistaken streets and avenues." A wrong address is an hour of drive time, a missed slot and an angry customer, all from one syllable.

Wave 2, days 11 to 20: the schedule

Dispatch is where a good admin becomes expensive to replace and a bad one quietly costs you a crew member. These rules are in no onboarding guide, because they come from the trucks. When that plumbing office admin asked, the crews gave them up:

• Do not send them to a last call 45 minutes or more from their house if they take trucks home. The tech eats that drive unpaid, and they will remember who scheduled it.
• Do not schedule outdoor work in the rain when it can move.
• One truck, one area. As a fellow dispatcher put it, "the last thing you want are guys passing each other on the freeway for no reason." Know which routes are affected by rush hour.
• Do not dispatch 30 minutes before a shift ends. They still have to clean out the truck and drive back.
• Send the right person, but do not play favourites. From an office person on the same thread: "You decide who goes to the profitable jobs. Meaning you decide which job will affect whose bonus. Be careful." If your techs are paid on performance, your dispatcher is quietly setting their pay. Say that out loud in week two so it is a known responsibility rather than an accidental one.

None of that is obvious to someone whose last job was in an office. All of it is obvious to your crew. Introduce the admin to your two most senior field staff in week one and tell them plainly that teaching the office how the road works is part of their job.

Wave 3, days 21 to 35: money coming in

By day 21 the admin has enough job context to chase money without asking you what a job was. Hand over in this order: sending invoices, taking deposits, following up on unanswered estimates, chasing invoices past 30 days.

Estimate follow-up goes first and gets measured hardest, because it is the task an owner reliably skips. Every unanswered quote in your inbox is a job you already paid to acquire and already paid to price. Giving that list to someone whose actual job is to work it, rather than to you at 9pm, is usually where the hire pays for itself. If your quotes and follow-ups live in a phone thread, the text message problem needs solving before the handover, not after.

Wave 4: money going out, and the split you never undo

This is the wave that never completes, on purpose, and week one is the only time you can set it up without it feeling like an accusation.

The rule is simple: the person who prepares a payment is not the person who approves it. The admin builds the supplier payment run, enters the bill, sets up the payroll. You, or your bookkeeper, release it. Bank statements come to your email, not theirs. That single split is the highest-value control available to a shop your size and it costs nothing.

The reason to do it now rather than later is in the data. The ACFE's Occupational Fraud 2026: A Report to the Nations, the 14th edition of the largest study of its kind, covering 2,402 investigated cases across 143 countries and more than $3.4 billion in losses, found a median loss of $104,000 per case. More usefully for a small shop, it found median losses rise steeply with tenure: $50,000 where the perpetrator had been employed under a year, $100,000 at one to five years, and $138,000 at six to ten. The new hire is not the exposure. The person you trust completely in year seven is.

A lack of internal controls was the primary weakness in 33% of cases, ahead of control override at 19% and lack of management review at 18%. Detection speed is the whole ballgame: schemes caught within six months carry a median loss of $40,000, while those running five years or more reach $1,115,000. Surprise audits, present at only 44% of organizations, were associated with a 50% reduction in median losses.

For a shop with one admin that means: split preparation from approval, keep the bank feed coming to you, and once a quarter pick a random month and read every transaction. Twenty minutes, four times a year.

Train by recording, not by writing

You are not going to write a procedures manual. You have never written one and you will not write one now, and every onboarding guide that assumes you will is written for a company with an HR department.

Record instead.

• Turn on call recording. One owner in a plumbing and HVAC operators group described reading his own call transcripts out of CallRail as the thing that changed how he trained phone staff. Have the admin listen to twenty real calls in week one: five that booked, five that did not, five awkward, five price-shopping. Better curriculum than anything you would write.
• Film the quote build on your phone. Two minutes, narrated, done in the truck. Do it for the five things you do most.
• Reverse the shadowing early. Standard advice is that the new person watches for two weeks. Flip it in week two: they do the task, you watch. You find out on day eight what you would otherwise learn on day forty.
• Have them write the SOP. Every task they learn, they document in their own words and you correct it once. By day 30 you have the manual you were never going to write, built by the person who needed it.

Your system is the onboarding program

Here is the uncomfortable part. How long onboarding takes is mostly not a property of the person you hired. It is a property of the system you are handing them.

A general contractor in Northern Ontario running commercial and residential divisions put the problem plainly on r/Contractor while shopping for replacement software: "onboarding new office staff can be challenging, there's a steep learning curve, especially for those without a construction background." His software was not broken. It was just built for someone who already knew the business.

The test another contractor offered in that thread is the right one: "see how your least tech-savvy staff handle it. If they can learn it in a week, it'll stick. If not, you'll be back to spreadsheets by next quarter."

If your pipeline is a whiteboard, your quotes are in one app, your job photos are in another, your invoices are in QuickBooks and the connective tissue is your memory, onboarding will take four months regardless of who you hired. If a lead lands in one place with stages that move in one direction, most of the training is reading the screen.

The 30-day scorecard

Judge the hire on numbers, not on how the handover feels. Four are enough.

Track them from the week before the admin starts, so you have the before picture. Without a baseline, month two becomes an argument about impressions.

The week by week checklist

Week 0. One page written. Logins created in a password manager under your account, not theirs. Bank feed and statements directed to you. Two senior field staff told that teaching the office how the road works is part of their job.

Week 1. Twenty recorded calls listened to. Intake script written by the admin. Address verification and the no-pricing rule drilled. They take live calls with you in the room.

Week 2. They run intake alone. You review every job note at end of day for five days, then stop. Dispatch rules taught by the crew, not by you.

Weeks 3 and 4. Schedule handed over. A fifteen minute end-of-day check-in, nothing longer. First scorecard read at day 30.

Weeks 5 and 6. Invoicing and estimate follow-up handed over. Payment preparation handed over, approval kept. Quarterly transaction review put in your calendar so it actually happens.

If it is still not working at day 45

Check three things in order.

First, the numbers. If calls are getting answered and quotes are going out same day, the handover is working, and what you are feeling is loss of control, which is the correct feeling and passes.

Second, the definition. If you cannot point at the one page and say which of the four paths they own, the problem is the role, not the hire.

Third, whether you actually let go. The most common outcome in a small shop is an admin hired to own a process the owner never stopped running in parallel. Two people doing the same job badly looks exactly like one bad employee from the inside.

And plan for the exit while things are good. Every login in a shared password manager under your account, every customer record in your system rather than their inbox, every process written down as they learn it. That costs nothing during onboarding and saves a fortnight if they leave. It is the same logic behind sorting your admin into buckets before handing any of it over: the work you never wrote down is the work you can never give away.

One operator in that r/Contractor thread, running a twenty-person company doing $11 million a year, called a competent office manager their hardest position to fill. Get the handover order right and you find out why in six weeks instead of six months.