Contractor Checklist: Tracking Subcontractor Insurance Certificates

A subcontractor certificate of insurance can arrive by email, sit in a folder, and still leave the person responsible unsure what is current. A simple tracking process gives each certificate an owner, a status, a renewal date, and a clear next action.

Use the checklist below to build a record your project team can review without treating a file attachment as the answer.

What should a contractor treat a certificate of insurance as?

Treat a certificate as a document to review against the project requirements. Do not treat it as the insurance policy or as proof that every requirement has been met.

ACORD explains that its standard certificate is issued for information only and does not amend, extend, or alter the coverage provided by the policies. That is why the certificate should be matched to the requirements in the subcontract and any project-specific insurance exhibit. ACORD

What information belongs in the tracking record?

Create one record for each subcontractor and each project requirement set. Keep the certificate file with the record, but make the important fields visible without opening the attachment.

Record:

• Subcontractor legal name
• Project or contract the record supports
• Certificate date
• Insurer and policy number, if your requirements call for them
• Coverage types required by the contract
• Policy effective date and expiration date
• Additional-insured, waiver, primary-and-noncontributory, or other endorsement requirements that apply to that contract
• Certificate holder details required for the project
• Reviewer name and review date
• Status: pending, received, needs correction, accepted, expiring, expired, or replaced
• The next action, its owner, and its due date

The list should come from the signed contract documents. Do not make the certificate tracker the place where someone guesses what the subcontract requires.

What should happen when a certificate arrives?

Log the document first, then review it against the requirement list. A received email is not the same as a reviewed record.

Use this intake checklist:

1. Save the original document using a consistent file name.
2. Attach or link the document to the subcontractor and project record.
3. Enter the certificate and policy expiration dates.
4. Compare the named insured to the subcontractor named in the contract.
5. Compare the listed coverage and limits to the contract requirements.
6. Check whether the document and any required endorsements support the project-specific requirements.
7. Mark the record accepted only when a designated reviewer has finished the comparison.
8. If something is missing or unclear, mark the record needs correction and state exactly what is needed.

A short correction request is easier to act on than a vague note that the certificate is "not compliant." Name the missing document, coverage item, endorsement, date, or holder detail.

When should the team follow up on an expiring certificate?

Set follow-up dates before the policy expiration date, then make one person responsible for the next request. The correct lead time depends on the contract, the project, and how your subcontractors obtain renewal documents.

A practical follow-up sequence has three parts:

• A first request before expiration
• A second request if no replacement is received
• An escalation path for a certificate that expires without an approved replacement

Keep the follow-up history in the same record as the certificate. The next reviewer should be able to see what was requested, when it was requested, and what is still unresolved.

How should a contractor handle exceptions?

Separate an exception from an accepted certificate. An exception needs a named decision-maker, the reason for the exception, the date of the decision, and any deadline for resolving it.

Do not erase the requirement to make the tracker look complete. Keep the record visible as an exception until the required document arrives or the authorized decision-maker closes it under the company’s process.

What should a weekly certificate review cover?

A weekly review should answer one question: which subcontractor records need action now?

Review these groups:

• Certificates not yet received
• Records waiting for review
• Records marked needs correction
• Policies approaching expiration
• Policies already expired
• Exceptions without a current decision or follow-up date

Send the list to the people who can move each item forward. The purpose is not to produce a report. The purpose is to make the next action obvious.

What makes the process reliable?

A reliable certificate tracker does four things: it keeps the original document, records the contract requirement, shows the current status, and assigns the next action to a person.

The tracker supports review. It does not replace the contract, the insurance policy, or advice from the people responsible for your company’s insurance requirements. When the contract language or certificate is unclear, route the question to the appropriate internal decision-maker or insurance professional before marking the record accepted.

Subcontractor insurance certificate checklist

Use this as a final pass:

• The subcontractor and project are identified.
• The certificate file is saved with the record.
• The applicable contract requirements are listed.
• Coverage, dates, holder details, and required endorsements have been reviewed against those requirements.
• A reviewer and review date are recorded.
• The record has a clear status.
• The next action has an owner and due date.
• Follow-up dates are set before expiration.
• Exceptions are documented separately from accepted records.
• Expired or unresolved records appear in the weekly action review.

The best system is the one that lets a contractor answer three questions quickly: What did we receive? Does it meet the requirement? Who owns the next action?

Related reading

For another document routine that keeps review with a person, read How Can You Prepare Construction Submittals Faster Without Skipping Review?. For another checklist a project team can run, read Should You Bid This Construction Project? A Go or No-Go Checklist.