Most organizations keep far more than they are required to. It feels like the safe choice. It is usually the expensive one — and in a dispute or an audit, it can be the damaging one.
This is a plain explanation of what a retention schedule is, why over-retention costs money and raises risk, and how to build one people will actually follow.
General information, not legal advice.
What a retention schedule is
A retention schedule is a written list of the record types your organization holds, how long each must be kept, and what happens at the end of that period. That is all. The difficulty is never the concept; it is getting the list to match reality and keeping it current.
Each entry needs four things: what the record is, where it lives, how long it is kept, and who is accountable for it.
Why keeping everything is not the safe option
Cost compounds quietly. Storage looks cheap per gigabyte, which is why nobody notices it. The real cost appears when that volume has to be searched, reviewed or produced — at which point you are paying to read material you were never obliged to keep.
Discovery scope follows what exists. If a record exists and is responsive, it is potentially discoverable. Material retained past its required life expands the volume that must be collected, processed, hosted and reviewed. Defensible disposition performed before any duty to preserve attaches removes that exposure entirely.
Data you hold is data you must protect. Every retained record is within scope of a breach. Reducing what you hold reduces what can be exposed.
Findability degrades. Search quality falls as volume rises. Ten years of superseded drafts makes the current version harder to locate, not easier.
Why under-retention is worse
Disposing of something you were required to keep is a materially more serious problem than keeping something too long. Regulatory retention obligations, contractual commitments and litigation holds all override a retention schedule.
This is why disposition must be documented and consistent. A record destroyed under a written schedule applied uniformly is defensible. The same record destroyed ad hoc is very hard to explain.
The litigation hold overrides everything
Once litigation is reasonably anticipated, the duty to preserve attaches and normal disposition must stop for anything potentially relevant. A retention schedule that cannot be suspended is a liability rather than an asset.
In practice this means knowing what a hold applies to, being able to suspend disposition for that material specifically, and documenting when the hold started and who was notified. Rule 37(e) consequences for failing to preserve are significant and entirely avoidable.
Building one people will follow
Start with what exists, not with a template. Inventory the record types actually held before deciding how long to keep them. A schedule describing records you do not have, while omitting the ones you do, is worse than none.
Group aggressively. A schedule with two hundred categories will not be applied. One with fifteen might be. Precision that nobody follows is not precision.
Name an owner per category. Retention without accountability decays within a year.
Automate the disposition, not the judgment. Systems can flag records reaching end of life. A person should confirm no hold applies before anything is destroyed.
Review annually. Regulations change, systems change, and the schedule drifts from reality faster than anyone expects.
Where to start
If none of this exists yet, the first step is not writing a policy. It is finding out what you hold and where. Almost every organization we work with is surprised by that inventory — usually by how much duplicate material sits in places nobody is accountable for.
Related
Need a retention schedule that reflects what you actually hold? Get in touch.
Pingback: Why Document & Data Management Matters More Than Ever - EDDM Consulting