Records retention vs legal hold

Retention disposes records on a schedule; legal hold suspends disposition. Getting the interaction right is exactly what auditors check — here is how the two differ and how to do both provably.

Retention and legal hold are often confused, but they do opposite jobs — and the place they intersect is where enterprises get into trouble. One is about disposing of records on time; the other is about freezing specific records regardless of schedule.

Doing both correctly, and being able to prove it, is the heart of defensible information governance.

Two different jobs

Retention applies time-based rules — keep a record for a set period, then dispose of it. Legal hold suspends disposition for records relevant to litigation, investigation, or audit, no matter what the retention schedule says. When a hold is in place, it must override retention.

Where it goes wrong

Manual processes are the failure point. Held records get disposed because the hold lived in a spreadsheet, or expired records linger for years because no one ran the schedule. Both are audit failures, and both are common when retention and holds are managed by hand across multiple systems.

Handling overlapping regulations

Real enterprises face conflicting jurisdictional retention laws. The defensible approach is to apply the strictest matching rule automatically and to show the governing regulation behind each decision, so the outcome is explainable rather than arbitrary.

Doing it provably

Automatic retention, a legal-hold override that blocks disposition, and a tamper-evident ledger of every action together make the outcome defensible. When an auditor asks what happened to a record, the answer is a hash-chained trail, not an apology.