The core idea
Offboarding coordinates the practical end of employment: communication, handover, pay, access and records. It follows the appropriate decision or departure process; it does not make an unfair dismissal fair. Resignation, redundancy, retirement and other exits raise different questions. A respectful close protects service continuity and gives the organisation an opportunity to learn without pressuring the departing person.
Source and attribution [1]Using it in practice
Confirm the relevant facts, notice arrangements and contacts. Assign owners for work handover, assets, access, final pay and questions. Check the applicable contractual and statutory obligations, including leave and authorised deductions, with suitable advice where needed. Keep sensitive reasons for departure restricted. Provide a clear explanation of the practical timetable rather than relying on a checklist circulated between departments.
An example, not a reported case
Worked example · illustrative
A fictional specialist resigns while holding knowledge about a recurring service problem. The manager agrees a proportionate handover and identifies who will receive it. HR offers an optional exit conversation, and payroll explains the final calculation. A later review finds the role had no effective cover, feeding a development action into workforce planning. The organisation does not assume the exit conversation alone explains why everyone in that role might leave.
What to watch for
Do not assume a disputed resignation, notice issue or dismissal is merely administrative. Seek advice promptly where the position is unclear. Protect personal information and use justified retention periods rather than deleting everything immediately or retaining it indefinitely. Be clear about confidentiality limits in exit feedback, and avoid making participation a condition of receiving contractual or statutory entitlements.
Protect continuity without unreasonable demands
Identify the few dependencies that matter most: open decisions, key contacts, recurring tasks and information needed by the successor. Agree what can realistically be completed during the remaining time. Give recipients responsibility for understanding the handover. Coordinate access changes with the circumstances rather than leaving them to an informal message after departure. Verify completion without unnecessarily expanding access to the person's records.
Reconcile pay and documentation
Use the correct dates, working pattern, leave record and agreed arrangements. Check the explanation before issuing it so the person can understand the result and query an error. Avoid using a general checklist as a substitute for current calculation rules. Retain an audit trail of corrections and consider whether an error reflects a wider process problem affecting other leavers.
Close the learning loop
Group exit insight with retention data, employee feedback and operational evidence. Distinguish voluntary exits, planned contract endings and other routes. Use comparable cohorts or suitable time-to-event analysis where helpful. Share themes carefully and assign an action that can be tested. Feed learning into workforce planning, attraction and onboarding so the next employment experience improves rather than producing another unused report.
Turn departure insight into organisational learning
Separate an individual account from a pattern that requires investigation. Combine exit themes with earlier listening, workload and tenure information, protecting confidentiality. Give recurring issues an owner and a review date. Plan knowledge transfer before the final week, focusing on unusual tasks and important relationships rather than collecting an unfiltered folder of documents.
Separate secure completion from learning about the departure
Access removal, final pay, equipment and records need clear ownership and timing. An exit conversation serves a different purpose: understanding experience and possible improvements. Explain how comments will be used and avoid promising anonymity that a small team cannot support. A departing employee may not feel able to be fully candid, so one account should be interpreted alongside earlier listening and operational evidence.
Turn a pattern into a testable improvement
If several leavers describe unpredictable shifts, examine actual scheduling patterns and whether current employees share the concern. Assign an owner to test a practical change, then review later experience and retention with comparable follow-up. Do not publish recognisable comments or use an exit label as a definitive explanation of turnover. Knowledge transfer should prioritise rare tasks, decisions and relationships, with a successor able to demonstrate understanding. The objective is organisational learning and a respectful departure, not merely a completed checklist.
Take it into your next conversation
Three useful questions.
- Which decision needs a clear owner and evidence?
- Whose experience or access could this approach overlook?
- How will you check whether the change improved the work?
Related terms
Go to the evidence
Sources & attribution
Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 15, 29. Edition & reading notes ↗
[1] Official guidance: www.acas.org.uk ↗
[2] GOV.UK: holiday pay when leaving ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.
Published 2026-09-23 · Reviewed 2026-09-25. Editorial approach