Demand Letters and Litigation Holds Before a Lawsuit Is Filed

The moment a dispute becomes real, two things happen at once. You gain the option of writing to the other side, and you acquire a legal duty to stop destroying evidence. Most parties act on the first and overlook the second, which is how a strong claim becomes a sanctions problem.

The trigger for both is the same standard: litigation is reasonably anticipated. That is an objective test applied to what the party knew at the time. It does not wait for a complaint, a lawyer, or a formal decision to sue.

One trigger, two obligations

A litigation hold is a directive that suspends routine deletion and instructs people who hold potentially relevant information to keep it. It is a common-law obligation rather than a rule requirement — no federal rule says "issue a hold" — but the consequences of failing to do so are set out in the federal rules, and courts assess the duty as of the date the party should have recognized the dispute.

The demand letter is the offensive move: a written statement of the claim, the facts, the relief sought, and a deadline. It can produce a settlement without a filing fee, satisfy a contractual notice condition, or establish a date for interest or statutory damages. It also announces, in writing, that the sender anticipated litigation. Anyone who sends a demand letter and later deletes relevant records will be asked why the letter did not trigger a hold on the sender's own files. The answer is usually unsatisfying.

Recipients face a mirror image. Receiving a credible demand is one of the clearest events that makes litigation reasonably foreseeable. A recipient who forwards a demand letter to three colleagues and takes no preservation step has generally started the clock without starting the process.

When the duty attaches, and how far it reaches

Reasonable anticipation is a judgment call made under pressure, and it is reviewed later by someone who knows how the dispute turned out. Events that commonly cross the line include a demand or cease-and-desist letter, a formal internal complaint, a regulator's inquiry, a serious incident with an obvious claimant, a counterparty's notice of default, and a decision by the party itself to sue someone. Ordinary commercial friction usually does not.

Scope is the harder question. The duty covers information that is relevant to the anticipated claims and defenses, held by people likely to have it — not every record in the organization. Over-broad holds are their own risk: they are expensive, they degrade compliance because custodians stop taking them seriously, and they are frequently abandoned in practice, which is worse than a narrower hold executed properly.

Scope also has to follow the data rather than the org chart. Electronically stored information now sits in collaboration platforms, ticketing systems, chat tools with default retention windows measured in days, personal devices used for work, and vendor-hosted systems the organization does not control. A hold that names only email and shared drives will miss the categories most likely to matter, and the categories most likely to disappear on their own.

Deadline discipline: auto-deletion is the single most common cause of preservation failure. Ephemeral messaging and short-retention chat settings continue destroying data while the hold memo circulates for approval. Suspend the deletion job first; refine the scope afterward.

What a defensible hold notice contains

• A plain statement that a dispute is anticipated or pending, with enough factual context that recipients can recognize relevant material.
• Named custodians and, separately, the systems and administrators who must act on retention settings.
• Concrete categories with date ranges and examples, rather than a request to preserve "all documents relating to the matter."
• Express instruction to stop deletion, including auto-delete rules, retention policies, device refresh cycles, and departing-employee wipe procedures.
• Coverage of non-email sources: chat, text messages, personal devices used for work, collaboration platforms, voicemail, and third-party systems.
• A named contact for questions and a required acknowledgment from each recipient.
• A reminder schedule and a documented process for adding custodians as the dispute develops.
• A record of when the hold issued, who received it, who acknowledged it, and what systems were changed in response.

The acknowledgment and the reminder are what separate a hold that works from a memo that was sent. When a preservation dispute reaches a judge, the question is not whether a notice existed. It is whether the party took reasonable steps, and the evidence of reasonable steps is the tracking record. A party that can show issuance, acknowledgment, system changes, periodic reissuance, and custodian additions is in a substantially different position from one that produces a single undated email.

What a demand letter does, and what it costs

A well-built demand letter states the parties and the relationship, the facts in chronological order, the legal basis without a treatise, the specific relief sought with a number where possible, a response deadline, and the consequence of silence. It is written on the assumption that a judge will read it later, because a judge frequently does.

The costs are real and are usually underweighted. Sending the letter can supply the actual controversy a recipient needs to file a declaratory judgment action first, in a court of the recipient's choosing — a common outcome in intellectual property disputes and a genuine strategic loss, because the forum question shapes everything that follows. Our brief on personal jurisdiction and venue covers how that choice is contested.

