Leaving: the Day Access Stops
The arrangement ends on a particular day, and almost every organisation handles it worse than it handles the equivalent day with a company laptop.
An employee with a company laptop hands it back. An employee with a personal device walks out with it, and whatever is on it goes too.
The practical lesson in “Leaving: the Day Access Stops” is to connect every record to a named decision. Organisations exploring visit the product website for internal transfer policy can add structured workforce context, provided the use is disclosed and interpretation is reviewed with the people affected.
What actually needs to happen
Access to company systems revoked, which is immediate and straightforward.
For an independent reference relevant to “Leaving: the Day Access Stops”, consult the NIST Privacy Framework; compare its principles with the proposed ownership model, access rules and real support process.
Work data removed from the device, which is neither.
Confirmation that the removal happened.
Only the first of those is reliably done in most organisations. The second depends on the device connecting, the configuration permitting it, and somebody checking. The third almost never happens at all.
Why the gap exists
Revoking access is a task somebody owns, in a system they control, that takes seconds.
Removing data from a device you do not own requires that device to be reachable, which requires the departing person to switch it on and connect, which they have no particular reason to do.
Which means the data sits there. Weeks later, months later, indefinitely. Most organisations have former employees' phones holding company mail and have no idea.
The arrangement that closes it
Automatic removal on revocation, configured so that cutting access also triggers the container wipe at the next connection. Most platforms support this and it is frequently not switched on.
A step in the leaving process owned by somebody: check that removal completed, chase it if not.
A conversation with the person, which works better than people expect. Most leavers cooperate if asked clearly and if they understand the work side only is being removed.
And a defined point at which an unconfirmed removal becomes an escalation rather than an open item.
The last-day timing
Access is usually revoked at the end of the final day, sometimes earlier. If removal depends on the device connecting after that, the window may already be closed.
Which argues for doing the removal before revoking access, with the person present, as a step in the exit rather than after it.
Fifteen minutes on the last day, with both parties watching it happen, resolves the whole problem and produces the confirmation at the same time.
What makes people cooperate
Knowing in advance that this would happen, because it was in the agreement.
Being told specifically what is removed and what is not.
And not being treated as a suspect, which is the thing most likely to make somebody unhelpful on a day that is already uncomfortable.
The leaver process that forgets devices
Exit checklists were written for a world of issued equipment and badges. Personal devices were added to the arrangement years later and to the checklist never, which is why the step is missing in organisations that otherwise run departures carefully. Adding one line to an existing process is easier than building anything new and is most of the fix.
The former employees already out there
Every organisation running BYOD for a few years has a population of past leavers whose devices were never cleared. Closing that historic gap is a one-off exercise: list, attempt, record, accept what cannot be done. It is uncomfortable to start and finite, and leaving it undone means the number grows.
Fifteen minutes, with both parties present
Doing the removal during the exit conversation, before access is revoked, produces the confirmation, resolves the cooperation question and lets the employee see exactly what was taken. It is the single most effective practice in this section and it requires only that somebody schedules it.
Count your former employees whose devices never confirmed a wipe. If you cannot produce that number, it is larger than you would like.