Offboarding Checklist: Everything HR and Managers Need to Do When an Employee Leaves

When an employee resigns, most organisations focus entirely on the logistics — the paperwork, the access revocation, the equipment return, the recruitment that needs to start. The human dimension of the departure gets treated as a nice-to-have if there’s time, which there rarely is.

This is a mistake, and it’s a costly one. The way a company treats people who leave is visible to every person who stays. A departing colleague who is rushed through a two-day handover, handed an envelope, and removed from Slack sends a signal to the remaining team about how dispensable people are here. A departing colleague who receives a genuine public farewell, a thorough knowledge transfer, and an exit interview that the company clearly intends to act on sends a very different signal.

This guide covers everything: the complete offboarding checklist from resignation to post-departure, the exit interview questions that surface honest answers, what a knowledge transfer document should contain, how to handle the human side of the departure well, and what the data says about why offboarding matters for the people who stay.

In this article

1. What is offboarding?
2. Why offboarding matters — and not just for the person leaving
3. The complete offboarding checklist
4. Knowledge transfer: how to preserve what the departing employee knows
5. Exit interview questions that get honest answers
6. The farewell: how to close well
7. Remote and hybrid offboarding
8. Offboarding vs onboarding: how the two connect
9. What offboarding data tells you about retention

What is offboarding?

Offboarding is the structured process of managing an employee’s departure from an organisation. It covers everything that happens between the moment someone announces they’re leaving and the period after their final day — including administrative tasks, compliance requirements, knowledge transfer, IT access management, equipment return, the exit interview, and the human moments that close the relationship well.

Offboarding applies across all departure types: voluntary resignation, mutual agreement, redundancy, retirement, and involuntary termination. The specific steps vary significantly by circumstance, but the need for a structured process is consistent. Without it, things get missed — forgotten access credentials, incomplete handovers, uncollected equipment, and exit feedback that was never gathered and never acted on.

The term is the inverse of onboarding — the process of integrating a new employee into the organisation. The parallel is deliberate: just as onboarding sets the foundation for an employee’s experience at a company, offboarding shapes their lasting impression of it and, through them, its reputation in the market.

Why offboarding matters — and not just for the person leaving

It’s a signal to the team that stays

Every remaining team member watches how a departing colleague is treated. A rushed, impersonal, or disorganised departure sends a message that the company views people as interchangeable and their tenure as a means to an end. A well-handled departure — genuine recognition, proper knowledge transfer, a meaningful farewell, an exit interview conducted with care — signals that the company takes the relationship seriously even when it’s ending.

This is not a minor point. Remaining employees are evaluating every day whether this is a place worth staying. The way the company says goodbye to someone is evidence they use to make that assessment.

Former employees have long memories and wide networks

A departing employee who leaves well is more likely to refer candidates, recommend the company to clients, and return as a “boomerang hire” later in their career. A departing employee who leaves badly — or who witnesses a badly handled offboarding of a colleague — will carry that impression for years and share it when people ask about the company, which they will.

Employer review platforms make this more consequential than it used to be. A genuine, thoughtful offboarding experience protects the employer brand in ways that no amount of recruitment marketing can compensate for if the experience itself is poor.

It protects the organisation

From a purely operational standpoint, a structured offboarding process reduces risk: data breaches from forgotten access credentials, compliance gaps in final pay and documentation, loss of institutional knowledge that existed only in one person’s head, client relationship disruption when a key contact leaves without a proper handover.

None of these risks require the company to treat offboarding as a human priority — they require it to treat it as an operational one. The good news is that the same structured process serves both goals.

The complete offboarding checklist

Phase 1: Immediately after the resignation or departure notice

The clock starts when the departure is confirmed. The priority in the first 48 hours is information and planning.

HR tasks

• Receive and acknowledge the resignation letter in writing
• Record the departure in your HR system and confirm the leaving date
• Review the employment contract for notice period requirements, non-compete clauses, and non-disclosure obligations
• Notify payroll of the departure date and initiate the final pay calculation — including any accrued and unused leave
• Notify finance of any outstanding expenses, advances, or reimbursements to be settled
• Begin the recruitment process if a replacement is needed — don’t wait until the last day

Manager tasks

• Have a private conversation with the departing employee to understand the context, confirm the timeline, and agree on the handover plan
• Notify the direct team once the departure is confirmed — before rumours do
• Send a company-wide announcement (appropriate timing and tone will depend on the size of the team and the seniority of the person)
• Begin mapping which responsibilities need to be redistributed and to whom

