Retention After Departure
Periods are driven by claim windows and statutory requirements, and are shorter than the indefinite holding most employers actually operate.
POST-DEPARTURE SCHEDULE
Each row with its trigger and its reason
- Core employment recordSeveral years from leavingDefence of claims, with the local limit
- Payroll and taxAs required by revenue rulesThe one with a hard statutory answer
- PensionPotentially decadesA genuine long retention, and the exception
- Health recordsShorter, unless a specific duty appliesSpecial category, so proportionality is tighter
- DisciplinaryShort after expiry, shorter if unsubstantiatedAn expired warning has no purpose
- RecruitmentAlready deleted, if the schedule workedCheck, because it usually has not
- EmailThe holding with no schedule at allWhere retention policies go to fail
- Deleted byMechanism and date, per rowA period with no mechanism is a wish
Employment records are kept after somebody leaves for reasons that are mostly specific and time-limited. The reasons are shorter than the practice.
The practical lesson in “Retention After Departure” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching employee monitoring software with screenshots, see the complete product overview can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
What actually drives the periods
Claim windows. The main driver for the core record. How long somebody has to bring an employment claim, plus a margin.
For a separate benchmark relevant to “Retention After Departure”, consult the Acas workplace-investigation guidance. Use it to test purpose, data flow, retention, access and response procedures rather than substituting a generic checklist for the organisation’s actual records.
Statutory requirements. Payroll and tax records have defined periods set by revenue authorities, and those are hard answers.
Pension obligations, which genuinely run for decades and are the real exception.
Regulatory requirements in some sectors.
Everything else is preference, and preference defaults to forever.
Why the practice diverges
Nobody deletes.
The HR system might purge on schedule. The shared drive does not. The email archive does not. The folder of signed contracts in a cupboard does not. The payroll provider keeps its own copy under its own rules.
Which means an employer with a correct schedule may still hold everything, and will discover this when a former employee makes a request.
The former employee request
More common than people expect, and it covers everything still held.
An organisation that deleted on schedule answers quickly and the deletion is itself a good finding. One that holds nine years of material answers slowly, at length, and exposes the gap between the schedule and the practice in the same response.
Health records specifically
Shorter than the general record unless a specific duty applies — some occupational exposure records carry long statutory periods.
Special category data held beyond its purpose is the holding with the weakest justification, and it is routinely retained with the general file because nobody separated it.
Email, which has no schedule
The largest post-departure holding and the one least likely to be covered.
A leaver's mailbox retained indefinitely, plus their messages in everybody else's mailboxes, which no retention policy touches at all.
Addressing the mailbox is straightforward. Addressing the copies in other people's mail is genuinely hard, and the honest position is to acknowledge it rather than to claim a schedule that does not reach there.
What drives the periods
Claim windows, statutory requirements, pension obligations, and sector rules. Everything else is preference, and preference defaults to forever.
The former employee request as a test
An organisation that deleted on schedule answers quickly and the deletion is itself a good finding. One holding nine years answers slowly and exposes the gap between its schedule and its practice in the same letter.
Email has no schedule
The largest post-departure holding and the one least likely to be covered. The mailbox is solvable; the copies in everybody else's mail genuinely are not, and saying so is more honest than claiming otherwise.
Shorter than the general file unless a statutory duty applies. Special category data held beyond its purpose has the weakest justification of anything in the file, and it is retained with the rest because nobody separated it.
Why practice diverges from schedule
Nobody deletes. The HR system may purge, the shared drive does not, the email archive does not, and the payroll provider keeps its own copy under its own rules.