New Hire Onboarding Checklist
A new hire forms their opinion of a company in about four days, and most of that opinion is set by logistics rather than by anything anyone says. Whether the laptop worked. Whether someone was expecting them. Whether they had anything to do by Wednesday.
This checklist is short on purpose. It is the manager's list — the five things that, if they happen, mean the first week went fine, and that if they don't, no amount of good intent recovers.
It assumes you are onboarding one person into an existing team, not designing an onboarding programme.
Access is the one to front-load
Hardware and account provisioning is first on the list because it is the only step with an external dependency and a lead time. Everything else on this list you can do on the day; a laptop that has not been ordered cannot be conjured on Monday morning.
The failure mode is not that it gets forgotten — it is that it gets started on the start date. Begin it when the contract is signed, not when the person arrives.
Why a buddy and not just a manager
New starters do not ask their manager the small questions. Where the good coffee is, whether people actually use that channel, whether this meeting is optional — those go unasked for weeks if the only person to ask reports on your performance.
A buddy is someone at the same level with no evaluative relationship. It is the cheapest intervention on this list and it consistently has the largest effect on how quickly someone starts contributing.
The end-of-week check-in is not a formality
Ask two questions and mean them: what has been more confusing than it should be, and what are you still waiting on. Both surface concrete, fixable problems while they are still cheap to fix.
It also establishes, in week one, that saying something is stuck is normal. That norm is much harder to introduce in month six.
Running it more than once
Onboarding is a checklist precisely because it recurs and because the cost of a missed step is delayed — you find out three weeks later that nobody set up the repository access.
Teams that onboard well are rarely more thoughtful than teams that onboard badly. They just run the same list every time instead of remembering it from scratch, and they add a line whenever something goes wrong.
The checklist
- IT hardware & software access provisioning
- Welcome breakfast/coffee intro
- Assign onboarding buddy
- Review team documentation and codebase/tools
- End-of-week check-in
Work top to bottom, or skip what does not apply. Nothing here is mandatory.
Questions
When should this start?
Provisioning starts the day the offer is accepted. Everything else belongs to the first week. The gap between signing and starting is where most preventable onboarding failures are created.
Does this work for remote hires?
Mostly. Two steps need translating: hardware needs shipping and confirming it arrived, and the welcome coffee needs to be a scheduled call rather than a hallway moment. The buddy matters more remotely, not less — there are no hallway questions at all.
Who owns this list, HR or the manager?
HR usually owns provisioning and paperwork. Everything on this list that determines whether the week felt good — the buddy, the introductions, the check-in — is the manager's, and it does not transfer well.
What if the team is too busy that week?
That is the most common reason onboarding goes badly, and it is worth naming rather than working around. If a week cannot be found, the honest fix is to move the start date, not to run a compressed version and hope.
Don't just read it. Run it.
Onboarding someone new works better as something that comes back on its own than as a list you have to remember to reopen. Kramaya turns this into a system that reappears when it should and keeps a record of the times you did it.
Get Kramaya on Google Play