The Decision You're Facing
Your team has a record that's outlived its active use. A contract from a closed project, an email thread from a resolved dispute, or a draft report no one references anymore. You're asking the same question legal operations teams ask every day: delete it now, or keep it just in case?
This isn't just an academic exercise. Your choice shapes your discovery footprint, legal costs, and credibility if litigation arises. Courts don't judge you for having records or not having them. They judge you for following a consistent, defensible process.
Let's map the decision.
Key Factors That Affect Your Choice
Three factors drive every retention decision:
Legal or Regulatory Requirement. Does a statute, rule, or industry standard mandate a minimum retention period? If FRCP, SEC regulations, or your state's statute of limitations requires seven years, you can't delete at five. Start here. If a clear requirement exists, your decision is made.
Litigation Anticipation. Have you received a demand letter, a preservation notice, or credible indication that a dispute is forming? Once you reasonably anticipate litigation, you must preserve relevant records regardless of your retention schedule. This isn't optional. It's a legal hold, and it overrides normal disposition.
Operational or Business Need. Does anyone still reference this record for decisions, audits, or ongoing projects? If the record supports active work, keep it until that work concludes. If it's sitting untouched in a folder no one opens, it's a candidate for disposition.
If none of these factors apply, you're in the zone where defensible deletion strengthens your position.
Path A: Delete It Now (Following Your Records Control Schedule)
Choose this path when:
- The record has reached the end of its approved retention period.
- No legal hold or pending litigation affects this category.
- No regulatory requirement mandates longer retention.
- The record serves no active business purpose.
Why this path works: Courts do not penalize organizations for following a reasonable, pre-established retention schedule. They scrutinize irregular cleanup. If your Records Control Schedule says contracts are kept for seven years after expiration, and this contract hit that mark, delete it. Document the disposition and move on.
What you need in place:
- A Records Control Schedule that ties retention periods to clear drivers (statute of limitations, audit cycles, contractual obligations). Not guesses.
- Regular disposition cycles. If you delete sporadically or only when storage fills up, you've lost defensibility. Consistency matters more than the specific timeline you choose.
- Clear documentation of disposition authority. Who approved this schedule? When was it last reviewed? Can you produce that record if asked?
What this path avoids:
Unlimited retention expands your discovery footprint. When you keep everything, opposing counsel reviews everything. That means higher legal costs, longer review cycles, and more opportunities for someone to isolate a sentence from a five-year-old draft and ask you to explain it under oath.
Over-retention also multiplies breach exposure. Sensitive contracts, employee records, and confidential communications remain accessible long after they serve a purpose. If a breach occurs, your liability scales with the volume you've stored.
Path B: Keep It (Because a Legal or Business Factor Requires It)
Choose this path when:
- A statute, regulation, or contractual obligation mandates retention beyond your standard period.
- You've received a legal hold notice or reasonably anticipate litigation involving this record.
- The record supports an ongoing audit, investigation, or active business matter.
- You're in a regulated industry (healthcare, financial services, government contracting) with specific preservation rules.
Why this path works: Defensibility isn't about minimizing storage. It's about following a rational, documented process. If you can explain why you kept a record, you're in a strong position. If you kept it "just in case" without a clear reason, you've created risk without benefit.
What you need in place:
- A legal hold process that identifies affected records and suspends normal disposition. Your team must know what changes when a hold is issued and where preserved records are stored.
- Event-based retention triggers for categories that don't follow fixed timelines. Consider records tied to product lifecycles, warranty periods, or ongoing contracts. These need clear cutoff rules so you know when the clock starts.
- A process for reviewing and lifting holds. Records frozen for litigation don't stay frozen forever. When the matter resolves, you need a documented release process that returns records to normal retention schedules.
What this path avoids:
Premature deletion during a dispute destroys credibility faster than almost any other governance failure. If you delete records after you should have anticipated litigation, you're explaining that decision to a judge. Even if the deletion was accidental, the appearance is terrible.
Path C: You're Not Sure (And That's the Real Problem)
If you can't confidently choose Path A or Path B, you don't have a retention decision problem. You have a governance gap.
This happens when:
- Your Records Control Schedule doesn't cover this record type.
- Retention periods aren't tied to specific legal or business drivers.
- No one knows whether a legal hold affects this category.
- Disposition happens irregularly or only when someone asks about storage costs.
The fix: Don't guess. Suspend disposition for this category until you can document a clear retention rationale. Then update your Records Control Schedule, communicate the change, and resume regular disposition cycles.
Uncertainty weakens your position in litigation. Consistency strengthens it.
Summary Matrix
| Factor | Delete Now | Keep It | Fix Your Process First |
|---|---|---|---|
| Retention period | Expired per approved schedule | Active or required by law/contract | No documented schedule exists |
| Legal hold status | No litigation anticipated | Hold issued or dispute forming | Team doesn't know how to check |
| Business need | No active reference or use | Supports ongoing work/audit | No one can explain why it's kept |
| Regulatory requirement | None applicable | Specific rule mandates retention | Unclear which rules apply |
| Disposition process | Regular, documented cycles | Suspended due to hold | Sporadic or reactive only |
Your records don't just tell your organization's story. In litigation, they become evidence that opposing counsel will examine for consistency, gaps, and adherence to policy. The question isn't whether you'll face scrutiny. It's whether your process can withstand it.