Other costs recur. Statements in the letter can be used against the sender if they turn out to be inaccurate; the protection given to compromise negotiations under the federal evidence rules is narrower than most senders assume and does not sanitize every assertion. A letter that threatens criminal referral or regulatory complaint to extract payment creates exposure of its own in several states. And the letter alerts the recipient, who may then move assets, harden positions, or — most commonly — retain counsel and stop talking.

Against that, some demands are not optional. Contracts frequently require written notice and a cure period before any claim may be brought, and a number of states impose pre-suit notice requirements in defined categories such as construction defect claims and certain consumer matters. Where a mandatory step exists, skipping it can defeat an otherwise sound claim. Check the contract and the statute before deciding whether the letter is a tactic or a condition.

The order of operations

1. Trigger event

   An incident, complaint, notice, or internal decision makes litigation reasonably foreseeable. Record the date and the reason; this is the anchor for every later argument about preservation.

2. Within days, not weeks

   Identify likely custodians and systems. Suspend auto-deletion on the systems that destroy data fastest, before the full scope is settled.

3. Hold issued

   Distribute the written notice, collect acknowledgments, and instruct system administrators separately from custodians.

4. Before the demand goes out

   Confirm the sender's own house is in order. A demand letter is an admission of anticipation, and the sender's preservation record becomes discoverable in the same dispute.

5. Demand delivered

   Send by a method that proves receipt, to the person or address the contract designates. Calendar the response deadline and the escalation decision.

6. Ongoing

   Reissue the hold periodically, add custodians as facts develop, and release the hold only by a documented decision when the matter is genuinely closed.

Sequencing matters because the two activities have different failure modes. A late demand letter costs leverage. A late hold costs evidence, and lost evidence cannot be recreated by working harder afterward.

Questions the desk gets

Does a demand letter have to come from a lawyer?

No. A party can write its own demand, and in small commercial disputes that is often sensible. What changes with counsel is not authority but calibration: what to claim, what to omit, which deadline to set, and whether the letter creates a forum risk. A letter that overstates the claim or misstates the facts can be produced later by the other side, and that risk exists regardless of who signed it.

Can we keep deleting under our normal retention policy?

Only for material outside the hold's scope. A documented retention schedule applied consistently is a defensible practice and courts recognize it. What is not defensible is continuing to run deletion against categories and custodians the hold covers, or accelerating deletion after the dispute surfaces. Suspend the relevant jobs, document what was suspended and when, and keep the rest of the program running normally.

What happens if data was already lost before anyone thought about a hold?

The analysis turns on when the duty attached, whether reasonable steps were taken, and whether the information can be restored or replaced from another source. Loss occurring before the duty attached is generally not sanctionable. Loss after it attached is assessed under a framework that treats prejudice and intent very differently, which our brief on electronic discovery and sanctions works through in detail.

Do holds apply to employees' personal phones?

They can, where work communications actually occur there. The practical obstacles are control and privacy: the organization may have no technical ability to preserve a personal device, and employment and privacy law limit what it may demand. The workable answer is usually a documented instruction to preserve, a defined collection process for relevant threads, and an honest record of what could not be reached — not a silent decision to ignore the source.

Does an arbitration clause change any of this?

It changes the forum and the discovery rules, not the preservation duty. Parties heading to arbitration still face spoliation consequences, applied by the tribunal under its own powers and the governing law. Whether that forum is preferable for a given dispute is a separate question addressed in our comparison of arbitration and court.

What to do next

Treat the trigger date as the organizing fact. Write it down, with the reason, on the day it happens. Everything afterward — the scope of the hold, the credibility of the demand, the defensibility of the preservation record — is measured against it.

Then run the two tracks in parallel rather than in sequence. Preservation is defensive, cheap at the start, and expensive to fix late; spoliation findings have changed the outcome of otherwise strong cases. The demand is offensive, reversible, and worth delaying by a week if that week is spent confirming that the sender's own records are intact.

For the procedural machinery that follows a filing, the discovery obligations in the federal disclosure and discovery rule and the consequences framework in Rule 37 are the primary texts, and the federal judiciary publishes general material on how civil cases proceed. Incident-driven disputes often carry parallel notification duties, covered in our brief on data-breach response. Related material sits in the Litigation & Dispute Resolution desk.

ATLAS Legal Briefing is an independent publisher, not a law firm. This is general information about civil procedure and preservation practice, not advice about any particular dispute.