The first week sets the tone for everything that follows, and most teams waste it. A new starter spends day one waiting for a laptop, hunting for a login that never arrived, and nodding along to a tour of fire exits they will never consciously think about again. The fix is not a fancier induction deck. It is starting before they walk through the door.
Pre-boarding: the part everyone skips
Pre-boarding is the gap between someone accepting the offer and their first morning, and it is where good employers quietly win loyalty. Send the equipment to their home address so it arrives a few days early. Set up the email account, the payroll record, and the software licences in advance so nothing is "pending IT" at 9am. A short, warm note from the manager - not HR, the actual manager - saying what the first day looks like removes a surprising amount of dread. (I have watched a developer nearly pull out of a role because nobody contacted her for three weeks after she signed; silence reads as chaos.)
Get the boring paperwork right, because it is not actually boring to the person whose pay depends on it. Right-to-work checks, the P45 or starter checklist, the National Insurance details, the pension auto-enrolment, the emergency contact - all of it should be collected and confirmed in week one, not chased in month two. Botch the first payslip and you have told your new hire exactly how much attention to detail they can expect from you.
A buddy beats a handbook
Assign a buddy who is not the line manager. People will ask a peer "where is the loo and is this Slack message too informal?" but will never ask their boss. The buddy should be someone organised enough to actually reply, with a standing fifteen minutes booked for the first fortnight.
Build a thirty-day plan they can see
Vague instructions to "settle in" leave ambitious people anxious and coasters comfortable. Write a real thirty-day plan with three or four concrete milestones: shadow two client calls in week one, own a small task by week two, present something back to the team by day thirty. Make it visible to them. This is the single highest-return thing you can do, and it costs nothing but an hour of thought.
- Day one: working kit, a clear desk or login, lunch with the team, no all-day meeting marathon.
- A buddy and a manager check-in scheduled, not improvised.
- By day thirty they should have shipped one real thing, however small, so they feel useful rather than decorative.
None of this guarantees retention - a strong onboarding cannot rescue a badly designed job or a manager who disappears after week two. But a person who feels expected, equipped, and useful by Friday is far harder to lose than one left to guess. Get the laptop there early.