How to build an employee onboarding checklist

Most onboarding checklists are a list of admin tasks.

IT setup. Payroll forms. Compliance training. Badge photo. Those things need to happen, but they are not what makes onboarding work. Completing them does not tell you whether the new employee feels oriented, connected, or clear on what is expected of them.

A good onboarding checklist is not a list of tasks to clear. It is a map of the first 90 days, a structure that ensures the new hire gets the right things at the right time, and that nothing important falls through the gap between HR, IT, and the hiring manager.

The checklist below is structured in four phases. Each phase has a clear purpose. The items are starting points, you will need to adapt them to your context.

Phase 1: Before day one

The goal of this phase is to eliminate the unknown. A new employee who arrives on their first day without context, access, or any sense of what to expect is already starting from a deficit. Most of what goes in this phase is pre-boarding, it happens before the first working day.

Send a structured welcome with practical details (start time, location or remote setup, who to ask for on arrival)
Set up accounts and system access before day one, not on day one
Assign an onboarding buddy or point of contact for the first week
Share the company handbook or relevant documentation
Send the first-week schedule so the employee knows what to expect
Complete any admin that can be done in advance (contract, payroll, equipment request)
Introduce the manager and buddy via email before the start date

Phase 2: Day one

The goal of day one is orientation, not information transfer. Keep it light. The employee is absorbing a lot, a new environment, new faces, new rhythms. Day one is about helping them feel welcome and giving them a clear picture of the week ahead.

Greet the employee at the start of the day, do not leave them to figure out where to sit
Walk through the space or the remote setup (tools, channels, how things work)
Introduce the immediate team, not the whole company, just the people they will work with directly
Share a clear agenda for the rest of the week
Confirm all system access is working
Have lunch with the team or schedule an informal video call
End the day with a brief check-in: how did today feel, what questions do you have?

Phase 3: The first week

By the end of week one, the employee should have done something real. Not necessarily something consequential, but something that is actually part of the job. The first week that consists entirely of watching, reading, and listening leaves new hires wondering when they are going to start contributing.

Run role-specific process walkthroughs with key team members
Assign a small, low-stakes first task that lets the employee produce something
Shadow the manager or a teammate in a relevant meeting or workflow
Set up introductory calls with key stakeholders across the organisation
Share documentation relevant to the role (processes, tools, decisions)
Clarify 30-60-90 day expectations, what does success look like in each window?
End the week with a check-in: what is going well, what is confusing, what do they need?

Phase 4: The first month

The first month is where the employee builds independence. They should be taking on work, forming relationships, and starting to understand how the organisation actually works, not just how it describes itself. Your role shifts from guide to support.

The employee takes on independent work, something they own end to end
Weekly 1:1 with the manager, focused on questions, blockers, and calibration
Formal mid-month check-in to confirm 30-day expectations are being met
Set career goals together, what does the employee want to develop in the next quarter?
Introduce the wider organisation: other teams, how decisions get made, who to know
Collect feedback from the employee on the onboarding experience itself
End of month: formal 30-day review conversation

How to use this checklist

A checklist is only as useful as the process behind it. A few things that determine whether it actually works:

Assign every item to an owner. If the checklist has tasks without names attached, they will be missed. HR owns some things, the hiring manager owns others, IT owns others. Make it clear.
Track completion visibly. The new employee should be able to see their own progress. A shared checklist removes ambiguity about what has happened and what comes next.
Customise by role.A developer's first week looks different from a sales hire's. Build a base checklist and adapt it.
Ask the employee how it is going. The most useful signal about whether your onboarding works comes from the people going through it. Ask directly, and actually use the answers.

Frequently asked questions

What should be on an employee onboarding checklist?

An onboarding checklist should cover four phases: pre-boarding (before day one), the first day, the first week, and the first month. Each phase has specific tasks related to admin, access, role knowledge, and relationship-building. The checklist should have an owner for each item, not just a list of things that need to happen.

How long does onboarding take?

For most roles, structured onboarding runs for 90 days. The first week covers orientation and setup. The first month focuses on learning and early contributions. The second and third months build toward independent performance. After 90 days, most employees should be operating without significant hand-holding.

Who should own the onboarding checklist?

There should be one clear overall owner, typically HR or the hiring manager. The checklist itself involves multiple people (IT, the manager, a buddy), but without a single person responsible for the overall process, tasks fall through the gaps and the experience becomes inconsistent between hires.