Resources/Core concepts/Insurance

Insurance

Certificate of insurance: the document that proves a policy exists. It names the insured, the insurer, the coverages and limits, the dates, and the party the producer issues it to. In Kuhlman, one certificate is one record under a project.

Applies to GCs, subcontractors, owners, brokers
Updated 2026-09-05

A certificate of insurance proves a policy exists. It names the insured, the insurer, the coverages and limits, the dates, and the party the producer issues it to. It is not the policy. In Kuhlman, one certificate is one record, and every certificate nests under a project, the same way a bond does.

A certificate has its own seats

SeatWho sits thereThe bond counterpart
InsuredThe party whose policy it is. On a GC’s project, usually a sub.Principal
InsurerThe carrier that wrote the policy.Surety
Certificate holderThe party the producer issues the certificate to, and who requires it: the GC, the owner, a city permit office. One certificate can name several holders.Obligee
ProducerThe insurance broker or agent who issues the certificate.Bond broker

Your insurance broker and your bond broker are different companies doing different work, even when one firm does both. Kuhlman seats them separately.

A certificate moves through its own chain

Certificates

  • Prep
  • Requested
  • In review
  • Delivered
  • Verified
  • Superseded

When the reviewer marks it Deficient, the ball goes back to the producer for a corrected certificate. When anyone on your team submits it again, it returns to In review. Anyone on your team can move a Rejected or Cancelled certificate from the status menu. We work out a lapse from the expiration date. No one sets it.

Figure 1. The certificate chain. The reviewer decides Verified. Today you set Delivered from the status menu.
StatusWhat it meansWho moves it
PrepYou know a certificate is required and have not requested it yet.You.
RequestedYou asked the producer for the certificate. The ball is in the broker’s court.You send. The broker produces.
In reviewOnce a clean document is attached, anyone on your team can submit the certificate for review. A reviewer is checking it against what the contract requires.The requiring party reviews. Never the insured, never the producer.
DeficientThe reviewer found gaps: wrong wording, a missing coverage, a limit too low. The producer has to correct it.The reviewer marks it. The producer fixes it.
DeliveredYou sent the certificate to every holder it names.Today you set Delivered from the status menu. Coming later: when you send a certificate, we email each holder it names a link to it.
VerifiedThe reviewer confirmed the coverage. The certificate is active.The reviewer.
SupersededA newer verified certificate replaced it, usually at renewal.We set it when the reviewer verifies the replacement.
CancelledThe carrier cancelled the policy.Anyone on your team can mark a certificate Cancelled from the status menu.

The party that requires the certificate is the one that verifies it

The producer produces and fixes a certificate. The party that requires it reviews and verifies it. A sub does not verify its own certificate, and a broker does not verify the one it issued. The interests are adverse by design, the same way an obligee, not the principal, releases a bond.

Reviewers reject wording more than anything else

A typical thread: a city permit office rejected a sub’s certificate because the Description of operations did not use the wording the city attorney requires. The producer sent back a corrected certificate without the permit number. The permit office marked up the next one too. Twelve emails across two weeks, five companies copied, and at the end nobody could say which version was current.

In Kuhlman that certificate is one record. Each time the reviewer rejects it, the certificate reads Deficient and the ball goes to the producer. Each time the producer sends a corrected certificate, we add a version to the record. Everyone talks on the record’s thread, and the current status answers the question the email thread could not.

If you are the sub: the certificate is yours and your producer issues it. The GC or owner who requires it verifies it. When it comes back Deficient, your producer fixes it; you do not verify your own certificate.

A renewal supersedes; the date decides a lapse

Every certificate carries an expiration date. A verified certificate past that date is expired. Nobody sets it; the date does. When the reviewer verifies the renewal certificate, we mark the old one Superseded. A lapse is the event everything on this page exists to prevent, because a sub with lapsed coverage on your job is your exposure.

You work with certificates on these screens

ScreenWhat it shows
InsuranceCertificates in process, open actions in your court, coverage by project, and certificate holders.
Certificate detailOne certificate: details, holders, open requests, the related project and coverage, thread, activity timeline, and documents. Actions change with status: submit for review, start review, verify, return for revision.
Request COIHow you ask a producer for a certificate, and seat the reviewer.

We use these terms

Policy, certificate
The policy is the coverage. The certificate is the document that proves it. Kuhlman tracks the certificate and what it says about the policy.
Certificate holder
The party the producer issues a certificate to. The insurance counterpart of a bond’s obligee.
Additional insured
A party the policy itself extends coverage to, by endorsement. Not the same as a certificate holder. A holder receives proof; an additional insured receives coverage.
Coverage, limits
The kinds of insurance on the certificate, and the most the insurer will pay for each.
Deficient
The reviewer found it short. The producer has to correct it before the reviewer can verify it.
Superseded
Replaced by a newer verified certificate.

Product pages that build on this concept: Track insurance certificates · Share a bond's status · Monitor license health