Employee Onboarding and Offboarding: A Process That Doesn't Forget Anything

A new hire turns up on their first day. Their laptop is still in its box, they have no login, and their manager is on leave. Six months later, someone else leaves, and three weeks after their last day they can still log in to the customer database.

Both problems have the same cause. Joining and leaving involve four or five teams, and the process lives in a spreadsheet with a tab per person, copied from whichever tab someone last remembered to update.

Why joiner and leaver checklists drift

Onboarding and offboarding look like simple checklists. In practice they are cross-team processes: HR, IT, payroll, facilities, the hiring manager and sometimes finance all have tasks, often with dependencies between them. IT cannot create accounts until HR confirms the start date. Payroll needs bank details before the first pay run.

The spreadsheet version usually fails in three ways:

• Copies diverge. Someone adds “set up access to the new reporting system” to one person’s tab, and nobody else’s.
• Nobody is notified. IT has to go and look at the sheet to find out they have work to do. Often they do not.
• Completion is unclear. A cell says “done” with no date and no name. When an auditor asks who removed a leaver’s access and when, nobody can say.

Offboarding is the riskier half. A missed onboarding step is annoying. A missed access removal is a security incident waiting to happen.

One template, many runs

The core idea is the same one behind The Client Onboarding Checklist That Runs Itself: keep a single master template of tasks, and generate a fresh set of tasks for each person from it.

Each template task has:

• What: “Create email account”, “Add to payroll”, “Revoke building pass”.
• Owner team: IT, HR, payroll, facilities, the manager.
• Timing: relative to the start or leaving date, such as five days before, on the day, or one week after.
• Conditions: only if the person is in sales, only if they need a vehicle, only if they are remote.
• Dependencies: which tasks must be finished first.

When HR creates a joiner or leaver record with a date, role and department, the tool generates the relevant tasks, assigns each to its owner team and sets due dates automatically. Change the template once, and every future run picks it up. Recurring Work: Turning Monthly Checklists Into Scheduled Processes uses the same pattern for monthly cycles.

A typical joiner set

Say a 120-person company hires a field sales rep starting on the 1st. The generated tasks might look like this:

An office-based hire would skip the vehicle row automatically. A contractor might skip payroll entirely and gain a “confirm contract end date” task.

Each owner sees only their own tasks in a queue, ordered by due date. Notifications vs. Queues: How People Should Find Out There’s Work to Do explains why a queue usually beats a flood of emails here.

Offboarding: the list of what to undo

Offboarding works the same way, with one important addition. Its checklist should be built partly from what the person actually has, not just from what a typical leaver might have.

That means pulling in:

• Equipment assigned to them, from your asset register. Building an Equipment and Asset Register People Actually Keep Current covers how to keep that list accurate.
• Systems they have access to, ideally from a record of what was granted during onboarding and any later access requests.
• Things they own: recurring reports, shared mailboxes, open approvals, customer accounts that need a new owner.

Access removal deserves firm rules. Agree a deadline, for example all access removed by the end of the last working day, and track it. For involuntary departures, removal often needs to happen within the hour, so make sure there is an expedite path and that IT knows how to trigger it.

Record completion properly

Every task should capture who completed it and when, automatically. Avoid letting people tick a box without that information being stamped.

For a few sensitive tasks, ask for a short note or evidence: “Access removed from finance system, confirmation reference attached.” This is what turns a checklist into an audit trail. Compliance Registers: Proving What Happened and When goes further if you are in a regulated industry.

Then build two simple views for HR:

• In flight: every joiner and leaver currently in progress, with the count of overdue tasks per person.
• Overdue by team: which owner team is behind, so the conversation is about capacity, not blame.

Keep personal data tight

Joiner records contain bank details, addresses, tax numbers and sometimes health or right-to-work information. Not everyone involved needs to see all of it. IT needs a name, role and start date. Payroll needs bank details. Facilities needs neither.

Use field-level or role-based permissions so each team sees only what its tasks require. Permissions That Make Sense: Who Should See and Edit What and Privacy Basics for Ops Teams: Handling Personal Data in Internal Tools cover the detail.

Where to start this week

1. Gather the last five onboarding and offboarding tabs and merge them into one master task list, noting owner team and timing for each.
2. Mark which tasks are conditional, and on what: role, location, employment type.
3. Pilot the generated checklist on the next leaver, since offboarding carries the most risk.
4. Ask each owner team to name one person who watches their queue, so no task sits unclaimed.