What is the difference between a litigation hold and a retention schedule, and what happens when they conflict?
A retention schedule and a litigation hold both govern how long information lives, but they serve opposite purposes and answer to different authorities. Understanding the distinction is essential because the two will, eventually, collide.
What each one is
A retention schedule is a routine, forward-looking governance instrument. It assigns each category of records a retention period based on legal, regulatory, operational, and historical value, and authorizes disposition (destruction or transfer) once that period ends. It applies organization-wide, in the ordinary course of business, and is built to be predictable and repeatable. Its goal is to keep what must be kept and defensibly dispose of the rest.
A litigation hold (also called a legal hold or preservation notice) is a reactive, event-driven directive. It is triggered when litigation, an investigation, or an audit is reasonably anticipated. It instructs custodians and IT to preserve potentially relevant information, suspending any routine process — including the retention schedule — that would otherwise alter or destroy it. Its goal is to prevent loss of evidence.
What happens when they conflict
When a hold attaches to records that are also eligible for scheduled disposition, the hold prevails. Preservation obligations override the retention schedule. You do not destroy material that is subject to a hold simply because its retention period has expired; the disposition clock is effectively paused for the affected items until the hold is released.
In U.S. civil matters, this duty to preserve flows from the litigation process and is reinforced by the Federal Rules of Civil Procedure, which address electronically stored information and the consequences of failing to preserve it. Destroying information after the duty to preserve arises can constitute spoliation and expose the organization to sanctions. Note that specific obligations, timing, and remedies vary by jurisdiction — state courts and other countries apply their own rules.
Practical implications
- Map your records categories so a hold can be applied precisely and lifted cleanly.
- Document when each hold begins, its scope, and when it is released, so the schedule can resume.
- Treat held items as a defined exception, not a reason to abandon routine disposition for everything else — over-retention carries its own cost and risk.
For related concepts, see e-discovery.
Sources & further reading
Authoritative government and non-profit references.
- Federal Rules of Civil Procedure — U.S. Courts
- The Sedona Conference publications — The Sedona Conference
How to cite this page
APA
RM University Editorial. (2026). What is the difference between a litigation hold and a retention schedule, and what happens when they conflict?. Records Management University. https://www.recordsmgmt.org/questions/litigation-hold-vs-retention-schedule-conflict/
MLA
RM University Editorial. "What is the difference between a litigation hold and a retention schedule, and what happens when they conflict?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/litigation-hold-vs-retention-schedule-conflict/.
Related questions
- A key custodian left the company—how do we preserve and collect their email and files after they're gone?
- An employee admitted to deleting emails relevant to a lawsuit—what do we do now?
- Are curative measures or monetary fines available when lost data can be replaced through other sources?
- Can a company be sanctioned for spoliation when an employee auto-deleted text messages or ephemeral chats?
- Can a court order cost-shifting or limit search terms when keyword searches return an unmanageable hit count?