Onboarding: what new hires need in the first week

A new hire spends their first days working out how things are done here and what is expected of them, and the answers they arrive at tend to persist. Someone who spends day one waiting for access to a system, unsure who to ask, learns that asking is awkward and that being blocked is normal. That lesson does not wear off quickly, and it shows up months later as someone who sits on problems rather than raising them.

The reason first weeks go badly in small businesses is rarely indifference. It is that the person who hired them is busy, the hire's arrival coincides with whatever crisis is current, and preparation loses to urgency. The work of onboarding is also invisible in advance — nothing breaks if you do not prepare, so it gets deferred until the person is standing there. This is what makes a checklist worth having: not because onboarding is complicated, but because it needs to happen on a specific day regardless of what else is happening, and anything that depends on remembering under pressure does not happen reliably.

The most avoidable first-day failure is a person who cannot do anything because nothing has been set up. Email, whatever systems the role uses, the shared drive and its relevant folders, any physical access such as keys or a gate pass, and the equipment they will work on. Each of these has a lead time, and several may depend on somebody who is not you.

Working backwards from the start date is what makes this reliable. If a system account needs to be requested from an external provider, that request goes in the week before, not on the morning. It is also worth logging in as them, or having them do it while you are present, because an account that exists but has the wrong permissions is functionally the same as no account and is discovered only when someone tries to use it. Two related items get forgotten regularly: payroll details and whatever documentation your obligations require, which if left until later tends to surface as an urgent problem at the end of the month; and adding the person to the internal channels where work is actually discussed, since being absent from those is a slow, invisible exclusion nobody notices for weeks.

A round of introductions where everyone says their name and role is politeness rather than onboarding, and almost none of it is retained. What a new person actually needs is to know who to go to for specific things, and that requires naming the thing rather than the department: who fixes it when the system will not let you in, who approves an expense, who knows the history with our largest customer, who to tell if you will be late.

A short written list of those names against those situations is worth more than a full team introduction, and it can be handed over on day one. Where the team is small enough, a brief individual conversation with each person the new hire will work with regularly beats a group meeting, because a one-to-one produces an actual working relationship while a group introduction produces a name. It is also worth telling the existing team who is arriving, what they will be doing, and what changes as a result. A new person walking into a team that was not told they were coming has to explain themselves repeatedly, and the team quite reasonably reads the arrival as something being done to them rather than with them.

Giving a new hire something small and completable in the first day or two does more for their confidence than any amount of orientation. It should be real work, useful to someone, and finishable — updating a set of records, handling a category of straightforward customer queries, producing one report. What matters is that at the end of it they have done something that counted.

The reason this works is that a new job is a prolonged period of feeling incompetent, and the antidote is evidence to the contrary. It also teaches you things no interview did: how they ask when stuck, whether they check before assuming, whether they tell you when they finish. What to avoid is either extreme. A week of reading documentation with nothing to do is demoralising and teaches nothing that sticks, because context without application does not stay. Being handed a critical task on day two is worse — the person has no way to judge what good looks like here, no relationships to draw on, and a failure they had no means of avoiding. The early task should be genuinely useful and genuinely low-stakes, which is a narrower target than it sounds and is worth choosing deliberately before they start.

If the job description stated what success looks like in the first three months, the first week is when to walk through it in detail and confirm it still reflects reality. If it did not, the first week is when to write it. Either way the new hire should leave their first days able to say what they are expected to have achieved and by when.

This matters most in small businesses, where roles are least defined and most likely to drift. A new hire without a stated target fills their time with whatever is asked of them, which produces a busy person whose contribution nobody can assess — including them. It is also the fairest basis for the probation conversation, since a review against goals someone was told about on day one is a genuinely different conversation from one against a standard that was never stated. Set explicit early checkpoints as well, at around two weeks and a month, and put them in the calendar during the first week. A checkpoint that exists as an intention gets skipped precisely when it matters most, which is when things are not going well and neither party wants the conversation.

Most onboarding checklists are written for the employer, listing what to arrange. The more useful pair includes one written for the new person: what they should know by the end of week one, who they should have met, what they should have access to, and what to do if any of it has not happened. Handing that over on day one does something a manager's private checklist cannot — it makes the gaps visible to the person best placed to notice them.

It also transfers a reasonable amount of responsibility in a way that feels supportive rather than demanding. Someone who has been told they should have drive access by Wednesday will say so on Thursday, whereas someone who does not know what they are entitled to expect will wait, assume it is normal, and work around it. A last item worth including is permission to ask about anything, and specifically about the things that feel too small to raise — where to eat, whether the hours are literal, who the people in the group chat are. Those are exactly the questions new employees sit on, and they are the ones that make somebody feel like an outsider for far longer than necessary.