WorkflowLegal Operations & Litigation

Legal Hold Management

Legal hold software that keeps every source held, checks it every morning and stops disposal before it runs

See one case, screen by screen ↓
Watch with transcript →

Built forLitigation counseleDiscovery managersIT preservation adminsLegal operations leads

The Problem Today

Legal sends hold notices, but HR and IT tools keep reimaging leavers' laptops and deleting mailboxes on schedule.

51%
of US in-house legal teams still manage holds by email published
15 days
of staff time per mid-size hold by hand, 5 rebuilding the record our estimate

Tracked by email and spreadsheet

  • Notices
  • Replies
  • Systems
  • Leavers
  • Holds placed, then not checkedNobody confirms next month that a source is still held
  • Record rebuilt for a motionSteps pieced together by hand from emails and tickets

The Solution

  1. Duty dated, people scopedThe trigger letter read and dated; custodians proposed with reasons
  2. Notices sent and chasedIn each custodian's language, with reminders, then escalation
  3. Held sources checked dailyHolds placed system by system, each one verified each morning
  4. Disposals stopped for counselA leaver's reimage or wipe halted before it runs; counsel decides

Built-in controls

  • Counsel signs each change and release
  • Agents may stop a disposal but cannot delete
  • Nothing on the trail can be edited

What You Get

When a spoliation motion lands, the record of reasonable steps already exists, built day by day as the hold ran.

  • Leaver data keptScheduled reimages, wipes and deletions stopped before they run
  • Failed checks cured fastA source that fails is retried, reported and cured
  • Safe releases across mattersA source released only when no other hold needs it
In short

What is Legal Hold Management?

Legal hold software runs a legal hold from the trigger to the release: dating the duty to preserve, choosing custodians, sending the hold notice and tracking acknowledgments, preserving data in each system and releasing it when the matter ends. Legal Hold Management adds seven agents that also check each held source each morning and stop a leaver's reimage, wipe or deletion before it runs, while counsel signs each change and release.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

A legal hold notice goes out, and the systems keep deleting on schedule

When litigation is reasonably anticipated, the duty to preserve starts. Legal sends the hold notice, chases acknowledgments by email and keeps a spreadsheet of who answered. But the data lives in systems Legal never sees: Microsoft 365, Slack, laptops, company phones, Salesforce, a PLM vault, HR files. Each needs its own hold, placed by IT, and nobody checks next month that it is still there.

Meanwhile the business keeps running its routines. A leaver's laptop is reimaged within days, the mailbox is deleted 30 days after leaving, the phone is wiped on exit, and someone shortens a retention policy. When a Rule 37(e) motion arrives, the question is whether the company took reasonable steps, and the record is rebuilt by hand from emails, tickets and spreadsheets, weeks later.

typical51%of US in-house legal teams still manage holds by email
typical35%manage them by spreadsheet
typical$76,907in fees and expert costs, plus an adverse inference, after a laptop was altered under a duty to preserve
Where a hold's working days goestimated
By hand14.5 days
With the solution1.7 days
  • Reading the trigger and dating the duty0.5 → 0.1 d
  • Choosing custodians and mapping their systems2 → 0.3 d
  • Sending notices and chasing acknowledgments3 → 0.5 d
  • Placing holds with IT, system by system2 → 0.3 d
  • Catching leavers, movers and retention changes2 → 0.2 d
  • Rebuilding the record when a motion lands5 → 0.3 d

Our estimated split for one mid-size litigation hold over its first months, by hand and with the solution.

How it works

Legal hold management, trigger letter through release

What comes in
Triggers in5 sources · letters, complaints, subpoenas, charges, HR and IT events
Agents at work
Intake agentduty dated
Then
Scoping agentcustodians, cited
Notice agentnotice + reminders
Then
Preservation agentheld, checked daily
Interview agent
Then
Watch agentstops disposal
Then
Release agentcross-matter check
A person decides
Litigation counselsigns each change and release
What comes out
Every source held
Releases on record
Rule 37(e) record
One case, step by step

A demand letter, a resigning engineer and a partial release on one hold

