A litigation hold notice is the document that formally instructs an organization to stop routine destruction of information that may be relevant to a threatened or pending case. Its legal purpose is narrow — trigger the preservation duty and put custodians on notice — but its practical purpose is much broader: it is the document a court will look at first if a spoliation dispute arises later, to judge whether the duty to preserve was met in good faith and with reasonable diligence.

A hold notice that is vague, sent to the wrong people, or never followed up on can be worse than no notice at all, because it creates a paper trail of an inadequate response. This guide covers what a hold notice needs to contain, who should receive it, and how to keep it effective over the life of a case. It is an educational explainer, not legal advice — the trigger for the preservation duty and the consequences of noncompliance vary by jurisdiction.

The duty to preserve typically arises when litigation is reasonably anticipated, which is often well before a complaint is actually filed — a demand letter, a serious internal complaint, a regulatory inquiry, or even certain internal red flags can trigger it. Waiting for a formal filing before issuing a hold is one of the most common ways organizations end up facing a spoliation argument, because routine deletion policies keep running during the gap.

When in doubt about whether litigation is reasonably anticipated, issue the hold. The cost of an unnecessary hold is modest inconvenience; the cost of a missed one, discovered later, is a spoliation motion that can result in adverse inference instructions or other sanctions regardless of how strong the underlying case is on the merits.

The most common substantive gap in a hold notice is scope — sending it only to the obvious custodians, or covering only email, while other sources of relevant information keep running their normal deletion or overwrite cycles untouched. Build the custodian and source list deliberately rather than from memory.

A hold notice should tell each recipient exactly what to stop doing and exactly what categories of information to preserve, described in terms the recipient can actually apply to their own daily work — not in abstract legal language borrowed from a pleading. Vague instructions like 'preserve all relevant documents' leave the custodian to guess at scope, and that guess is precisely what gets scrutinized if a gap surfaces later.

Include an explicit instruction to suspend any auto-delete settings, retention-policy purges, or device-recycling procedures that would otherwise apply to the identified sources, and name a specific point of contact for questions about what the hold covers. The notice should also state clearly that it remains in effect until formally released, so custodians do not assume it expires on its own after some period of time.

A hold notice issued once and never revisited is a common weak point in a later spoliation defense. Send periodic reminders, confirm receipt and acknowledgment from each custodian, and update the custodian list as the case develops — new custodians identified in discovery, employees who depart the organization, and new information sources that come to light as the facts become clearer.

Keep a record of who received the notice, when, what it covered, and every reminder or update sent afterward. That record is what demonstrates reasonable, good-faith diligence if preservation is ever challenged, and it is far more persuasive built contemporaneously than reconstructed after a dispute has already arisen.