Ending a Litigation Hold
Almost every organization has holds still running on matters resolved long ago, and a few that were lifted while an appeal was pending. Release is the least governed step in the process and the one with the least room for error.
The rule in short
A hold ends when the matter that created it is over and no other obligation covers the same material. That requires checking for appeals, related proceedings, regulatory retention periods and other holds on the same custodians before anything is released. The release itself is a written instruction reversing the original, and the record of what was held, collected and released is retained after the material itself is disposed of.
Holds are issued with care and lifted by accident. A matter settles, the file closes, and the notice that froze six mailboxes and a shared drive is never mentioned again — or, worse, an administrator clearing space asks whether anything still applies and is told no by someone who does not know. Both outcomes are common, and only one of them is a problem.
What has to be true first
The duty to preserve runs while litigation remains reasonably anticipated, which is not the same as while a case is open. A judgment entered does not end anticipation if the time to appeal has not run. A settlement does not end it if the agreement contains obligations that could be enforced. A dismissal without prejudice ends very little.
Related proceedings are the second check. The same events frequently generate a civil claim, an agency charge and an internal investigation, each with its own timeline, and the release of one does not release the others. Where a regulator has an open inquiry, the material may be subject to a separate obligation with different scope and a different endpoint.
Contractual undertakings form a fourth category and are easy to miss because they sit outside both the legal and the records functions. Supply agreements, insurance policies and joint venture documents frequently require records relating to a claim to be retained and produced on request, sometimes for a period measured from resolution rather than from the events. Those terms bind independently of any court.
Third, other obligations may cover the same records for unrelated reasons. Employment regulations require personnel records to be kept until the final disposition of a charge or action. Health information rules impose a six-year documentation period. Sector rules for regulated firms impose their own terms. None of these depend on the litigation, and none of them end when it does.
| Apparent trigger for release | What may still block it | Usual outcome |
|---|---|---|
| Case settled and dismissed | Enforcement obligations under the agreement | Partial release; keep the settlement-related material |
| Judgment entered at first instance | Appeal period and post-judgment motions | Hold continues until the periods run |
| Claim withdrawn without prejudice | The claim may be refiled | Hold continues, often narrowed |
| Agency charge closed | Private right of action arising from the same events | Hold continues on the same custodians |
| Matter concluded entirely | Regulatory or contractual retention period | Litigation hold released; retention rule governs |
Who authorizes the release
Release is a legal judgment and belongs to whoever owns the matter, usually the attorney responsible for it. Neither the custodian nor the systems administrator is in a position to make it: the custodian does not know the procedural posture, and the administrator sees only a configuration that has been in place for a long time and appears to have been forgotten.
The authorization should be recorded in the same place as the original notice, with the reason stated. A one-line entry saying that the matter concluded, that the appeal period expired, and that no other hold covers the custodians is enough. What is being created is the answer to a question that will be asked years later by someone with no memory of the matter.
Where holds overlap, the release has to be scoped rather than blanket. A custodian subject to three holds who is released from one remains subject to two, and lifting a person-level suspension in an administrative console can release all three at once. This is the most common technical failure in the release step, and it is silent.
Most systems apply holds to accounts, while the legal record tracks them by matter. When two matters cover the same person, removing the account from a hold policy for one matter removes it for both. The release process has to reconcile the matter list against the console state before anything is changed, and after the change it has to confirm that the remaining holds are still in force.
The sequence of a release
The order is straightforward and rarely followed. Confirm that the matter and every related proceeding are concluded. Check for other holds and other retention obligations covering the same custodians and systems. Confirm that whatever needed to be captured has been captured and verified, drawing on the acquisition and chain-of-custody record. Then authorize, and only then change any setting.
Notice to custodians follows. The people who received the original hold notice should be told in the same channel that it no longer applies, naming the matter so that nobody generalizes the release to a hold that is still running. Silence at this stage leaves employees under an instruction nobody intends to enforce, which is how a program loses its credibility.
The technical reversal is the last step and belongs to the same people who applied the suspension. Retention policies are returned to their scheduled behavior, backup sets are returned to rotation, and excluded accounts are returned to the ordinary offboarding process. Each change is recorded against the matter, which closes the loop opened when automated destruction was first suspended.
Resuming disposal without over-correcting
Resumption is not the same as deletion. Returning a system to its ordinary schedule means that material will age out in the normal course; it does not mean that anything should be purged immediately to recover the storage the hold consumed. A bulk deletion executed on the day of release looks purposeful in a way that gradual expiry does not.
Timing helps here as well. Where the storage pressure is genuine, narrowing a hold during a matter is usually a better answer than an aggressive purge after it. Categories that have plainly ceased to matter as the claims narrowed can be released as they fall away, with each narrowing recorded, so that the end of the matter is not also the moment of a single large deletion.
Where a large preserved set exists in a collection platform rather than in the source systems, disposal of that set is its own decision. It may contain material collected for one matter that is relevant to another, and it will contain personal data that privacy commitments require to be removed once its purpose ends. Those two pressures point in opposite directions and are resolved matter by matter.
What is kept after the data is gone
The hold record outlives the material it protected. It contains the trigger, the notice, the custodian list and its revisions, the acknowledgments, the suspension tickets, the collection log and the release authorization. None of that is bulky, and it is the only evidence that the process functioned.
Its value is not confined to the matter it documents. An organization whose preservation program is challenged in a later case is asked how the program works in general, and a set of complete records across several closed matters answers that far better than a policy document. It is also the material that supports a proportionality position when the organization next receives a preservation demand from an opponent, because it shows what the organization actually does rather than what it says it does.
Points to carry away
- A matter is not over for preservation purposes until appeal and enforcement periods have run.
- Overlapping holds on the same custodians must be checked before any release.
- Regulatory and contractual retention periods survive the end of the litigation duty.
- Release is authorized by the person who owns the matter, not by the custodian or the administrator.
- The release instruction should name the systems and settings being returned to normal operation.
- The hold record is kept after the data is disposed of, because it evidences the process.
Questions readers ask
Is there any obligation to release a hold?
No rule requires it, and an organization that keeps everything indefinitely faces no sanction for over-preservation. The pressures are practical rather than legal: storage cost, the burden of searching a growing corpus in every new matter, and privacy commitments that promise data will not be kept beyond a stated period. Permanent holds also erode the credibility of the program, because custodians who are subject to a dozen notices they have never seen lifted stop treating any of them as meaningful.
What is the risk of lifting a hold too early?
The duty runs while litigation remains reasonably anticipated, which extends past a judgment through the appeal period and any enforcement proceedings. Material destroyed after an early release is assessed exactly as material destroyed after no hold at all: whether it should have been preserved, whether reasonable steps were taken, and whether it can be restored. A documented release decision that turned out to be wrong is better than an undocumented one, but neither restores the data.
Who should hold the release record after disposal?
The record of the hold outlives the data it protected, and it is usually retained by the legal function rather than by records management. What matters is the ability to reconstruct the process later: when the duty was recognized, who was notified, which systems were suspended, what was collected, when the release was authorized and by whom. That reconstruction may be needed in an unrelated matter years afterward, when the only question is whether the organization's preservation program functions as described.
Sources
- Federal Rule of Civil Procedure 37, Cornell LIILoss after a premature release is assessed under the same reasonable-steps and tier analysis as any other loss.
- Federal Rule of Civil Procedure 26, Cornell LIIProportionality supports narrowing or releasing a hold once the material can no longer bear on the case.
- 29 C.F.R. § 1602.14, Cornell LIIRequires records to be preserved until final disposition of a charge or action, an obligation that outlasts many holds.
- 45 C.F.R. § 164.316, Cornell LIIA six-year documentation retention period that continues regardless of any litigation.
- Records Control Schedules, National ArchivesIllustrates how scheduled disposition resumes once records are no longer needed for a proceeding.
- 18 U.S.C. § 1519, Cornell LIICriminal exposure for destroying records with intent to obstruct a federal matter, including after a release.
Rapid Response Law is a publication, not a law firm. This article states general rules and cites its sources; it is not advice about any particular case, and the law differs by state and changes over time.
More in Evidence Preservation
When the Duty to Preserve Begins
The obligation to preserve evidence arises when litigation is reasonably anticipated rather than when a suit is filed. Federal Rule of Civil Procedure 37(e) presupposes that duty by asking whether information that should have been preserved was lost because reasonable steps were not taken. Anticipation is judged objectively on what an organization knew, and knowledge held by managers and counsel is generally attributed to the organization.
Collecting Data Without Altering It
An electronic record carries system-generated attributes that establish when it was created, who handled it, and where it sat. Ordinary copying overwrites several of them. Forensic imaging captures a bit-level duplicate and verifies it with a hash value; targeted collection captures defined items with their metadata intact; self-collection by custodians is the least reliable and the most commonly criticized. A chain-of-custody record documents each transfer.
Spoliation of Things That Are Not Electronic
Rule 37(e) applies only to electronically stored information. Loss of physical evidence is addressed under a federal court's inherent authority, where the older circuit standards survive and negligence can support measures that would be unavailable for electronic material. State courts run on their own law, which in some states includes a separate tort and in others only evidentiary inferences and discovery sanctions.