Construction document retention: what to keep and how long

A construction company should keep each record for the longest period any rule or risk requires. In practice that means at least 3 years for most tax and payroll records, 4 years for employment tax records, 5 years for OSHA injury logs, 3 years after final payment for federal contract records, 3 years after completion for Davis-Bacon payrolls, and much longer for project files that could be needed to defend a defect claim. Set a written retention schedule, apply it to paper and digital files alike, and stop destruction when a claim or audit is pending.

Retention periods set by federal rules

The OSHA access rule at 29 CFR 1910.1020 states that it applies to construction employers. If you monitor exposures to things like silica or noise, those records fall in the 30-year category. See silica exposure rules for contractors.

State laws add their own periods for state payroll, unemployment, prevailing wage, licensing, and public contracts, and they can be longer. Check each state you work in.

Project records: think in claims, not just statutes

No federal rule tells you how long to keep shop drawings or daily logs on a private job. The deciding question is how long someone could bring a claim about the work. Every state sets statutes of limitations and statutes of repose for construction claims, and contracts can add warranty periods and audit rights. The IRS also reminds taxpayers to check whether insurers or creditors require records longer than the tax rules do. Ask your attorney for your state's repose period and use it as the floor for closed project files.

What to keep in the permanent project file

• Executed contract, subcontracts, and all change orders
• Plans, specifications, addenda, and as-built drawings
• Approved submittals and shop drawings, plus the RFI log
• Daily logs, photos, inspection reports, and certificate of occupancy
• Pay applications, lien waivers, and retainage release records
• Subcontractor insurance certificates and endorsements for the project dates
• Warranties, O&M manuals, and the closeout package
• Correspondence on delays, claims, and disputes

How to build a retention schedule in 6 steps

1. List record types. Group them: tax and accounting, payroll and HR, safety, project, contracts, equipment.
2. Assign the longest applicable period from federal rules, state rules, contracts, and your claims risk.
3. Define the trigger. End of tax year, termination date, final payment, project completion. A period means nothing without a start date.
4. Choose storage. Scan paper to searchable PDFs in a standard folder structure. See how to set up project folders for every job.
5. Set a litigation hold process. When a claim, audit, or lawsuit is likely, stop deleting anything related until counsel releases it.
6. Purge on a schedule. Once a year, destroy what has passed its date, and log what was destroyed and when.

Storing records so you can actually find them

Retention only helps if the record can be produced. Some deadlines are short: OSHA gets 4 business hours to receive your injury records during an inspection under 29 CFR 1904.40. An auditor asking for 2023 certified payrolls on a closed federal job will not wait while someone searches an old laptop.

Use one folder structure for every job, name files the same way, and keep a closeout step that moves the whole file to an archive with the retention date written on it. Back up the archive somewhere other than the office server. Photos and texts from the field count as records too, so give crews a way to send them into the job file instead of leaving them on personal phones.

Who should own the schedule

In a small contractor, the controller or office manager usually owns the retention schedule, with sign-off from the owner and the company's attorney. Project managers own getting complete files into the archive at closeout. The safety manager owns OSHA and exposure records, and HR or payroll owns I-9s and payroll. Write the owners next to each record type so nothing falls between roles.

Worked example: a federal job and a private job closing the same year

Say a GC completes a federal clinic renovation in June 2026 with final payment in September 2026, and a private retail building in August 2026. Its schedule looks like this.

Notice the clinic payroll and the clinic contract file have different triggers. Keeping them together and using the later date is simpler and safer.

Mistakes to avoid

• Keeping everything forever. It raises storage costs and makes discovery in a lawsuit more expensive.
• Keeping nothing past seven years by habit, without checking whether a longer rule applies.
• Storing project records only in a PM's email, where they leave when the PM does.
• Deleting files after a claim letter arrives.
• Forgetting digital records like photos on phones and texts with owners.

Related guides and tools

See how to close out a construction project, how to manage construction documents and drawings, construction data security basics, and the project closeout checklist. Smart Business Automator stores project documents, daily logs, change orders, and compliance records by job so a closed project's file is complete and searchable. See construction workflow automation.