Retention schedules and legal holds, handled

Records retention is a promise an organization makes to itself and to the people it is accountable to: we will keep what we are required to keep, dispose of what we are supposed to dispose of, and be able to prove we did both. It is also, at most places, a policy document that lives in a binder while the actual files do whatever they drift into doing.

The gap between the retention policy and the retention practice is where the risk lives. Records that should have been destroyed years ago sit around as liability. Records that should have been kept get deleted by someone clearing space. And when a regulator, an auditor, or opposing counsel asks you to account for it, the honest answer is a shrug.

A policy is only as good as its enforcement

Everyone with a retention schedule knows what they are supposed to do. The problem is that the schedule and the documents live in different worlds. Enforcement depends on people remembering to apply the policy to individual files, and people do not, because there are thousands of files and one of them.

Retention becomes a property of the record, not a task on someone's list.

The mechanics

Here is how a record is governed from the day it is filed to the day your policy says it can go.

01

Lock the schedule

A record, or a whole class of records, is locked to the retention schedule your policy requires.

02

Hold when needed

A legal hold freezes the affected documents, overriding retention until the hold is lifted.

03

Dispose on time

Time-limited records are tracked to their disposition date. Permanent records never expire.

04

Prove it

Every governance action lands in the audit trail, so compliance is a record, not a story.

1

Lock the schedule

A record, or a whole class of records, is locked to the retention schedule your policy requires.

2

Hold when needed

A legal hold freezes the affected documents, overriding retention until the hold is lifted.

3

Dispose on time

Time-limited records are tracked to their disposition date. Permanent records never expire.

4

Prove it

Every governance action lands in the audit trail, so compliance is a record, not a story.

Retention schedules that run on the record

You lock a record, or a class of records, to a retention schedule that reflects your policy. Permanent records are held permanently. Time-limited records are tracked to their disposition date. The schedule travels with the document, so retention is enforced by the system rather than by memory. Nothing is disposed of early, and nothing lingers past when your policy says it should go.

Legal holds that override everything

When litigation, an investigation, or an audit is reasonably anticipated, you place a legal hold, and it freezes the affected documents in place, overriding any retention or disposition until the hold is lifted. That is how you avoid the nightmare scenario where a routine retention rule quietly disposes of something you were obligated to preserve. Holds are permission-gated, so only authorized people can place or lift them.

Deletion that is reversible

Even ordinary deletion is a soft-delete: the underlying file is retained, not destroyed. Combined with retention and holds, this means the two failure modes organizations fear most, losing something that should have been kept and destroying something under hold, stop being live risks.

An audit trail that proves it

Every view, share, download, and governance action is recorded. When you need to demonstrate that a record was retained for its required period, disposed of on schedule, or preserved under hold, you have a trail rather than a story. For regulated organizations, that provability is the whole point.

It works across everything you keep

Retention is not just for one kind of document. The same schedules and holds apply to gift and grant agreements, contracts, and board records, so your whole archive is governed by one consistent, enforceable policy instead of a dozen local habits.

What week one looks like

You do not roll a retention program out everywhere at once. You start where an auditor would start.

Keep reading

See how governance underpins the whole system on the security page, or read more about the audit trail behind every document.