A formal written policy that specifies how long an organization must keep different types of business and employment records, when and how to destroy them, and the procedures for suspending destruction during litigation or government investigations.
Key Takeaways
A record retention policy answers a simple question for every piece of information in your organization: how long do we keep this, and what do we do with it when the time is up? That sounds straightforward until you consider that over 26 federal statutes impose record retention requirements, each state adds its own, and different record types within the same employee file can have different retention periods. Payroll records need three years. Tax records need four. OSHA exposure records need 30. Personnel records need one year after separation under EEOC guidelines, but two years if you're a federal contractor. Without a written policy mapping all of this, compliance depends on individual judgment, and individual judgment isn't reliable at scale. The policy also needs to address the other side of the equation: destruction. Keeping records too long increases storage costs, data breach exposure, and the volume of documents that could be subpoenaed in litigation. A proper retention policy establishes destruction schedules and procedures, including who authorizes destruction, how destruction is verified, and when destruction must be suspended.
The retention schedule is the centerpiece of any retention policy. It's a master list mapping every document type to its required retention period, governing law, and destruction method.
| Document Category | Minimum Retention | Governing Law/Agency | Recommended Retention | Notes |
|---|---|---|---|---|
| Payroll records (wages, deductions, hours) | 3 years | FLSA (DOL) | 7 years | State laws may require longer; California requires 3 years |
| Time cards and schedules | 2 years | FLSA (DOL) | 3 years | Keep with payroll records for consistency |
| Personnel records (general) | 1 year post-separation | EEOC (Title VII, ADA) | 7 years post-separation | 2 years for federal contractors (OFCCP) |
| I-9 forms | 3 years from hire or 1 year post-separation (whichever later) | DHS/ICE | Follow the formula exactly | Keeping too long creates liability too |
| Tax records (W-4, 941, W-2) | 4 years after tax due/paid | IRS | 7 years | Covers extended statute of limitations |
| OSHA injury/illness logs | 5 years | OSHA | 5 years | Calendar year plus five |
| OSHA exposure/medical records | 30 years | OSHA (29 CFR 1910.1020) | 30 years | Duration of employment plus 30 years for some |
| FMLA records | 3 years | DOL | 3 years | Includes leave requests, certifications, notices |
| Benefits plan documents | 6 years after plan terminates | ERISA | Permanent while plan exists | Includes SPDs, 5500 filings |
| Job applications (not hired) | 1 year | EEOC | 2 years | 2 years for federal contractors |
| Background check reports | See FCRA | FCRA | Destroy promptly after use | FCRA requires secure disposal |
| EEO-1 reports | 1 year | EEOC | 3 years | Keep originals and copies of filed reports |
A retention policy that just lists timelines isn't enough. It needs operational detail that tells people exactly what to do in every common scenario.
Define which departments, locations, and record types the policy covers. Most organizations create one master policy that covers all records, with a retention schedule attachment that breaks down timelines by department. Be explicit about whether the policy applies to physical records only, electronic records only, or both (it should cover both). Include email, chat messages, voicemails, and any other medium where business records might exist.
The schedule should list every record type, its retention period, the triggering event that starts the retention clock (creation date, separation date, plan termination, etc.), and the governing law or regulation. Where multiple laws apply to the same record, use the longest retention period. Update the schedule annually to capture regulatory changes.
This is the most critical section. When litigation is filed, threatened, or reasonably anticipated, all routine destruction must stop for records relevant to the dispute. The policy should name who can issue a litigation hold (typically legal counsel), how the hold is communicated to records custodians, how compliance with the hold is monitored, and when the hold is released. Destroying records subject to a litigation hold is spoliation, which can result in sanctions, adverse inferences, or even default judgment.
Specify approved destruction methods (cross-cut shredding for paper, secure digital deletion for electronic records), who authorizes destruction, and what documentation is required. Maintain a destruction log that records the document type, date range covered, destruction date, method used, and authorizing person. If you use a third-party destruction vendor, require a certificate of destruction for your records.
Assign clear ownership. Who maintains the retention schedule? Who reviews records for destruction eligibility? Who issues and monitors litigation holds? Who trains new employees on the policy? Without named owners, the policy becomes a document that exists in theory but isn't followed in practice.
These mistakes surface repeatedly in compliance audits and litigation. Each one is avoidable with proper policy design and enforcement.
Organizations with employees in multiple states face overlapping and sometimes conflicting retention requirements. Managing this correctly requires careful analysis.
States frequently impose retention periods that exceed federal requirements. California requires three years for payroll records (matching the federal FLSA minimum) but requires four years for apprenticeship records. New York requires six years for many employment records. Texas requires five years for workers' compensation records. Multi-state employers must identify the longest applicable retention period for each record type across all states where they have employees and apply that as their standard.
Most employment attorneys recommend a simplified approach: use the longest applicable retention period across all jurisdictions as your default for each record type. This is easier to administer than maintaining different retention periods for employees in different states, and it eliminates the risk of destroying records that are still within their required period in some states. The trade-off is slightly higher storage costs, but the compliance certainty is worth it.
Data that shows why formal retention policies matter for compliance and cost control.
Getting a retention policy written is step one. Getting the organization to follow it is the harder part.
Have employment counsel review all applicable federal, state, and local retention requirements for every jurisdiction where you have employees. Don't rely on internet lists. Regulations change, and a 2022 chart may not reflect 2026 requirements. The legal review produces your authoritative retention schedule.
Write a clear, specific policy that covers scope, the retention schedule, litigation hold procedures, destruction methods, roles, and enforcement. Avoid legal jargon where possible. The people following this policy are HR generalists and department managers, not attorneys. If they can't understand the policy, they won't follow it.
Every person who creates, stores, or handles employment records needs training on the policy. This includes HR staff, payroll, hiring managers, and administrative assistants. The training should cover what records they're responsible for, how long to keep them, where to store them, and what to do when they receive a litigation hold notice. Annual refresher training keeps the policy top of mind.
Conduct annual compliance audits to verify that retention schedules are being followed, destruction logs are accurate, and no unauthorized destruction has occurred. Hold department heads accountable for compliance within their areas. A policy that isn't enforced isn't a policy. It's a suggestion.