What is defensible deletion — and why it matters for ediscovery

Defensible deletion is the practice of permanently destroying data in accordance with a documented, consistently applied retention policy, in a manner that can withstand legal, regulatory, or judicial scrutiny if challenged. It’s not enough to simply delete the data. Defensible deletion means the organization can show that it followed a principled, good-faith process rather than destroying information selectively or opportunistically.

In the context of ediscovery, defensible deletion is less about the act of deletion itself and more about the program behind it. Organizations that maintain clear retention schedules, apply them consistently, and suspend them appropriately when litigation arises are far better positioned than those that either delete haphazardly or, conversely, keep everything indefinitely.

Why “save everything” isn’t a strategy

It’s tempting to treat unlimited data retention as a safe default. Storage is cheap, the thinking goes, so why not keep it all? But that instinct creates its own set of problems — and in some cases, its own legal exposure.

For one, the scope of ediscovery tracks the scope of your data. The more you retain, the more you may be obligated to search, review, and produce in litigation. Keeping years of Redundant, Obsolete, or Trivial (ROT) data doesn’t just cost money in storage — it multiplies the cost of every future ediscovery event. A well-run defensible deletion program reduces that burden before litigation ever begins.

Another more pressing reason why organizations can’t just save everything: Privacy regulations like the GDPR and CCPA actually require data deletion. Under the GDPR’s data minimization and storage limitation principles, organizations are obligated to retain personal data only as long as necessary for its original purpose. CCPA grants consumers the right to request deletion of their personal information. Keeping data beyond its useful life, or beyond what regulations allow, is no longer a neutral choice. It’s a compliance risk.

The modern view is that sound data management requires both a disciplined deletion program and a reliable preservation process — and that these aren’t in conflict. They operate on different timelines and serve different purposes.

What makes deletion “defensible”?

Not all deletion is defensible. Deleting files in anticipation of litigation, deleting selectively to remove inconvenient documents, or deleting without any documented policy are all scenarios that can draw sanctions from courts. What distinguishes defensible deletion from problematic deletion comes down to four elements:

A written retention schedule. The foundation of any defensible deletion program is a retention policy that defines how long each category of data should be kept, and when it should be destroyed. This schedule should reflect both business needs and any applicable regulatory requirements for specific data types or industries.

Consistent application. Courts are far more skeptical of deletion that appears targeted or selective. A retention policy applied uniformly across the organization is what makes the process defensible. Sporadic or partial adherence undermines the entire program.

Documentation. Organizations should be able to show that data was deleted according to policy, when it was deleted, and who authorized it. This audit trail is what transforms a deletion event from a liability into a demonstration of good-faith records management.

A legal hold process that suspends deletion. This is where defensible deletion and ediscovery intersect most directly. When litigation is reasonably anticipated, normal deletion activity must stop. The legal hold process is the mechanism for doing that — and a mature defensible deletion program treats legal hold integration as a core requirement, not an afterthought.

Legal holds and the moment preservation begins

A common misconception is that the obligation to preserve evidence doesn’t arise until a formal legal hold notice is issued. That’s not accurate — and the gap between when the duty attaches and when a legal hold is actually sent can be legally significant.

Under established case law, the duty to preserve evidence arises when litigation is “reasonably anticipated” — not when a complaint is filed, and not when a legal hold notice is distributed internally. A formal legal hold is the mechanism an organization uses to fulfill that duty, but it doesn’t create the duty itself.

In practice, this means a serious employee complaint, a threatening letter from opposing counsel, a regulatory inquiry, or even an internal escalation about a significant dispute can trigger a preservation obligation before any lawsuit exists. Organizations that continue running routine deletion after receiving a demand letter — because no formal legal hold had been issued yet — have faced spoliation sanctions as a result.

This is one of the more consequential points for in-house legal teams and legal ops professionals: The legal hold decision is often a judgment call made in real time, and making it too late can have the same consequences as not making it at all. A defensible deletion program needs to account for this by building clear escalation paths that connect business-level signals (a serious complaint, a regulator’s inquiry) to the legal team’s preservation decision-making process.

Defensible deletion as ediscovery readiness

Defensible deletion is often categorized as an information governance practice, as it lives in the space of records management, data lifecycle management, and compliance. But its downstream effect on ediscovery is substantial.

Organizations that run mature deletion programs tend to have smaller, better-organized data footprints when litigation begins. They’ve reduced their ROT data. Their retention schedules create a logical map of what data exists and why. Their legal hold processes are already connected to deletion workflows, which means suspension is faster and more reliable. And because their deletion has been documented, they’re better positioned to defend against spoliation claims — demonstrating that any missing data was destroyed pursuant to a routine, good-faith policy, not in response to litigation.

The relationship between information governance and ediscovery is worth understanding in its own right. (Nextpoint’s blog on the IGRM and EDRM frameworks covers this in more depth.) For now, the key point is that defensible deletion isn’t separate from ediscovery preparedness — it’s part of what makes an organization ready to begin litigation.

From pre-litigation to collection: Your next step

Defensible deletion is about managing data before litigation begins. Once a legal hold is in place and discovery is underway, the next challenge is collecting that data strategically — without over-collecting, breaking chain of custody, or blowing up your review budget.

The Nextpoint Data Collection Checklist walks through the key questions and best practices for getting collection right, from identifying custodians to phasing your collection strategy. It’s a practical complement to the information governance work that defensible deletion is part of.

Frequently asked questions about defensible deletion

What is the difference between defensible deletion and a legal hold? Defensible deletion is a proactive, ongoing records management practice — the routine destruction of data according to a documented retention policy. A legal hold is a reactive measure that suspends that routine when litigation is reasonably anticipated. The two are designed to work together: Defensible deletion reduces the volume of data an organization carries into any legal matter, while the legal hold process ensures that relevant data is preserved once a matter arises.

When does the duty to preserve evidence begin? The legal obligation to preserve evidence attaches when litigation is “reasonably anticipated” — not when a lawsuit is filed, and not when a formal legal hold notice is issued. An internal legal hold notice is the mechanism for fulfilling that duty, but the duty itself can arise from a demand letter, a regulatory inquiry, a serious employee complaint, or any other circumstance in which a reasonable person would anticipate litigation might follow.

Can deleting data ever constitute spoliation if you have a retention policy? Courts have generally held that routine deletion pursuant to a consistently applied retention policy does not constitute spoliation, even if the deleted data later becomes relevant to litigation — provided deletion was suspended once litigation was reasonably anticipated. The key factors are consistency (the policy was applied uniformly, not selectively), documentation (the deletion can be shown to have followed the policy), and timing (deletion stopped when it should have).