A competitor says two of its former engineers, hired by one of the company's subsidiaries, brought its pressure-sensor designs into a new sensor program. Its lawyers' letter arrives on a Monday morning. Here is how the hold runs, screen by screen.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 01Wednesday morning

    Each custodian and each system on one grid

    eDiscovery manager

    The eDiscovery manager runs 31 active holds for the group. This hold opens as a grid: 24 custodians down the side, nine systems across (mailbox, OneDrive, Teams, Slack, laptop, phone, Salesforce, PLM vault, HR file). This morning 130 of 138 sources are preserved and verified, 21 of 24 custodians have acknowledged, and one row is red: an engineer who leaves at the end of the week.

    “Four disposals were scheduled on this engineer's data. The agent stopped each one on its own, under its rule, and needs two decisions.”

  2. 02Monday, 08:47

    The letter dates the duty

    Intake agent

    The intake agent reads the four-page letter from the competitor's lawyers and classifies it as a demand letter that threatens suit, quoting the line that says the competitor intends to commence proceedings. It dates the duty to preserve from receipt, proposes the scope (the competitor, the new sensor program, an older product line and the two hires, from a set start date) and sets the clock to issue by Tuesday 17:00. The hold goes out at 10:14 on Tuesday, 25 hours after the letter.

    Search and collection stay locked until the hold is issued.

  3. 03The same day

    A reason for each custodian

    Scoping agent

    From the letter, the complaint, the org chart and message counts, the scoping agent proposes 25 people, each with the reason and a confidence: one ran the supply negotiations with the competitor, with 412 messages to its domain. Counsel approves 21, removes three with a reason each, and keeps a former employee's archived mailbox without a notice. The agent counts messages only; no content is read before the hold.

    The scoping agent does not add or remove a custodian; counsel decides.

  4. 04Tuesday, 10:14

    A notice people understand, in their own language

    Notice agent

    Version 2 of the notice goes out in English, German and Spanish, in plain words: what this is, what to keep, what not to do, what IT has already done. The notice agent reminds on day 3 and day 7, escalates to the manager on day 10 and re-notices every 90 days. On this hold the median time to acknowledge is 1.1 hours; one custodian, after three reminders, has been escalated twice to their manager.

    The notice agent does not edit an approved notice; a new version goes to counsel.

  5. 05As answers come back

    Answers that change the scope

    Interview agent

    Each custodian answers six questions when they acknowledge. One names a colleague who ran the price comparisons against the competitor, and the colleague is added a week after the notice. Another mentions a WhatsApp group with an engineer from an outside contractor. A third still has a USB drive from their time at the competitor. Each answer becomes a proposal for counsel, quoted word for word.

    The interview agent does not add a source or a person itself.

  6. 06Each morning, 07:00

    Holds checked each morning instead of assumed

    Preservation agent

    The preservation agent placed holds the way each system supports them: litigation and case holds in Microsoft 365, Slack's legal hold, reimage blocks on laptops, wipe blocks on phones, retention locks in the PLM vault. Each morning it confirms that each one is still present: 2,974 checks since the hold went out. Today the PLM vault timed out once and passed on retry at 07:10.

    “A source counts as preserved only if it passed in the last 24 hours.”

  7. 07That Wednesday, 09:12

    A key engineer resigns, and four disposals are already scheduled

    Watch agent

    The HR system records the engineer's resignation, last day Friday. The watch agent matches them to the hold, since they are named in the complaint, and finds what IT already has queued: a service-desk ticket to reimage the laptop on Friday at 17:00, an exit wipe of the phone, mailbox and OneDrive deletion 30 days after leaving, and Slack deactivation. By 09:14 the ticket is on hold, the wipe blocked, both deletions paused and Slack confirmed to keep the messages.

    The watch agent may only stop a disposal. It does not delete, release or drop a custodian.

  8. 0809:31

    Counsel keeps the engineer in the hold and approves the image

    Senior litigation counsel

    The agent hands counsel the two decisions it may not make, with the HR event, the ticket, the complaint paragraphs and its confidence of 0.98. Counsel picks the reason code “Key custodian, keep after departure”, ticks that the decision is theirs and types their name. The mailbox is kept as an inactive mailbox under hold, and the IT preservation admin images the laptop remotely: 238 GB, SHA-256 verified.

    “I have read the evidence and this decision is mine.”

  9. 09After the stipulation

    Release only what no other hold needs

    Release agent

    A joint stipulation withdraws the claims on the older product line. The release agent proposes releasing the six custodians held only for those claims and checks their 34 sources against 30 other open holds. Four sources of one custodian (mailbox, OneDrive, Teams and Salesforce) are still needed by a warranty claim on another matter, so they stay held. Counsel signs; retention resumes on 30 sources, and each release notice says what stays held.

    A full release stays closed until a dismissal, settlement or judgment is on the docket.

  10. 10Ready for a motion

    The reasonable-steps record, built as the hold ran

    eDiscovery manager

    The defensibility record has each step with its time and source: letter to hold in 25 hours, 24 of 24 custodians told in writing, 2,974 daily checks with 3 exceptions, each cured within 2 hours, 0 sources lost, and the release with its authority. A draft preservation declaration is written from the log for counsel to edit; nothing is filed until counsel approves it.

    Each export is logged with who took it and why.

