What Happens to Records Destruction During a Legal Hold

TL;DR: A legal hold suspends the retention schedule entirely. Once litigation, an audit or an investigation is reasonably anticipated, all disposition of potentially relevant records stops, including routine scheduled deletion, and stays stopped until the hold is lifted in writing. The schedule does not resume on its own.

Most people who destroy records under hold are not covering anything up. They are doing a cleanup.

That is what makes this worth understanding even if you have no legal role. The person who deletes the wrong folder is usually a coordinator working through a backlog, following a retention schedule correctly, unaware that a matter opened last month put part of that backlog off limits.

University records offices write about this in a register they use nowhere else. Duke's guidance switches to capital letters: "DO NOT dispose of any records or data if an investigation, legal action or proceeding, audit or program review is forthcoming or in progress." (Duke University Libraries)

The University of Alberta's guidance on source documents is equally blunt, stating that in the event of an access request or litigation concerning official or transitory records, destruction must cease. (University of Alberta)

Compare that to the measured tone of the same documents three paragraphs earlier, where they are explaining folder naming. The shift is deliberate.

What is a legal hold?

A legal hold, sometimes called a litigation hold or preservation notice, is an instruction to preserve all records potentially relevant to a legal matter, overriding whatever the retention schedule would otherwise say.

Three properties make it different from ordinary retention rules.

It overrides everything. A record that reached the end of its retention period yesterday and is eligible for destruction today does not get destroyed if it is in scope. The hold wins.

It starts before anyone files anything. The trigger is reasonable anticipation of litigation, not the arrival of a lawsuit. Duke's phrasing captures this: the prohibition applies to a proceeding that is "forthcoming or in progress." By the time you have been served, the obligation has usually existed for a while.

It ends only when someone lifts it. Holds are released in writing by the office that issued them. They do not expire, and a matter that seems to have gone quiet is not a released hold.

What counts as destruction under a hold?

More than deliberate deletion, which is what catches people out.

Emptying a mailbox folder counts. Letting an auto-delete policy run counts. Reimaging a laptop counts. Clearing a scanner output folder counts. So does a well-intentioned cleanup where somebody consolidates duplicates by keeping one copy and deleting the rest, because the copy they deleted may have had different metadata or annotations from the one they kept.

Penn State's guidance shows how close routine IT operations sit to this line. Its process for a retiring employee says that "Within thirty (30) days of said retirement, the employee's computer can be scrubbed and put back into use, unless subject to a litigation hold (then contact the Office of General Counsel)." (Penn State AD35 FAQs)

That is an ordinary asset recovery task, scheduled by a team with no visibility into legal matters, and the only thing standing between it and a preservation failure is somebody remembering to check.

Who does a legal hold bind?

Everybody who holds potentially relevant records, which is usually a much wider group than the one that gets the notice.

This is where shared drives become a specific risk. A hold notice goes to custodians the legal office knows about. But the material sits in departmental folders, in personal folders inside shared drives, in mailboxes, and in the download folders of people whose involvement nobody has mapped. Any of them can run a cleanup.

Carleton's guidance illustrates how quietly copies spread beyond the custodian list. It warns that sending a document as an attachment rather than a link means "Sending attachments will create a duplicate copy in the SharePoint library of the recipient." (Carleton University Records Storage Guide)

Each of those recipients now holds a copy that may be in scope, in a location the legal office has no map of.

How do organizations breach holds by accident?

Four ways, in rough order of frequency.

The cleanup that was already scheduled. Somebody was told in March to clear the shared drive. They get to it in September, by which time a matter has opened. Nothing connects the two events.

The departing employee. Their drive gets reassigned, consolidated or scrubbed on the standard timeline, because the standard timeline is run by HR and IT rather than legal.

The storage squeeze. A quota is reached, and the fastest fix is deleting the oldest material, which is exactly the material most likely to be under hold.

