How to Implement and Track a Litigation Hold Across Every Custodian

A litigation hold is easy to treat as a communication task. Identifying the right employees, sending a notice, and collecting responses. The harder work starts after that as custodians change roles, new data sources surface, claims evolve, and the legal team still needs to be able to show what the organization asked people to preserve and how that scope changed over time.

To implement a litigation hold effectively, legal teams need a repeatable way to define scope, map custodians to relevant systems, issue matter-specific instructions, document follow-up, resolve exceptions, and release the hold when the preservation obligation ends. The goal isn’t paperwork for its own sake, it’s a record that lets counsel explain what the organization did, when it did it, and why.

This article focuses on that full lifecycle. For a deeper look at the notice itself, our previous guide to drafting a matter-specific litigation hold notice covers how to turn the triggering matter and preservation scope into instructions employees can act on.

A Litigation Hold is an Ongoing Preservation Process, Not a One-Time Notice

A litigation hold is a written directive to preserve potentially relevant information, but the directive sits inside a broader preservation process. In U.S. federal litigation, the Federal Rules of Civil Procedure address the loss of electronically stored information (ESI) that should’ve been preserved in anticipation or conduct of litigation. A useful benchmark is the HHS litigation hold policy, which requires the agency to identify custodians, track confirmations, revise scope, send reminders, document newly discovered information or custodians, and communicate when a hold is lifted.

Private organizations use different procedures, but the consistent thread is that preservation has to be managed over time. That’s also why both under-preservation and over-preservation can create problems. A scope that’s too narrow can miss evidence, while a scope that’s too broad can freeze large amounts of data that later have to be collected, processed, and reviewed. Good hold management keeps the scope tied to the matter as it develops.

1. Define What the Litigation Hold Actually Needs to Preserve

Start with the facts that triggered the preservation duty, not with the template. Counsel should identify the claims or issues that are reasonably in play, the events they turn on, the relevant time period, and the types of information that could affect those questions.

A practical initial scope should answer four questions:

1. What issues matter?
2. Which people are likely to have relevant information?
3. Which systems or repositories may contain it?
4. What date range is reasonably connected to the dispute?

Those answers give the hold a working boundary and make the later notice more specific. However, the first scope is not necessarily the final scope. New allegations, interviews, document review, or discovery can surface additional custodians or sources. Treat the initial scope as a reasoned starting point that counsel can revisit instead of a fixed list created on day one.

2. Build a Custodian and Data-Source Map Before Sending the Hold

Once the legal team knows what information might matter, the next step is to map who’s likely to control it and where it lives. This is where a generic employee list becomes a matter-specific custodian map.

Identify the People Who May Control Relevant Information

The obvious custodians are the people directly involved in the events at issue, but the list often extends beyond them. Managers, employees copied on key communications, IT or records personnel, former employees, departing employees, and appropriate third parties may all control information that matters to the case. The initial custodian list should also remain open to revision. For example, if interviews or document review identify another person who created, received, stored, or administered relevant information, the team should be able to add that custodian without losing the history of the original scope.

Map Where Each Custodian’s Relevant Information Lives

For each custodian, identify the likely sources of relevant information. Depending on the matter, that could include email, messaging and collaboration platforms, shared drives, document management systems, business applications, local or mobile devices, and physical records. At minimum, the working map should capture the custodian, why that person is relevant, the likely data sources, and the relevant time period. This simple structure helps counsel spot gaps before the notice goes out and gives collection teams a stronger starting point later.

3. Draft a Litigation Hold Notice for the Actual Matter, Not From a Generic Template

The notice should turn counsel’s scope analysis into instructions that a nonlawyer can follow. Generic instructions to preserve “relevant documents” leave far too much judgment with the recipient, who may not know what legal considers relevant to the dispute.

A matter-specific notice should explain why the hold exists, what categories of information and date ranges are in scope, which systems or sources deserve attention, what routine deletion or modification needs to stop, how questions should be raised, and how the recipient should confirm receipt when the organization’s process requires it. It should also make clear that the obligation continues until legal releases or changes it.

Harvey can support the drafting step by working from the triggering documents and an approved exemplar. The lawyer still owns the scope, verifies the instructions, and approves the notice before it goes out. That helps move drafting faster without shifting the preservation judgment away from counsel.

4. Create a Compliance Record for Every Custodian

Once notices are issued, the legal team needs a reliable record of what happened next. “Notice sent” is not enough if the team later has to reconstruct the process from email threads, spreadsheets, and memory. The authoritative record should live in the organization’s established legal-hold or preservation process. The important point is that it should preserve both current status and history, so counsel can see who was in scope, what each person was told, what follow-up occurred, and what changed over time.