Who it’s for

Litigation counsel, eDiscovery and IT around one legal hold

The four people who carry a hold, and how their week changed once the agents kept it.

eDiscovery manager
Runs the group's active holds
Before
Can say who was told, but cannot say on any given day that each mailbox is still on hold.
Now
Opens one grid per hold with each source checked at 07:00, the people who have not acknowledged, and the leavers already caught.
Senior litigation counsel
Decides custodians, leavers and releases
Before
Needs the reason for each custodian and the date each system was preserved, ready for court.
Now
Gets each decision drafted with its evidence and a due time (a leaver, a new custodian, a release) and signs with a reason code.
IT preservation admin
Places holds and owns the reimage queue
Before
Learns that a leaver is on hold only after the laptop has already been reimaged.
Now
Sees the reimage ticket put on hold with the hold reference, images the laptop when counsel approves, and is told when a retention change touches held data.
Legal operations systems lead
Connects systems, sets roles and rules
Before
Wants each preservation rule in one place, with a version and an approver.
Now
Sets reminder days, verification time, leaver look-ahead and guardrails once; each change becomes a new version for counsel to approve.
The agents

Intake, notice, watch and release agents that run the legal hold

Scoping, notices, holds, daily checks and a watch on HR and IT events are split across seven agents; counsel signs each change and release.

Intake agent

Reads each trigger (demand or preservation letter, complaint, subpoena, agency charge), classifies it, dates the duty to preserve, proposes subjects, period and key people, and sets the issue-by clock.

  • Never issues a hold
  • Never opens search before a hold is issued
  • Cites the words it relied on
Scoping agent

Proposes custodians and their systems from the trigger, the complaint, the org chart and message counts, with the reason and a confidence for each.

  • Never adds or removes a custodian; counsel decides
  • Uses message counts only; never reads content before the hold
Notice agent

Sends notices in plain words and the custodian's language, tracks acknowledgments, reminds on day 3 and day 7, escalates to the manager on day 10 and re-notices every 90 days.

  • Never edits an approved notice; it drafts a new version for counsel
Preservation agent

Places the hold each system supports and checks each held source each morning at 07:00, retrying failures three times and reporting pending, failed and cured.

  • Never removes a hold
  • Never collects data without counsel's approval
Watch agent

Reads HR, identity, service-desk, device and retention events, matches each to all open holds, stops or pauses a scheduled disposal of held data and hands any keep, release or imaging decision to counsel with its evidence and confidence.

  • May only stop a disposal
  • Never deletes, releases or drops a custodian
Interview agent

Reads each questionnaire answer within a minute of its return, turns a “yes” or a name into a proposal for counsel with the answer quoted, and drafts interview agendas.

  • Never adds a source or a person itself
Release agent

Watches the docket for stipulations, orders, settlements and judgments, proposes releases source by source, restores retention and sends notices after counsel signs, and keeps the defensibility record and the draft declaration current.

  • Never releases without a signature and a reason
  • Never releases a source another hold needs
Litigation counsel

Signs each custodian change and release.

Ask in plain words

Plain-word answers about a hold, a custodian or a release

Ask in plain words. Each answer points to its source and opens the screen it is about. These answers use the sample data.

Why is the departing engineer's data at risk?

