“Free Employee Onboarding Checklist Template (Fillable + Example)”

What should an onboarding checklist template include?

Five phases, and the first one starts before the contract is signed. The table below is the skeleton; the detail follows.

The phase names matter less than the boundaries. Each one should end with something produced: a signed contract, a working login, a shipped task, a written 30-day review.

The pre-boarding section

This is where the first impression is decided, and it is the section most templates skip.

• Signed contract, tax forms and right-to-work documents returned
• Background check completed, if applicable
• Payroll record created and bank details confirmed
• Laptop ordered, configured, and tested with the right image
• Phone, headset, monitor and any role-specific hardware allocated
• Company email, SSO account and password manager invitation sent
• Access to the tools the role needs on day one — not day five
• Seat assigned, and the team told the start date and the person’s name
• Onboarding buddy assigned and briefed for 30 minutes
• First-week calendar populated, including the first 1:1
• Welcome message sent two working days before the start date

Two of those items are quietly decisive. Equipment ordered late is visible and forgivable; access missing on day one is invisible and corrosive, because it teaches the new hire that the company does not plan. And a buddy who has not been briefed is worse than no buddy, because the new hire spends a week not asking questions to avoid bothering someone who clearly was not told.

The day-one section

Day one should be short, human, and end with one real task.

• Welcome from the manager, 15 minutes, in person or on video
• Office or remote workspace tour, including where to find things
• Team introductions with one sentence on what each person does
• Access verification: email, chat, drive, project tool, HR portal
• Security and data-handling briefing, signed
• First-week schedule walkthrough, so nobody wonders what happens next
• Lunch or coffee with the buddy
• One small, real task finished before the end of the day

That last item is the most underrated line in any onboarding checklist template. A new hire who completes something on day one — even a documentation fix — arrives on day two as a participant rather than a visitor.

The week-one section

• Tool training: project management, documentation, communication, and the two systems specific to the role
• Business context: how the company makes money, who the customers are, what this quarter’s priority is
• Role clarity: what success looks like at 30, 60 and 90 days, written down
• Shadowing: two meetings observed, one customer call or site visit
• First deliverable assigned, with a review
• Daily check-in, 10 minutes, for the first five days only
• Introduction to the two people outside the team they will work with most
• Buddy check-in at the end of the week, with one question: “what was confusing?”

The month-one and 90-day sections

• 30-day review: what is working, what is not, what the manager will change
• Access review: remove what is not needed, add what was missing
• First independent piece of work delivered and reviewed
• 60-day goals agreed and written down
• 90-day review against the goals set in week one
• Onboarding feedback session: what should the checklist say next time
• Checklist updated within a week of that session, by the person who owns it

How do you fill the template so it actually gets used?

A checklist that lives in a document nobody opens is a compliance artefact. Four rules keep it alive.

One owner per line. Not “HR and IT”. A single name, with a backup. Shared ownership is how laptops arrive on Wednesday.

Dates relative to the start date. “Day −5” and “Day 3” survive a start-date change; “12 March” does not.

A proof column. For equipment, it is the asset tag. For access, a screenshot or a green tick in the tool. For a deliverable, the link. Proof turns a checklist into a record.

A hard stop on ambiguous items. “Get to know the team” cannot be completed. “Meet 1:1 with six team members, names listed” can.

Here is the fillable structure, one row at a time:

Copy that table into a spreadsheet, a project tool, or a document with checkboxes, and you have a working template in ten minutes. The format matters far less than the three columns.

What does a worked example look like?

Here is a real-shaped example: a Customer Success Manager starting at a 60-person software company, reporting to the Head of Customer Success.

Pre-boarding (days −10 to −1). HR sends the contract on day −10 and the welcome pack on day −8. IT orders a laptop on day −9 because the lead time is five working days, and configures it on day −3. The hiring manager assigns Priya as buddy on day −7 and books 30 minutes to brief her. Access to the support tool, the CRM, the shared drive and the project workspace is requested on day −4, a full week before the start.

Day one. Welcome at 9:00, team intro at 9:30, access verification at 10:00. The first real task: read the last five customer health reviews and write three observations by 16:00. The manager reviews them the same afternoon. Total manager time: 70 minutes.

Week one. Two product sessions, one shadowed customer call, one ride-along with an account manager. The first deliverable is a rewritten welcome email template, reviewed by Priya on day four. Daily 10-minute check-ins, ending Friday.

Month one. By day 30 the new hire owns eight accounts, has run three QBRs with support, and has a written 30-day review. The review produces one change to the checklist: the CRM training was scheduled for week two but was needed on day two, so it moves forward.

What it cost. Around 22 hours of colleague time in the first two weeks, plus 6 hours of manager time, plus the HR and IT tasks. That is roughly 30 hours, or about $1,650 at a $55 loaded rate — before counting the new hire’s own ramp.

