The First Ninety Days Are a Series of Handoffs: Seven Onboarding Checkpoints for Small Employers
Most small businesses do not lose new hires over salary. They lose them to a first week that nobody planned, a manager who was on the road, and a job description that described someone else's job. Without an HR department to run a formal program, onboarding becomes whatever the owner remembers to do on a Friday afternoon.
That is survivable — but only if you stop thinking of onboarding as a packet of forms and start treating it as a sequence of handoffs. Each one is a moment when the new hire decides, consciously or not, whether staying was a good idea. Below are seven of them, in roughly the order a new employee experiences them, with notes on what to say, what to document, and what to avoid.
Checkpoint 1: The Pre-Start Message, Two Business Days Out
Between the signed offer and the first morning there is a silence that small employers routinely fill with nothing. The fix is one short message from the direct manager — not from a software platform — confirming the start time, where to park, which door to use, what people actually wear, and the name of the person who will meet them.
Say: We are glad you are coming. Here is the practical information you need. Your first day will end at a specific time.
Document: The message itself, plus any logistical question the person raised and the answer you gave.
Avoid: An automated welcome email with no human name attached, or a single attachment of tax forms sent by a payroll provider. Neither answers the question every new hire is actually asking: did I make the right choice?
Checkpoint 2: The First Hour of Day One
Before the tour, before the handbook, before the benefits portal, the new hire should hear two sentences about why the position exists and what success looks like at ninety days. That is it. Everything else can wait until the second hour.
Say: This role matters because of a specific problem it solves. By the end of your first ninety days, we will consider this a success.
Document: Those expectations in writing, even if the document is one page and slightly imperfect.
Avoid: Sequencing the day so that the person spends three hours on compliance paperwork and forty minutes with the team. The paperwork is necessary; it is not onboarding.
Checkpoint 3: The First Real Assignment, Days Two and Three
A new hire needs something small and finishable — a task with a visible end, a real recipient, and a reviewer who is named in advance. Shadowing someone for two weeks produces a person who has watched work but has not done any.
Say: Here is the task, here is who uses the output, and here is who will look at your draft by Thursday.
Document: The task, the reviewer, and the deadline. A short note in a shared file is enough.
Avoid: Assigning busywork that no one reads. New hires notice, and it teaches them what the company considers real.
Checkpoint 4: The Week-One Debrief
By the end of the first week, the new hire knows things the employer does not. Some of it is small — where the supplies are kept. Some of it is not — a process that only works because one person has memorized it.
Say: Three questions. What made sense this week? What did not? What is still unclear going into next week?
Document: The answers, and specifically any correction you promised to make.
Avoid: Asking whether there are any questions and treating silence as a yes.
Checkpoint 5: The Thirty-Day Conversation With Someone Other Than the Manager
This is the checkpoint small employers skip most often, and it is the one that surfaces problems early enough to fix them. An owner or operations lead — someone with authority but not the person assigning daily work — sits down for twenty minutes and asks about workload, clarity, and whether the job matches what was described in the interview.
Say: I am not your supervisor for this conversation. I want to know what is harder than expected and what is easier.
Document: The date, a short summary, and any commitment made. If the person raises a concern about conduct or treatment, treat it as a complaint and route it into a documented process rather than a hallway conversation.
Avoid: Framing the meeting as a satisfaction survey. The purpose is to catch misalignment while it is still cheap to correct.
Checkpoint 6: The First Mistake
Every new hire makes one. What matters is whether the response teaches the person something or teaches them to hide errors.
Say: Here is what went wrong, here is the effect, and here is what we will do differently next time. If the cause was missing training, say so plainly and fix the training.
Document: A dated note of the conversation. If the error carries real performance weight — a safety lapse, a client-facing failure — the note belongs in the personnel file.
Avoid: Two opposite errors. Do not save the conversation for an annual review, and do not issue a written warning for a gap in your own training.
Checkpoint 7: The Ninety-Day Conversation
Pull out the expectations document from the first hour of day one and go through it line by line. Confirm what has been met, adjust what was unrealistic, and confirm what happens next.
Say: Here is what we agreed on in week one. Here is where we are. Here is what changes.
Document: A revised version of the expectations, acknowledged in writing, plus any change to pay, schedule, or classification discussed at this point.
Avoid: Letting any introductory period lapse in silence, and making classification or pay changes orally. Confirm them in writing the same week.
What This Does Not Require
None of the seven checkpoints depends on an HR department, a learning management system, or a budget. They require a calendar reminder, a manager who prepares for thirty minutes, and a shared file where notes actually get saved. A five-person company can run all seven with a single document and a recurring meeting.
What they do require is consistency. A new hire who receives a thoughtful first week and then nothing for eleven weeks learns that the attention was a performance. The handoffs matter less individually than the pattern they create.