Offboarding checklist redaction is the removal of personal identifiers from a leaver's exit task list. The same sheet that proves an account was closed also records the account name that was closed, which is why UK GDPR Art. 32(1)(b) treats the ongoing confidentiality of your processing systems as a security duty in its own right. anonym.plus marks each name, login, and contact on your device, so the steps stay readable while the person behind them is hidden.
When this applies
An exit list ties one named worker to their logins, their building pass, and their kit. Left in a shared folder, it is a map for anyone who wants a way in, and unauthorised access to a computer is an offence under s.1 of the Computer Misuse Act 1990 whatever the motive. The archived copy also outlives its purpose: Art. 5(1)(e) says personal data may be kept no longer than the offboarding it evidences requires.
How anonym.plus handles it
- Open the checklist in anonym.plus on your device.
- The tool flags the worker, logins, and contact lines.
- Local OCR reads a scanned, signed sheet.
- Keep the task names and status columns intact.
- Swap or black out the confirmed identifiers.
- Save the clean sheet locally.
What you need to provide
- The exit task list (PDF, DOCX, XLSX export, TXT).
- An operator (Replace keeps the steps readable).
- Optional allow-list for asset tags you must keep.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | Liam O'Connor → [LEAVER] |
| Contact | EMAIL_ADDRESS | l.oconnor@example.co.uk → [EMAIL] |
| Identifiers | NATIONAL_ID | pass 88312 → [PASS] |
| Contact | PHONE_NUMBER | ext 4410 → [PHONE] |
| Dates | DATE_TIME | exit 30/06 → [DATE] |
| Location | LOCATION | desk 4B → [DESK] |
Compliance achieved
- Serves UK GDPR Art. 32(1)(b), the duty to ensure the ongoing confidentiality and integrity of your processing systems.
- Removes the live account names that make a stray copy useful to anyone committing the Computer Misuse Act 1990 s.1 offence of unauthorised access.
- Applies storage limitation under UK GDPR Art. 5(1)(e) to a sheet that is usually archived and forgotten.
- Works towards the anonymity bar in UK GDPR Recital 26 before the checklist reaches IT or a supplier.
- AES-256-GCM protects the working copy at rest, and batch mode clears up to 20 sheets when a team leaves at once.
Anonymise offboarding checklists offline — see plans & start free →
Limitations & cautions
A checklist can still betray a person through a unique asset tag or desk, especially where the same tag appears on the equipment return log. The tool flags named items. Use the allow-list with care, and confirm nothing in a kept column points back to one worker.
Frequently asked questions
Why redact a routine exit list?
It links one named person to logins, a pass, and assets, which is exactly the confidentiality Art. 32(1)(b) asks you to protect. Stripping those details keeps the process record without the map.
Can I keep the asset tags?
Yes, via the allow-list, but only if a tag cannot single out the worker. A serial that also appears on the return log will re-link the two files.
Does processing need internet?
No. The whole run is offline, so the sheet never leaves your machine.