What it saved. The week-two CRM training was wasting about 90 minutes per hire and one confused customer conversation. Small, specific, and exactly what a review is for.

How long should onboarding take?

Longer than most companies plan for, and the benchmarks converge on a number that surprises managers.

The pattern is consistent: a competent hire in a familiar sector needs three to four months to perform like a peer. Someone switching sectors needs roughly double. A new graduate can take most of a year.

That has a planning consequence. A 90-day onboarding checklist is not generous, it is roughly the minimum window in which the investment pays back. And a company that measures onboarding by whether the paperwork was filed is measuring the wrong week.

How do you calculate what better onboarding is worth?

Three numbers, all reproducible with your own inputs.

First, the ramp cost. Take a $75,000 salary, loaded at 1.3× for benefits and overhead, which is $97,500, or about $375 per working day. If structured onboarding shortens ramp by 20 working days, that is 20 × $375 = $7,500 of recovered output per hire. Ten hires a year: $75,000.

Second, the colleague drag. A new hire absorbs somewhere around 100 hours of colleagues’ time in the first months, based on European survey estimates. At a $55 loaded rate that is $5,500 per hire. A checklist does not remove the hours, but it moves them from repeated interruptions to scheduled sessions, which is where the same hours buy more.

Third, the retention effect. Brandon Hall Group’s best-in-class comparison puts first-year retention at 91% for structured onboarding against 30% at the worst-performing organisations, with an 82% improvement in retention overall. Use the direction, not the decimal. If your first-year attrition is 20% and a proper process cuts it to 15%, you avoid one exit in twenty hires — and SHRM’s replacement-cost research puts an exit at 50–200% of salary.

Put together on a 60-person company hiring 12 people a year: $90,000 of recovered ramp output, $66,000 of colleague time spent more deliberately, and one avoided exit worth perhaps $50,000. The checklist itself costs the hours of writing it, which is a day.

What are the most common onboarding mistakes?

Starting the checklist on day one. By then, the two things that ruin the week — missing equipment and missing access — are already decided.

Confusing orientation with onboarding. A day of presentations is orientation. Onboarding is the 90-day path from visitor to contributor, and it needs owners and dates.

Assigning a buddy without time. An unbriefed buddy answers questions resentfully. A briefed buddy with two booked hours answers them well.

Writing goals in week one and never reading them again. The 30-day review exists to catch a mismatch while it is still cheap to fix.

Never revising the template. Every hire generates three corrections. A checklist that is not edited after each hire is a document about the company as it was two years ago.

Measuring nothing. Time-to-first-deliverable and 90-day retention are two numbers any company can track from day one, and they tell you more than a satisfaction survey.

Does the checklist need to be different for remote hires?

Yes, in three places. Pre-boarding becomes heavier, because equipment ships rather than gets collected, and lead times are longer. Day one needs an explicit social block — a video call with the team is not the same as sitting nearby, and remote hires report isolation fastest in weeks two and three. And the buddy role becomes a scheduled 15 minutes twice a week for the first month, not an open invitation to ask.

Add four lines for remote hires: shipping confirmation with tracking, a home-office stipend decision, a recorded walkthrough of the two most-used tools, and a named person for IT questions in the first week.

Where does Doitify fit?

Doitify is our product, so this is disclosure. Onboarding is a project with a fixed start date, a set of owners and 30-odd tasks that repeat every time — which is exactly the shape a project management tool handles well. You can keep the template as a project template, generate a copy per hire, assign each item to an owner with a due date, and track completion in a board or a checklist inside each task.

The parts that genuinely help: templates that clone per hire, checklists that live inside a task rather than in a separate document, workload views so the buddy’s hours are visible before they are promised, and import so an existing spreadsheet template comes across rather than being retyped. Doitify Copilot can turn a role description into a first draft of the 30-60-90 section, which is a reasonable starting point and a poor substitute for a manager’s judgement.

It is not necessary for a company hiring three people a year — a document and a calendar reminder will do. It becomes useful when onboarding competes with delivery work for the same people’s attention, which is the point at which a checklist in a shared doc starts to slip.

Conclusion

An onboarding checklist template is not paperwork. It is the difference between a new hire who spends week one guessing and one who spends it producing. The template above covers five phases, roughly 35 items across a full 90 days, and one rule that makes all of it work: every line has an owner, a date, and a proof.

Copy it, cut a third of it, assign the rest, and review it with your next hire in their fourth week. The version you have after three hires will be worth more than any template you download, including this one.

If this post on onboarding checklist template was helpful, you might also enjoy What Is the Critical Path in Project Management? and Task Management vs Project Management.