Image
Workflow
Back office

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

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.

Today

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 departureFour separate listsOne tracked checklist
Starting the processEach team hears at a different timeEvery item opens when the departure is confirmed
System accessRemoved from the systems IT remembersChecked against the full list of systems the person used
EquipmentCollected if someone asksListed by item, with its return tracked
HandoverUp to the manager's memoryOpen work listed for the manager to reassign
Proof it is doneNobody can say for sureA 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.

01

Start from a confirmed departure

A named person marks the departure as confirmed, with the last day. The agent starts nothing before that.
02

Build the checklist from the person's record

It lists the systems the person had access to, the equipment assigned to them, their open work and the payroll and benefits steps your template includes. Gaps in that record are flagged, because an account nobody listed is the one that stays open.
03

Open each item with its owner

Access removal goes to IT, final pay and benefits steps to payroll, badges and equipment to facilities, and open work to the manager. Each item carries the last day as its deadline.
04

Human gate: owners revoke, settle and sign off

IT revokes each account, payroll settles final pay and benefits, facilities collects what was issued, and the manager reassigns the work. The agent opens and tracks items, and revokes, pays or deletes nothing itself. A named person signs off the closed checklist.
05

Check access against the full list

After the last day it checks each listed system for remaining access and reports anything still active to IT. Someone who has left has no assigned work, and NIST's definition of least privilege limits access to what a person's assigned work needs.
06

Keep the record

It files the closed checklist with the personnel record under your retention policy. Retention periods are a question for your counsel. As one reference point, the EEOC's recordkeeping page states that if an employee is involuntarily terminated, their personnel records must be retained for one year from the date of termination.

Stays with people

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

Workflow / Automate a Workflow

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?

QuestionOnboardingOffboarding
What can go wrongSomething is missing on day oneSomething stays open after the last day
The riskA slow first weekAccess and equipment outside your control
The check that mattersIs everything ready?Is everything closed?
SensitivityUsually lowOften high, so wording to the person stays human
Tier 1 / Prove
How It Works

Questions, answered

No, and it does not need to. It receives a confirmed departure and a last day. Reasons, circumstances and any agreement stay with the people handling them.
AI Opportunity Audit · Offboarding

Close every account when people leave

Bring the last departure you handled and check which systems still know that person.