Litigation Hold vs. Standard Retention: Why It Matters

A litigation hold suspends your normal retention schedule for specific people and specific records, for as long as a matter is live — and it has to be actioned deliberately, because standard retention policies don't know it exists. A firm's Outlook rules or Google Vault policy will happily auto-delete a partner's mailbox after three years on schedule, litigation hold or not, unless someone has gone in and told the system to stop. This is the gap that turns an ordinary dispute into a spoliation problem: not bad faith, just a retention policy running exactly as configured while nobody remembered to pause it.

Picture the sequence. A former client sends a letter of demand in March. The matter partner flags it internally, everyone assumes IT or the practice manager will "sort out the emails." Nobody sends a written hold notice. Nobody touches the mailbox retention rules. In June, the firm's standard three-year auto-delete policy runs as scheduled and quietly removes a batch of correspondence from 2023 — some of it directly relevant to the dispute. By the time discovery requests land in September, that correspondence is gone, and the firm can't say when the duty to preserve should have kicked in versus when the deletion happened. That's not a hypothetical; it's the most common way small firms end up explaining a gap in production to a court.

The real compliance requirement

Standard retention and litigation holds are governed by different logic. Retention schedules are about how long you keep records in the ordinary course of business — seven years for financial records under the Corporations Act 2001 (Cth), seven years after matter closure for client files under most state legal profession rules, six years under the UK Limitation Act 1980 for contract claims. A litigation hold overrides all of that. It's a common law duty to preserve potentially relevant evidence that arises the moment litigation is reasonably anticipated — not when proceedings are filed, not when a lawyer confirms it, but when a reasonable person in your position would expect a dispute.

In Australia, the Federal Court's Practice Note GPN-DISCO expects parties to have preserved discoverable documents from the point litigation was reasonably in contemplation, and courts have real teeth if they haven't: adverse inferences, cost penalties, and in professional contexts, conduct complaints. UK practice is similar — CPR Practice Direction 31B and the disclosure pilot scheme both assume a preservation obligation predates the claim form, and failure to preserve can affect costs orders and credibility with the court. US practice under FRCP 37(e) is the most codified version of the same idea, and it's the one most firms have heard of via Zubulake-line cases, even if they're not litigating in a US court — the operational lesson travels regardless of jurisdiction.

The exposure isn't limited to litigation lawyers. Accounting practices facing a dispute with a former client, financial advisers facing an AFCA complaint, and consultancies facing a contract dispute all carry the same duty the moment a claim becomes reasonably foreseeable — well before anyone files anything.

What most small firms actually do

Most firms under 20 people have a retention policy that exists as a folder rule or a mailbox size limit, not a documented schedule someone actively manages. When a hold is needed, it's usually an email from a partner saying "keep everything on the Smith matter" — sent to one person, filed nowhere, with no corresponding change to any system setting. Nobody maintains a register of active holds. Nobody reviews whether a hold is still needed six months later, or whether it was ever actually implemented. The auto-delete rule, if one exists, keeps running underneath it the entire time. This works fine until the first real dispute — at which point the firm discovers it has no way to prove what was preserved, when, or by whose instruction.

What good looks like

An audit-ready approach to litigation holds has a few concrete characteristics, and none of them require a dedicated compliance team.

Continuous capture, independent of mailbox state. If your archive captures mail as it's sent and received rather than relying on what happens to still be in someone's inbox, you're not dependent on an individual's deletion habits or a scheduled auto-purge in the first place. This is the single biggest structural fix — it removes the race between "did the hold get applied in time" and "did the schedule run first."

A hold that can be applied without disturbing everything else. Good systems let you suspend deletion for specific custodians or date ranges — the people and period actually relevant to the matter — while the rest of the firm's retention schedule keeps running normally. You shouldn't have to choose between "protect this one matter" and "stop deleting anything for anyone, indefinitely."

A written, timestamped record of the hold itself. Who was notified, when, what was preserved, and when the hold was lifted. If a court or regulator ever asks what you did and when, "we sent an email" is a much weaker answer than an audit log showing the hold was applied to the relevant mailboxes on a specific date and stayed in place until the matter closed.

Coverage of sent mail and attachments, not just inboxes. Discovery requests rarely care only about what a custodian received — outgoing correspondence and attachments are usually the more contested material.

Fast, defensible export. When a hold converts into an actual discovery obligation, you need to produce the preserved material quickly, in a form that preserves metadata, without a week of manual PST-hunting.

This is the specific problem AutoArchive Mail is built around: it captures mail continuously and independently of mailbox retention settings, so a litigation hold means flipping a switch on the affected custodians rather than hoping an email instruction gets remembered and manually implemented before the next scheduled purge.

The practical path forward

Start with the cheap part. Write a one-page litigation hold procedure — who can issue one, who gets notified, where it's logged — and put it somewhere every partner can find it. That's a 30-minute task, and it closes the biggest gap, which is that most firms have no written process at all.

Next, find out whether your current retention setup can actually suspend deletion for specific people without you disabling it for the whole firm. If the honest answer is "we're not sure" or "it's all manual," that's worth fixing before you need it, not during a dispute. You can Start Free Trial to see how continuous, hold-aware archiving removes that guesswork.

When a real trigger event happens — a letter of demand, a regulator inquiry, a departing employee threatening a claim — issue the hold in writing immediately, log it, and confirm with IT (or your archive provider) that deletion has actually been suspended for the relevant custodians, not just requested. Review open holds at least quarterly; holds that outlive their matter create their own storage and privacy problems. For anything with genuine litigation risk — a formal claim, a regulator contact, a significant employee dispute — loop in your lawyer on scope and duration rather than guessing.

One limitation

This covers email specifically. Litigation holds properly extend to any system holding relevant material — shared drives, practice management software, Teams or Slack messages, even paper files — and a hold that only touches the mail server isn't a complete hold. If your matter involves material outside email, get advice on the full scope before you assume you're covered.

← Back to all articles