IT tasks

• Log the departure date in the IT system and begin planning access revocation
• Identify all systems, tools, and accounts the employee has access to
• Do not revoke access yet — this happens on or after the final day

Phase 2: During the notice period

The notice period is where most of the substantive offboarding work happens. This phase is about knowledge transfer, compliance, and setting the departure up to close well.

Knowledge transfer (covered in detail below)

• Begin the knowledge transfer process within the first week of the notice period
• Identify the departing employee’s key responsibilities, projects, contacts, and undocumented knowledge
• Decide who inherits each responsibility and make introductions where necessary
• Produce a knowledge transfer document (or update existing documentation)

HR and compliance tasks

• Prepare the final pay statement and ensure all calculations are accurate — regular pay, unused leave, any bonuses or commissions due, and any applicable severance
• Review benefits — health insurance continuation, pension or retirement plan options, stock or equity vesting status
• Prepare any required separation documents — redundancy paperwork, compromise agreement, reference letter (if agreed)
• Confirm the return timeline for company equipment — laptop, phone, access cards, company credit cards

Ongoing work and client management

• Notify clients, suppliers, or external contacts who had a primary relationship with the departing employee — with appropriate timing and care, not at the last minute
• Introduce the person taking over those relationships before the departure where possible
• Handover meeting notes, pending actions, and relationship context to the relevant successor

Phase 3: The final week

The final week is where logistics and human moments converge. Neither should crowd out the other.

HR and admin tasks

• Confirm the final pay amount with payroll and verify payment date
• Prepare any reference letters or employment verification documents the employee has requested
• Confirm all equipment return arrangements — collection date, return shipping, or in-person handover
• Schedule the exit interview — ideally in the penultimate week so there’s still time to act on anything urgent

IT and security tasks

• Prepare to revoke access to all systems on the final day (or when the employee physically leaves, for remote workers)
• List every system requiring access revocation: email, Slack, MS Teams, project management tools, code repositories, cloud storage, CRM, finance systems, HR platforms, third-party tools, VPN access
• Set up email forwarding or auto-response for the departing employee’s address
• Plan the reassignment of any licenses or accounts that need to be transferred rather than deleted
• Back up or transfer any files, documents, or data from the employee’s accounts that need to be retained

The farewell (covered in detail below)

• Plan the public farewell — format depends on team culture and the employee’s preferences
• Give colleagues advance notice so they can prepare contributions if appropriate
• Ensure the recognition moment is specific and genuine, not generic

Phase 4: The final day

Logistics

• Collect all company equipment — laptop, phone, access cards, keys, any other physical assets
• Revoke all system access — this should happen at a specified time on the final day, not haphazardly
• Process any remaining expenses or reimbursements
• Confirm the departing employee has received all documentation they need — payslip, reference letter, any certificates or records they’re entitled to
• Remove the employee from internal systems, mailing lists, and team channels (after the farewell, not before)

The human close

• The line manager or a senior leader says something specific and genuine — publicly, to the team
• Colleagues have the opportunity to add their own appreciations
• The departing employee has space to say what they want to say
• The exit is marked as a moment, not glossed over

Phase 5: After the final day

Offboarding doesn’t end when the employee leaves the building.

Immediate post-departure

• Confirm all system access has been revoked and run a final check
• Confirm all equipment has been returned and is accounted for
• Update the employee’s status in all HR systems
• Ensure email auto-forward or redirection is working correctly

Within two weeks

• Conduct a final security audit — check for any access that may have been missed
• Archive the departing employee’s personnel file in accordance with your data retention policy (local regulations vary significantly — confirm requirements for your jurisdiction)
• Review any outstanding actions from the exit interview
• Share relevant exit interview themes with the relevant leaders — not the raw responses, but the patterns

Within 30 days

• Add the former employee to your alumni network if you maintain one
• Send a check-in message if appropriate — particularly for long-tenured employees or those with whom you want to maintain a positive relationship
• Begin the post-mortem on the departure: was this predictable? What, if anything, could have changed the outcome? What does the exit interview data tell you?

Knowledge transfer: how to preserve what the departing employee knows

