Deleting data in regulated industries requires almost nothing. No form, no second opinion, usually no record that it happened. Meanwhile every organization I have worked in has a careful process for adding things: a new field needs a reason, a new form needs a sign-off, a new report gets reviewed by someone who did not build it.
I find that backwards. Adding a field creates work, and removing one destroys evidence. Only one of those is reversible.
Why the asymmetry exists
It is not carelessness. Deleting data in regulated industries simply looks like nothing, because additions are visible and removals are not. When you add a field, everyone sees it on the form tomorrow. When you delete one, nothing appears; the form is simply shorter, and nobody outside the room knows anything happened.
So governance forms around the visible act, because that is the one people notice. Meanwhile the act with the permanent consequence goes unremarked. In other words, we govern what interrupts us rather than what matters.
There is a quieter reason too, and it is worth saying plainly. Deleting feels like tidying. It reads as good housekeeping rather than as a decision, and nobody asks permission to tidy.
What actually gets lost
Not just the values. That part is obvious, and it is not the worst of it.
What goes is the ability to interpret everything around them. Say a field recorded who verified a batch. Someone removes it, and now two years of batch records show that verification happened without showing who performed it. The remaining data is not wrong. It is simply no longer sufficient, and nobody discovers that until somebody asks.
The gap is silent as well. A deleted field leaves no marker saying a field used to be here. Therefore the person reviewing those records in 2028 does not see an absence. They see a complete record that happens to be missing something they have no way to know about. Anyone who has tried to reconcile a process that lived half in a spreadsheet will recognize the feeling.
The three questions I would ask first
Not a committee. A pause, and three questions that take about a minute between them.
- What is the retention obligation on this data, and has it actually ended?
- Does anything else depend on this, meaning a report, a rule, an export, or a process nobody has mentioned?
- Can we retire this rather than remove it, and if not, why not?
That third question matters most, because the answer is usually yes and nobody thought to ask. A field can generally be deactivated while its data stays intact, and a record can generally be archived instead of deleted. When those options exist and go unused, the deletion was not necessary. It was just the first thing on the menu. I wrote about the mechanics of retiring a field rather than erasing it on Tuesday, though a mechanism only helps if somebody stops long enough to choose it.
What the regulator actually expects
Worth noting that regulators are not asking for hoarding. They are asking for deliberateness, and those are different things.
The Office of the Privacy Commissioner of Canada made this concrete in its March 2026 findings on retention practices, where the issue was not that information had been kept or discarded, but that the organization could not demonstrate its treatment of that information met the standard it claimed. The international records management standard, ISO 15489, frames disposition the same way: as a documented decision with a rationale, rather than an operational reflex.
Both point at the same thing. What gets examined afterward is not the outcome so much as whether anyone decided it.
Why deleting data in regulated industries should feel uncomfortable
Here is the part I expect disagreement on. I think permanent deletion should be uncomfortable to use. Not blocked, because legitimate reasons exist, including erasure requests you are legally required to honour. Uncomfortable.
Most systems make it the smoothest action available. Delete sits next to edit, takes one click, and asks a confirmation question phrased so that yes is obviously the answer. Meanwhile the safer alternative, archiving or deactivating, hides in a settings screen if it exists at all.
Software teaches people what is normal through what is easy. So if deletion is the easiest thing in your system, your team will delete, and no policy document you write will outrank the interface.
Make it a decision, then let people make it
I am not arguing for friction as a virtue. Friction for its own sake gets routed around, and a process nobody follows is worse than no process, because it creates a paper record of compliance that does not exist.
What I am arguing is narrower. Deleting data in regulated industries should leave a trace of having been chosen: who asked, what the retention position was, and why retiring it was not enough. That costs a minute. Reconstructing why a field vanished in 2026 costs considerably more, assuming it can be done at all.
If you are weighing what your own system makes easy, and what that is quietly teaching your team, talk to an expert.
