The onboarding checklist that survives the first 90 days
Onboarding is usually measured by whether the laptop arrived. Here is a checklist built around the milestones that actually predict whether someone stays.
Most onboarding checklists are procurement lists. Laptop, email, badge, handbook, done. They are easy to complete and they predict almost nothing, because the reasons people leave in their first quarter are rarely equipment problems. They are clarity problems: what am I meant to be doing, who decides if I did it well, and does anyone notice I am here.
A checklist worth keeping tracks two things in parallel: the administrative work that must be legally and operationally complete, and the human milestones that tell you whether the hire is landing.
Before day one
Pre-boarding is where the most avoidable failures happen, because the hire has accepted but has no way to chase anything. Silence between offer and start date is the single cheapest thing to fix.
- Contract issued and signed, with the start date and probation terms explicit.
- Right-to-work and visa steps started, with an owner and a date, not just a status.
- Payroll profile created: bank details, tax or WPS identifiers, salary structure.
- Equipment ordered and shipped to a confirmed address, tracked to delivery.
- Accounts provisioned but not yet active, so day one is a switch-on and not a support ticket.
- A written first-week plan sent to the hire, so the first email is not a surprise.
Day one and week one
The goal of the first week is not productivity. It is orientation: enough context that the hire can ask good questions, and enough contact that they know who to ask. Every access request that day one generates is a week-one hour spent not learning the job.
- Every system the role needs is already working, tested against the actual role, not a generic template.
- A named buddy who is not the manager and who has been told they are the buddy.
- A first task that can genuinely be completed in week one and that someone will review.
- Policy acknowledgements captured and stored, not emailed and forgotten.
- A scheduled end-of-week check-in that exists in the calendar before the hire arrives.
The 30 / 60 / 90 checkpoints
These are the checkpoints that predict retention, and they work because they force a written answer to a question managers otherwise defer: is this working?
| Checkpoint | What is assessed | Decision it forces |
|---|---|---|
| Day 30 | Context and tooling: can they operate without blocking on others? | Fix access, ownership or expectation gaps while they are cheap |
| Day 60 | Output on real work, reviewed against the role's actual bar | Correct scope or support before probation becomes a surprise |
| Day 90 | Probation decision with written evidence from the prior checkpoints | Confirm, extend or exit, never a decision made cold |
What to automate and what not to
The administrative half of onboarding should be almost entirely automated: records, contracts, payroll profiles, access provisioning and policy acknowledgements are deterministic and benefit from never being forgotten. The human half should not be automated but it should be scheduled, prompted and recorded.
Automate the parts that fail from forgetfulness. Schedule the parts that fail from avoidance.
The practical test of an onboarding process is whether a manager hiring their first person can follow it without asking HR what happens next. If the process only works when an experienced person drives it, it is not a process, it is that person.
See it run on your own data.
Teamio handles onboarding, payroll, attendance and reporting end to end and holds anything consequential for your approval.