The Complete Employee Onboarding Checklist for 2027 

The laptop wasn’t ready. IT had the ticket, but no one flagged the start date, so a new analyst spent her first morning borrowing a spare and waiting on a password reset.

Small failure. It cost about three hours, and it cost the first impression, which you only get once. Almost every onboarding problem looks like this one. The process was fine. A single task had no owner.

Below is a single checklist, organized by phase, that you can work through today. Print it or screenshot it. Paste it into whatever your team already uses.

What is an employee onboarding checklist?

What is an employee onboarding checklist?

It’s a structured, step-by-step list of tasks running from paperwork and equipment setup through to the first-week check-ins. HR works from it alongside managers and IT so nothing gets missed when a new person joins, and so the experience stays consistent from one hire to the next.

Your checklist isn’t the same as an onboarding process. The process covers how you design the whole thing. Who owns what. Why each stage exists. Your checklist is the working document you actually tick through. If you want the design layer, our employee onboarding process post covers it. Otherwise, stay here.

Why a structured checklist matters

Ad hoc onboarding rarely fails dramatically. It fails by degrees, one forgotten task at a time, until a leaver mentions in their exit interview that they never got a proper introduction to the wider team.

Three reasons, and none of them is about tidiness.

Consistency comes first. Without a shared list, every manager onboards differently, and the quality of somebody’s first month depends on who they happened to report to. That’s a fairness problem before it becomes anything else.

Compliance is the second. Tax forms, policy acknowledgments, right-to-work documentation and equipment receipts all carry a paper trail somebody may ask for later. A checklist is how that trail gets built while it’s easy, rather than reconstructed under pressure.

Retention is the third, with the longest tail of the three. New hires form their view of an organization fast. SHRM’s guidance on measuring onboarding success recommends setting performance benchmarks per role and tracking time-to-productivity against them, which only works if the underlying process runs the same way each time. This document is what makes the process repeatable enough to measure.

The complete checklist, phase by phase

What should be included in a new hire onboarding checklist?

Four phases. Pre-boarding handles paperwork and equipment logistics, plus the workspace. Day 1 brings the tour and introductions, plus verifying access actually works. The first week is for goal-setting and stakeholder meetings. Then come the check-ins at 30 days, with further reviews at 60 and 90. Organize by phase, not by task type.

Screenshot this. Each phase expands into a full task table below.

A quick word on how to use the tables. Each one lists the task alongside its owner, plus roughly when it should be done. Swap the owners for your own job titles and the timings for your own notice periods. The structure holds; the labels are yours.

Print the four tables below, or paste them into whatever your team already uses. The point is that a manager can work through them without reading the surrounding prose twice.

Pre-boarding checklist: before Day 1

This phase does the most work and gets the least attention. Everything here happens while the new hire is still finishing somewhere else, which makes it the cheapest time you’ll ever have to get organized.

Table 1. Pre-boarding. Eleven tasks, three owners, all completed before anybody walks in.

Two of these tend to slip. Equipment ordering slips because nobody watches the lead time, and the welcome email slips because it’s the only creative task on the list. Our onboarding email templates handle the second problem if that’s where yours gets stuck.

Where teams automate this phase, they usually start with account provisioning and the reminder sequence, since both are pure chasing. A candidate portal that lets a new hire upload documents before their start date removes another chunk of it.

One practical note on ownership here. Split the phase between HR and IT explicitly, because the handoff between them is where equipment requests go quiet. HR knows the start date; IT knows the lead time. Neither knows both unless one of them writes it down.

Day 1 checklist

Keep this light. Day one should be about people, and most of the admin belongs either side of it.

Table 2. Day 1. The first line is the one that fails most often.

Lunch is on the list deliberately. It’s the cheapest item here and the one new hires mention years later, which makes it hard to justify cutting when the day gets busy.

First week checklist

Week one decides whether a new hire orients themselves or starts guessing.

Table 3. First week. Goals written down beat goals discussed.

Notice how little of this week belongs to HR. After the paperwork closes, onboarding becomes a manager activity, and programs that don’t make that handover explicit tend to stall around day four.

The buddy session earns its place here. A new hire will ask a colleague things they would never raise with their manager, which is exactly why the role exists.

