Employee Onboarding Checklist: Owners for the First 90 Days

Key takeaways

• Every onboarding task needs one named owner: HR, IT, the manager, or a buddy, so nothing stalls between departments.
• Structure the checklist in four phases: pre-boarding, day one, and 30/60/90-day milestones with defined deliverables.
• Pre-boarding failures are the most common: ship hardware at least three business days before the start date.
• Day one has one goal: the new hire ships something small and real before going home.
• Start the template in a spreadsheet and move to a task tool only when hiring more than a few people per quarter.

An employee onboarding checklist assigns every task in a new hire's first 90 days to a named owner (HR, IT, manager, or buddy) and a phase: pre-boarding, day one, then 30/60/90-day milestones. Below is a full template structure you can copy into your own tooling, built so nothing sits unowned and no one finds out a laptop wasn't ordered until the hire's first morning.

What should an employee onboarding checklist actually cover?

An employee onboarding checklist is a single list of every task needed to take a new hire from signed offer to productive team member, with each task assigned to a named owner: HR, IT, the hiring manager, or a buddy. It covers four phases: pre-boarding (contracts, equipment, accounts), day one, and 30/60/90-day goals.

HR practitioners broadly agree that onboarding should extend well past the first week and focus on building relationships and role clarity, not just paperwork. That is why a good checklist includes 90-day check-ins and defined success milestones, not just laptop setup.

Without named owners, tasks stall between departments and the new hire feels it. The sections below break the checklist into phases you can copy into your own tooling, or run in a platform like Task22 (see pricing).

Why does ownership matter more than the list itself?

A checklist with no named owner is a wish list. When every task carries one accountable person, you get a single source of truth for onboarding: you can see what is done, what is stuck, and who to ask, without chasing three people to find out who dropped the ball.

The four owners: HR, IT, manager, buddy

Split every task across four roles. HR owns contracts, payroll, and compliance paperwork. IT owns accounts, hardware, and access provisioning. The manager owns the 30/60/90-day plan, priorities, and feedback. The buddy owns the informal layer: where things live, who to ask, how decisions actually get made. One task, one owner, always.

What happens when nobody owns a task

Unowned tasks are where onboarding quietly fails. "Set up Slack access" sits in limbo because HR assumed IT did it and IT assumed HR did it, and the new hire spends day one idle. That is the same fragmented-tools problem you already feel in project work: conversations in one place, tasks in another, no accountability anywhere. Assign the owner in the checklist itself, not in someone's head.

What happens before day one: the pre-boarding checklist

Most onboarding failures happen before the new hire logs in. Workplace research consistently finds that only a small minority of employees rate their onboarding as excellent, and a poor start correlates with lower engagement and higher early attrition. Pre-boarding is where you fix that, by assigning each task to a named owner.

HR tasks before day one

HR sends the offer confirmation and welcome email, collects signed contracts and tax forms, and adds the hire to payroll. They also assign the buddy and confirm the 30/60/90 plan exists in writing.

IT and device tasks before day one

IT orders the laptop, creates accounts and email, and sets up access to the tools the role actually uses. Ship hardware at least three business days early so it arrives, not "arrives."

Manager tasks before day one

The manager writes the first-week schedule, books introductions, and defines the first deliverable. One table, three owners:

| Owner | Task | Deadline | | :--- | :--- | :--- | | HR | Contract signed, payroll set, buddy assigned | 5 days before start | | IT | Device shipped, accounts and tool access ready | 3 days before start | | Manager | Week-one schedule, intro meetings, first deliverable | 2 days before start |

If any row slips, the start date slips.

What should happen on day one?

Day one has one goal: the new hire ships something small and real before they go home. Everything else is setup.

• IT (before 9am): laptop issued, accounts created, password manager enrolled, access to the three tools the role actually uses. No "we'll get to the rest."
• Manager (morning): 30-minute kickoff covering the first 90 days at a glance, then hand over the day-one task list so the hire plans their own time instead of reacting to it.
• Buddy (lunch): eating together, plus a walkthrough of where conversations, decisions, and tasks live. Context that lives in three places disappears fast.
• HR (afternoon): payroll, benefits, and policy sign-offs completed in one sitting.
• New hire (end of day): one small deliverable shipped, and a two-line note to the manager on what was unclear. That note is your checklist's first bug report.

What does the 30/60/90-day onboarding plan look like?

30 days: context and first wins

The manager owns this phase: introduce the new hire to every team they'll depend on, assign two or three small deliverables with clear deadlines, and confirm tool access is complete. The buddy checks in weekly. HR schedules a benefits and payroll confirmation before day 30 closes.

60 days: ownership and dependencies

At 60 days the new hire takes real ownership of a workstream, not just tasks. The manager maps which colleagues and approvals that workstream depends on, so nothing stalls waiting on a name nobody introduced. HR runs a mid-point check-in on the role's expectations.

90 days: full accountability

By 90 days the hire owns outcomes, reports on them, and flags scope changes themselves. The manager and HR close out probation with a documented review, and the checklist template gets updated with whatever this hire's first quarter exposed.