They resigned this morning, and their last day is Friday. Four disposals were scheduled: the laptop reimage in an open service-desk ticket, the exit wipe of the phone, mailbox and OneDrive deletion 30 days after leaving, and Slack deactivation. The watch agent stopped each one by 09:14 under its rule. The engineer is named in the complaint, so counsel must decide whether to keep them in the hold and approve the image.

Who hasn't acknowledged the hold yet?

3 of 24: one custodian, already escalated twice to their manager, and two people added later, with 2 reminders each. All their systems are already held, so nothing is at risk while we wait.

Can we release the custodians held only for the withdrawn claims?

Yes, with one exception. The joint stipulation withdraws the claims on the older product line, so six custodians are held only for it. Four sources of one of them (mailbox, OneDrive, Teams, Salesforce) are still needed by another open hold and stay held. 30 sources would resume retention. The departing engineer is not affected. Counsel signs.

Draft the preservation declaration for this matter

Drafted for the eDiscovery manager to sign, from the log: the duty from the demand letter, the hold 25 hours later, 24 custodians told in writing, 2,974 daily checks with 3 exceptions each cured within two hours, and the leaver disposals stopped before they ran. Nothing is filed until counsel approves it.

The screens

Screens from a live hold: the grid, a stopped reimage, the record

From the working solution, on its sample data. Pick one to see it large.

The hold gridCustodians by system, each source preserved, pending, at risk or stopped; acknowledgments and flags; and the watch agent's run beside it.
New holdThe trigger inbox, the letter with the words relied on highlighted, and the intake agent dating the duty and setting the clock.
ScopeEach proposed custodian with why they are in scope, where it came from and a confidence, counsel's decision, and the org chart.
Notices and acknowledgmentsThe notice in three languages, the acknowledgment funnel, who is still waiting and the reminder cadence.
Interviews and questionnairesAnswers that change the scope, each turned into a proposal for counsel, the questionnaire returns and counsel's interviews.
SystemsHow each system holds, sources per system, 14 days of daily checks and this morning's run, step by step.
One source, its proofA leaver's laptop: the reimage ticket on hold, how it is held, the hold reference and each day's check.
WatchEvents from HR, identity, the service desk, devices and retention matched to all open holds, what the agent did, and its eight rules.
Counsel decides and signsKeep the leaver in the hold: what happens to each system, the image, the reason code, the attestation and the typed name.
DecisionsEverything waiting on a person across all holds, with its due time, the evidence and what the agent recommends.
ReleaseA partial release on a stipulation, the cross-matter check source by source, and what stays held for another matter.
Defensibility recordLetter to hold, notices, daily checks, exceptions and releases on one timeline, with the reasonable-steps summary and exports.
Your rulesReminder days, re-notice, verification time, retries, leaver look-ahead and the guardrails, versioned and approved.
Governance

Counsel signatures and a sealed trail behind each legal hold

Counsel signs each changeEach custodian change, leaver decision, image and release is signed by counsel with a reason code, an attestation and a typed name. The agents propose; counsel decides.
The watch agent may only stopIt may stop or pause a scheduled reimage, wipe, deletion or purge of held data on its own, under a numbered rule. Keeping, releasing or imaging goes to counsel.
Hold before searchNo search or collection opens on a matter until the hold is issued, and before then the scoping agent reads message counts only, not content.
Each decision cites its sourceThe duty date cites the letter, each custodian cites the complaint paragraph, org chart, message counts or questionnaire answer, and each release cites its stipulation, order or settlement.
Releases checked across mattersBefore any release, each source is checked against all other open holds. A source another hold needs stays held, and the release notice says so.
Nothing on the trail can be editedNotices, reminders, holds, checks, decisions and releases, by people and by agents, are on the audit trail with their time and hold. Rule changes are versioned and approved by counsel.
Configuration

Reminder days, daily checks and leaver look-ahead in your legal hold policy

The clocks and guardrails the agents follow are settings, versioned and approved by counsel before they change.

SettingDefaultChoose from
Issue a hold within1 business day of the duty dateAny number of business days
RemindersDay 3 and day 7 after the noticeAny two days after the notice
Escalate to the manager on day10Any day after the notice
Re-notice every90 daysAny number of days
Daily verification at07:00, local time of the businessAny time of day
Retry a failed check3 times, 10 minutes apartAny number of retries
Look ahead for leavers14 daysAny number of days
Two counsel sign a release on holds open over 3 yearsOffOn · Off
Connections