First 90 days checklist

Summary level only here, since the detail belongs elsewhere.

Table 4. First 90 days. Book the six-month date while you’re already in the review.For role-specific goals across these three months, our 30-60-90 day onboarding plan breaks it down properly. And if you’re wondering why engagement dips right after this period ends, the 90-day onboarding cliff explains what happens next.

Checklist variations by situation

Three situations genuinely change the list. Everything outside them runs on the tables above.

Most teams over-engineer this part. They build a separate checklist for remote hires, then another one for engineers, and eventually a third covering internal moves. Within a year all three have drifted apart, and nobody trusts any of them.

Three situations change the list. Everything else stays as above, so only add what’s genuinely different.

Add-ons, not replacements.

The pattern holds across all three. Whatever a variation genuinely adds, add it. Anything it genuinely removes gets marked as skipped. Everything else stays on the core list, which is how one document stays current instead of three going stale.

What’s the difference between a pre-boarding checklist and a Day 1 checklist?

Pre-boarding covers everything finished before the person arrives. Paperwork gets collected. Equipment is ordered and access requested. The Day 1 list covers what happens once they’re present, physically or virtually. That means the tour and the introductions, plus verifying that everything you provisioned in pre-boarding actually works.

How do you onboard a new employee remotely?

Ship equipment early with tracked delivery. Run every Day 1 touchpoint over video against a fixed schedule. Over-communicate the expectations an in-office hire would absorb by osmosis. And assign a buddy whose specific job is informal context.

Notice how short each variation is. That’s deliberate. A variation that runs longer than five lines usually signals that someone has started rebuilding the core list.

IT-heavy roles

Add environment and repository access, on-call rota assignment, and security training that completes before any system access is granted. Nothing gets removed. These sit on top of the core list.

Internal transfers and promotions

Skip company orientation and the handbook. Payroll setup stays as it is. Add new team introductions, revised goals for the new role, and access changes running in both directions. People forget the removal half.

Internal transfers get skipped more than any other variation. The person already works here, so nobody triggers a process, and they end up learning a new role with less support than an external hire would get.

Five mistakes that undo good planning

Each of these turns up inside processes that a team genuinely designed with care, which is what makes them worth naming.

Table 5. Five failure modes. Four of the five fixes cost nothing but a decision.

The second one causes the most damage per occurrence. A task assigned to Priya gets done. The same task assigned to the HR team sits there. If you want the underlying framework behind why these five matter, the 5 C’s of onboarding covers it.

Keeping the checklist from falling apart as you scale

Every HR team eventually hits the point where a document that worked fine stops working. It usually arrives with hiring volume rather than headcount.

A shared spreadsheet works fine at one hire a month. At four or five it stops working, and it stops quietly.

Nobody notices the moment it breaks, which is the difficult part. You find out when a new hire mentions in their day 30 review that they never got the handbook.

Version control goes first. Somebody copies the tab for a new starter, edits it, and now two versions exist with no way to tell which is current. Then the chasing gets worse. HR spends its week asking IT whether the account was created and asking the manager whether the check-in happened, because a spreadsheet can’t tell anybody what’s overdue.

The manager side degrades too. A manager running three onboardings at once has no way to see which one is behind, so the quiet new hire gets less attention than the one who asks questions. That’s rarely intentional and always noticed.

What fixes it is unglamorous. Assign tasks automatically by role. Send reminders without anyone writing them. Give the manager a view of what’s outstanding across their team, and keep documents in one place with proper access controls.

None of that requires changing how your team works day to day. The checklist stays the same document; what changes is that it chases people instead of waiting for them.

Manager dashboards matter more than the automation does. Automation stops tasks being forgotten; visibility is what lets a manager fix a stalled onboarding while it still matters.

Frequently asked questions

A checklist is only as good as its owners

Two organizations can run the same list and get different results. The difference is whether each line has a name against it.

Consistency is what this document buys you. Every new hire gets the same start, every manager works from the same list, and the parts that carry compliance weight get done while they’re still easy. None of that requires a longer checklist than the one above. It requires a name against each line and a habit of checking at day 90, not day one.