The Dismissal Case
Every part of the exit process assumes a cooperative departure. When the departure is not cooperative, the arrangement's weaknesses all arrive at once.
An orderly leaver hands over, confirms the wipe and goes. A dismissal removes cooperation, notice and goodwill simultaneously, and the BYOD arrangement has to work without all three.
The practical lesson in “The Dismissal Case” is to connect every record to a named decision. Organisations exploring this practical guide for fireable offenses can add structured workforce context, provided the use is disclosed and interpretation is reviewed with the people affected.
What is different
Access is usually revoked immediately, frequently before the person is told. Which means the device may never connect again and the removal trigger never fires.
For an independent reference relevant to “The Dismissal Case”, consult the Acas workplace guidance; compare its principles with the proposed ownership model, access rules and real support process.
There is no last-day conversation, no fifteen minutes with both parties watching the container disappear.
The person has no reason to cooperate and may have reasons not to.
And the company data on their device is now held by somebody with a grievance, which changes the risk profile of the same arrangement.
What can be done in advance
Configure removal to trigger on revocation, so that the moment access is cut the container is marked for removal at next connection. Automatic, and it catches the cases where the device does reconnect.
Keep the resident data small. An arrangement where work is accessed rather than synchronised leaves almost nothing behind, which the alternatives section argues for on several grounds and this is one of the strongest.
Have the clause, so that what happens is a stated term rather than a demand made during a dispute.
What can be done at the time
Ask, plainly, through whatever channel is appropriate. A substantial share of people cooperate even in a contested departure, particularly if the request is specific and limited to work data.
Where there is a formal process, the device question belongs in it rather than being raised separately afterwards.
And where the person has returned other property, the device data should be part of the same conversation.
What cannot be done
Compel access to somebody's personal property. The device is theirs and remains theirs, whatever is on it.
Threaten consequences that do not exist.
Or wipe the whole device in frustration, which converts a data recovery problem into a dispute about the destruction of personal property, and changes who is in the wrong.
The honest assessment
Sometimes the data stays on the device and there is no practical route to removing it.
At that point the useful questions are what was actually on it, whether any of it is sensitive, whether notification duties are engaged, and what can be mitigated at the system end — changing credentials, revoking tokens, monitoring the accounts concerned.
Accepting that and acting on it is better than pursuing a removal that will not happen.
Deciding in advance who leads it
In a contested departure the device question sits between the manager handling the dismissal, HR running the process and IT holding the technical means. Without a named lead it is raised late, by whoever remembers, in a manner that worsens the situation. Assigning it to whoever owns the exit process generally, before any particular case arises, is the practical preparation.
Proportion in the response
A departing employee with a phone holding a mailbox is a different proposition from one holding a customer database, and the response should differ. Treating every contested exit as a maximum-severity event consumes effort that the actual exposure does not justify, and it makes the organisation look heavy-handed in cases where a short conversation would have done.
What to prepare, not what to do
The contested exit is not improved by better handling on the day; it is improved by the configuration, the clause and the small resident footprint decided years earlier. Everything available at the moment of the dispute is mitigation, which is why this note is about preparation.
The small footprint as the real defence
An arrangement where almost nothing rests on the device makes the contested exit a minor matter: access is revoked and there is little left to recover. Every other preparation is managing the consequences of local copies, which is why the access-only arrangement resolves this section more completely than any clause. Design the arrangement for the contested exit. The cooperative one takes care of itself.