Microsoft 365, Slack, HR and the service desk, where held data lives

Legal inbox and docketdemand and preservation letters, complaints, subpoenas, agency charges and filings on open matters
Microsoft 365litigation and case holds on mailboxes, OneDrive and Teams
Slack Enterprise Gridlegal holds on members and channels, kept after deactivation
HR system and identity directoryleavers, movers, managers, the org chart and account lifecycle rules
IT service desk, device and mobile managementreimage and redeploy tickets, reimage blocks, keep tags and wipe blocks
Salesforce, PLM vault and HR filesrecord and field-history holds and retention locks
What it changes

The effect of legal hold software on lost sources and rebuilt records

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0lost
held sources to reimaging, wipes, deletions or retention changes, the design goal
5 of 5 at-risk sources kept
4 disposals stopped in the sample case
target
100%
of held sources verified every 24 hours: the reasonable steps Rule 37(e) asks for
Hold placed oncenever re-checked
With agentschecked every 24 hours
target
1day
from the trigger letter to a hold issued; 51% of in-house teams still run holds by email

“demo” = seen in the working solution, on its sample hold · “target” = the design goal, measured in the live solution · “estimated” = our estimate: about 15 days of staff time for one mid-size hold by hand, the sum of the split on this page, rounded up · “typical” = published figures (Association of Corporate Counsel survey with a legal technology vendor, 2024 — 51% of US in-house teams manage holds by email, 35% by spreadsheet, vendor-sponsored; Beard Research v. Kates, Del. Ch. 2009 — adverse inference and $76,906.80 in fees and costs). Context: FRCP 37(e) on reasonable steps; Hoffer v. Tellone, 2d Cir. 2025. Names on the screens are sample data.

Questions

What litigation counsel ask about legal hold software

What is legal hold software?

Legal hold software runs a legal hold from the trigger to the release: dating the duty to preserve, choosing custodians, sending the hold notice and tracking acknowledgments, preserving data in each system and releasing it when the matter ends. Legal Hold Management adds seven agents that also check each held source each morning and stop a leaver's reimage, wipe or deletion before it runs, while counsel signs each change and release.

How does it stop a departing employee's data being destroyed?

The watch agent reads HR, identity, service-desk, device and retention events and matches each to all open holds. When a custodian resigns, it puts the reimage ticket on hold, blocks the phone wipe and pauses the mailbox and OneDrive deletion under its rule, then asks counsel whether to keep the person in the hold and image the device.

Does it check that holds are still in place?

Yes. The preservation agent checks each held source each morning, retries a failed check three times, and writes the result to the grid and the record. A source counts as preserved only if it passed in the last 24 hours; on the sample hold that is 2,974 checks in 23 days.

How does it decide who is a custodian?

The scoping agent proposes people from the letter, the complaint, the org chart and message counts (not message content, before the hold), with the reason and a confidence for each. Counsel approves each addition and removal, and questionnaire answers that name new people or sources come back as proposals.

How are holds released without losing data another matter needs?

The release agent proposes a release from a stipulation, order, settlement or judgment, and checks each source against all other open holds. Sources another hold needs stay held and the release notice says so; retention resumes on the rest only after counsel signs.

Does it help with a Rule 37(e) motion?

It keeps the record the reasonable-steps question turns on, as the hold runs: when the duty arose and the hold went out, who was told and acknowledged, what was held and each daily check, each exception and its cure, and each release with its authority. It also drafts the preservation declaration from that log for counsel to edit.

Can an agent delete data or release a hold on its own?

No. The agents propose, and the watch agent may only stop a disposal. Counsel signs each custodian change, leaver decision, image and release with a reason code, and each action by a person or an agent is on an audit trail that cannot be edited.

What does legal hold software need from our policies and systems?

Your hold policy, notice templates and the systems your data lives in. The Agentic Solution Engine builds and deploys it from your requirements and those documents, and it goes live once each quality gate has passed. We will walk you through it on one of your own open matters first.

Run legal hold software
on one of your open matters.

We'll run Legal Hold Management on one of your own open matters and the systems it touches.