Determine document retention periods based on regulatory requirements, business needs, and litigation holds. Calculate the maximum retention for each document category.
This calculator compares three retention drivers for the same record set: the regulatory minimum, the business-use period, and any active litigation-hold period. It then uses the longest of those periods as the controlling retention horizon.
That makes it useful as a records-management worksheet, especially when teams are trying to document why one category must be held longer than another. The page does not determine the correct retention rule for a specific jurisdiction or record type. It only shows how the entered periods interact once you have identified them.
The built-in category defaults are broad examples, not a substitute for a record-by-record retention schedule. Real retention policies still need to be tied to the governing regulations, contract obligations, industry rules, and hold notices that apply to the organization.
This page is useful for turning competing retention drivers into one visible controlling period. It helps with policy drafting, records inventories, and destruction planning, but it should be treated as a scheduling worksheet rather than as stand-alone legal advice or a substitute for jurisdiction-specific records rules.
Retention Period = max(Regulatory Requirement, Business Need, Litigation Hold) Destruction Date = Document Creation Date + Retention Period
Result: 7 years retention required
With a 7-year regulatory requirement, 5-year business need, and no litigation hold, the maximum of 7 years controls. Documents can be destroyed after 7 years from creation.
Start by inventorying all document categories across the organization. For each category, identify all applicable federal, state, and industry regulations that specify retention periods. Layer in business requirements and ensure the schedule accounts for cross-jurisdictional obligations.
Litigation holds must be issued promptly when litigation is reasonably anticipated. Track holds systematically, communicate clearly to custodians, and release holds only when counsel confirms the matter is resolved.
Modern records management platforms can automate retention tracking, destruction approvals, and hold management. Investing in these tools reduces human error and ensures consistent application of the retention schedule across the organization.
Last updated:
This page compares the entered regulatory-retention period, business-need period, and litigation-hold period, then uses the longest of those values as the controlling retention horizon. It is a worksheet for documenting why one driver controls the schedule, not a legal engine that determines the correct retention period for a specific record class by itself.
The built-in document-category defaults are examples only. Real retention schedules still have to be tied to the statutes, regulations, contractual duties, and hold notices that apply to the organization's records.
A litigation hold (legal hold) is a directive to preserve all potentially relevant documents when litigation is reasonably anticipated. It overrides normal retention schedules and failure to comply can result in severe sanctions including adverse inference instructions.
Retention periods vary by record type, jurisdiction, and industry. The values shown on this page are broad examples only. A real schedule should be built from the specific statutes, regulations, contracts, and hold notices that govern the records in question.
No. Premature destruction can create regulatory, contractual, or litigation risk. Documents should be retained for the full duration of the longest applicable requirement, including any litigation holds.
The retention decision usually falls back to business need, contractual obligations, limitation periods, and litigation risk. There is no universal 7-year answer for every record type, so the rationale should be documented in the retention policy.
Electronic records require the same retention treatment as paper records. Implement automated retention policies in document management systems, email archiving, and cloud storage to ensure electronic records are properly retained and destroyed on schedule.
Defensible disposition is the practice of destroying records in accordance with an established, consistently applied retention schedule when no holds apply. Having a documented policy that is regularly followed protects against claims of selective destruction.