What a legal hold notice is, and what makes one hold up

A legal hold notice is a written instruction that suspends normal deletion and routine disposal of material that may be relevant to anticipated or actual litigation. It tells custodians and other personnel what to preserve, what ordinary practices to stop, and how to acknowledge and continue the preservation obligation.

The notice is not the source of the preservation duty itself. The duty arises from the law when litigation is reasonably anticipated. The notice is the mechanism an organization commonly uses to discharge that duty and to document that it has communicated the obligation to people who control relevant information. Conflating the duty with the notice can create two problems: an organization may assume that the duty begins only when a notice is sent, and it may treat a signed notice as the end of its preservation work rather than the start of an ongoing process.

What it means to be on legal hold#

Being on legal hold means that specified material must be preserved instead of being deleted, overwritten, discarded, or disposed of through ordinary information-governance and retention processes. The obligation generally reaches material within an organization’s possession, custody, or control when it may be relevant to the anticipated or actual litigation. The notice identifies who must act and what they must do; it does not create a general requirement to preserve everything indefinitely.

The legal hold therefore operates as a targeted override of routine destruction. An organization may have established schedules for deleting messages, disposing of files, purging backups, rotating data, or destroying paper records. A hold can prevent those processes from affecting the covered material. It does not make irrelevant information relevant, and it does not require an organization to search for information outside the reasonable scope described in the notice.

The people responsible for implementing a hold are commonly called custodians. A custodian may be an employee, contractor, executive, department manager, or other person whose information could contain relevant material. The term “custodian” is often used more broadly in litigation-support practice to describe both people who hold information and the systems or locations from which it may need to be collected.

When the duty arises#

The preservation duty attaches when litigation is reasonably anticipated. That determination depends on the facts known at the time and is usually made before a complaint is filed. A signed complaint is not the only event that can put an organization on notice. The practical question is whether the information existing at that point gives a reasonable basis to expect litigation, not whether litigation has already begun.

Events that commonly lead to a hold include a threatened claim, a demand for relief, an investigation that presents a substantial possibility of litigation, a complaint received from another party, or the communication of a litigation position that creates a dispute likely to result in a lawsuit. These are examples of circumstances that prompt a preservation assessment, not a fixed checklist or a substitute for the fact-sensitive judgment the rule requires.

An organization does not need to wait for every dispute to become a lawsuit before evaluating preservation. Conversely, a general business disagreement does not automatically establish that litigation is reasonably anticipated. The relevant inquiry focuses on the information available when the decision is made. That timing matters because materials may be deleted through routine systems soon after a dispute begins, and those deletions can become irreversible.

The duty also is not limited to documents in a particular file format or to information stored in a single system. The hold assessment should consider the forms of electronically stored information and other records that could be relevant, subject to the organization’s factual circumstances and the scope of the anticipated or actual litigation. Email, shared files, chat messages, text messages, collaboration platforms, local devices, and other repositories may require consideration when they could contain responsive material.

How long a hold lasts#

A hold lasts while the preservation obligation lasts. That means a legal hold notice should not be treated as a permanent status merely because the underlying matter remains open. A hold may need to remain in place during the anticipation of litigation, through the active case, and potentially while a post-litigation preservation obligation continues. The duration depends on the matter’s status and the continuing risk that relevant material could be lost.

The common failure is leaving holds in place indefinitely because nobody owns releasing them. An organization may preserve more information than necessary, burden custodians, consume storage, complicate collection and review, and create avoidable operational risk. At the other end, releasing a hold too early can expose the organization to spoliation concerns and may eliminate evidence that later proves important.

Release therefore requires an explicit decision rather than an assumption. The record should identify who authorized the release, when it occurred, which custodians or information sources were affected, and whether the preservation obligation had ended. A release communication is as important as the original notice because it tells personnel that the suspension of ordinary disposal has ended and identifies any actions that may now resume.

Where litigation remains pending but a portion of the population or a category of information is no longer within the reasonable scope, practitioners may consider adjusting the hold. Any narrowing should be communicated clearly and documented. Custodians should not be left to guess whether a general instruction still applies to them or to particular systems.

What a legal hold notice contains#

A workable notice is specific enough for a custodian to act on without legal training. It generally identifies the recipients, describes the covered material in terms people can recognize, states the preservation instruction, requests acknowledgement, and explains how reminders will work. The notice may also provide a contact point for questions and a process for reporting lost or inaccessible information.

The recipient section should identify the custodians and personnel responsible for taking action. It may identify individuals by name or role and may include system owners, records managers, information-technology personnel, or other people who can stop an automated deletion process. If a notice applies to a group, the group must be defined by criteria that recipients can understand. “All employees” may be too broad to implement and may dilute the instruction.

