New hire onboarding checklist scattered? Build one trackable list

Short answer: onboarding goes wrong when steps live in many places and no one can see what is done. Build one master checklist, give every step an owner and a due date relative to the start date, and create a copy for each new hire. Then one person can open one view and see what is open.

At a glance

Swipe sideways to see all columns.

Item	Number	What it means for you
Items one view can process	5,000 items	Each hire adds a row per step. Archive finished hires so views stay fast.
Recommended unique permissions	5,000 per list	Limit who sees the list by group, not by item, to stay under this.
File on a list item	250 MB	Enough for a signed form or a handbook PDF on a step.
Flow with no trigger activity	90 days	A flow that never runs in 90 days might be turned off. Hiring gaps count.
Flow run length	30 days	A flow waiting on an approval times out after 30 days.

Why scattered onboarding fails

A new hire needs many things: a laptop, accounts, access, a desk, payroll forms, a manager meeting, training and introductions. Each step belongs to a different person. HR does the forms. IT does the laptop. The manager does the first-week plan.

When each person keeps their own notes, three things happen:

A step is missed because everyone thinks someone else did it.
The new hire arrives and the laptop is not ready.
Nobody can answer "where are we on this person?" without asking four people.

The cost is mostly time and a poor first week. A new hire who waits for access has little to do and may form a weak first view of the team.

Signs your checklist is scattered

The list is in an email thread that is forwarded each time.
HR has one document, IT has another, the manager has a third.
Each new hire gets a slightly different set of steps.
You find out access was missing on day one.
Someone rebuilds the checklist from memory every time.

Step 1. List every step once

Gather HR, IT, facilities and a few managers for a short session. Walk through the last new hire from the offer to the end of the first month. Write down every step, even small ones, such as "order a badge" and "add to the team chat."

Group the steps into stages:

Before day one (offer accepted to the day before start)
Day one
First week
First 30 days

Step 2. Give each step an owner role

Use a role and not a person's name: HR, IT, Hiring Manager, Facilities, Buddy. Roles stay valid when people change jobs. Then name the person for each role in a small lookup.

Each step needs one owner. If two roles share a step, split it into two steps.

Step 3. Set due dates relative to the start date

Do not write real dates in the master list. Write offsets, for example:

Order laptop: 14 days before start.
Create accounts: 5 days before start.
Welcome message from manager: 2 days before start.
Setup meeting: day 1.
Review of first week: day 5.

When a person is hired, the tracker works out the real date from their start date. This is what makes the checklist reusable.

Step 4. Put it in one tracker

A SharePoint list handles this well. Use two lists:

A template list: one row per standard step, with owner role and offset in days.
A tracker list: one row per step per new hire, with the real due date, owner, status and notes.

When you add a hire, create their rows from the template. A Power Automate flow can do this for you. If you do not want automation yet, copy the rows by hand and check them once.

Columns for the tracker list:

New hire
Step
Stage
Owner
Due date
Status (Not started, In progress, Done, Blocked)
Notes

Step 5. Build views people actually use

Make three saved views:

By new hire: all steps for one person. HR and the manager use this.
By owner: all open steps for me. IT and facilities use this.
Late or blocked: anything past due or stuck.

Color late items red with column formatting so they stand out.

Step 6. Send reminders to owners

A daily flow can find steps due in the next few days and message each owner with one summary. This stops the "I forgot" problem. See "Late tasks nobody notices: setting up late alerts" for the setup. Keep it to one message per person per day.

Step 7. Check in with the new hire

At the end of week one and the end of month one, ask the new hire what was missing or confusing. Add those items to the template. The checklist gets better with every hire.

Keep private data out of the list

A checklist needs task names and dates, not sensitive details. Do not put salary, ID numbers, health information or bank details in the tracker. Link to the secure HR system for those. Limit who can see the list to people who need it.

Honest limits

A tracker shows what is done. It does not do the steps. If IT is short on staff, the laptop will still be late, but now you will see it a week ahead and not on day one. Templates also need upkeep: when a process changes, update the template, or the list will drift out of date. Start with one team or one job type, then expand.

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

Updated 2026-10-27.

Who should own the onboarding checklist?

One person, often in HR or operations, owns the template and the tracker. Other people own individual steps. The template owner reviews it every quarter.

Do I need an HR system for this?

No. A shared list can track tasks, owners and dates. A full HR system helps with payroll, benefits and legal forms, and the list can link to it.

How many steps should the checklist have?

As many as the real process needs, but keep each step small and clear. Count the steps from your last hire. That is your real number.

Can the new hire see the list?

You can make a separate view with only the steps for the new hire, such as "read the handbook" and "meet your buddy". Keep internal steps, like "order laptop," out of that view.