The knowledge transfer is the most practically consequential part of offboarding, and the most commonly underestimated. Every employee carries three kinds of knowledge when they leave: documented knowledge (the things in the wiki, the process doc, the code), undocumented knowledge (the things they know but haven’t written down), and relational knowledge (the context they hold about clients, colleagues, and stakeholders that doesn’t exist anywhere else).

The documented knowledge is the easiest to transfer. The relational knowledge is the hardest — and often the most valuable.

What a knowledge transfer document should cover

A good knowledge transfer document covers the following for each of the departing employee’s key responsibilities:

Overview of the responsibility — what it is, why it matters, how often it recurs, and what good looks like

Step-by-step process — written as if explaining to someone with no prior context. The test is whether someone unfamiliar with the role could follow the process without needing to ask questions.

Key contacts — internal and external. For each contact: their name, their role, the nature of the relationship, and any context the successor needs to manage it well. This is the section most people write too briefly.

Current status of ongoing work — for any project or responsibility that is mid-stream: where it is, what’s been decided, what’s pending, and what the next step is.

Known risks and things to watch for — the things the departing employee would flag to a successor that aren’t in any document but that they know from experience. These are often the most valuable entries.

Location of all relevant files, tools, and logins — clear paths to everything needed, not just “it’s in the shared drive.”

How to make the knowledge transfer actually happen

The most common failure mode in knowledge transfer is leaving it to the departing employee, who has one foot out the door and limited motivation to spend their final weeks writing documentation. The manager needs to actively drive the process — scheduling dedicated sessions, reviewing drafts, asking questions, and following up.

Buddy sessions work better than written handovers alone. Have the departing employee walk the successor through each area of responsibility in person — recorded if possible — and use the written document as a companion, not the primary medium.

Exit interview questions that get honest answers

The exit interview is one of the most valuable data sources available to HR and leadership — and one of the most consistently mishandled. Interviews that feel like a performance, ask leading questions, or are conducted by someone the departing employee doesn’t trust produce useless data.

The conditions that produce honest exit interview data: the interview is conducted by someone the employee trusts (often HR rather than their direct manager), it’s framed as genuinely confidential, the questions are open rather than leading, and the company has a visible track record of actually acting on exit interview feedback.

Questions that surface real answers

About the role and workload

• How did the role compare to what was described when you joined?
• Was the workload sustainable throughout your time here?
• Were there resources or tools you needed but didn’t have?

About management and leadership

• How would you describe your relationship with your manager?
• Did you feel your manager supported your development?
• How well did you feel senior leadership communicated the direction of the company?

About culture and recognition

• Did you feel your contributions were recognised and valued?
• How would you describe the team culture?
• Was there anything about the way the company worked that made your job harder than it needed to be?

About the departure itself

• What was the primary reason for your decision to leave?
• Was there anything the company could have done differently that might have changed your decision?
• Is there anything you wanted to raise during your time here but didn’t find the right moment to?

Looking forward

• Would you consider returning to the company in the future, in a different role or at a different time?
• Would you recommend us as an employer to people in your network?
• Is there feedback you’d like to leave for your team or manager that you’d be comfortable with us sharing?

The exit survey as a complement

An exit interview conducted in conversation has limitations — people are less candid face-to-face than in writing, and the data from a single conversation is harder to compare across departures. An exit survey — sent a week before the final day or immediately after — captures structured, comparable data that compounds in usefulness as departures accumulate.

Questions about recognition and management quality in exit surveys feed directly back into culture analytics — and the patterns they reveal over time are often more actionable than any individual exit interview.

The farewell: how to close well

This is the section most offboarding guides either skip or treat as a single bullet point. It deserves more than that.

How a company marks the departure of an employee is one of the clearest expressions of its culture available to the remaining team. It’s also one of the few moments in the employment relationship where the organisation has the opportunity to express genuine appreciation in a way that leaves a permanent impression.

What a good farewell looks like

It is specific. “Sarah was a great colleague and we’ll miss her” is not a farewell — it’s filler. “Sarah rebuilt our customer onboarding process from scratch in 2024, reducing time-to-value by 60%. She did it with almost no visibility, no fanfare, and no recognition in the moment. We’d like to correct that now” is a farewell. The specificity is the signal: someone noticed. Someone paid attention.

It is public. A private goodbye from the manager is kind. A public goodbye in the main team channel, or at the all-hands, or in the general Slack, is what closes the chapter well. The departing employee sees that their colleagues were present for the moment. Their colleagues see that departure is handled with dignity here.

