What Changes on the Last Day
Access ends, the basis for most processing narrows, and almost nothing actually happens in the systems.
EXIT DATA CHECKLIST
Separate from the HR offboarding list, which covers property
- AccessEvery system, including ones not in the main directoryThe list is usually incomplete
- MailboxRetained, forwarded, or delegatedEach has a different justification and duration
- Personal deviceWork data removed, confirmedWhere the device is theirs
- ImagesRemoved from site and internal useUsing the list from the image register
- DirectoryEntry removedIncluding cached and printed versions
- Shared drivesTheir folders reassigned or archivedNot left as an orphan with their name
- Retention clockStarted, with the trigger date recordedThis is the step that never happens
- Manager notesTransferred or deletedNot silently inherited
The last day triggers a set of data consequences that are separate from the HR offboarding process, and most organisations run the second without the first.
The practical lesson in “What Changes on the Last Day” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching limbic resonance in relationships, how teams evaluate limbic resonance in relationships can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
Access
Revoked the same day, across every system.
For a separate benchmark relevant to “What Changes on the Last Day”, consult the CIPD discipline and grievance 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.
The difficulty is the list. Most organisations can revoke the main systems and miss three: a supplier portal registered in the person's name, a shared account whose credentials they knew, a cloud service procured by their team.
The access register is usually incomplete, and the exit is the moment that proves it.
The mailbox
The decision nobody makes deliberately.
Options are deletion, retention without access, forwarding to a successor, or delegated access for a period. Each has a different justification and a different duration.
Forwarding somebody's mail to their replacement indefinitely means the replacement reads personal correspondence sent to a person who no longer works there. A bounce-back with a redirect address is almost always the better arrangement.
The basis narrows
While employed, most processing rests on contract necessity or legitimate interests connected to the employment.
After departure, the contract basis largely falls away. What remains is narrower: legal obligations around pay and tax, defence of potential claims, and genuine ongoing purposes like pension administration.
Which means some processing should stop on the last day and usually does not, because nobody reviews it.
The retention clock
The step that is missed most often.
Retention periods for employment records run from the leaving date. If nobody records that date against the records, nothing is ever deleted, because the trigger never fires.
A single field — leaving date, recorded in the systems holding their data — is what makes the whole retention schedule operate.
What the HR checklist usually covers
Property, final pay, references, notice. All necessary and none of it about data.
Adding a short data section to the existing checklist is easier than creating a second process, and it is the arrangement that actually gets followed.
The mailbox decision
Deletion, retention without access, forwarding, or delegated access for a period. Forwarding indefinitely means the successor reads personal correspondence sent to somebody who no longer works there. A bounce-back with a redirect is almost always better.
Adding it to an existing checklist
A short data section on the HR offboarding list is easier than creating a second process, and it is the arrangement that actually gets followed.
The field that makes retention work
The leaving date, recorded against the records in every system holding them. Without it the clock never starts and nothing is ever deleted, whatever the schedule says.
The access list is usually wrong
Most organisations revoke the main systems and miss three: a supplier portal in the person's name, a shared account whose credentials they knew, a service procured by their team.
The basis narrows on the last day
Contract necessity largely falls away. What remains is narrower: legal obligations, defence of claims, genuine ongoing purposes like pension administration. Some processing should stop and usually does not.
The access list the exit proves
Most organisations discover at this point that their register is incomplete. The missing three are always the same kinds: a portal in the person's name, a shared credential, a service their team bought.