What happens if I keep a record past its retention period instead of destroying it on time?
Holding a record beyond the end of its retention period is sometimes called “over-retention.” It may feel safer than destroying something, but keeping records past their scheduled disposition date carries real risks. A records retention schedule is meant to be followed in both directions: records should be kept for as long as required, and then disposed of when that period ends (unless a legal hold or other exception applies).
Why over-retention is a problem
- Legal exposure. Records you still possess can be subpoenaed or requested in litigation, audits, and (for public agencies) freedom-of-information requests. Information you could have lawfully destroyed on schedule may now have to be searched, reviewed, and produced.
- Privacy and security risk. The longer you keep personal or sensitive data, the larger the “attack surface” for a breach. Data-minimization principles favor keeping information only as long as there is a business or legal reason to do so.
- Cost and clutter. Storage, indexing, migration, and e-discovery review all cost more when obsolete records linger. Larger collections also make it harder to find the records that genuinely matter.
- Loss of defensibility. A retention program is strongest when it is applied consistently. Routinely ignoring disposition dates can make a program look arbitrary, weakening the legal protection that timely, scheduled destruction normally provides.
The important exception: legal holds
Never destroy a record simply because its retention period expired if it is subject to a legal hold, litigation, investigation, audit, or a pending records request. In those situations the duty to preserve overrides the schedule. Disposition should resume only after the hold is formally lifted.
What to do instead
- Apply disposition on schedule through a documented, repeatable process.
- Keep records of what was destroyed, when, and under what authority, so the action is auditable.
- Treat over-retained records as a backlog to review and clear, not as a permanent state.
- Coordinate with legal, privacy, and program staff before changing or suspending any schedule.
In short, over-retention is not a neutral choice. Disposing of records on time, except where a hold applies, is what keeps a program lawful, lean, and defensible.
For related guidance, see the retention and disposition topic hub.
Sources & further reading
Authoritative government and non-profit references.
- Records management (NARA) — National Archives (NARA)
- The Sedona Conference publications — The Sedona Conference
How to cite this page
APA
RM University Editorial. (2026). What happens if I keep a record past its retention period instead of destroying it on time?. Records Management University. https://www.recordsmgmt.org/questions/what-happens-if-i-keep-a-record-past-its-disposition-date/
MLA
RM University Editorial. "What happens if I keep a record past its retention period instead of destroying it on time?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/what-happens-if-i-keep-a-record-past-its-disposition-date/.
Related questions
- Can a company be fined for keeping records longer than the law requires?
- Can any manager authorize destroying records, or does it have to be someone specific?
- Can deleting emails too soon be considered illegal spoliation of evidence?
- Can different copies of the same document have different retention periods?
- Can GDPR storage limitation requirements force you to delete records you are legally required to keep elsewhere?