Document retention policies that survive litigation discovery

Rachel Okonkwo · 2024-12-18

Document retention policy is half a security measure and half a litigation defense. Get one half wrong and you may compromise the other. The firms that get into trouble usually have a clean security story and a messy litigation story.

The three levers

Every retention policy is built from three components:

Retention period. How long the document is kept by default.
Legal hold mechanism. How that default is suspended when litigation is reasonably anticipated.
Deletion audit trail. Proof that deletion happened on schedule, not in response to an inquiry.

A policy that lacks any of the three is more risk than protection.

Common retention defaults

Reasonable starting points by document type (US-centric; check your jurisdiction):

Tax return preparation files: 7 years from filing date
Audit work papers: 7 years (some standards require 10)
Engagement letters: life of relationship + 7 years
Contracts and amendments: life of contract + 6 years (statute of limitations driven)
Correspondence: 3 years for general; longer if tied to a regulated matter
Marketing collateral: 3 years
HR personnel files: 7 years post-separation

These are floors, not ceilings. State-specific obligations (e.g., New York attorney trust accounting at 7 years vs Connecticut at 7) and federal regimes (FINRA, SEC, OSHA) can extend them.

Legal hold mechanics

A legal hold suspends normal retention when:

Litigation is filed or threatened
A regulatory investigation begins
An internal investigation is opened
A preservation letter is received

The hold scope must be defined (which custodians, which matters, which document types). The trigger must be auditable (when did counsel determine litigation was reasonably anticipated). The release must follow a documented process (typically requires written counsel approval).

Where firms get into trouble

The litigation discovery cases that go badly almost always share one of these patterns:

Auto-purge that overrides hold. The retention policy ran. The legal hold was misconfigured. Documents that should have been preserved were destroyed. This is a sanction-worthy event in many jurisdictions.
No log of what was purged. Opposing counsel asks what documents existed. You can't produce them and can't prove you ever had them. Adverse inference attaches.
Hold scope ambiguity. The hold covered "matter X" but a related communication thread fell outside scope. Sanctions follow.
Manual hold processes. A partner forgot to forward the hold notice. The custodian deleted material in good faith. The system can't prove the notice was issued.

Retention without legal hold isn't a policy — it's a liability. Build the hold mechanism first, retention defaults second. The opposite order is how firms end up with adverse inference instructions.

Written by Rachel Okonkwo. Have feedback? Reach out at hello@verifypg.com.