Skip to content
The Leaver File

Employment compliance, read backwards from the exit

The paperwork holds. Until somebody leaves.

Fifty notes on what a departure has to produce. Not a guide to dismissal law — a working account of the record that should already exist before anyone is told, the shape of a fair process, what the last day has to produce, what is owed and when, what follows the person out of the door, and the file somebody will ask for two years later.

What continues after the last day, in one organisation's own contracts

Confidentialityno end date

Information learned in the role, with no end date written anywhere.

Non-solicitation of clients12 months

The longest of the restrictions, which is the usual shape.

Non-dealing with staff12 months

Reaches people who are still employed.

Non-compete6 months

Six months from the last working day, not from the notice date.

Reference policyno end date

No stated period; the same two lines are given for as long as anyone asks.

Personal data retention72 months

Six years, set by the retention schedule rather than the contract.

Two of the six have no end date the person could name, and one of those two is the one everybody forgets. Every row is what one organisation wrote in its own contracts — not a statement of what any jurisdiction permits or requires.

No jurisdiction is told what its law requires. Every figure here is an illustration of what an organisation recorded for itself, labelled as such. Nothing in this collection is legal advice: what a lawful dismissal requires, what notice and payments are due, and what a post-termination restriction may cover differ by jurisdiction, by sector and by agreement, they change, and they are a question for somebody qualified in the place concerned.

The two things nobody looks at until it is too late

A dismissal for conduct, step by step, as one organisation recorded it

StepOwnerStateWhen
01Concern recorded in writing at the timeLine manager○ Outstanding-
02Investigation meeting held and minutedHR adviser✓ Done19 Mar
03Allegations put in writing before the hearingHR adviser✓ Done21 Mar
04Hearing held, companion offeredSenior manager✓ Done28 Mar
05Outcome given in writing with reasonsSenior manager! Overdue11 Apr
06Right of appeal explained in the letterSenior manager○ Outstanding-
07Appeal heard by someone not already involvedDirector– Not applicable-

The step that was never done is the first one. Nothing was written down until the organisation had already decided; everything after that is an investigation into a conclusion. This is one organisation's own file, not a statement of what any jurisdiction requires.

A final payment, line by line, as one organisation computed it

Salary to the last working day£2,140.00✓ Done
Accrued untaken leave, 6.5 days£642.00✓ Done
Notice not worked, 4 weeks£2,153.85○ Outstanding
Expenses submitted and approved£188.40○ Outstanding
Training cost recovery-£400.00○ Outstanding
Total gross£4,724.25

Three of the five lines were still unpaid six weeks after the last day, and the person had to ask twice. The deduction on the last line was taken under a clause the employee had signed on their first day; whether such a clause is enforceable, and whether it may be deducted from a final payment at all, is a question for somebody qualified in the place concerned.

Why this is written backwards

An exit is the audit nobody scheduled. Everything an organisation did or failed to do about a person — the concern raised in a corridor and never recorded, the pay change agreed verbally, the contract that was never issued, the access that was granted for one project in 2021 — arrives at once, on a single day, usually with a deadline attached and sometimes with a lawyer on the other end of it.

The payment question in “The paperwork holds. Until somebody leaves.” depends on a complete and correct work record, not simply the latest dashboard total. For organisations researching employee monitoring software with screenshots, Monitask can connect hours with projects and approvals, provided disputed entries remain correctable and payroll applies the relevant contract and local rules.

This collection is organised the way the work actually lands rather than the way the law is written. It starts with what has to exist before anybody is told, because that is the part that cannot be retrofitted. Then the shape of a process, which is remarkably similar wherever you are even though the detail is not. Then the last day itself, which is a logistics problem disguised as a legal one. Then what is owed and when. Then the obligations that outlive the employment. Then the file, which somebody will ask for long after everyone involved has left. And finally what a year of exits looks like in aggregate, which is usually the most useful thing an organisation has and the thing it least wants to read.

For an independent reference relevant to “The paperwork holds. Until somebody leaves.”, consult the NIST Cybersecurity Framework. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

No jurisdiction is told what its law requires anywhere here. That is deliberate: the rules differ, they change, and getting them from a web page is how organisations end up defending a position nobody chose. What is here is the work that has to happen under any of them.

The short version

Write it down before you have decided

Almost everything that goes wrong in an exit went wrong months earlier, when a concern was handled in a corridor and never written down. The record made before a decision is the only one worth anything afterwards. Everything else — the process, the last day, the final payment, the file — is work that can be listed, assigned and checked off, and most of it is not hard. It is only invisible.