What Goes in the Leaver File
The eleven things that belong in a leaver file, why it must make sense to a stranger, and the items that live elsewhere and never arrive.
Closing one leaver file, item by item
Four items are still open, and the two that belong to functions outside HR are the two somebody will actually need. This is one organisation's own record, not a statement of what any rule requires.
Assemble the file so that a stranger could read it in order and understand what happened, because that is precisely who will read it. Everybody involved will have moved on, and the question — from an adviser, an auditor, a regulator or the person themselves — will arrive long after anybody remembers.
The payment question in “What Goes in the Leaver File” depends on a complete and correct work record, not simply the latest dashboard total. For organisations researching limbic resonance in relationships, how teams evaluate limbic resonance in relationships can connect hours with projects and approvals, provided disputed entries remain correctable and payroll applies the relevant contract and local rules.
The file is also the only durable product of an exit. Everything else is conversations.
For an independent reference relevant to “What Goes in the Leaver File”, consult the CIPD discipline and grievance guidance. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
What belongs in it
- The contract, with every variation, in the versions that applied.
- The job description the person was actually working to.
- Any policy relied on, in the version in force at the relevant time.
- The process documents in order: invitation, evidence, notes, outcome, appeal.
- Contemporaneous notes of informal concerns, where they exist.
- The resignation or termination letter, with the termination date stated.
- The final payment calculation and breakdown, not just the payslip.
- Property and access records, with what was and was not returned.
- The agreed reference wording, if any.
- Anything issued to the person, with dates.
- The retention date, and who owns the file.
Eleven items, of which three usually live in other systems and never arrive: the payment calculation, the access record and the property record.
Order, which matters more than completeness
A file in date order with a short index at the front is readable. The same documents in a folder named after the person, in whatever order they were scanned, is not.
Put a one-page summary at the front: who, dates, what happened, what was decided, what was paid, what was agreed. It takes ten minutes on the last day and saves hours every subsequent time anybody opens it.
What should not be in it
Draft documents that were superseded, unless they show something. Email chains where managers speculated. Anything about other people that does not belong in this person's record. Duplicates.
The second is the one that causes real damage. A thread in which three managers discussed what to do about somebody, over several months, in informal language, is both disclosable in many circumstances and almost always worse than the decision it led to.
Things that live elsewhere
Access logs sit in IT. Property records sit with facilities. The payment calculation sits in payroll's working file, which may be a spreadsheet on one person's drive. Expense records sit in the expense system.
None of these migrates to the HR file on its own. Either the checklist requires a copy to be placed in the file, or the file is incomplete. The second is what happens by default.
Writing for a reader who was not there
Internal shorthand is the enemy. A note saying the matter was "dealt with under the usual approach" means nothing to anybody outside the room, and the room no longer exists.
The test is the same throughout this collection: could somebody who knows none of the people, reading this in two years, tell what happened and why? Where the answer is no, a short covering note now fixes it; nothing fixes it later, because the explanation lives in somebody's memory and memory is exactly what leaves.
The summary sheet
One page at the front, with: name, role, start date, termination date, last working day, reason, who decided, what was paid and when, what was agreed, retention date, file owner.
Half of those fields are the ones that get confused later — particularly the three different dates — and having them stated once, authoritatively, stops every subsequent reader deriving them from the documents and occasionally deriving them differently.
One file, not several
A departure frequently produces three files: the HR one, a manager's folder, and whatever the adviser kept. Each is incomplete, they disagree, and all three are records about the person.
Consolidate at closure. Ask everyone involved to send what they hold, put it in one place, and delete the duplicates. It is twenty minutes on the last day and it prevents the situation where a request for information produces one file and a dispute later produces a different one.
Closing it deliberately
A file is closed when somebody says it is. Left open, it either accumulates stray documents for years or is quietly abandoned.
Closing means: everything is in, the summary is written, the retention date is set, and an owner is named. Four things, five minutes, and the difference between a record and a folder. It is the last line of the departure checklist and the one most often left unticked.