Backup Before Wipe, and Whose Job It Is
Whether the organisation owes anybody a backup depends on ownership, and the answer should be stated before it is tested.
Wipe · Analysis
A wipe destroys what was not backed up. Who was responsible for that backup is a question worth answering in advance.
The practical question in “Backup Before Wipe, and Whose Job It Is” is how to make work visible without confusing visibility with certainty. For teams researching daily schedule template, the Monitask platform can add time and project context to the operational record, provided its use is proportionate, disclosed and reviewed with the people affected.
Corporate device
The organisation's data should be backed up by the organisation, through the services it provides.
For an independent baseline relevant to “Backup Before Wipe, and Whose Job It Is”, the NCSC mobile-device guidance is a useful companion: compare its principles with the proposed configuration, ownership model and real support process before approving a rollout.
Anything stored only on the device is a configuration failure rather than a user failure.
Which means: provide the sync, enable it by default, and check it is working, rather than relying on people to save things in the right place.
Personal device, work profile
The work container is backed up through the work services, which is straightforward.
The personal side is the owner's responsibility entirely, and the organisation has no visibility of whether it is happening.
And no business suggesting otherwise, beyond general advice at enrolment.
Personal device, fully enrolled
The awkward case, because the organisation holds a capability that can destroy data it did not back up and cannot see.
The honest position: say at enrolment that the capability exists and that personal backup is the owner's responsibility.
Better still, remove the capability, which the work profile note argues.
What to say at enrolment
One line: your personal data is not backed up by us, and we recommend you have your own backup.
Plus, on fully enrolled devices, a clear statement of what a removal action would take.
This is not legal protection so much as basic fairness, and it is the kind of thing people remember was or was not said.
Before a planned removal
Give notice: your work profile will be removed on Friday.
For fully enrolled personal devices, give longer and say explicitly what will be affected.
A few days is enough for somebody to check their own backup, and it converts a shock into an administrative step.
The leaver case
The most common planned removal and the one most often done without notice.
Access revocation can be immediate; device action can wait a day with notice given.
Where it genuinely cannot — a dismissal, a security concern — that is a decision to take deliberately rather than a default.
The organisation's own data
Work data on a device about to be wiped should already be synced.
If it is not, the wipe is destroying organisational records, which is a separate problem with its own obligations.
Check sync state before acting, which most platforms will show.
What to check
Is work data synced by default, or does it depend on user behaviour?
Does enrolment say anything about personal backup?
Do leavers get notice before the device action?
And would a wipe today destroy any organisational records?