What to Track for Each Custodian

A concise custodian register should usually capture six categories of information:

• Identity and relevance: Name, role, business unit, and why the custodian is in scope
• Scope and sources: Relevant data sources, date ranges, and information categories
• Notice history: Notice version, issue date, and any supplemental instructions
• Response history: Acknowledgment or confirmation status, follow-ups, and open questions
• Exceptions and status changes: Departures, device changes, inaccessible sources, or other preservation issues
• Release history: When the custodian or source was released and whether another obligation still applied

The exact fields will vary by organization and matter, but you need to be able to reconstruct the decisions and actions without relying on one person’s inbox.

Turn Scattered Compliance Information Into Structured, Reviewable Data

The formal hold record might sit in a dedicated process or system, while useful matter data is spread across exports, spreadsheets, and document sets. Structuring that information can make legal review faster without changing where the official preservation record lives. For example, Harvey’s Review Table Agent workflow can map custodian metadata from a Relativity export into new table columns, then filter, flag, and route rows for review. That makes it easy to analyze matter information and surface exceptions.

5. Monitor the Litigation Hold as the Matter Changes

A litigation hold can remain in place for months or years. During that time, the matter can change faster than the original notice. Because of this, monitoring needs to be both periodic and event driven, with additional review when the facts, people, systems, or claims materially change.

Follow Up on Incomplete or Unclear Compliance

An unanswered notice is an obvious follow-up item, but the more important questions often sit underneath the response. A custodian may not know whether a personal device is in scope, may identify a system legal did not know about, or may report that an automatic deletion process is still active. Those are preservation issues, not administrative details, and follow-up should resolve the uncertainty and document the result. If the answer changes the custodian map or preservation scope, update the record instead of leaving the new information buried in correspondence.

Revisit Scope When New Facts Emerge

Common triggers for a scope review include amended pleadings, new witnesses, additional custodians appearing in communications, newly identified repositories, changes to the relevant date range, and findings that emerge during collection or document review. When scope changes, counsel might need to supplement the notice or preservation instructions for affected custodians. The change should also be traceable to a reason, a date, and a defined set of people or sources.

Keep a History of What Changed and Why

Don’t overwrite yesterday’s scope with today’s scope. Keep a change history that documents the prior scope, revised scope, date, reason for the change, affected custodians, and follow-up taken. That history is more useful than a clean current-state spreadsheet because it shows how the process responded as the matter and context developed.

6. Treat Exceptions as Issues to Resolve, Not Notes Buried in Email

Exceptions are where a hold process truly gets tested. Maybe a custodian replaced a phone, a former employee left before preservation was confirmed, a relevant collaboration platform wasn’t included initially, or routine deletion is running for a source in scope. Treat each exception as a small issue to close by recording what happened, who owns the response, what action was taken, when the issue was resolved, and whether the preservation scope changed. This approach makes exceptions visible to the team and reduces the chance that a risk gets buried in an email chain.

7. Use the Custodian Record to Make Downstream eDiscovery More Efficient

Preservation is upstream of collection, review, and production. A well-maintained custodian map gives the discovery team a head start because the likely people, systems, time periods, and known exceptions are already documented. That doesn’t eliminate the need to refine collection scope, but it does reduce the amount of basic fact-finding that has to be repeated once eDiscovery begins. Our earlier guide to AI for eDiscovery explains how legal teams can use tools like Harvey later in the process for document review, privilege analysis, and early case assessment while maintaining controls around accuracy and defensibility.

Move From Custodian Metadata to Document-Level Analysis

Once relevant material has been preserved and collected through the organization’s established process, the work shifts from tracking people and sources to understanding the documents themselves. Harvey Vault is built for large-scale document organization, review, and analysis. Litigation teams can use review tables to structure findings across document sets, filter and flag issues, and organize discovery work. The primary value that litigation teams receive here is downstream analysis of collected material, not just preservation itself.

8. Release the Litigation Hold Deliberately When the Preservation Obligation Ends

A hold should end because counsel has made a release decision, not because the matter has gone quiet. Before releasing a custodian or source, confirm whether the matter has ended, whether the preservation scope has narrowed, and whether another litigation, investigation, regulatory, or records obligation still applies.

The release notice should be as clear as the original hold. Identify what obligation is ending, who or what’s being released, and whether ordinary retention and deletion practices may resume. If only part of the hold is lifted, make the remaining obligations explicit — but remember to keep the hold history after release. Your organization may no longer need to preserve the underlying information for that matter, but the record of when the hold began, how it changed, and when it ended can still matter.

