The Ultimate Employee Onboarding Checklist for Small Teams

Everyone has a first-day horror story: the laptop that never got ordered, the manager who turned out to be on holiday, the new hire who spent day one reading a wiki because nobody could say whose job it was to do anything else. The people involved almost always cared. The problem is the shape of the work. Onboarding runs occasionally, it's owned by several people, and every deadline hangs off a start date that changes with each hire. That's a hard combination to run from memory.

So don't. Run it from a checklist, copied from a template, with an owner and a due date on every line. The useful questions are what goes on it, who each line belongs to, and how much of it should run without you. Let's take those in order.

What to include, phase by phase

Before day one. The goal is simple: on the morning they arrive, nothing is missing.

• Contract signed and filed; payroll, tax and personal details collected
• Laptop ordered, accounts provisioned: email, SSO, the core tools
• Access requested for the systems their role needs (and only those)
• Team told who's coming, when, and what they'll be doing
• A first-week schedule drafted, so day one has a shape

Day one. By the evening, they should be able to say what the company does, what their team does, and what they'll do.

• Their manager meets them at the door, physical or virtual. The first thirty minutes belong to the manager, not to IT setup.
• A tour of the tools: where work is tracked, where people talk, where documents live
• Only the paperwork that genuinely must happen on day one: security basics, workplace essentials
• A first small, real task. Nothing says "you work here now" like shipping something in the first week.

Week one. This week is about context and connections.

• Introductions with the people they'll actually work with, booked as calendar entries rather than good intentions
• A buddy who isn't their manager, for the questions people don't ask managers
• Policies to read and acknowledge (handbook, code of conduct, security policy), with a record of who confirmed what. Here's how to run that properly.
• An expectations conversation: what good looks like in the first month

The first 90 days. The goal here is that nobody is surprised at the probation review.

• Regular check-ins, booked ahead of time rather than promised in passing
• A 30- or 60-day review of how things are going, in both directions
• The probation review itself, created when the person starts and due when it's due, so it can't be forgotten ten weeks later

The three mistakes that kill checklists

Everything is assigned to HR. An onboarding checklist has at least four legitimate owners: the new hire ("complete your profile", "read the handbook"), their manager ("expectations conversation"), HR or an admin ("payroll details"), and named individuals. "Order the laptop" belongs to whoever actually orders laptops: a person, not a department. A checklist where every line says "HR" is really a to-do list for one overworked coordinator, and it will silently stop being followed.

No dates, or absolute ones. "Order laptop" with no date is a wish. Write it as an offset from the start date instead: laptop at start − 7 days, manager meeting on day 0, probation review on day 80. Offsets make the template reusable for every hire, whenever they join.

One template for everyone. An engineering hire and a sales hire share maybe half a checklist. Keep a common core plus per-role templates, and treat them as living documents. One thing to demand from any tool here: editing a template must never change checklists already in flight. A running checklist is a record of what was asked of a real person.

What should run without you

This is where a tool earns its keep, because everything below can and should happen without a human remembering.

• Start on hire, automatically. The checklist should exist the moment the employee record does (or the moment they accept their invite), items assigned, due dates computed from the start date. And if there's no template yet? Hiring goes ahead anyway. Automation should never block the thing it supports.
• Date triggers for the follow-ups. A probation review that starts itself at start + 80 days. An annual security training that fires every year on the hire anniversary, skipping anyone who already completed this year's.
• Event triggers for the exceptions. A parental-leave handover that starts itself when an approved leave is 30 days or longer. These are the processes nobody remembers, because they only come up a couple of times a year.
• Nudges with a cap. Overdue items should remind their assignee at most once a day, and stop after seven reminders, so an abandoned checklist goes quiet instead of nagging forever. Reminders that never stop teach people to filter them.
• Handover on departure. When someone leaves, every open item assigned to them on other people's checklists should move to their manager or an admin automatically. A checklist quietly waiting on a departed employee is how "order the laptop" fails for the next hire.

Where this lives in SquadBear

Checklists live under People → Checklists. Templates hold the reusable shape, up to 50 items each, and every item names its owner: the person themselves, their manager, an admin, or a pinned named person, with a fallback to an active admin if that person ever leaves. Due dates are offsets from an anchor day, and editing a template never touches checklists already running from it.

The built-in Onboarding template starts itself when a hire is created or accepts an invite, and Offboarding starts when someone is offboarded. Custom templates can start manually, on an event (with conditions like leave type and minimum duration), a set number of days after the start date, or yearly on the start-date anniversary. Triggers only ever add a checklist, so a misconfigured template can't block a hire or a leave approval. Starting a checklist for a whole team fans out to one per member, skipping anyone who already has that template running.

Everyone sees their open items on the My Tasks dashboard card, and the Templates tab includes a gallery of suggested templates (probation review, parental-leave handover, annual security training, equipment return) that arrive with working triggers in one click. Your AI assistant can drive all of it:

"Start the engineering onboarding checklist for Aleksandra with a March 1 anchor, and show me everything assigned to me before her first day."

Steal this starting template

Ten lines, four owners, all offsets. Trim it to your reality:

Start free and the onboarding template fires for your very next hire, or ask the demo to show you a checklist mid-run.

Related reading: policy acknowledgments, the week-one line item that deserves its own audit trail.