Certificates of Insurance for Shuttle and Charter Operators: COI Requests, Additional Insureds, and Venue Requirements

Before most shuttle and charter operators drive a single passenger for a new client, they are asked for one document: a certificate of insurance. Hotels want it before a standing airport run, venues want it before a wedding shuttle rolls into the lot, corporate clients attach it to every master service agreement, and government RFPs reject bids that arrive without it. The certificate is not the insurance itself — it is proof of the insurance — and the operator who can produce an accurate one quickly wins work that slower competitors lose.

This guide covers the paperwork side of being insured: what a certificate of insurance actually certifies, why so many counterparties demand one, what an additional insured request really means, how to keep certificates current across an entire client list, and how to make your COI turnaround a selling point instead of a bottleneck. This is distinct from choosing the coverage itself — the limits, liability forms, and physical damage decisions behind a passenger-fleet policy are a separate exercise — because many operators hold solid coverage and still lose bookings over a document they could not produce in time.

What a Certificate of Insurance Actually Is

A certificate of insurance is a standardized summary — most commonly produced on the ACORD 25 form for liability coverage — that your insurance agent or broker issues to describe an existing policy. It states who is insured, which coverages and limits apply, the policy effective dates, and the insurer providing the coverage. It is informational, not contractual: signing it does not create coverage, and the form itself says so.

Three practical consequences follow from that. First, only your agent or broker issues a certificate — you cannot type one up, and a client who receives a doctored or self-made certificate will treat it as grounds to end the relationship. Second, the certificate reflects the policy as it exists; if your policy lapsed last week, the certificate cannot hide it, and requesting one may even surface the lapse to you before it surfaces to a client. Third, the certificate binds nobody: a venue holding your certificate has not accepted any obligation, and you have not granted them any — those outcomes only happen through the endorsements discussed below.

Why Everyone Asks for One

The demand for certificates comes from how risk is pushed down through a transportation engagement. A hotel that contracts your shuttle, a wedding venue that hosts the pickup, a corporation that buys a commuter program, or a broker that feeds you airport work all have one thing in common: if your vehicle injures someone on their property or under their program, plaintiffs will name them alongside you. The certificate is their evidence that a layer of insurance stands between the incident and their own balance sheet.

For the operator this is good news, because the requests are routine and predictable. The pattern to internalize is that the certificate requirement arrives at the same point in every relationship — contract execution, or the first trip, whichever comes first — and it repeats annually, because certificates expire when policies renew. Operators who treat the first request as a one-time errand get caught when the contract auto-renews, the venue re-verifies vendors, and the certificate on file is twelve months stale.

The Additional Insured Request

The most common complication in a COI request is the sentence "please name us as additional insured." This is not the same as just listing someone on the certificate. An additional insured endorsement is an actual policy amendment — your broker files it with the carrier — that extends defined parts of your liability coverage to the named party. When a hotel becomes an additional insured on your auto policy, your insurer may be obligated to defend that hotel in a lawsuit arising from your operations, within the terms of the endorsement.

Understand the common variants before forwarding a request to your broker, because the wording changes your exposure:

• Blanket additional insured. The endorsement extends additional insured status automatically to any party who requires it in a contract with you. This is the version to ask your broker about if you serve many venues and clients, because it eliminates per-request turnaround.
• Primary and non-contributory. The requested endorsement states that your insurance pays before the certificate holder's own insurance, and their carrier contributes nothing first. Clients with sophisticated risk departments ask for this routinely; brokers approve it routinely, but only when it is properly endorsed rather than merely written on the certificate.
• Waiver of subrogation. The client asks that your insurer give up the right to recover payments from them after a claim. Again, this lives in the endorsement, not in pencil on the form.

The rule that keeps you safe and fast: never alter a certificate yourself, and never promise a client an endorsement your broker has not confirmed. Route the client's exact written language to your broker, get the endorsement filed, and then issue the certificate that reflects it. Quotes about "what the certificate says" without the underlying endorsement are the most common way operators end up contractually out of position after a claim.

Where the Requests Come From

Different counterparties ask for certificates in different flavors, and knowing the pattern lets you pre-assemble the right package:

• Hotels and travel accounts. Typically a certificate plus additional insured status for the property, requested at contract signing and refreshed at each policy renewal. The front-office contact changes often, so confirm where the current certificate should be sent.
• Event venues and wedding coordinators. Often want to be listed as certificate holders at minimum, sometimes as additional insureds, and sometimes with specific instructions printed on the certificate about the event date. Ask for their exact language rather than guessing.
• Corporate clients and brokers. Master service agreements usually specify limits, additional insured, waiver of subrogation, and a notice-of-cancellation requirement — often thirty days, which your broker must arrange with the carrier rather than promise informally.
• Government and municipal contracts. RFPs list required coverages and endorsements in detail, and procurement rejects nonconforming certificates without negotiation. Match the RFP language exactly and let your broker translate it into endorsements.
• Airports. Permit and access agreements carry their own insurance schedules tied to operating on airport property; the certificate supports the permit, not just the customer relationship.

Keeping Certificates Current Across a Client List

Once you serve more than a handful of contract accounts, certificate administration becomes a system rather than an errand. The fundamentals are simple. Track every certificate you issue with the recipient, the date, the endorsements attached, and the policy expiration it inherits. When a policy renews, a new certificate is required for every holder of the old one — a single renewal can trigger a batch of re-issuance, so keep the list ready. Calendar the renewal dates of your own policies at the start of the year, because clients notice lapses faster than they notice price increases.

Responding fast is the competitive part. A client's onboarding checklist often stalls on the vendor who cannot produce a certificate, and in many procurement processes the operator who returns a complete certificate package the same business day simply moves to the front of the queue. Ask your broker once for a standard turnaround commitment, gather your most common client requirements into a file you can forward, and treat every new request as an addition to that template library. The same discipline of recording what happened — who required what, when it was issued, and what language they asked for — is what makes next year's renewal a checklist instead of an archaeology project, and it is the same habit that separates operators who can prove their performance from those who remember it, as covered in this guide to fleet utilization and operating metrics.

When a Request Is Unreasonable

Most COI requests are routine, but a few deserve scrutiny before you forward them. Requests for limits far above the coverage you carry are a business decision, not paperwork — raising limits costs premium, and the client's requirement may justify it or may be boilerplate you can negotiate down. Requests to name a client as additional insured on your physical damage coverage, or to cover claims arising from their own negligence, are unusual enough that your broker should read the language before anything is endorsed. And requests that you indemnify a counterparty for injuries caused by their own conduct shift real risk onto you; that is a conversation for your broker and, on larger contracts, an attorney.

The posture to keep is cooperative but not automatic. The vast majority of requests come from risk departments applying standard templates, and brokers resolve them daily. The rare nonstandard demand is a signal to slow down, not to refuse — the client who insists on strange terms after you flag them is telling you something about how the account will behave when a claim actually happens.

Turning Paperwork Into an Advantage

Handled well, certificates of insurance become one of the least painful parts of growing a transportation company. You hold one current policy, your broker issues accurate certificates on request, your endorsements blanket the routine additional insured demand, and a tracked list of certificate holders gets refreshed at every renewal without anyone chasing you. Prospective clients read that responsiveness correctly: an operator whose paperwork is current is usually an operator whose maintenance, drivers, and records are current too. Build the system once, and the document that stalls your competitors' deals becomes a reason yours close.