The new person shows up at eight. Someone finds them a desk. There is a laptop, maybe, still in the box, or maybe the one the last employee used, with the last employee's files on it and no password written down anywhere.
By nine they are sitting in the break room with a coffee, waiting.
By noon the office manager has made four phone calls trying to find out who created the last account, and the answer is a person who left in March.
The email account gets sorted out on Thursday. Two days of salary went to a person who could not do the job they were hired for.
The cost is boring, which is why nobody counts it
A new hire waiting two or three days is not a crisis. It is money leaving quietly. You pay a full day's wage for a day the person cannot work, and then you pay the office manager's day too, because she is the one on the phone. Add the colleague who stops their own work to explain where the shared drive lives, because there is no other way to learn it.
Do that two or three times a year and it stops being a rounding error. It also sets a tone. A first week spent waiting teaches a new employee that things here are improvised, and that the way to get anything done is to find the right person and ask.
Gallup found that roughly 1 in 10 employees strongly agree that their organization does a good job of onboarding. Gallup's own experience is that most people need twelve months or more to get up to speed in a job, and about a third of new employees do not last 90 days. The first week is not the whole story, but it is the part the new hire remembers.
The list is longer than you think
Ask an owner what a new hire needs and the answer is usually "email and the files." The real list for a five-person office is closer to this: email, the shared drive, the accounting package, the scheduling or dispatch tool, the supplier portal, the phone system, the door code, the alarm code, the shared inbox the invoices land in, the label printer, and whoever's login the postage meter runs on.
Nobody wrote that list down, because it accumulated. Each item was added the week somebody needed it, by whoever was closest to the problem. That is not sloppiness. It is what happens when a business is busy.
Zylo's research on software portfolios found that organizations underestimate how many applications they use by a factor of about 1.7, and that IT directly manages only around 13 percent of them. A small business is not exempt from that pattern. Tools arrive on a credit card and a free trial, and the knowledge of how they are wired lives in one person's head.
What good looks like instead
A checklist. One page, written down once, organized by role rather than by person.
Accounts get created before the start date, in the new hire's own name. Not "we'll just give them the front desk login." Their own name means you can shut it off in one place when they leave, and you can tell who did what.
Access follows the role. The bookkeeper gets the books. A new estimator does not need payroll, and handing it over "so they have it" only creates a cleanup job later.
The checklist has a name next to it. Not "the team." A person, who knows they are the one who preps a laptop on Friday for a Monday start.
And there is a one-page note for the new hire: where files live, how to print, who to ask about what. It sounds trivial until you remember learning all of that by interrupting people.
Run the same list backwards
Most small businesses are good at adding access and bad at removing it. When someone leaves, the mailbox gets forwarded, the account stays open, and nobody closes it, because closing it might break something. A year later there are active accounts for people who have not worked there since the previous owner.
That is the same missing checklist, pointed the other direction. If you can write down what a new hire needs, you can write down what a departing employee has, and work through it on their last Friday.
Start with one page
If someone started on Monday, what would you have to do? Write it down while you do it for the next hire. That document is the whole project.
Then once a quarter, pull the list of accounts and ask which ones belong to people who are not here. It takes an afternoon the first time and twenty minutes after that.
You do not need new software for most of this. You need the list, a name beside it, and someone who checks it.