How to Request a Certificate of Insurance From a Vendor (With Email Templates)

Almost every guide on this topic tells you to send a formal request and keep a paper trail. That's true, and it isn't the part that goes wrong.

What goes wrong is specificity. A vendor who receives "please send your certificate of insurance" forwards that to their broker, and the broker issues a standard certificate showing whatever the vendor happens to carry. It arrives, you check it, and it's missing the additional insured endorsement — so you ask again, wait another week, and the vendor starts work in the meantime because the job can't wait.

A request that names the exact entity, the exact limits, and the exact endorsements produces a compliant certificate on the first attempt. The same email, sent with five extra lines of detail, removes an entire round trip and a week of exposure. That is the whole difference, and it costs nothing.

This guide covers when to ask, who to ask, what to specify, and the words to send — including templates you can paste straight into your email client.

The single biggest mistake is timing. Most businesses request the certificate once the vendor has been selected and the work is about to begin. At that point you have no leverage: the schedule is set, the crew is booked, and refusing to let them start costs you more than it costs them.

Ask during procurement instead — in the RFP, the vendor application, or as a condition of the contract. Before signature, insurance requirements are simply part of the deal, and a vendor who cannot meet them tells you something useful while you can still choose someone else.

Practically, allow a week. A broker typically issues a certificate within one to three business days, but requests for specific endorsements can take longer if the endorsement has to be added to the policy first. Asking on Friday for a Monday start is how businesses end up accepting whatever arrives.

A certificate of insurance is issued by a licensed producer — an agent or broker — on behalf of the insurer. The vendor cannot legally issue their own.

So the strongest version of the request asks the vendor to have their broker send the certificate directly to you. This is a small change in wording with a disproportionate benefit: the document never passes through the hands of the party who benefits from altering it, which removes the most common route to a forged certificate. Our guide on how to spot a fake certificate of insurance covers why that matters and what forgeries look like.

It also gives you a named contact at the agency. When something needs correcting — a missing endorsement, a misspelled entity name — you can deal with the broker directly rather than playing telephone through a contractor who is busy on site.

This is the part that determines whether you get a compliant certificate first time. Vague requests produce vague certificates.

Note the first item in particular. The certificate must name the exact legal entity that signed your contract, not a trading name, an abbreviation, or a related company. A certificate covering "Smith Building Co." does nothing for you if your contract is with "Smith Building Company LLC", and this mismatch is one of the most common reasons a certificate fails at claim time rather than at check time.

Paste this into your email client and replace the bracketed fields. It's deliberately short; the specificity is in the list, not in the prose.

Subject: Certificate of insurance required before [project / start date]

Hi [Name], before we can confirm [project name / start date], we need a current certificate of insurance on file. Please ask your insurance broker to issue it and send it directly to [your email]. So the certificate is right first time, here is exactly what it needs to show: Certificate holder — [Your Legal Entity Name], [address]. Named insured — [Vendor Legal Entity Name]. Coverages and minimum limits — General liability $1,000,000 per occurrence / $2,000,000 aggregate; Workers' compensation as required by law; Auto liability $1,000,000 combined single limit. Endorsements — [Your Legal Entity Name] named as additional insured; waiver of subrogation in favor of [Your Legal Entity Name]; primary and non-contributory wording. We'll need this by [date] to keep the start date. Please let me know if any of the above is a problem so we can discuss it now rather than at the last minute. Thanks, [Your name]

That closing line does real work. It invites the vendor to raise a coverage gap early, which is far better than discovering it when the certificate arrives non-compliant on the day work is due to start.

Send this three to five business days after the initial request if nothing has arrived. Keep it friendly and factual — most delays are the broker's queue, not obstruction.

Subject: Reminder — certificate of insurance for [project]

Hi [Name], following up on the certificate of insurance we requested on [date]. We still need it before [start date] and can't confirm the schedule without it. If it's easier, send me your broker's contact details and I'll request it directly. The requirements are in my email below. Thanks, [Your name]

Offering to contact the broker yourself removes the most common bottleneck, which is a busy contractor who hasn't got round to forwarding the request.

This is the one almost everybody forgets, and it is where lapses actually happen. A certificate is a snapshot of a single day. The vendor you onboarded correctly in March is uninsured in September if nobody asked again.

Send this 30 days before the expiration date shown on the current certificate.

Subject: Insurance certificate expires [date] — renewal needed

Hi [Name], our records show your certificate of insurance expires on [date]. To avoid any interruption to work on [project / property], please ask your broker to send an updated certificate before then. The requirements are unchanged from your original certificate. Thanks, [Your name]

If you are tracking more than a handful of vendors, this email is the one to automate first — it is entirely predictable, it recurs forever, and missing it is what causes the incident described in the real cost of a lapsed vendor policy.

Decide the consequence before you need it, and write it into the contract. An escalation path you invent under pressure is one you will not enforce.

The gate that actually works is access. "No certificate, no site access" is unambiguous, easy for a site manager to apply, and does not require anyone to make a judgment call in the moment. Payment holds work too, but they bite later — after the uninsured work has already happened.

These are the patterns that turn a one-email task into a three-week negotiation.

One request is an email. Sixty vendors, each with their own renewal date, is a standing operational job that nobody owns and everybody assumes someone else is doing.

The work splits cleanly. Composing a specific request, chasing on a schedule, and re-requesting before expiry are mechanical and repeat forever — they should be automated. Judging whether an arriving certificate is genuine and adequate is human work, and it benefits from arriving early with the gaps already highlighted.

That split is how CoverSynx is built. It gives each vendor a link to submit their certificate without creating an account, reads what arrives, checks it against your requirements, and emails the vendor before their policy lapses — with a weekly summary to you of anything that needs attention. It assists verification; it does not certify coverage. The broader process is covered in how to track certificates of insurance, and if you're currently doing this in a spreadsheet, that comparison is worth reading.