A new hire’s first days set the tone for everything that follows. Yet onboarding is often thrown together at the last minute: a stack of forms, a laptop that isn’t ready and a manager stuck in back-to-back meetings. A good onboarding checklist turns that scramble into a calm, repeatable sequence, so every new employee feels expected, equipped and clear on what success looks like. This guide answers the questions HR teams ask most, and ends with a checklist you can adapt.
Why does onboarding matter so much?
Onboarding is not paperwork; it is the first impression that decides whether someone stays. Employees who go through a structured onboarding are far more likely to still be there a year later, and they reach full productivity weeks sooner. The opposite is just as real: a confusing, neglected start quietly pushes people toward the exit before they have had a chance to contribute. Two outcomes are worth tracking. Retention — how many new hires are still with you at 90 days and at one year. Time-to-productivity — how long until someone is doing the job without constant help. A checklist improves both, because nothing important gets forgotten.
What are the phases of onboarding?
Think of onboarding as four phases, not a single day. Pre-boarding (before day one) covers everything you can prepare in advance. Day one is about welcome and setup, not a firehose of information. The first week builds context, relationships and early wins. The first 30, 60 and 90 days turn a new face into a contributing member of the team, with clear goals and honest check-ins. Spreading the work across these phases is the single biggest improvement most teams can make.
What belongs in each phase?
Match each task to the moment it actually matters:
- Pre-boarding. Send the offer paperwork and compliance documents for e-signature, order equipment, create accounts, and email a friendly note on what to expect on day one.
- Day one. Greet them, confirm system access works, hand over equipment, cover the essentials (payroll, benefits, policies) and introduce the team and their buddy.
- First week. Walk through role expectations, set early goals, book core training, and schedule introductions with the people they’ll work with most.
- First 30/60/90 days. Hold regular check-ins, review progress against goals, gather feedback on the onboarding itself, and confirm the role is on track.
A worked onboarding checklist
Here is an example you can copy and tailor. Treat it as a starting point, not a rule.
- Before day one: contract and tax forms signed, ID and right-to-work verified, laptop and access provisioned, workspace or software ready, welcome email sent.
- Day one: warm welcome, office or remote tour, logins tested, security and policy basics, lunch with the team, buddy introduced.
- First week: role and goals explained, first task assigned, key-tools training booked, one-to-one with the manager, meetings with partner teams.
- First 30 days: goals confirmed, early feedback exchanged, questions answered.
- At 60 days: progress reviewed, any gaps in training closed.
- At 90 days: formal check-in, honest two-way feedback, confirmation the role and fit are on track.
Who owns which part?
Onboarding fails when everyone assumes someone else has it. Make ownership explicit. HR owns paperwork, compliance, policy, benefits enrolment and the overall checklist. The hiring manager owns role clarity, goals, the first assignments, introductions and the check-ins — this is the part most often dropped. IT owns equipment, accounts and system access, which must be ready before day one, not requested on it. A shared checklist with a named owner per task keeps the handoffs from falling through the cracks.
What are the most common onboarding mistakes?
- Drowning day one in paperwork. Front-load signatures into pre-boarding so day one can be about people, not forms.
- No manager plan. If the manager has nothing prepared, the new hire spends day one guessing. Agree the first-week plan in advance.
- Access not ready. Nothing says “we forgot you” like a laptop that won’t log in. Provision early and test it.
- No buddy. A peer to ask the “silly” questions shortens the awkward first weeks dramatically.
- No 30/60/90 check-ins. Onboarding that stops after week one misses the moment problems surface. Keep the check-ins on the calendar.
- Treating it as one-size-fits-all. A senior remote hire and a first-job junior need different things. Adapt the checklist to the role.
Start with one solid checklist, run it for your next few hires, and refine it from what they tell you. The goal is simple: on day one, every new person should feel expected and equipped — and know exactly what the first 90 days look like.
Frequently asked questions
When should onboarding start?
Before day one. Pre-boarding — sending paperwork for e-signature, ordering equipment and provisioning accounts — means the first day can be about welcome and work rather than admin.
How long should onboarding last?
Plan for at least 90 days. The first day and week matter most for the welcome, but the 30, 60 and 90-day check-ins are where retention and productivity are really won.
Who is responsible for onboarding?
It is shared. HR owns paperwork, compliance and the overall checklist; the hiring manager owns role clarity, goals and check-ins; and IT owns equipment and system access. Each task should have one named owner.
What is the biggest onboarding mistake?
Cramming everything into day one, especially paperwork, while leaving no manager plan and no later check-ins. Spread the work across phases and keep the 30, 60 and 90-day reviews.
FulcrumGrid HR Suite
Keep your onboarding in one place
FulcrumGrid HR Suite brings onboarding checklists, tasks, e-signatures and account provisioning together, so nothing slips through the cracks.