Preserve First, Panic Later: Building a Litigation Hold Program Before the Demand Letter Arrives

Every litigator has a version of the same war story: a demand letter arrives, everyone scrambles, and six weeks later someone learns that an IT migration quietly purged the email archive — or that a departing manager's laptop was reimaged per standard policy. No one acted in bad faith. The company simply never built the machinery it needed.

Litigation holds are where legal strategy meets operations, and that intersection is where mid-sized companies are most exposed. The good news is that the fix is procedural, not heroic.

When the Duty to Preserve Actually Attaches

Under federal law, the obligation to preserve relevant evidence arises when litigation is "reasonably anticipated" — a standard that is deliberately earlier than the moment a complaint is filed. A threatening letter from a former business partner, an internal complaint of discrimination forwarded to HR, a regulatory inquiry requesting documents: each of these can start the clock.

The 2015 amendments to the Federal Rules of Civil Procedure made clear that courts expect reasonable, proportionate preservation efforts — not perfection. But reasonableness presupposes a program. A company that cannot show it had any process will find courts far less sympathetic than one that can point to a documented, consistently applied protocol.

The critical mistake is treating the duty as reactive. "We'll deal with it if it comes" is not a strategy; it is a spoliation motion waiting to be drafted by opposing counsel.

Why Informal Holds Fail

Most failed preservation efforts share the same anatomy. A verbal instruction goes out — "don't delete anything related to Project X" — with no written scope, no custodian list, and no follow-through. Six months later, key personnel have moved on, auto-delete policies have run their course, and nobody remembers who was told what.

A defensible hold requires four things: a written notice identifying the trigger and subject matter; a defined custodian list; suspension of routine deletion for the systems those custodians touch; and periodic acknowledgments and refreshers. Anything less is a memory exercise, and memory exercises lose motions.

An Operational Framework You Can Hand to the Business

General counsel cannot run preservation alone. The hold lives or dies with the operations, IT, and HR teams who actually control the data. Here is the framework to institutionalize now, before any trigger event.

Step 1: Build the custodian map in peacetime. Identify, by role, who touches which categories of business records — sales, finance, engineering, HR. When a hold triggers, you select custodians from a map rather than reconstructing one under pressure.

Step 2: Inventory your data systems, including the awkward ones. Email and shared drives are the obvious layer. The gaps live elsewhere: Slack and Teams channels, text messages on personal devices used for business, cloud collaboration tools, and — critically — third-party vendors. Payroll processors, CRM providers, e-signature platforms, and offsite records storage all hold data you are obligated to preserve but may not control directly.

Step 3: Draft the hold template before you need it. Include a plain-language description of the matter type, a do-not-delete instruction covering all formats, and an explicit acknowledgment requirement. Legal jargon that operations managers cannot parse is a failure mode in itself.

Step 4: Suspend, don't just instruct. A hold notice that says "don't delete" while the email system auto-purges at 90 days is internally contradictory. Coordinate with IT to lift auto-deletion, mailbox quotas, and device wipe schedules for in-scope custodians.

Step 5: Re-acknowledge on a schedule. Holds that last years without refresh decay. Quarterly acknowledgments cost nothing and demonstrate diligence.

The Retention Checklist Most Mid-Sized Companies Lack

Use this as a starting audit:

• Email and messaging: Defined retention period; ability to suspend auto-deletion per custodian; policy on business texts.
• Documents and cloud storage: Version retention; offboarding process that preserves rather than purges departed employees' files.
• Vendor records: Contract terms addressing data return and preservation; a current list of vendors holding company records.
• HR and finance: Litigation-relevant records (performance files, payroll, expense reports) retained on a documented schedule.
• Governance: A named owner of the hold process; written procedures; training for department heads.

The Strategic Payoff

Companies with a standing preservation program respond to trigger events in days, not weeks. They reduce the risk of sanctions, strengthen their negotiating position, and — not incidentally — spend far less on forensic recovery and emergency e-discovery.

The demand letter is not the time to design the system. Build it while the stakes are hypothetical, so that when the stakes become real, your only job is execution.