What belongs in an onboarding checklist
The top onboarding checklist templates agree on the phases: before day one, day one, the first week, the first month, and the stretch to 90 days. They mostly stop at headings. An onboarding checklist template is useful only when each item is concrete enough to be ticked by a specific person on a specific day.
- Before day one. Paperwork, equipment, access, a welcome message that says exactly when and where to show up, and a buddy. This is where most first-day problems are created.
- Day one. Forms, a working laptop or a uniform, a first conversation with the manager about what good looks like in 30 days, and lunch with someone who is not the manager.
- The first week. Required training, introductions to the handful of people they will depend on, and one small piece of real work finished end to end.
- The first 30 days. Weekly check-ins and a 30-day conversation about what is unclear.
- Days 31 to 90. A first real responsibility and a review.
- Done when. The line that ends onboarding.
- Open issues. One place for whatever is blocked.
Give every item an owner and a date
Onboarding fails at the handoffs between HR, IT and the manager. Each assumes the other ordered the laptop. The fix is boring and works: every line gets one person's name and a due date, worked back from the start date. "IT to provision access" becomes "Dev access requested (@Claire) by Nov 4". When a date passes, the owner is obvious and so is the conversation.
Work backwards from the start date for the before-day-one section. Equipment that ships needs a week. Security approvals can take five working days. A welcome email sent the evening before reads like an afterthought.
Define when onboarding is done
None of the top-ranking checklists says when onboarding ends. Without an end, it fades: the check-ins stop, nobody asks for feedback, and three months later the new hire is still unsure what is expected of them.
Write the Done when section before the person starts. It should be a measurable sign of independence for this role: a solo shift on a busy night, a change shipped to production, a first deal closed, a time-off request approved without asking anyone. Tell the new hire what it is on day one. When it is true, the manager signs it off, HR collects feedback, and onboarding is over. Ongoing goals move to a 30-60-90 day plan or the regular one on one.
Remote and hybrid hires
A remote new hire cannot pick up context by overhearing it, so the checklist has to do more of the work. Ship equipment so it arrives two working days early. Write both time zones in the header and book every first-week meeting inside the new hire's working hours. Choose a buddy whose day overlaps theirs. For US hires, arrange the I-9 document check in advance, since it cannot wait until they visit an office.
Common mistakes
- Owners that are departments. "HR" never does anything. A named person does.
- A first week of slides. People learn the job by doing a small piece of it. Put a real task in week one.
- One checklist for every role. Keep a shared company section and write the rest per role.
- Forgetting internal moves. A promotion into management changes access, peers and the shape of the week. It deserves its own checklist, as the fourth example shows.
- Granting access with no end date. Contractors and temporary staff need the removal written down when the access is granted.
When to use a different template
For the new hire's own goals over the first three months, use a 30-60-90 day plan. When the person whose work the new hire is taking over is leaving or moving, ask them for a handoff document before their last day. And if the same onboarding steps repeat for every hire, the company-wide part is worth turning into an SOP.
An onboarding checklist that reminds people instead of waiting to be reread
Save this checklist as a template in Scribelet, give every line an owner and a due date, and let open items appear in each person's task list until they are done. Encrypted, free to start.
Free plan, no credit card. See pricing