A certificate of insurance with more than one policy: how it becomes separate licenses
A certificate of insurance is rarely one policy on one date. Insurers routinely print general liability, workers’ compensation and sometimes an umbrella or auto policy on the same page, each with its own policy number, its own carrier, and — this is the part that causes trouble later — its own end date.
Treated as a single document, a COI like that is easy to file and easy to misread. Treated as the several separate policies it actually is, it stops being one certificate and starts being several tracked renewals, which is what it needs to be.
Each policy is read on its own
When a COI with more than one policy is uploaded, each one is read separately — its own policy number, its own insurer, its own end date, each checked against the policy period printed as “From … To …” rather than against a single date for the whole page.
The result is shown as a list of the policies found, each with its own suggested details. From there you choose to save one of them, or all of them, as separate licenses, in one click — no retyping, and no need to upload the same certificate again for the second policy.
Why splitting them matters
Two policies on the same certificate almost never share a renewal date, even when they come from the same insurer. A general liability policy might run January to January while the workers’ comp on the same page runs March to March.
Treating the COI as a single record means the whole certificate shows as current right up until the policy that renews first has already lapsed — and because the document on file still looks fine at a glance, that’s exactly the kind of gap nobody notices until someone asks for proof.
Splitting the policies at the point of upload means each one gets its own countdown and its own reminders from day one, rather than a single reminder tied to whichever date happens to be read first.
What to check before confirming
Multi-policy certificates are exactly the documents worth a closer look before confirming: check that the policy number and date pulled for each line actually matches that line, not a neighboring one, especially on a certificate with small print or several similar-looking rows stacked close together.
A common shape for this to take
The most frequent version of this is a subcontractor’s COI that bundles general liability and workers’ comp on one page, because that’s how most insurance brokers produce them. If you’re collecting certificates from several subs for the same job, it’s worth checking each one the same careful way rather than assuming the format is identical from sub to sub — different brokers lay out the same two policies differently, and the extraction treats each certificate on its own terms.
What this avoids downstream
The alternative to splitting policies at upload is doing it manually later, after noticing a renewal clock applies to only part of a document you filed as one thing. That’s not a hard fix, but it’s an avoidable one — the moment a multi-policy certificate is uploaded is the cheapest possible time to separate the policies, before any reminders have been set and before anyone has built a mental model of the certificate as a single renewal.
Where ContractorLicenseAlert fits
How dates are read from documents
General liability vs workers’ comp: two different renewal clocks