The reason the phases matter is that most onboarding failures are planning failures, not effort failures. One ops lead described the pattern plainly: "I do find myself getting projects mixed up and would like to find a better way to Plan my projects as opposed to React to them" (r/projectmanagement). A 30/60/90 plan is the antidote: each phase has a named owner, a deliverable, and a review point, so you plan the ramp instead of improvising it. The 30-day phase buys context, the 60-day phase transfers ownership of one workstream with its dependencies mapped, and the 90-day phase makes the hire accountable for outcomes and scope decisions. If a hire stalls, the plan tells you which phase broke, which is far more useful than a vague sense that onboarding "isn't clicking."

How do you turn this into a reusable template?

Build the template once, with owners and phases baked in, so every new hire runs the same checklist without you rebuilding it each time. Structure it as columns: task, phase (pre-boarding, day one, 30/60/90), owner role, and done-when criteria. The owner is a role, not a person, so the template survives staff changes.

Spreadsheet vs task tool: the tradeoffs

A spreadsheet is free, familiar, and fine for your first few hires. It breaks down when two people need to check off tasks at the same time, or when you want due dates that alert the owner. A task tool handles those, but adds setup overhead, the exact problem ops leads describe when managing the software takes longer than the work. Start in a spreadsheet; move to a task tool when you hire more than a few people per quarter.

Excel template structure that survives growth

Use one row per task, one sheet per phase, and a summary tab that counts incomplete tasks by owner. Freeze the header row, add data validation on the owner column, and keep task descriptions under one line. If a task needs more detail than that, it belongs in a linked doc, not the template.

Which tool should hold your onboarding checklist?

Criteria: owners, phases, visibility

Any tool you pick must do three things: assign every task a named owner (HR, IT, manager, buddy), support phase-based templates that match pre-boarding, day one, and 30/60/90, and give you one portfolio view across every hire in flight. If a tool fails any of the three, your checklist fragments again and you're back to managing the software instead of the work.

How Task22 fits, and where it falls short

Task22 handles owners and phases natively: each checklist item carries an assignee and a due date tied to the hire's start date, so a 90-day template duplicates cleanly per new employee. The honest gap: Task22 has no built-in federal form tracking, so your HR owner still files the I-9 and W-4 separately per USCIS requirements and links them as a completed task. If you need deep dependency mapping across hires, that's thinner here than in the tools below.

ClickUp, Asana, monday.com, Wrike, Trello at a glance

ClickUp, Asana, monday.com, Wrike, and Trello all support owner-assigned, phase-structured onboarding templates. The differentiator is overhead: Trello is fastest to set up but weakest on cross-hire reporting; Wrike and ClickUp are strongest on visibility but heaviest to configure. Pick the lightest one that still gives you the single view.

What about offboarding?

An onboarding checklist assigns work to bring someone up to speed; an offboarding checklist assigns work to close them down cleanly. The logic is the same: every task has a named owner and a deadline. The difference is that offboarding runs on a countdown, usually the notice period, so sequencing matters more.

The offboarding mirror checklist

Run the same four-owner structure in reverse. HR owns the resignation acknowledgment, final pay, and benefits termination. IT owns device return, credential revocation, and access removal, ideally on the last day, not the week after. The manager owns knowledge transfer and a handover document. The buddy or a peer owns reassigning open tasks and dependencies so nothing sits unowned.

Two tasks deserve extra care at a 20-50 person company: revoking access to shared finance tools and expense cards, and documenting which recurring approvals the departing person held. Miss either and you find out through an incident.

Offboarding is also where a single source of truth pays off. If onboarding, devices, and approvals live in one system, the departure checklist writes itself from the same record.

FAQ

How long should a new employee onboarding checklist be?

Long enough to cover pre-boarding, day one, and 30/60/90-day milestones, which typically lands around 40 to 60 tasks for a small company. If it exceeds that, split detailed instructions into linked docs and keep one line per task. Under 20 tasks usually means you're missing the 60-day ownership handover or pre-boarding device work.

Who should own the onboarding checklist at a small company without an HR team?

Give it to the hiring manager, with the same four-role split compressed into fewer people. The manager absorbs HR duties like contracts and payroll setup, IT duties fall to whoever handles accounts, and a peer takes the buddy role. The rule still holds: one task, one named owner, even if that owner wears three hats.

Can I use one employee onboarding checklist template for every role?

Yes, for roughly 80% of it. Contracts, accounts, payroll, buddy assignment, and the 30/60/90 structure are identical across roles. What changes is the tool access list and the first deliverable, so keep those as a short role-specific addendum rather than duplicating the whole template. Update the shared template each time a hire exposes a gap.

How do I track onboarding tasks without adding another tool to manage?

Start with a spreadsheet: one row per task, columns for phase, owner role, and done-when criteria, plus a summary count of incomplete tasks by owner. That handles your first several hires. Move to a task tool only when you're hiring more than a few people per quarter or two owners need to check off tasks simultaneously.