What Is a Certificate of Insurance and What Should Your Lab Check Before Signing?

A certificate of insurance is a document that confirms a policy was in force on a specific date, listed the limits shown on the certificate, and named the certificate holder for informational purposes. That is what it does. It does not guarantee the policy will stay in force tomorrow, does not amend or grant any coverage that is not already in the underlying policy, and does not create rights the holder would not have without it. Labs that rely on a certificate as their full verification of a vendor’s, contractor’s, or partner’s insurance are relying on less protection than they assume, and the gap shows up when a claim arises and the actual policy responds (or does not) on its own terms.

What the Certificate Is, and What It Is Not

A standard ACORD certificate carries the producer’s name, the insured’s name, the carriers writing each line, the policy numbers, the effective and expiration dates, the limit structure for each line, and a section for additional remarks. The disclaimer in the document is the most important sentence on it: the certificate is issued as a matter of information only, it confers no rights upon the certificate holder, and it does not amend, extend, or alter the coverage afforded by the policies listed. The producer issues it from the agency management system, not from the carrier directly, and the document reflects what the producer’s system shows on the day of issuance.

That is a different thing from what most certificate holders read it as. A hospital outreach contract, a reference-lab agreement, or a contractor onboarding document treats the certificate as proof of coverage. The proof is narrower than it looks: proof on that day, of those limits, for those policy numbers, for general informational purposes. The certificate does not bind the carrier to anything beyond what the policy already says, and the policy is the document that controls.

Where the Gap Actually Lives

Three gaps surface most often. The first is that the certificate may list additional insured status for the holder, but the actual endorsement on the policy may be narrower than the contract requires, or may not exist at all, the precise mechanism described in what an additional insured endorsement is. The certificate is evidence; the endorsement is the grant. The second is that the certificate reflects coverage on the issue date and does not survive a mid-term cancellation, a non-renewal, or a coverage reduction the carrier makes later. A certificate dated three months ago does not prove the policy is still in force today. The third is that the wording on the certificate’s remarks section may not match the underlying policy’s wording on key conditions, including primary and non-contributory language, waiver of subrogation, and notice of cancellation. The mismatch lives until the claim, then surfaces.

For a lab, the most consequential certificates are the ones the lab receives from its couriers, its contract phlebotomists, its IT and software vendors, its waste-disposal contractor, and its reference-lab partners. Each of those relationships carries a contractual insurance requirement, and the certificate is the document the contract asks for. The document is the start of the verification, not the end.

What to Check Before Signing

Five checks turn a certificate from a piece of paper into actual verification. Confirm the named insured on the certificate matches the contracting party exactly: a parent company on the certificate when the contracting entity is a subsidiary is a mismatch. Confirm the limits meet or exceed the contract requirement on each line: a per-occurrence limit that meets the requirement and an aggregate that does not is a partial answer. Confirm the additional insured language on the certificate is backed by an actual endorsement on the policy, and ask for the endorsement form number, the same discipline that applies in a hospital outreach or reference lab contract. Confirm the policy effective dates extend through the period of the work, and set a renewal reminder for the policy expiration. Confirm the certificate references any required terms (primary and non-contributory, waiver of subrogation, notice of cancellation) and that those are actually on the policy.

For higher-risk relationships, request a sample of the underlying policy or a specific endorsement page, not only the certificate. A contractor who refuses to provide an endorsement page when the contract requires the endorsement is signaling something. The broader program logic for the lab’s own program sits in what insurance a CLIA-certified lab needs, and the certificates the lab issues to its own customers carry the same disclaimer in reverse.

The Certificate Is the Beginning of Trust, Not Its Substitute

The cheap discipline is to read every incoming certificate against the contract that asked for it, not against a generic checklist. Where the certificate matches and the underlying endorsements have been confirmed, the document does what the contract intended. Where it does not, the gap is documented, fixable, and visible before the relationship goes live. The expensive version is the discovery at claim that the document everyone relied on did not deliver what it appeared to.

A specialty review through Tower Street Insurance can confirm whether the certificates a lab receives from its vendors and partners actually correspond to the policy terms the contracts require, and where the lab’s own outgoing certificates match the obligations it has agreed to.