An offboarding checklist that actually closes the loop

Onboarding gets attention because it is a first impression. Offboarding gets attention when something goes wrong: a former employee still in the shared drive three months later, a laptop nobody can locate, a settlement dispute, a reference request that arrives two years on and nobody can answer.

Offboarding is the same problem as onboarding run backwards, with one difference that changes everything. Onboarding has slack in it, because a task missed on day one can be done on day three. Offboarding does not. After the last working day the person is gone, their access should be too, and anything you failed to collect or record is now a phone call to someone who no longer works for you.

This is a checklist you can adopt as it stands. It assumes a small team without a dedicated HR function, and it works the same for a resignation and a termination, with the timing differences noted.

The shape: six groups, every item with an owner and a date

Everything below hangs off one date, the last working day, and every item is expressed relative to it. That is the whole trick. An offboarding process that is a list without dates is a list of things that will be done late.

The six groups are: dates and paperwork, knowledge transfer, access, assets, money, and documents. Nobody owns all six.

Group 1: dates and paperwork, on day one of notice

Record three separate dates. The date the resignation or termination was communicated, the notice period the contract requires, and the agreed last working day. These are frequently not the same, and the difference between them is what any notice recovery is computed from. Record them the day you know them.

Acknowledge in writing. A short acceptance of resignation, or the termination letter drafted with advice if it is a termination. Verbal acceptance is not a record.

Check the contract. Notice on both sides, any garden leave provision, restrictive covenants, and what the appointment letter says is recoverable. Read it now rather than at settlement.

Tell the small number of people who need to know, in the order you decided. Manager, the person’s team, finance, IT, and anyone with a client relationship that needs a handover. Not the whole company on day one.

Book the exit interview and the settlement timeline now, so both have owners rather than intentions.

Group 2: knowledge transfer, across the notice period

This is the part small companies systematically under-plan, because it is the only item on the list that takes weeks rather than minutes.

Name the receiver. Not “the team”, a person. Then have the leaver write down the things that exist only in their head: the recurring tasks and when they fall, the accounts and vendors they deal with, the passwords held in a personal manager rather than a shared one, the half-finished work and where it stands, and the tacit knowledge about who to call when something specific breaks.

Two practical rules. Ask for it in writing rather than in a meeting, because the document survives and the meeting does not. And schedule it in the first half of the notice period, not the last week, when the person has already left mentally and the calendar is full of farewells.

Group 3: access, on a schedule you set in advance

Make a list of every system before you need it, and keep it. Email and calendar, single sign-on or the identity provider, code repositories and cloud infrastructure, customer and finance systems, shared drives, chat, password manager, VPN, physical access such as badges and keys, and anything where the person is an administrator of an account rather than a user of it.

Then decide the timing rule in advance rather than case by case:

• A resignation on good terms: access ends at the close of the last working day.
• A termination, or anyone with access to money, production systems or customer data: access ends at the moment the conversation happens. This is not a statement about the person. It is a control, and controls that get applied selectively are not controls.
• Email: forward or delegate to a named colleague for a defined period rather than leaving the mailbox live. A live mailbox belonging to a former employee is an authentication factor sitting outside your control.

Log each revocation with who did it and when. This is the part a security questionnaire will ask about, and “we do it when someone leaves” is a worse answer than a dated log. How to answer an HR security questionnaire covers what reviewers are actually looking for.

Where the HR system and the access list are connected, exits enforce the checklist rather than depending on someone remembering. In the Capstan core, an exit closes access and asset items before it closes the record, and each step lands in an activity log the admin can filter and export themselves.

Group 4: assets, before the last day and not after

Laptop, phone, monitors, peripherals, security keys, badges, credit cards, and anything issued that has a serial number. For a remote employee this needs a courier arranged in advance and a tracking number recorded, which takes a week and is therefore not a last-day task.

Record the condition on return, and record anything not returned, because the value of unreturned property is a line in the settlement. If issuance was never tracked, this is the exit where you discover that. Asset Management keeps the issued-to record against the person or the contractor engagement, so the return list is a lookup rather than an argument.

Group 5: the money

Finance owns this, HR feeds it.

Sweep outstanding reimbursements with an explicit cut-off, so nothing arrives after the settlement is paid. Confirm the leave balance with the employee and get an acknowledgement. Close the attendance period and produce the day counts. Identify recoveries: unserved notice where the contract provides for it, advances, unreturned assets.

Then hand clean inputs to whoever computes. The full sequence, including who owns which step, is in the full and final settlement guide. If you use the Payroll module, the exit prorations travel as dates and payable days rather than as computed amounts, because the computation belongs to your payroll partner.

Group 6: the documents the person leaves with

Agree this list before your first exit rather than during it. It usually includes the settlement statement, the final payslip, a letter confirming the last working day and that dues are settled, and an experience or service certificate stating the role and dates. Some jurisdictions add statutory or tax documents.

Generate them from the record rather than retyping them, and file each one against the person. A certificate with the wrong dates on it is a document the leaver will have to come back for, and by then the person who typed it has also gone.

The exit interview

Keep it short, keep it consistent, and hold it after the settlement terms are agreed so nobody feels they are negotiating.

Ask the same small set of questions every time. Why are you leaving, what would have kept you, what should the next person in this role know, and what is one thing that would make this a better place to work. Consistency is the entire value: one exit interview is an anecdote, ten comparable ones are a finding.

Write the notes somewhere they can be read together later. If exit feedback lives in individual manager inboxes, you have collected sentiment and thrown away the information. Where you track a small set of people numbers already, attrition and its reasons belong beside them; HR metrics for startups covers the short honest list worth keeping.

After the last day

Close the record, do not delete it. Employment, pay and tax records carry statutory retention periods that run for years after employment ends. Removing access to the record is right; removing the record is not. HR data security and compliance covers retention alongside deletion obligations, and the DPDP Act and employee data covers the Indian position specifically.

Plan for the leaver who writes to you in 2028. They will need a payslip, a letter or a tax document, and they will write from an address you no longer host to a colleague who has also left. At a steady rate of leavers this becomes a permanent background task. Alumni Access turns it into self-service on the person’s personal email, scoped to documents that were already theirs.

Update the org chart and the hiring plan. If the role is being backfilled it belongs in the hiring plan with a date, not in a good intention.

The one-page version

On notice day: record the three dates, acknowledge in writing, read the contract, name the knowledge receiver, book the exit interview.

Across the notice period: knowledge transfer in writing, asset return arranged, reimbursement cut-off announced, leave balance confirmed.

On the last day: access revoked on schedule and logged, assets returned and recorded, documents issued, farewell.

After: settlement paid with a statement, record closed and retained, exit notes filed where they can be compared, backfill decided.

Six groups, every item with a name and a date. That is the difference between an exit that closes cleanly and one that keeps arriving in your inbox for a year.