The scope section should connect the preservation duty to the anticipated or actual litigation and describe the information categories that may be relevant. A definition such as “all documents and electronically stored information” is usually less useful than a focused description of the topics, issues, time period, and information sources relevant to the dispute. The description does not need to disclose every legal theory or sensitive detail. It needs to give recipients enough information to recognize potentially responsive material.

The instruction should state plainly that routine deletion, destruction, alteration, disposal, and other routine practices must stop for the covered information. It should cover both active material and material held in systems or locations subject to automatic deletion. The notice should also make clear that preserving information does not authorize people to change it, move it casually, or create new copies outside the preservation process.

Legal language should not substitute for operational clarity. A custodian who does not understand what is covered may delete a relevant message because the instruction appears to apply only to a particular category. Conversely, an overly vague description may cause the recipient to preserve everything or fail to identify the material that requires action. A notice written in legal language that custodians do not understand is not an effective instruction merely because it uses sophisticated terminology.

Why acknowledgement matters#

Acknowledgement gives the organization evidence that the notice was received and that the recipient was told to act. It also creates an opportunity to identify misunderstandings before information is lost. A signed form, electronic response, recorded confirmation, or other documented acknowledgment can establish that the organization communicated the instruction and tracked its receipt.

Acknowledgement does not by itself prove that the information was preserved. It confirms communication, not compliance. The organization may still need to determine whether a recipient changed conduct, whether information was deleted before the hold took effect, and whether systems or third parties require separate action. Those questions are especially important when a custodian’s information is held in a shared service, a personal device, or a system managed outside the organization.

The acknowledgement process should be practical for the recipient and compatible with the organization’s preservation system. A response should confirm the recipient’s identity, the notice received, the date of receipt, and an understanding that the covered material must be preserved. If the notice asks the recipient to identify relevant systems, the response can also surface gaps that require follow-up.

Reminders and continued communication#

Reminders are not an optional substitute for the initial notice. They help maintain attention to a preservation obligation that may continue for an extended period and provide a dated record of continued communication. A reminder can repeat the central instruction, identify the affected custodians and information sources, and ask for confirmation that the preservation obligation remains in effect.

Reminders also support the organization’s ability to demonstrate that the obligation was not a one-time communication that faded from view. They can be used after personnel changes, system migrations, updates to the litigation posture, or other events that affect the hold. A reminder should not introduce a different scope without explaining the change. If a hold is narrowed, expanded, or released, the communication should state that clearly.

Documentation and the preservation record#

What matters afterward is the dated record of what was decided and done. A defensible record generally connects the reason for the hold to the decision-making process, identifies the custodians and sources brought within scope, and documents the notice, acknowledgements, reminders, collection activity, adjustments, and release. The purpose is not to create a perfect paper trail disconnected from operations. The purpose is to show what the organization understood, when it understood it, and how it responded.

The record should preserve the reasoning behind the trigger assessment. If litigation was reasonably anticipated, the file should explain which facts supported that conclusion and when the organization recognized it. Later reviewers should not have to infer the trigger solely from the date on the first hold notice. The record should also show what happened when the duty arose, rather than only when collection began.

Documentation should track implementation across the organization. The legal team may decide that a hold is required, but information-technology personnel, records managers, and business owners may control the systems needed to suspend deletion. The file should identify those actions and responsible owners without suggesting that sending the notice alone completed the preservation process.

Rule 37(e) of the Federal Rules of Civil Procedure addresses electronically stored information that should have been preserved and was lost. Under the rewritten two-tier framework, a court may order measures no greater than necessary to cure the prejudice only upon a finding of prejudice. Under the second tier, a court may presume that the information was unfavorable, instruct the jury that it may make that presumption, or dismiss the action or enter default judgment only upon a finding that a party acted with the intent to deprive another party of the information.

That framework makes the preservation record more than an administrative artifact. It can bear on what the organization knew, when it knew it, and what it did in response. A dated record cannot guarantee a favorable outcome, and a missing document does not itself establish the required intent. It does, however, allow the organization to explain the decisions and actions that followed the preservation obligation. The focus is on a documented, good-faith process, not on claiming that every outcome was perfect.

A legal hold is therefore both an operational control and a communication. The duty begins with the legal obligation to preserve when litigation is reasonably anticipated. The notice translates that obligation into instructions recipients can follow. Strong implementation depends on clear scope, plain language, acknowledgement, reminders, accountable ownership, and a contemporaneous record of the decisions and actions taken. The measure of the process is not whether the hold notice looked sophisticated; it is whether the organization understood the obligation, communicated it, and preserved the material while the obligation continued.