
Offboarding as one checklist instead of four
When someone leaves, four teams each keep their own list, and the account nobody remembered stays open for months. An agent turns the departure into one checklist with owners and dates. Revoking access, final pay and the conversation stay with people.
The short answer
An agent runs offboarding by turning a confirmed departure into one checklist across every team: access removal with IT, final pay with payroll, equipment and badges with facilities, handover with the manager.
Each item has an owner and a date. People revoke the access, settle the pay and handle the conversation with the person leaving.
Why does the departed employee still have a login months later?
IT has a list for leavers. Payroll has its own. Facilities collects badges when someone remembers to tell them. The manager is supposed to reassign the work. Nobody holds all four lists together, so each team finishes its own part and assumes the others did theirs. Months later someone finds the old account still active in a tool nobody thought to check, or a laptop that never came back.
Who is this for?
Whoever ends up handling departures, usually an owner or an office manager, at a company where several teams each do a part and no HR coordinator holds the whole. It suits businesses with a list of the systems people use, even an incomplete one. Decisions about why someone leaves, and how, are not part of this workflow.
What changes when there is one list?
| Part of the departure | Four separate lists | One tracked checklist |
|---|---|---|
| Starting the process | Each team hears at a different time | Every item opens when the departure is confirmed |
| System access | Removed from the systems IT remembers | Checked against the full list of systems the person used |
| Equipment | Collected if someone asks | Listed by item, with its return tracked |
| Handover | Up to the manager's memory | Open work listed for the manager to reassign |
| Proof it is done | Nobody can say for sure | A closed checklist with who did each item and when |
How it works, step by step
The departure is decided before the agent is involved. It organises the follow-through and never touches the decision.
Start from a confirmed departure
Build the checklist from the person's record
Open each item with its owner
Human gate: owners revoke, settle and sign off
Check access against the full list
Keep the record
What does the agent stay out of?
The decision to part ways
It begins only after a person confirms the departure.
The conversation. Exit meetings, references and anything said to the person leaving belong to people.
Revoking or deleting
Owners do it. The agent checks and reports.
Final pay and legal terms
Payroll and your advisers handle amounts, timing and any agreements.
Deleting records. It files them. Retention and destruction follow your policy.
Where this fits
One departure, from confirmation to a signed-off checklist, is a single process: Tier 1, Automate a Workflow covers it. Your system list and offboarding template are what the readiness checklist will look at first. An account that stays open is exactly the kind of gap exception detection and routing across your ops stack is built to surface, and the paperwork at the other end of employment lives in onboarding paperwork and checklist coordination. The sign-off by one named person follows approval gates. The use case library has the rest.
How does offboarding differ from onboarding?
| Question | Onboarding | Offboarding |
|---|---|---|
| What can go wrong | Something is missing on day one | Something stays open after the last day |
| The risk | A slow first week | Access and equipment outside your control |
| The check that matters | Is everything ready? | Is everything closed? |
| Sensitivity | Usually low | Often high, so wording to the person stays human |
Related reading
- Onboarding paperwork and checklist coordination: the start of employment, run the same disciplined way.
- Exception detection and routing across your ops stack: catching what falls between systems, such as an account nobody closed.
- When not to automate: why the human side of a departure stays human.
