Certificate of Insurance Issuance and Accuracy Checklist

This checklist covers the pre-issuance review of a certificate of insurance against the source policy, endorsements, and the underlying contract or request. It checks named insured details, policy dates, limits, required endorsements, and any special wording before the certificate is sent. It is designed to catch issuance errors and unsupported statements, not to replace legal review of the contract itself.

Use it every time a COI is prepared for a client, landlord, general contractor, vendor, lender, or other certificate holder. It is especially important when the request includes additional insured, waiver of subrogation, primary and noncontributory wording, or project-specific language. It should be completed before issuance, not after the certificate has already been sent.

A trained insurance producer, account manager, risk coordinator, or compliance reviewer should complete it before issuance. The reviewer should have access to the policy declarations, endorsements, and the request or contract that drives the certificate language. If the request is unusual or the wording is not clearly supported, escalate it for carrier, broker, or legal review.

It supports compliance with common insurance certificate controls, contract administration practices, and risk transfer requirements, but it does not replace the policy or endorsement language. Many requirements come from contract terms, carrier forms, and industry standards rather than a single law. Use it alongside your organization’s insurance review process and any applicable state or carrier rules.

Common mistakes include using an expired policy date, listing the wrong named insured, showing limits that do not match the declarations, and adding additional insured wording without an active endorsement. It also catches unsupported special wording, incorrect holder addresses, and vague descriptions of operations that overstate coverage. These errors can create disputes even when the underlying policy is valid.

Yes. You can add fields for construction projects, landlord requirements, vendor onboarding, fleet operations, or professional liability depending on the certificate request. Many teams also add carrier-specific notes, approval routing, and required attachment fields for endorsements or declarations pages. The structure should stay focused on source-document verification and issuance approval.

Recheck whenever the underlying policy renews, the contract changes, or the holder requests updated wording. If the certificate is tied to an ongoing project or vendor relationship, set a renewal reminder before policy expiration so the certificate does not become stale. A certificate should also be reviewed again if the insured’s operations, limits, or endorsements change.

An ad hoc review depends on memory and individual judgment, which increases the chance of missing a mismatch between the request and the policy. This checklist creates a repeatable control for verifying the same critical items every time. It also leaves an audit trail showing who reviewed the certificate, what source documents were checked, and whether any exceptions were approved.