The duplicate consolidation. Well-meant deduplication that deletes copies on the assumption they are identical. Under a hold, where a copy lived and what was annotated on it can matter as much as its content. This is one reason the question of which copy is authoritative is worth settling in advance, covered in official copy vs duplicate.

Every one of these is a competent person doing their job. None involves bad faith. That is the point.

What should you do when a hold is in place?

Stop all disposition in scope, immediately and over-inclusively. If you are unsure whether something is in scope, it is in scope until someone with authority says otherwise. The cost of keeping too much for a few months is storage. The cost of destroying one item is not comparable.

Suspend automated deletion, not just manual deletion. Anything on a timer needs to be identified and paused. This is the step most often missed, because automated processes do not report to anyone.

Write down where the records are. Not just the primary folder. Mailboxes, personal folders, chat, the scanner folder, the copies that went out as attachments.

Route deletion requests through one person. During a hold, disposal stops being a distributed decision.

Get the release in writing. When the matter ends, the hold lifts by an explicit instruction, and only then does the retention schedule resume.

Duke's staging advice is a good default even with no hold active: move candidates to a temporary "To Be Destroyed" folder and "wait 30 days before deleting them." A thirty day delay between decision and deletion is often exactly the window in which somebody realises a matter is open.

Can software enforce a legal hold?

No, and this is the claim to be most skeptical of when evaluating any document management tool.

A hold depends on facts that do not exist inside a file system. Whether litigation is reasonably anticipated is a legal judgment. Which records are potentially relevant is a legal judgment. When the hold is released is a legal judgment. None of these is inferable from a document's content, location or age, and a tool that claims to determine them is claiming to practise law.

What software can honestly do is reduce the surface area for accidental destruction. It can find where copies of a document ended up. It can surface which folders relate to a given client, matter or period, so a preservation scope can be drawn quickly. It can make a drive legible enough that the question "what do we hold about this matter" has an answer in an afternoon rather than a fortnight.

The Drive AI holds to that boundary. It organizes and searches across connected storage, so locating everything related to a matter is a question rather than an excavation. It does not apply holds, it does not determine scope, and it does not delete records on a retention timer, which means it cannot delete something under hold on a schedule you forgot to pause.

The honest version of the value here is narrow and worth saying plainly: the main preservation risk on a messy drive is not that you cannot delete things, it is that you do not know what you have or where the copies went. That part is a findability problem, and findability problems are solvable.

Frequently Asked Questions

What happens to records destruction during a legal hold?

It stops entirely for records within the hold's scope. The retention schedule is suspended, including any automated deletion, and no disposition occurs until the hold is released in writing. This applies even to records that have already passed the end of their retention period.

When does a legal hold begin?

When litigation, an audit or an investigation is reasonably anticipated, which is usually before any formal filing. Duke's guidance applies the prohibition to any proceeding that is "forthcoming or in progress," making anticipation rather than service the trigger.

Does a legal hold apply to duplicate copies?

Generally yes. Copies held by other custodians can be within scope, and deleting duplicates during a hold is risky because copies may differ in metadata, annotations or location in ways that matter evidentially. Deduplication should be paused for material in scope.

Who is responsible for complying with a legal hold?

Everyone holding potentially relevant records, not only the named custodians who received the notice. In practice this is why breaches happen through routine cleanup by staff who were never notified a matter existed.

Can a document management system enforce a legal hold automatically?

No system can determine on its own whether litigation is anticipated, which records are relevant, or when a hold is released, since these are legal judgments made outside the system. Software can help locate records and reduce accidental deletion, but enforcement of a hold remains a human and legal responsibility.

Where to start

Find out who at your organization issues holds and whether your unit is on their notification list. A surprising number of departments are not, and discovering that during a matter is the wrong time.

Then look at what deletes itself on your drives without anyone deciding. Auto-empty policies, retention automation and asset recovery schedules are the mechanisms that breach holds while everyone is looking elsewhere.

For the process that holds override, see records retention schedule compliance. For the cleanup work that most often collides with a hold, see what is ROT data.