Updated Certificate of Insurance: When You Need a New COI

Last updated August 2026.

A vendor must send you an updated certificate of insurance whenever the information printed on the current one stops being true. In practice that means renewal, cancellation and rewrite, a mid term change of carrier or policy number, a change in limits, the addition or removal of an endorsement you require, and a change to the vendor's legal name. A policy number that changes mid term always requires a new certificate, because the certificate identifies coverage by policy number and yours now points at a policy that no longer exists.

The reason this matters is not paperwork tidiness. A certificate is a snapshot of a policy on the day it was issued, and it carries no mechanism for telling you it has gone stale. Nothing on the document updates itself. If the vendor's carrier cancels and rewrites the policy in June, the certificate you filed in January still shows the old policy number, the old effective dates and the old limits, and it will keep showing them until somebody asks for a replacement.

Does a policy number change mid term mean you need a new certificate of insurance?

Yes. The policy number is how a certificate ties itself to real coverage. Every limit shown in the grid on an ACORD 25 sits on a row identified by that number, and the whole point of the document is to say that this named insured holds that policy with that carrier. Once the number changes, the certificate on your file describes a policy the carrier no longer has open, so it cannot be used to verify anything.

Policy numbers change mid term more often than people expect. A carrier may rewrite a policy after a change in ownership or entity structure. A broker may move the account to a different carrier at a mid term renewal date. An insurer may reissue under a new number after a material change in the operations described in the application. In each case the coverage may be perfectly good and the vendor may be entirely compliant, but your evidence is out of date and you have no way to prove compliance if somebody asks.

What changes actually require a new certificate of insurance

Not every change on a vendor's policy needs fresh paperwork. The test is simple: does the change alter something the certificate prints? If it does, ask for a replacement.

Renewal is the obvious trigger and still the one that gets missed

Most commercial policies run twelve months, so every vendor file goes stale once a year on a date that has nothing to do with your contract dates. A vendor onboarded in March with a policy expiring in September gives you six good months and then becomes unverified, and nothing in your files announces it. This is why expiration date is the single field worth automating first. Everything else on a certificate can be reviewed once at onboarding. The expiration date has to be watched continuously, and our COI renewal tracking software exists specifically because that watching does not scale by hand.

Ask for the renewal certificate before the current one lapses rather than after. Brokers issue renewal certificates as a batch in the two or three weeks around the renewal date, so a request that lands in that window costs them nothing. A request that lands three weeks later is a separate job for somebody, and it takes correspondingly longer. If you want a fuller answer on how long the document itself stays good, we cover that in how long a certificate of insurance is valid.

What happens if the policy is cancelled and rewritten

This is the change worth treating as urgent, because a cancellation and rewrite can leave a gap. If the old policy cancelled on the 15th and the new one incepted on the 20th, there are five days during which the vendor had no coverage. Work performed in that window has no policy behind it, and no later certificate will fix that. The only way to see the gap is to compare the expiration date on the old certificate against the effective date on the new one, which is exactly the comparison nobody makes when certificates are filed as PDFs in a folder.

Ask for the new certificate and keep the old one. The pair of documents is your evidence of continuous coverage, and if there is a gap you want it discovered while you still have leverage rather than after a claim. What follows if the gap is real is covered in what happens when a vendor's insurance expires.

Does adding an endorsement require a new certificate?

Yes, if the endorsement is one your contract requires. The certificate reflects endorsement status in three places: the ADDL INSR column, the SUBR WVD column, and whatever free text sits in the Description of Operations box. When a vendor finally buys the additional insured endorsement you have been asking for, none of those three change on the copy in your file. You need a reissued certificate to evidence it.

It is worth remembering how little the certificate proves here even when it is current. The checkboxes are typed by whoever produced the document, and several common contract requirements have no checkbox at all. A per project aggregate endorsement has nowhere to appear on an ACORD 25 except as free text, and so does a primary and noncontributory requirement. For those, an updated certificate tells you what somebody typed, and only the endorsement page tells you what the vendor actually bought.

What if the vendor changes its legal name?

Treat a name change as a full re-verification rather than a document swap. The named insured on the policy has to match the entity that signed your contract. If the vendor reorganized from an LLC into a corporation, or was acquired and now trades under a parent's name, the question is not only which name prints on the certificate but whether the policy follows the entity performing your work. Ask for the updated certificate, confirm the named insured matches your contracting party, and check whether the contract itself needs to be assigned to the new entity. The same corrected name usually has to flow into your accounts payable vendor records and your W-9 on file, so it is worth handling once across all three rather than three times separately.

Can a certificate of insurance be issued for two years?

No, not in any meaningful sense. A certificate cannot evidence coverage beyond the policy period of the policy it describes, and commercial policies are almost always written for twelve months. A certificate showing a two year span would either be describing a rare multi year policy or would simply be wrong. If a vendor offers you a certificate that appears to cover two years, look at the effective and expiration dates in the grid rather than at any summary language, because those dates are the policy period and nothing overrides them.

How long should you give a vendor to produce an updated certificate?

Five business days is a reasonable standard for a routine reissue, and most brokers turn one around in one or two. The request goes to the vendor's broker rather than the vendor, so the practical bottleneck is usually the vendor forwarding your email. Naming the exact document you want shortens this considerably. A request that says please send a current certificate naming us as certificate holder, with the additional insured endorsement page attached, gets a usable response far more often than one that says please send your insurance. There is more on getting that first response right in how to request a COI from a vendor.

Put the standard in the contract rather than in an email. An insurance clause that requires the vendor to furnish a replacement certificate within five business days of any change in coverage gives you something to point at, and it moves the obligation onto the vendor where it belongs. Insurance is rarely the only recurring obligation buried in these agreements, and teams that already track renewal dates, licenses and attestations in one place tend to run this through the same compliance obligation tracking rather than keeping insurance in a separate spreadsheet.

How to stop chasing updated certificates by hand

The manual version of this job is a spreadsheet of expiration dates and a calendar reminder, and it fails for a predictable reason: the reminder fires, somebody sends an email, the broker replies with a PDF, and the PDF then has to be read and compared against the previous one by a person who has fifty other things to do. The comparison is where the value is and it is the step that gets skipped.

Reading the replacement certificate as data rather than as a document is what makes the comparison possible. Pull the policy numbers, effective and expiration dates, limits and endorsement flags off each new certificate, hold them against the prior version, and the interesting cases surface on their own: a limit that dropped, an endorsement that disappeared at renewal, a five day gap between a cancelled policy and its replacement. Those are the three findings that justify the whole exercise, and none of them are visible when certificates are filed as flat PDFs.

Upload a certificate at the top of this page to see the fields pulled out, or read how the full workflow fits together in a COI tracking system.

The short version

Ask for a new certificate whenever the policy number, the dates, the carrier, the limits, the required endorsements or the named insured change. Ignore changes that do not print on the document. Treat cancellation and rewrite as urgent because of the gap risk, treat a name change as a re-verification, and put a five business day turnaround into the contract so the obligation sits with the vendor. Then compare each new certificate against the one it replaces, because the change between two certificates is where the compliance failures actually live.