Where Legal AI Fits in Litigation Hold Compliance (and Where it Doesn’t)

Legal AI is most impactful on areas of the hold process that involve repeated drafting, extraction, structuring, and review. It should make those tasks easier for lawyers without obscuring who owns the preservation decision or where the authoritative hold record sits.

AI Can Accelerate Matter-Specific Drafting

A complaint, demand letter, internal investigation record, and approved hold exemplar can all give legal AI the context needed to generate a stronger first draft than a blank template would. That reduces the time spent assembling routine language while keeping the matter-specific scope in front of the lawyer. The output still needs legal review, so AI organizes facts and draft language while counsel decides which custodians, periods, sources, and categories are in scope.

AI Can Structure and Analyze Custodian and Matter Information

Custodian and matter information often arrives in inconsistent formats. Review tables can turn that information into structured fields that are easier to filter, compare, and review, which is especially helpful when the team is looking for missing metadata, changed statuses, or rows that need escalation. This analysis layer can sit alongside the preservation process, but it shouldn’t be a substitute for the technical controls that preserve data or the system that records formal hold actions.

Agents Can Support Recurring Review and Reporting

Recurring status work is another place legal AI can dramatically improve efficiency. Harvey Agents can run scheduled reports, updates, and reviews on a cadence that the team chooses, then return review-ready output for attorney oversight. For litigation hold work, the useful pattern is specifically recurring analysis around the matter, not unattended legal decision-making. Counsel should still decide what changed, whether scope needs to move, and what action the preservation process requires.

AI Does Not Replace the Preservation Process or Attorney Judgment

AI can help draft notices, compare templates, structure custodian information, analyze document sets, and prepare recurring reports. However, it doesn’t fully satisfy the organization’s duty to preserve, and it should not be treated as the authoritative record of legal-hold actions unless the organization has deliberately implemented a system for that purpose. Drafting, comparison, and extraction are appropriate AI-assisted tasks. Running the hold, formally tracking preservation obligations, and preserving or collecting the data remain with the organization’s established process and the people responsible for it.

Litigation Hold Implementation Checklist

A practical litigation hold process should cover the full lifecycle:

1. Identify the event that triggers the preservation obligation.
2. Define the claims, issues, time periods, and information categories in scope.
3. Identify the custodians who may control relevant information.
4. Map each custodian to likely data sources and repositories.
5. Draft and issue matter-specific preservation instructions.
6. Record responses, follow-up, and unresolved questions.
7. Monitor changes in custodians, systems, claims, and scope.
8. Document exceptions, escalation, and how issues were resolved.
9. Carry the custodian and source map into collection and eDiscovery.
10. Formally release the hold when counsel determines the obligation has ended or narrowed.

Make Litigation Holds Easier to Review as the Matter Changes

A defensible hold process should be understandable without reconstructing months of emails. Counsel should be able to see who was in scope, what they were told, which sources mattered, what changed, what issues arose, and how the team responded.

This is where legal AI can add useful leverage. Drafting, extraction, structuring, document analysis, and recurring review can move faster, leaving lawyers more time for the preservation of judgments that require legal expertise.

Harvey for Litigation supports legal teams across case assessment, discovery, analysis, drafting, and trial preparation. If your team is evaluating where legal AI can streamline repetitive work without giving up attorney control, request a demo to see how Harvey fits into your litigation workflows.

FAQs About Litigation Hold Compliance

Is a litigation hold the same as a legal hold?

These terms are often used interchangeably. “Legal hold” can be used more broadly for preservation obligations tied to investigations, regulatory matters, or other proceedings, while “litigation hold” usually refers to preservation connected to actual or reasonably anticipated litigation.

Does sending a litigation hold notice automatically preserve the data?

No. The notice communicates the preservation obligation to custodians. The organization still needs the appropriate operational and technical controls to stop deletion, preserve relevant sources, and collect information when needed.

How long does a litigation hold stay in place?

There is no universal fixed duration. A hold remains in place until counsel determines that the relevant preservation obligation has ended or changed. A custodian or source may also remain subject to another hold even after one matter is released.

How often should litigation hold compliance be reviewed?

There isn’t a single “ideal” review interval that fits every matter, but the cadence should reflect the matter’s duration, complexity, risk, and rate of change. It should also include additional review when material events occur, such as new claims, new custodians, employee departures, or newly identified data sources.

Can AI track litigation hold compliance?

Yes. AI can help organize, analyze, and report on structured information associated with a litigation hold. It can also help surface missing fields, changed statuses, or issues that need review. Formal preservation controls and the authoritative record of hold actions should remain within the organization’s established legal-hold process unless the organization has implemented a purpose-built system for those functions.