What Resources Are Used When a Litigation Hold Is Lifted?
Meta description: Learn what legal, records, IT, and e-discovery resources help organizations lift a litigation hold safely, document the decision, and manage retained information.
Lifting a litigation hold is more than sending a notice that a case is over. An organization must confirm that its preservation duty has ended, identify every affected source, coordinate with the people and systems that maintained the information, and document what happens next. Legal counsel, records management, IT, e-discovery providers, and business teams may all be involved. A careful process reduces the risk of destroying information that still needs to be preserved or retaining it indefinitely without a business or legal reason.
What It Means to Lift a Litigation Hold
A litigation hold, also called a legal hold, instructs relevant people and departments to preserve potentially important information because of actual or reasonably anticipated litigation, an investigation, or another legal matter. The hold may suspend routine deletion, overwriting, and document-destruction practices for specific records, devices, accounts, or data sources.
Lifting the hold means the organization has determined that the preservation obligation connected to that matter no longer requires the hold. It does not necessarily mean the case has ended, that every related record can be deleted, or that all preservation duties have expired. Other lawsuits, regulatory requirements, contracts, audits, or business needs may still apply.
In federal civil litigation, Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation. The rule makes preservation and potential remedies fact-specific. It does not provide a universal checklist for lifting a hold, so organizations generally rely on counsel’s assessment, applicable law, and internal procedures.
Resources Needed Before a Hold Is Lifted
Legal counsel and matter owners
Legal counsel is central to the decision. Counsel should assess the matter’s status and determine whether the duty to preserve has ended, narrowed, or continues for particular information. Relevant factors can include settlement terms, dismissal orders, appeal deadlines, related claims, regulatory inquiries, and obligations imposed by a court or agreement.
The responsible matter attorney or legal operations team typically confirms which hold notice, custodians, and data sources are in scope. When outside counsel, co-counsel, insurers, or government agencies are involved, the organization may need to confirm that no related preservation request remains active. The assessment should be recorded rather than inferred from a case-management status such as “closed.”
Hold records and matter-tracking systems
A reliable legal hold platform, matter-management system, or controlled tracking document helps identify who and what the hold affected. Useful records include the original notice, acknowledgments, reminders, custodian changes, collection details, preservation exceptions, and prior releases. These records help prevent an incomplete release or an accidental removal of a separate hold.
Organizations should also check whether one person or data source is subject to multiple holds. A mailbox, shared drive, phone, or backup may be preserved for more than one matter. A hold should be removed only from information no longer covered by any applicable preservation duty.
Records management and retention schedules
Records management staff help translate the legal decision into the organization’s retention rules. They can identify whether records are subject to a retention schedule, an industry-specific requirement, a contract, or an internal policy. They can also determine which records must be retained for ordinary business purposes even after the litigation hold ends.
Retention schedules vary by record type and applicable law. For example, employment records, financial documents, health information, and regulated business records may have different retention obligations. The legal team should resolve conflicts between a schedule and a hold before routine disposition resumes.
Technical and Operational Resources
IT administrators and system owners
IT staff are often responsible for implementing and reversing technical preservation measures. They may have paused email deletion, disabled automatic file cleanup, retained chat messages, protected user accounts, or prevented devices from being wiped. System owners can explain which controls were actually applied and what steps are required to change them safely.
Technical work may involve Microsoft 365 or Google Workspace retention settings, archive systems, endpoint management, cloud storage, databases, collaboration tools, mobile-device management, or backup policies. The release should be scoped to the relevant matter and users; removing a broad setting without checking its impact could affect other legal holds or compliance controls.
E-discovery and information governance teams
E-discovery professionals help connect the legal hold inventory to collections, processing, review, and production records. They can identify preserved copies, legal hold repositories, exports, forensic images, and data hosted by outside providers. This is particularly useful when the organization no longer has a clear picture of where all matter data resides.
Information governance teams may map the affected data to current systems and retention rules. They can also help distinguish between the source data that was subject to a hold and separate copies created for legal review. Those copies may have their own access, security, and retention requirements.
Outside vendors and service providers
Some organizations use e-discovery vendors, cloud providers, archiving companies, or forensic specialists to preserve or host information. The legal or vendor-management team may need to send written instructions authorizing a change to preservation settings or requesting a final inventory, status report, or data return.
Vendor contracts and security requirements matter. Before a provider deletes hosted data or changes access, the organization should confirm who owns the data, whether another hold applies, and whether the contract requires retention or secure disposal. A vendor’s automated “case closed” process should not substitute for the organization’s legal approval.
Business custodians and department contacts
Employees who received the original hold notice may need a clear release notice. It should identify the matter, explain that the specific hold has ended, state whether ordinary records policies resume, and remind recipients that other holds and retention rules remain in force. A release notice should not suggest that employees may delete anything they choose.
Managers or department contacts can help address local files, paper records, shared accounts, and business processes that central IT cannot fully control. They can also flag documents that remain necessary for operations, contractual duties, or another legal matter.
What Happens to Preserved Information?
After legal approval, the organization decides how each category of information will be handled. The answer depends on the record, the system, the applicable retention schedule, and any remaining obligations. Common outcomes include returning to ordinary deletion cycles, retaining records for a defined period, keeping material for an active related matter, or securely disposing of data that has no continuing retention basis.
| Information or control | Possible action after review | Key check |
|---|---|---|
| Email and collaboration data | Resume scheduled deletion or retain under a separate policy | Check other holds, user accounts, and retention settings |
| Shared drives and cloud files | Restore normal lifecycle rules or preserve selected records | Confirm ownership, version history, and overlapping matters |
| Devices and mobile data | Return devices to normal management or reassign them | Check whether required data has been collected and preserved |
| Vendor-hosted collections | Retain, return, archive, or securely delete under written instructions | Review contract terms and obtain completion confirmation |
| Paper records | Return to approved storage or follow the records schedule | Check for other legal, regulatory, or operational needs |
Preserved collections and review workspaces should not be confused with the original source records. A case workspace may contain collected copies, attorney notes, privileged communications, or work product. Those materials often require restricted access and separate retention decisions. Deleting a source mailbox does not automatically authorize deletion of a legal collection, and retaining a collection does not necessarily justify keeping every source record forever.
A Practical Release Workflow
- Confirm the legal basis. Counsel documents why the hold can end, whether the release is complete or partial, and whether related matters remain open.
- Check for overlapping obligations. Review active holds, court orders, subpoenas, investigations, regulatory requirements, contracts, and applicable retention rules.
- Reconcile the inventory. Compare the hold notice and custodian list with system settings, collection records, vendor inventories, and known data sources.
- Approve a scoped technical plan. Specify which controls may be changed, which records remain preserved, and who is authorized to make the changes.
- Notify affected people and providers. Issue a clear release notice and send written instructions to vendors where needed.
- Implement and verify changes. IT and records teams document the settings changed, the date, the systems involved, and any exceptions.
- Close and retain the audit trail. Store the release approval, notices, implementation evidence, and final disposition decisions in the appropriate matter or governance system.
A staged release may be safer than changing every system at once. For example, a team may first remove a hold flag from a specific mailbox while keeping a separate legal archive intact. Verification helps confirm that ordinary retention has resumed only where intended and that unrelated preservation controls remain active.
Documentation and Risk Controls
Good documentation shows who authorized the release, what information was affected, when technical steps occurred, and what exceptions remained. It can also help an organization explain its process if a later dispute arises about whether data was lost or improperly destroyed. Records should be factual and consistent with the actual steps taken.
Common controls include role-based approval, a second-person review of high-impact changes, change tickets for technical work, and a final check against the active-hold register. Organizations may also retain confirmation from a vendor that requested actions were completed. These controls are especially valuable when a hold covered many custodians or systems.
Security remains important after a hold ends. Legal collections may include sensitive personal information, confidential business data, or privileged material. Access should remain limited to authorized users, and any disposal should follow approved security procedures and applicable privacy requirements.
Common Mistakes to Avoid
- Assuming a closed case means the hold is over. Appeals, related claims, enforcement, or regulatory issues may continue.
- Sending a vague release notice. Recipients need to know which hold ended and that other legal or retention obligations still apply.
- Deleting all preserved material immediately. Some records or legal collections may need to remain under a schedule, another hold, or a business requirement.
- Changing system settings without checking other holds. Shared systems and custodians can be subject to multiple preservation duties.
- Leaving controls in place indefinitely. Unreviewed holds can create unnecessary storage, access, privacy, and compliance burdens.
- Failing to verify vendor actions. Written instructions and completion records help close gaps in outsourced preservation.
The right resources for lifting a litigation hold are the people and systems that can validate the legal decision, locate the affected information, safely change preservation controls, and preserve an audit trail. The precise process depends on the facts, applicable law, and organizational policy. Because a premature release can create serious consequences, final approval should come from qualified counsel familiar with the matter and relevant obligations.
References and Further Reading
- Federal Rule of Civil Procedure 37, including Rule 37(e) on electronically stored information.
- Federal Rule of Civil Procedure 26, addressing discovery scope and case management.
- U.S. National Archives and Records Administration guidance on records management.