It is given space for the team to contribute. The manager’s words are not the only words that matter. Giving colleagues the opportunity to add their own appreciation — in the channel, in a farewell card, in a few words at a team gathering — produces the most meaningful moments in an offboarding and the ones the departing employee remembers longest.

It gives the departing employee space to say something too. A farewell that’s entirely performed at the departing employee rather than with them misses the point.

What a bad farewell looks like

The access revoked before the goodbye is posted. The Slack message with three emoji reactions. The manager who is too busy to attend the leaving drinks they organised. The all-hands where the departure is mentioned in passing between two agenda items. The email from HR that reads like a press release.

These are all real. All of them send the same message: getting the work done mattered; the person doing it did not.

Using Karma to mark the departure publicly

If the team uses Karma for peer recognition, the departing employee’s final day is the right moment to send a company-wide recognition in the main channel — specific, warm, and tied to what they actually contributed. The recognition feed records the moment permanently, and the departing employee can look back at it.

More meaningfully: the departing employee’s recognition history — the kudos they’ve received throughout their tenure — is a record of what their colleagues noticed and valued. Sharing highlights of that history on the final day turns the farewell into a genuine tribute rather than a polite formality.

Remote and hybrid offboarding

Remote offboarding requires the same structure as in-person offboarding but creates different logistical challenges and different human ones.

Equipment return is the most practically awkward element. Establish a clear process before the final day — prepaid return shipping, a collection service, or a drop-off arrangement. Don’t leave it to the departing employee to figure out on their last day.

Access revocation should be treated with more precision for remote employees because there is less natural visibility over which tools are being used. Maintain a comprehensive access register from day one of employment — not just when someone leaves — so that offboarding IT tasks are a matter of working through a list rather than trying to reconstruct one.

The farewell is harder to get right remotely. The spontaneous contributions that make an in-person farewell warm — the conversation before the meeting, the card going round the office, the leaving drinks — don’t happen naturally in a remote context. Plan for them deliberately. A dedicated farewell thread in Slack, a video call with time set aside specifically for contributions from the team, or a short video compilation from colleagues all recreate the function of the in-person moment without requiring physical presence.

Knowledge transfer tends to need more structure remotely because the casual knowledge-sharing that happens naturally in shared physical space doesn’t. Formal sessions, recorded walkthroughs, and written documentation are all more important for remote employees than for those who work alongside their colleagues every day.

Offboarding vs onboarding: how the two connect

Onboarding is the beginning of the employee lifecycle. Offboarding is the end. They are more connected than most organisations treat them.

The same things that make onboarding effective — clear expectations, a structured process, a human welcome — make offboarding effective. Organisations that invest in onboarding but neglect offboarding are focused on the beginning of the relationship to the exclusion of the end, which is visible to every employee who witnesses a poorly handled departure.

There’s a data loop between the two processes that most companies are missing. Exit interview data should feed directly back into onboarding: if departing employees consistently cite unclear role expectations, the onboarding process is the place to fix it. If they cite poor management, the answer might be in the 1:1 cadence established during onboarding. If they cite feeling unrecognised, the answer is a recognition program established early in the employee lifecycle.

The offboarding checklist and the onboarding checklist are, in this sense, a closed loop. What the exiting employee tells you about their experience should become the input that improves the experience for the next person starting.

What offboarding data tells you about retention

Exit interview data is only useful if it’s collected systematically and acted on visibly. The organisations that treat offboarding as a data collection exercise — gathering consistent data across departures, identifying patterns, and reporting them to leadership — are the ones that reduce preventable turnover over time.

The most revealing exit data points are the ones that recur across multiple departures. A single employee leaving because they received a better offer is a market event. Five employees in two years citing the same manager as a primary reason for leaving is an organisational problem. The exit interview data is the only place that pattern reliably surfaces — if anyone is looking for it.

What the data most commonly reveals about recognition specifically: employees who felt consistently unrecognised are significantly more likely to cite it as a contributing factor in their decision to leave, even when they name a different primary reason. Recognition is often the background variable — the thing that would have made the decisive difference if it had been present, but whose absence is only named on the way out.

This is the retention case for investing in peer recognition. The exit interview is the wrong time to discover that someone left partly because their work went unnoticed — by their manager, by their peers, or both. The peer recognition feed, the culture analytics, the recognition gaps visible in the monthly report — these are the early warning signals that exit interviews confirm too late.