The litigation hold — when the duty to stop deleting starts, and how far it reaches

Nothing in the federal rules tells a business to keep everything forever. They fix a moment after which losing things has consequences, then ask whether what you did after that moment was reasonable. Almost every fight about destroyed evidence is those two questions in that order, and the first is where small businesses lose.

The trigger is anticipation, not service

The duty to preserve is a common-law duty, not written into the Federal Rules of Civil Procedure — which is why people looking for a rule number never find one. The Sedona Conference states the test in the form most courts work from: a reasonable anticipation of litigation arises when an organisation is on notice of a credible probability that it will become involved in litigation, seriously contemplates initiating litigation, or takes specific actions to commence litigation.

Read the second and third limbs again: they point at the person thinking about suing, not the person being sued. Sending a demand letter does not start a clock only against the recipient — it is good evidence that the sender seriously contemplates litigation, and their own files come under the duty from that moment.

The Seventh Circuit worked this ground in 2025. In Pable v. Chicago Transit Authority, decided 28 July 2025, the plaintiff contacted attorneys about his termination on 29 October 2018 and deleted his entire Signal thread with a colleague four days later. He did not sue for another year. The district court found his duty to preserve had been triggered before the deletion, and the court of appeals held that was not clear error. Four days of contact with a lawyer was enough.

What the notice says, and who has to receive it

A hold notice is an internal instruction to stop the normal disposal of information. It has no statutory form. What makes one effective is that people can act on it without a second conversation.

It goes to more people than the ones named in the dispute: the custodians who hold the documents, whoever administers the systems, and third parties holding your data on contract — the bookkeeper, the IT provider, the cloud platform, each of whom needs their own short compliance notice. A hold that never reaches the person who can switch off the retention rule is a hold in name only.

The duty does not stop at your email server

Scope is decided by Rule 34's phrase possession, custody, or control, not by what feels like company property. Laptops, the work phone, the shared drive, the accounting system and the chat workspace are obviously in. So are the tools people actually used, which in most small businesses means text messages and a group chat rather than email.

For an owner-managed business that cell mostly collapses: the company cannot say it lacks control over the director's phone when the director is the company. The question worth asking is narrower — which accounts did we run this job through, and who else was on them.

Auto-delete is where a small business actually loses

The 2015 committee note to Rule 37(e) is explicit that routine operation is not a shield: the prospect of litigation may call for reasonable steps to preserve information by intervening in that routine operation. Nobody has to decide to destroy anything. The settings do it.

The ones that catch people are ordinary consumer defaults. On an iPhone, Settings › Apps › Messages › Keep Messages offers 30 Days, 1 Year or Forever, and Apple warns that anything other than Forever removes conversations and their attachments automatically once the period elapses — and that with Messages in iCloud on, deleting on one device deletes across all of them. Chat platforms carry workspace retention rules an administrator set once and forgot. Signal and WhatsApp both offer disappearing messages per conversation.

That last feature was the second half of the Pable case. About a year after the first deletion, on 29 October 2019, he switched on Signal's disappearing-messages feature for the same thread, which then deleted messages twenty-four hours after they were read. The pattern is established: in NuVasive v. Kormanis (M.D.N.C. 2019) a defendant was held to have been obliged to disable the automated destruction feature on his own phone.

Rule 37(e) has two doors, and only one ends the case

The rule bites where information that should have been preserved is lost because a party failed to take reasonable steps, and it cannot be restored or replaced through additional discovery. That last condition does quiet work: if the thread survives on the other participant's phone or in a backup, there is usually nothing to sanction.

The numbers in Pable show what the right-hand door costs. The complaint was dismissed with prejudice while still in discovery, $75,175.42 was awarded under Rule 37(e) and split equally between the client and his lawyer, and the lawyer alone paid a further $53,388 under 28 U.S.C. § 1927 and $21,367 under Rule 37(a)(5). The claim never reached its merits.

A hold is not permission to sit on documents

Two mirror-image mistakes follow the notice. The first is treating a hold as a shield: it changes what you may delete, not what you must hand over, and it makes nothing privileged. The second is issuing it and then doing nothing — one court sanctioned a defendant whose counsel neglected to oversee the process after perfunctorily issuing a hold (Franklin v. Howard Brown Health Center, N.D. Ill. 2018). Monitoring compliance is part of the obligation.

There is a criminal edge that has nothing to do with Rule 37. Under 18 U.S.C. § 1519, knowingly destroying or concealing a record with intent to impede the investigation or proper administration of a matter within the jurisdiction of a federal agency — including in relation to or contemplation of such a matter — carries up to twenty years. On 26 January 2024 the FTC and the DOJ Antitrust Division updated their standard preservation letters and compulsory process to address collaboration tools and ephemeral messaging explicitly.

Releasing the hold

A hold that is never lifted stops being a legal instrument and becomes an accidental retention policy. Data you no longer need is data you will one day have to search, produce, or explain a breach of. The release is a real step: confirm the duty has ended, cross-check the custodians and systems against every other live matter so you do not strip preservation from something a second dispute still needs, then tell everyone who received the original notice — including the IT provider and any third parties — that it is lifted.

The judgement call is when the duty ends, and it is later than people assume. Not at the handshake, but when the settlement is executed, releases exchanged and any appeal window closed — and not at all if the same facts could support a claim by someone who has not sued yet. A limitation period still running on a related claim is a reason to keep the hold, not to lift it.

The whole discipline reduces to something a business owner can do in an afternoon: fix the date the duty started and write it down, list the accounts and devices the disputed work ran through, switch off the settings that delete on them, tell the handful of people involved in one email, and keep a note of what you did and when. It is not the elaborate exercise the literature implies. What makes it urgent is that the cheap version only works if it happens in the first week — and the thing that starts that week is usually a letter nobody thought was serious.