COI fundamentals

What a certificate of insurance shows—and what it does not

A certificate of insurance is a summary of insurance information prepared for a particular purpose. It is useful evidence, but it is not the policy and does not independently create coverage.

The four documents people often confuse

Insurance policy

The contract containing coverage grants, definitions, conditions, exclusions, limits, and other terms.

Endorsement

A document that changes or clarifies the policy. An executed endorsement may add an additional insured, modify priority of coverage, or waive certain recovery rights, subject to its wording.

Certificate of insurance

A snapshot of selected policy information on the date it is issued. It generally does not amend or extend the underlying policy.

Contract insurance requirement

A promise between contracting parties about insurance. The requested terms still need to be available and properly reflected in the actual policy documents.

Fields worth checking first

The exact named insured and business entity.
Policy effective and expiration dates.
Coverage lines and their individual limits.
Certificate holder name and address.
Indicators for additional insured or waiver of subrogation.
Description of operations, project, or location when requested.
Separate endorsements or supporting documents requested by the client.

Do not make coverage conclusions from a certificate alone. If a requirement matters to the job or a potential claim, have the licensed agent or broker confirm it against the policy and endorsements.

Certificate holder is not the same as additional insured

A certificate holder receives the certificate as evidence. Additional insured status, when available, comes from the policy or an endorsement—not simply from placing a name in the certificate holder field. This distinction is one of the most frequent sources of confusion in contractor onboarding.

A practical next step

Gather the client’s written requirements and use the free rejection-risk checker. The result is a preparation aid, not an approval or coverage determination.

A practical reading sequence

Start with the question, then find the right source

A certificate can answer useful administrative questions: which named insured is displayed, which insurer and policy period are listed, what limits appear, who is shown as certificate holder, and whether the form refers to other evidence. It cannot, by itself, answer every question about policy wording, insured status, contract satisfaction, or how coverage would apply to a loss. The safest workflow is to identify the decision you need and then use the source and person authorized to support it.

Client question

What is being requested?

Use the current contract exhibit, portal instruction, bid document, lease, or a dated clarification from the client. Preserve its version and project scope.

Issuer question

What can the policy support?

Ask the licensed agent, broker, insurer, or authorized issuer about policy-backed evidence, endorsements, document identity, and availability.

Contractor task

What must be organized?

Confirm project facts, compare fields, control package versions, submit through the required route, and keep the observable response.

Reviewer decision

What has the client accepted?

Record the reviewer’s dated outcome separately from the issuer’s answer and separately from proof that a file was delivered.

Use this four-part source hierarchy

Written requirement: defines what the client currently asks to receive. A portal summary and a contract exhibit can differ, so retain both and request clarification rather than choosing silently.
Policy and issued endorsements: contain the actual insurance terms. The certificate summarizes selected information but does not replace those documents.
Licensed-issuer response: explains what evidence can be issued and which document or policy provision is relevant. It should not be replaced by contractor-created wording.
Delivery and reviewer record: shows what was sent, received, questioned, corrected, or accepted. An upload confirmation proves a workflow event, not coverage.

Example: additional insured evidence

Suppose a client asks to be shown as an additional insured for ongoing and completed operations. First preserve the exact entity name, project, operations, policy line, and requested timing from the written requirement. Next ask the licensed issuer which policy document, if any, addresses each part of that request. Compare the returned certificate and supporting evidence with those facts without interpreting unfamiliar wording yourself. Finally, deliver the controlled package and retain the reviewer’s actual response. A certificate-holder address, an “AI” checkbox, a description sentence, an issued endorsement, and a client acceptance message are related records, but they are not interchangeable.

Choose the next step for your situation

If a submission was rejected, begin with the COI Rejection Risk Checker and preserve the reviewer’s exact reason.
If the wording is unclear, use the Requirement Phrase Explainer to separate client and issuer questions.
If limits are involved, compare each line with the Coverage Limit Comparator.
If several documents or messages conflict, create an Evidence Source Register before deciding what needs clarification.

Keep the boundary clear: these steps reduce administrative ambiguity. They do not verify coverage, interpret a contract or policy, or guarantee that a reviewer will accept evidence.