Picture a bloke hiring his first proper employee. Good hire. Sharp, keen, turns up early on day one. And then spends most of that first morning sitting at an empty desk with no laptop login, no email address and nobody quite sure who's meant to be looking after him.
The boss is out on a job. The office manager thought IT had sorted the accounts. IT, which is a mate who does it on weekends, didn't know a start date had been set. So by lunchtime the new starter is reading the fire exit sign for something to do.
Nobody did anything wrong, and that's the point. There was just no checklist, so every step lived in somebody's head, and somebody's head was somewhere else.
This is the fix for this week, and it's boring in the best way. An employee onboarding checklist that runs itself.
Why small businesses get this wrong
A big company has an HR department. A small business has the owner, who is also the salesperson, the bookkeeper and the person who unblocks the printer.
So onboarding happens in whatever gaps are left. You remember the contract but forget the pension enrolment. You remember the login but forget to tell the team he's starting. You remember to show him the kettle but not the one process that will cause him grief in week two.
And every missed step costs something. Not dramatic money, just a steady drip. The new starter loses a morning. Somebody else loses an hour fixing access. And worst of all, the new person decides in the first week whether this is a proper outfit or a shambles. First impressions stick. You can't buy that back.
What the checklist actually needs
Forget the 40 page onboarding manual nobody reads. You need one list, split into four stages, and each item needs an owner and a due date relative to the start date.
Before they start (two weeks out to the day before)
- Signed contract and right-to-work check
- Payroll and pension details collected
- Email account, software logins and any hardware ordered
- Team told who is arriving, what they'll do and when
- Day one plan sent to the new starter, so they know where to be, what to wear and who to ask for
Day one
- Laptop and accounts working before they walk in
- Welcome from the boss, in person or on a call, in the first hour
- A named buddy who answers the daft questions
- A tour that includes the boring practicalities, like where the first aid kit lives
First week
- One small, real task they can finish and feel good about
- Shadowing the two or three processes they'll own
- Short check-in at the end of day three and again on Friday
First month
- Written expectations for the next ninety days
- A proper conversation at the four week mark about what's working
Look, that's it. Four stages, maybe twenty items. If you can't fit it on two pages, you've written a manual, not a checklist.
Where the automation comes in
But here's the bit most owners skip. A checklist in a Word document is better than nothing. A checklist that fires itself is a different animal.
So think about what triggers it. The moment you mark someone as "hired" in whatever system you use, whether that's a CRM, a spreadsheet or a project board, the whole sequence kicks off. Tool-agnostic, so use what you've already got.
Here's what it does without anyone touching it:
- Creates the tasks. Every item above becomes a task, assigned to the right person, with a due date counted back from the start date. The person ordering the laptop gets a nudge two weeks out, not the day before.
- Sends the paperwork. The new starter gets an email with the forms to fill in and a day one plan. No chasing.
- Tells the team. A short message goes out to the staff channel: who's starting, when, and who their buddy is.
- Nags the owner. If a task is still open the day before the start date, you get a message. One message, not a flood.
- Books the check-ins. Day three, end of week one and the four week conversation land in the diary automatically.
- Closes the loop. On day thirty, the system asks the new starter three questions: what was clear, what was confusing and what should we change. The answers go straight back to you.
And that last one is the gold. You get a free audit of your own business from someone who sees it with fresh eyes, and you only get that window once. After a month they've gone native and stopped noticing the weird stuff.
Do the maths
Let's use made-up numbers, because they're easy to follow. Say you hire two people a year. Each one burns about half a day of their own time and half a day of somebody else's on avoidable onboarding hiccups. That's two days of wages for each hire, four days across the year.
At a day rate of one hundred and fifty pounds, that's six hundred quid a year in plain lost time. Not a fortune.
But that isn't the real cost. The real cost is the starter who decides in week one that you're disorganised, and starts glancing at job ads by week six. Replace someone and you pay in recruitment time, lost productivity and months of the team carrying the gap. One avoided early resignation covers the checklist many times over.
And the setup takes an afternoon. Maybe two if your process is a mess, which is also useful to find out.
How to build it this week
You don't need a clever tool. Here's the order I'd do it in.
First, write down what actually happened the last time someone started. Not what should have happened. What did. Ask the person who started, because they'll remember the gaps better than you.
Second, turn that into the four stages above. Cut anything that doesn't change the new starter's first month.
Third, and this matters, give every line an owner. A task with no name next to it is a wish.
Fourth, wire up the trigger. Put the checklist into your project tool or CRM as a template, and set the due dates relative to the start date. Most tools can do this with a few clicks, and the ones that can't can be joined to a simple automation.
Fifth, run it on the next hire, then fix it. The first version will be wrong in two places. Good, because you'll know where, because the day thirty survey will tell you.
The same list works for contractors and freelancers
If you bring in a freelancer or a seasonal worker, run a trimmed version. Same bones, fewer steps. Access, a briefing, a named contact and a check-in. It takes ten minutes to set up, sort of, once you've done the full version, and it stops the contractor wasting their first day, which you're paying for.
What I'd leave alone
But don't automate the welcome itself. The call from the boss, the buddy lunch, the bit where you tell them why you started the business. That's the human part, and it's the part they'll actually remember.
So automate everything around it, so you turn up to the human part with your head clear and nothing left to chase. That's the whole job. The machine does the paperwork, you do the welcoming.
If you want to talk this through with people who are actually doing it, come join us in The Autonomous Business on Facebook. No gurus, no waffle, just real conversations with business owners building systems that run themselves.
Brewed by Steven, poured by Viktor
About Steven Tann: Steven helps business owners build systems that run themselves using AI. After 10+ years helping 7,000+ businesses and building his own autonomous operations, he's the bloke who actually does it, not just talks about it. Find out more at steventann.com.