How to handle legal holds with an AI agent

Counsel decides when a hold starts, what it covers and when it ends; the agent does the rest of the legwork. It maps the people and systems likely to hold relevant material, drafts the hold notice, tracks acknowledgements, suspends routine deletion through approved requests and checks that nothing in scope is destroyed. Releasing a hold stays with counsel.

What is a legal hold, and who owns it?

A legal hold, sometimes called a litigation hold or preservation notice, suspends normal deletion for information that may be relevant to actual or reasonably anticipated litigation, a regulatory investigation or an audit. Once the duty to preserve arises, destroying relevant material, even through routine retention schedules, can lead to serious consequences for the firm in the proceedings.

Legal owns holds: in-house counsel decides when the duty to preserve arises, defines the scope and issues the notice. Records management and IT carry out the preservation. Custodians, the people whose email, files and records are in scope, must acknowledge and comply. Holds are often triggered from elsewhere in the business, for example by a complaint that mentions legal action, so the agent's first job is often noticing that one may be needed.

What does the agent do at each step, and at what depth?

1. Agent, depth 1: spots possible triggers. Complaints and correspondence mentioning solicitors, claims or proceedings; regulator letters opening an investigation; dismissals likely to be contested. It flags them to legal with the text quoted. It does not decide that a hold is needed.
2. Person, counsel: decides to issue a hold and sets its scope: matter, subjects, date range, types of information.
3. Agent, depth 1: maps custodians and sources. From the scope, it identifies likely custodians, systems, shared drives, case files, call recordings and agent logs that may hold relevant material.
4. Person, counsel: confirms the custodian and source list.
5. Agent, depth 2: drafts the hold notice in plain language: what to keep, what not to delete, how long, who to ask. Counsel approves it.
6. Agent, depth 3, within bounds: sends the approved notice to confirmed custodians, tracks acknowledgements and sends approved reminders.
7. Agent, depth 2: drafts preservation requests to system owners to suspend deletion for the scoped data. System owners apply them.
8. Agent, depth 1: monitors compliance. Checks that deletion jobs exclude held data, and flags custodians leaving the firm, whose accounts would otherwise be wiped.
9. Person, counsel: reviews the hold periodically and releases it. The agent drafts the release notice for approval.

Which controls apply, and what evidence does each leave?

Trigger flags reach counsel quickly. A hold issued late may not protect material already deleted. Evidence: flag time against hold issue time.

Acknowledgements tracked. Each custodian's acknowledgement, and reminders sent, are logged. Evidence: a list you can show a court or regulator.

Preservation confirmed by owners. The agent asks; system owners act and confirm. Evidence: each system's confirmation and the date.

Deletion jobs checked. The agent compares scheduled deletions against held data. Evidence: monitoring results and any exceptions caught.

Hold register. Every hold, its scope, custodians, systems and status in one place. Evidence: the register itself, which erasure and retention processes must check; handling erasure requests relies on it.

Release only by counsel. The agent cannot close a hold. Evidence: release decision and notice.

What should you measure?

• Time from trigger to hold issued.
• Custodian acknowledgement rate by the reminder deadline.
• Deletion events caught by monitoring. Each should have been prevented; any that were not need investigation.
• Holds open past their review date, which keep data longer than needed and undermine data minimisation.
• Systems found holding relevant data after the hold was issued, which shows gaps in the custodian and source map.

Where does it usually go wrong?

Agent logs and memory left out. Conversation records, summaries and decision logs of AI agents are business records. If agents interacted with the customer or matter, their records are in scope.

Leavers. A custodian leaves, IT wipes their mailbox on the standard schedule, and relevant email is gone. Joiner-mover-leaver processes must check the hold register.

Holds never released. Data kept indefinitely "in case" breaches retention principles and raises the cost of every later search. Review dates matter, and the agent should remind counsel of each one with the matter's current status.

The agent deciding scope. Asked to "find everything relevant", an agent will set a scope. Scope is a legal judgement with consequences in both directions, and the agent should only propose.

Advice dressed as process. The hold notice tells custodians what to do; it should not give them legal views on the matter. Whether an AI agent can give legal advice explains the line. Related, but separate: a hold does not itself make any decision about a customer; for the concept of a decision with legal effect see the glossary.

The stance on compliance agents overall is in AI compliance agents.