How Legal Holds Suspend Disposition

A records retention schedule is, in normal operation, a standing authorization to destroy records once they reach the end of their approved retention period. Disposition is the routine, defensible endpoint of the records lifecycle: records that have outlived their legal, fiscal, administrative, and historical value are systematically destroyed or transferred. But that authorization is not absolute. The moment an organization reasonably anticipates litigation, an audit, a government investigation, or another formal proceeding, the ordinary right to dispose of relevant records is suspended. The instrument that accomplishes this suspension is the legal hold (sometimes called a litigation hold or preservation hold).

A legal hold does not change a record’s retention period or rewrite the schedule. Instead, it acts as an override that freezes specific records in place, preventing their scheduled destruction for as long as the underlying obligation persists. Understanding the relationship between holds and disposition is essential to running a defensible program, because the failure point most likely to draw a court’s attention or sanctions is not over-retention but the inadvertent destruction of records that should have been preserved.

The Duty to Preserve and When It Attaches

The legal foundation for suspending disposition is the common-law duty to preserve evidence, reinforced in the federal context by the Federal Rules of Civil Procedure, particularly the rules governing discovery and the sanctions available when electronically stored information is lost. This duty does not wait for a lawsuit to be filed or for a subpoena to arrive. It attaches when litigation is reasonably anticipated—when an organization knows, or reasonably should know, that specific information may be relevant to a present or future dispute.

That triggering moment is a judgment call, and it is frequently the subject of dispute itself. A demand letter, an internal complaint, a regulatory inquiry, a serious workplace incident, or even credible internal awareness of a problem can all start the clock. Once the duty attaches, any routine disposition that destroys potentially relevant records is no longer protected by the “ordinary course of business” rationale. This is why mature programs treat the identification of triggering events as a defined, documented process rather than an ad hoc reaction.

How a Hold Overrides the Schedule

In operational terms, a legal hold sits above the retention schedule in the hierarchy of controls. When a record falls under both an expired retention period and an active hold, the hold wins: the record cannot be destroyed. The schedule resumes governing only when the hold is formally released.

A defensible hold typically involves several coordinated steps:

• Issuing a hold notice to custodians and stewards who control relevant records, clearly describing the scope of information to be preserved and the obligation not to delete it.
• Suspending automated disposition for the affected record series, mailboxes, repositories, or systems, including any routine purge or auto-deletion routines.
• Identifying and securing sources across structured systems, shared drives, email, messaging platforms, and backups where relevant information may reside.
• Tracking acknowledgment and compliance so the organization can later demonstrate that custodians received and understood the obligation.
• Reissuing and updating the hold as scope, custodians, or systems change over the life of the matter.

A single record may be subject to multiple overlapping holds at once. In that situation, the record remains preserved until the last applicable hold is lifted—never the first. Releasing a record while any hold still covers it is a common and serious error.

Documentation and Defensibility

The value of a legal hold is realized only if the organization can prove what it did. Courts evaluating a preservation dispute look less at whether every relevant byte survived and more at whether the organization acted reasonably and in good faith. That assessment rests on documentation: when the duty was recognized, when notices went out, who received them, what scope was defined, what systems were suspended, and when and why the hold was eventually released.

The Sedona Conference, whose consensus guidance is widely cited by courts on preservation and electronic discovery, has long emphasized reasonableness and proportionality rather than perfection. A program that can show a consistent, documented process is far better positioned than one that preserved more but cannot explain its decisions. Conversely, the destruction of relevant records after the duty to preserve attached—particularly if done with intent to deprive another party of the information—can lead to spoliation findings and sanctions ranging from adverse-inference instructions to default judgment.

Releasing the Hold and Resuming Disposition

A hold is not permanent. When the matter that triggered it concludes—settlement, final judgment, closed investigation, completed audit—and no other obligation requires continued preservation, the hold should be formally released. Release is itself a controlled event: it should be documented, approved by the appropriate authority (often legal counsel), and checked against any other active holds before any record is returned to the normal disposition stream.

Once released and verified clear of other obligations, affected records re-enter the retention schedule. Records already past their retention period can then be dispositioned through the program’s normal, approved process, while records not yet expired continue counting toward their scheduled disposition date. This disciplined release step closes the loop and prevents holds from accumulating indefinitely, which itself becomes a cost and risk if records that should have been destroyed linger under stale, forgotten holds.

Building Hold Capability Into the Program

Legal hold is not a bolt-on; it is a core capability that should be designed into the broader retention and disposition framework. Modern electronic records management expectations reflect this. After NARA revoked its endorsement of the DoD 5015.2 standard in 2022 in favor of the Universal Electronic Records Management Requirements and the related FERMI effort, the emphasis shifted toward functional outcomes—including the ability to apply, track, and release holds across diverse systems—rather than certification against a single product standard.

Practically, an organization should be able to apply a hold quickly and broadly, suspend disposition reliably, track scope and custodians, and release cleanly with an audit trail throughout. These capabilities connect directly to the rest of the lifecycle described in the retention and disposition topic hub. When holds and schedules work together—holds suspending disposition precisely when the duty to preserve demands it, and disposition resuming promptly when that duty ends—the organization achieves the dual goal of defensible destruction and defensible preservation.