Can employee offboarding be automated?

The answer

Partly. Revoking access, updating records, preparing final pay inputs and starting file transfers are largely automatable. In our model about 55% of offboarding time can go to software. Recovering equipment, handing over client relationships and the exit conversation need people. Access removal is the step where automation matters most, because a missed account is a security risk.

The tasks, and how much of each is automatable today

Six tasks make up offboarding. Updating HR records is about 95% automatable and revoking access about 85%. Final pay inputs are about 75% automatable and transferring files and ownership about 60%. Recovering equipment is about 30% automatable. The exit interview stays about 85% human.

Task	Activity type	Min / week	Automatable
Revoke access across every toolAutomatic for tools in the access register with APIs. Unlisted tools are the risk.	Processing data base rate 69%	80	85%
Recover laptops and equipmentReturn labels and reminders are automatable. Collecting and checking the device is not.	Predictable physical work base rate 81%	60	30%
Prepare final pay and holiday balance for payrollCalculated from HR and timesheet data. Commission and disputes need a check.	Processing data base rate 69%	40	75%
Transfer files, inbox and client ownershipBulk transfers are automatable. Deciding who takes which client is the manager's call.	Processing data base rate 69%	60	60%
Hold the exit interviewA survey can capture part. Honest reasons usually come out in conversation.	Interacting with people base rate 20%	60	15%
Update HR records and the org chartStatus, end date and reporting lines update from the HR trigger.	Processing data base rate 69%	20	95%
Whole process		320	56%

Base rates are McKinsey Global Institute's technical automation potential for each activity type. The share for each task is our adjusted estimate. Method.

Hours saved per week

For a 120-person company with about two leavers a week, offboarding takes about 5.5 hours a week by hand. Automating the tasks above returns about 3 hours a week, around 140 hours a year. More importantly, access is removed on the last day rather than whenever someone remembers.

Modelled on: A 120-person company with about two leavers a week, offboarded by HR using a checklist and emails to IT and finance.

Two leavers a week, each with about ten tool accounts.
One in three leavers works remotely and must return equipment by courier.
Leavers own client records, files and shared documents that need new owners.
Final pay includes holiday balance and any commission due.

5.5 hours a week by hand, 3back with automation. Formula: the sum of each task's minutes multiplied by its automatable share, divided by 60, rounded to the nearest half hour.

Tools that do the job

You need a trigger from the HR record, an access register showing what the leaver had, and API access to revoke it. n8n or Make does the revoking and transfers. Airtable or Google Sheets holds the register. Slack and Gmail handle notifications and inbox forwarding. QuickBooks or Xero receives final pay inputs.

n8n: Suspends accounts through APIs at the end of the last day and logs each one.
Airtable: The access register: every tool each person has, so nothing is missed.
Gmail: Forwards the leaver's email to their manager and sets an auto-reply.
HubSpot: Reassigns the leaver's contacts and deals to new owners.
Xero: Receives final pay inputs for the last payroll.
Slack: Deactivates the account and tells the manager which steps are done.

A simple workflow

The workflow starts when HR records a leaving date. Before the last day it schedules file transfers, equipment return and final pay inputs. At the end of the last day it suspends every account in the access register, forwards email to the manager and reassigns CRM records. A person confirms each step.

TriggerHR records the leaving date. Pull the leaver's access list from the register.
PrepareSend return labels, ask the manager to assign new owners, and calculate final pay inputs.
TransferOn the last afternoon, transfer files and reassign CRM records to the chosen owners.
RevokeAt end of day, suspend every listed account and forward email to the manager.
ConfirmPost a checklist of completed and failed steps for HR to confirm.

Keep these human

The exit conversation and the handover of client relationships.
Confirming that every account was actually closed, especially admin and finance access.

Where it goes wrong

Accounts nobody knew about. If a tool is missing from the register, automation cannot revoke it. Review card spend for unlisted tools.
Deleting instead of suspending. Deleted accounts can take files and history with them. Suspend first, delete after the retention period.
Revoking too early. Cutting access at 9am on the last day stops the handover. Schedule revocation for end of day.

What most guides miss

Most offboarding checklists treat access removal as one line item. It only works if you know every account the person had. That depends on logging access during provisioning. Firms that skip the register end up guessing at offboarding, and the forgotten account is usually the one that matters, such as a payment platform.

The evidence

Processing data has a technical automation potential of 69%; interacting with people sits at 20%.McKinsey Global Institute, A future that works: Automation, employment, and productivity (2017)
One in five US payrolls contains errors, and each error costs $291 on average.EY (via Business Wire), EY survey: Payroll errors average $291 each, impacting the economy (2022)