Ask people about their first day and nobody mentions the policy acknowledgements. They remember whether their laptop worked, whether anyone was expecting them, whether they had somewhere to sit and someone to eat lunch with. Most onboarding checklists are written by the department that owns the paperwork, which is why the workplace half, the half people remember, keeps getting missed.
The short version
- Onboarding starts before day one: accounts, kit, desk and access sorted in advance, not in the lobby.
- Day one is about arrival working smoothly: booked desk, working badge, a buddy and a plan.
- Week one builds rhythm: anchor days with the team, the first one-to-one, self-service set up.
- Month one closes the loop: expectations agreed, check-in done, and the checklist itself reviewed.
Before day one
Everything on this list can be done the week before, and every item done early removes a queue on the day.
- Contract signed and records created, with self-service access so the new starter enters their own details once.
- Accounts, email and core tools provisioned; laptop and kit ordered and tested.
- Access card or mobile credential ready for collection, not requested on arrival.
- Desk booked for the first week, near the team, and parking arranged if they drive.
- A buddy named, and a first-week calendar with the team’s office days already in it.
- Manager sends a short welcome note: where to come, when, what the first day holds.
The first day
One goal: arrival works. The new starter should walk into a building that expects them.
- Reception knows the name, the badge is waiting, and the buddy meets them at the door.
- The booked desk is where the team sits, the laptop signs in, and the printer is a mystery for another day.
- A team lunch, booked in advance. It reads as a small thing and is remembered longer than any presentation.
- Thirty minutes with the manager at the end of the day: what the first week looks like, nothing heavier.
The first week
Rhythm beats information. A new starter who knows which days the team is in, how to book a desk near them and who to ask stupid questions has what matters; the rest of workplace onboarding follows from there.
- First one-to-one with the manager, in person on an anchor day if the role is hybrid.
- Introductions to the people they will actually work with, not the full org chart.
- Shown how to book desks, rooms and parking themselves, and how leave requests work.
- Access to the systems the role needs verified by using them, not by a licence list.
The first month
Onboarding fails quietly in week three, when the calendar attention stops and nobody notices the new starter drifting. Close the loop deliberately.
- Expectations for the first three months agreed in writing, with the manager owning them.
- A thirty-day check-in that asks what has been confusing, not just how it is going.
- Buddy duty formally ends, feedback collected from both sides.
- The checklist itself updated with whatever this starter hit that it missed.
The hybrid difference
In a hybrid team the office is not the default, so nothing about the workplace can be left to osmosis. The first days should be office days with the whole team present, the desk should be booked before the commute, and the working pattern, which days, which office, what counts as attendance, should be stated on day one rather than discovered by trial and error. A starter who spends week one on video calls from an empty office has technically been onboarded and practically been abandoned.