How Long Should You Keep Subcontractor Certificates of Insurance?

What determines how long a contractor should keep COIs?

Start with the project jurisdiction, signed agreements, insurance requirements and any unresolved matter. Ask counsel to turn those inputs into an instruction your controller can administer. “Keep everything for seven years” leaves unanswered which records it covers and when counting begins.

Travelers' contractual risk-transfer guidance recommends retaining project records and consulting legal counsel about duration and applicable requirements. It also calls for communicating the policy to project management. That gives you a practical starting point: obtain a written instruction and make sure the people closing projects can find it.

The uncertainty is familiar. A Construction Financial Management Association discussion describes a GC receiving conflicting advice about post-completion insurance records. That is an operational question, not authority for a retention deadline. This guide provides a worksheet for the decision; confirm the final schedule with counsel and your broker or carrier.

Why should you keep expired certificates of insurance?

A renewal answers a question about a later policy period. It does not replace the document you received while a subcontractor worked on an earlier job. Preserve expired certificate of insurance records under their original policy years so the current vendor screen does not become your entire insurance history.

Suppose an auditor asks about work performed before the vendor changed carriers. The current COI points to the wrong period. The earlier certificate helps identify the insured, carrier, policy number and dates reported then. Travelers' general-liability audit guidance specifically addresses keeping certificates covering the time subcontractors performed work, including evidence from adjoining terms when necessary.

Preserving that evidence is separate from collecting future renewals. For a current lapse, use the mid-project insurance expiration guide. For post-completion collection, have the contract's continuing requirements reviewed before stopping requests. Neither decision should overwrite the historical file.

How do statutes of repose and legal holds affect COI retention?

Keep these concepts separate in your certificate of insurance retention policy. They answer different questions, even when a lawyer considers them together:

• Retention schedule: your approved instruction identifying the records, starting event, duration and disposal process.
• Statute of repose: a legal deadline for certain claims measured from a specified event. Counsel determines applicability, the trigger and exceptions.
• Legal hold: a preservation instruction for relevant information when litigation is pending or reasonably anticipated. Follow counsel's direction on scope and release.

A repose deadline is not a universal records law or an automatic deletion date. Avoid entering “completion plus X years” because someone used it on another project. Ask which completion event counts, which obligations were considered and what happens if a dispute arises before routine disposal.

Route a claim notice or preservation concern to counsel promptly. Do not wait for a lawsuit to ask whether records must be preserved. Suspend proposed disposal while that question is reviewed, including any routine cleanup that could remove relevant emails or attachments. Record the instruction and its owner.

Which documents should stay with each policy year and project?

Build a packet someone outside the original project team can follow. Keep these document classes linked by project, subcontractor legal entity and relevant policy period:

• The original COI, corrected versions and renewal certificates for the work dates.
• Issued endorsements, referenced schedules and supporting policy pages; obtain fuller policy evidence when your reviewer requires it.
• The executed subcontract, insurance exhibit, amendments and documented exceptions.
• Work dates, completion records, return visits and relevant invoices supporting the timeline.
• Review decisions, producer correspondence, cancellation information and preservation instructions.

Each document has a job. The contract records the obligation; the certificate summarizes reported insurance; the policy and issued endorsements establish the insurance terms. The Texas Department of Insurance certificate FAQ explains that a certificate cannot go beyond the policy and that policy or endorsement copies can be provided. Do not turn a retained certificate into a coverage guarantee.

At closeout, assign this packet using the subcontractor closeout checklist. Keep the coverage explanation short in the records schedule. Our completed operations coverage definition explains that concept. If claims-made coverage is involved, ask the broker which continuity, retroactive-date and reporting-period evidence belongs in the packet. Retention alone cannot repair an insurance gap.

How do you build a COI retention schedule?

Copy this filled example into your records register. The names and project are fictional. It deliberately shows a file awaiting approval: missing legal instructions should remain visible rather than become a guessed destruction date. Use one entry per project/entity and document class, with separate policy-year references where the work crosses renewal.

Once reviewed, replace the pending instruction with the approved duration, exact trigger, approval date and schedule version. Record any continuing renewal requirement separately, including who decides when it ends. A preservation flag and a renewal task can have different owners and different end dates.

Add a proposed disposal-review date only after the trigger is verified. Treat it as a checkpoint requiring authorization, not a scheduled purge. Before disposal, the owner checks for holds, outstanding audits, claims and contract obligations, then records what was authorized and by whom.

How do you retrieve insurance records for an old project?

In October 2026, Alder receives a question about water damage at River Street Clinic. Cedar's installation crossed the 2021 and 2022 policy years, and its return visit occurred in September 2022. The coordinator finds a 2026 renewal first. Here is the retrieval test for the historical packet, without deciding which insurance responds to the reported damage.

1. Reconstruct the timeline. Retrieve installation records, completion evidence and the return-visit record. Keep work dates separate from the alleged damage and discovery dates; provide all of them to the reviewer.
2. Retrieve both work-year packets. Find the 2021 COI identifying GL-218 and the 2022 COI identifying GL-319. They establish what insurance details were reported for those terms, not whether this loss is covered.
3. Match issued evidence. Open each term's endorsements and schedules with the supporting policy pages. Check policy numbers, insured names and referenced entities or locations. Flag missing pages for the broker.
4. Retrieve the agreement. Open the executed subcontract and insurance exhibit. They show what Cedar agreed to provide. Include amendments and exceptions so the reviewer does not rely on an outdated requirement.
5. Record the handoff. Give counsel and the broker or carrier the indexed packet, timeline and missing-document list. Ask counsel for preservation instructions. Record who received it and who owns the next action.

If the 2021 endorsement is missing, mark that gap plainly. Do not substitute a blank specimen or assume the 2022 form applied earlier. Ask the producer or carrier for the issued evidence and retain the request and response. An incomplete packet with a clear gap is more useful than an unexplained “insurance approved” note.

For a premium-audit request, attach the relevant work and payment records as well. The contractor insurance audit guide explains that separate exposure. A past acceptance decision should be traceable to the evidence available then, even if today's team would request more documents.

How to preserve access when a vendor leaves or software changes

A PDF linked only from a former employee's inbox is a fragile record. Before offboarding a vendor or replacing software, inventory the files and their index. Keep company-controlled copies in readable formats, identify the records owner and check access after staff changes.

Use filenames that distinguish entity, policy period and document class. Preserve received originals and identify corrections separately. After a migration, compare the inventory with the destination, open sample attachments and confirm that referenced schedules survived. Have a colleague retrieve the example packet using the register alone.

Travelers also recommends backups and maintaining electronic accessibility through system upgrades. Assign those checks to a person. Confirm download, account-closure and storage terms before a system change; a dashboard link is useful only while the underlying file remains accessible.

Can SubDoc manage your COI retention policy?

SubDoc supports centralized vendor document handling, certificate data extraction and team expiration notifications. Those features help organize the ongoing workflow. For that process, follow the subcontractor COI tracking guide. Deciding how long to keep subcontractor COIs still requires your approved schedule and a person accountable for applying it.

Do not assume immutable archives, automatic legal holds, a retention-policy engine or indefinite storage. Confirm your storage and access arrangements before relying on any workspace as the sole historical repository.

How should you review old COIs before deletion?

Deciding how long to keep certificates of insurance becomes manageable when every packet has an owner, an approved instruction and a tested retrieval location. Start with one completed project, resolve the missing instructions with counsel and your carrier, then apply the schedule consistently. These questions cover the decisions that often come up during cleanup.

Frequently Asked Questions