Rental ManagementMar 16, 20268 min readSuper AdminUpdated Oct 29, 2026

How to Collect Certificates of Insurance for Rentals

Q: What is a rental certificate of insurance?

A rental certificate of insurance (COI) is a one-page document issued by an insurer confirming that a policy exists, what it covers, its limits, and when it expires. Rental businesses both issue them — when a venue or corporate client requires proof of coverage — and collect them from customers renting high-value equipment.

Q: Do I need a COI for every rental?

No. Most consumer party rentals do not require one. They become necessary for venue-controlled events (schools, municipal parks, hotels, corporate campuses) and for high-value equipment where you require the renter to carry their own coverage. Trigger the requirement by venue type and by equipment replacement value rather than applying it to every booking.

Q: What does "additional insured" mean on a rental COI?

Naming a venue or client as an additional insured extends your liability coverage to them for claims arising from your work at that event. Many venue contracts require it, and some require a specific endorsement form rather than just a mention in the description field — confirm which before requesting the certificate from your agent.

Q: How far ahead should I request a certificate of insurance?

Request outbound certificates at least seven days before delivery. Agents typically turn them around in one to three business days, and the extra margin covers a rejection for a misspelled entity name or a missing waiver of subrogation — both common and both slow to fix on a Friday.

Q: What should I check when a customer sends a COI?

Three fields decide whether it is usable: the expiry date compared against the event date (not today's date), the named insured matching the exact entity renting from you, and the limits meeting your contract minimum. A valid-looking certificate that expires before the event, or that names a different LLC, provides no protection.

Run Your Business

A rental certificate of insurance is the one-page proof that somebody else's policy will respond when something goes wrong on your job. Two different versions matter to a rental business: the COI you issue when a venue or corporate client demands proof of your coverage, and the COI you collect from a customer before releasing high-value equipment. Both fail the same way — requested too late, chased by text message on a Friday afternoon, and stored in an inbox nobody else can see. Operators who stop losing Saturdays to insurance paperwork treat the COI the way they treat a signed contract and a paid deposit: a named requirement on the reservation that blocks dispatch until it is satisfied.

The two COIs a rental business deals with

They look like the same document and have completely opposite workflows. Confusing them is why staff chase the wrong party.

The COI you issue (outbound). A venue, school district, municipal park, hotel, or corporate client books you and their contract requires proof that you carry general liability — frequently $1M per occurrence — and that they are named as an additional insured for that event. This is a request to your insurance agent, not to your customer. It takes the agent anywhere from an hour to a few business days, which is exactly why it cannot start on Thursday for a Saturday delivery.

The COI you collect (inbound). A contractor rents a lift, a trailer, or a generator, and your terms require them to carry their own coverage before you hand over an asset worth more than their deposit. This is a request to your customer, and it is the one that most often gets skipped for a "regular" — right up until the regular drops the machine.

The outbound COI is a scheduling problem. The inbound COI is a risk problem. Shops that run reservations, documents, and dispatch on one system handle both as reservation state rather than as somebody's inbox discipline.

Know what the venue will actually demand

Most venue requirements repeat the same handful of fields, and a COI gets rejected for small mismatches far more often than for inadequate coverage. Before the certificate is requested, you need five things from the customer or venue:

The exact legal name and address of the entity to be named — "Riverside Events LLC," not "Riverside." A certificate naming the wrong entity is a certificate that gets bounced back on delivery day.
Required limits — commonly $1M per occurrence and $2M aggregate for event work, higher for municipal and school contracts.
Whether additional insured status is required, and whether they want it on a specific endorsement form rather than just listed in the description box.
Whether a waiver of subrogation is required — common in municipal and institutional contracts, and something the agent must add deliberately.
The event date, site address, and a description that matches the reservation, because the certificate holder will compare them.

Collect these at quote time, not at delivery. The question "does your venue require a certificate of insurance?" belongs on the booking form for any corporate, school, municipal, or hotel job — right next to the delivery address, the same way online rental booking already captures site details before a deposit locks the date.

Build the request into the reservation, not the inbox

Both COI types need the same three things: a trigger, an owner, and a blocker.

Trigger. Flag the reservation the moment a venue requirement or a high-value equipment item appears on the order. For outbound, that is usually a venue-type field or a corporate client. For inbound, tie it to an equipment class or a replacement-value threshold, so the requirement attaches itself instead of depending on who takes the call.
Owner. Outbound COIs are requested from your agent by one named person, not by whoever is free. Inbound COIs are requested from the customer with the same automated cadence you use for unsigned contracts — send at deposit, remind at 48 hours, escalate inside 24 hours of delivery. A named owner per weekend fits the same roster discipline as rental weekend staffing.
Blocker. Mark the job COI required on the dispatch board and treat it exactly like an unsigned contract: loading needs a manager override with a logged reason. Without a blocker, the flag is decoration.

Lead time is the part people underestimate. Set the internal deadline at seven days before delivery for outbound certificates, which gives the agent room and still leaves time to correct a rejected name or a missing endorsement. For inbound, require it before the balance-due date so you are not deciding at 6 a.m. whether to release a $40,000 machine to someone who never sent proof.

Store it where the crew and the office both look

A certificate that lives in one person's email is not on file. Attach the PDF to the reservation, alongside the signed agreement, with three fields a human can actually scan: expiry date, named insured, and limits. Those three decide whether the document is still good.

Two checks worth building into the routine:

Expiry against the event date, not today's date. A policy expiring three weeks before an eight-month-out wedding is the single most common inbound COI failure. Verify against the delivery date and re-request when the renewal lands.
Named insured matches the renting party. A certificate in the name of a contractor's other LLC, or a personal policy for a commercial job, does not cover the rental. This is the detail that gets waved through for familiar customers and then matters exactly once.

For repeat commercial accounts, track the policy renewal date at the customer level rather than per booking. Annual accounts should produce one COI request a year, not one per reservation — and the reservation should inherit the certificate on file if it is still valid on the event date. Tie the requirement into your terms so the contract and the workflow agree; this is the same alignment problem as digital rental contracts, where the document has to match what the calendar sold.

Measure the chase, not the paperwork

If nobody watches the numbers, COI discipline decays into "we'll grab it at delivery" by peak season. Four things worth reviewing monthly:

Lead time from flag to certificate on file — if the median is under three days you are fine; if it is the day before, your trigger is firing too late.
Rejected certificates — how many came back for a wrong entity name or a missing endorsement. High numbers mean you are collecting venue requirements too loosely at quote time.
Override count — jobs dispatched without a required COI. Same metric as unsigned contracts, same meaning: a policy with habitual overrides is not a policy.
Expired-at-event catches — certificates that were on file but would have lapsed by the event date. Every one you catch is a claim you did not have to argue about.

A rental certificate of insurance is not a filing chore. It is the difference between a venue letting your truck through the gate and a crew sitting in a parking lot, and between a damaged machine being somebody's covered claim or your write-off. Flag it at quote, own it by name, block dispatch until it lands, and keep it on the reservation where the crew can open it.

_Ready to track COIs, contracts, and deposits on the same reservation your crew dispatches from? Start your free 14-day trial or see how GRS handles equipment rentals._

Frequently asked questions

A rental certificate of insurance (COI) is a one-page document issued by an insurer confirming that a policy exists, what it covers, its limits, and when it expires. Rental businesses both issue them — when a venue or corporate client requires proof of coverage — and collect them from customers renting high-value equipment.

No. Most consumer party rentals do not require one. They become necessary for venue-controlled events (schools, municipal parks, hotels, corporate campuses) and for high-value equipment where you require the renter to carry their own coverage. Trigger the requirement by venue type and by equipment replacement value rather than applying it to every booking.

Naming a venue or client as an additional insured extends your liability coverage to them for claims arising from your work at that event. Many venue contracts require it, and some require a specific endorsement form rather than just a mention in the description field — confirm which before requesting the certificate from your agent.

Request outbound certificates at least seven days before delivery. Agents typically turn them around in one to three business days, and the extra margin covers a rejection for a misspelled entity name or a missing waiver of subrogation — both common and both slow to fix on a Friday.

Three fields decide whether it is usable: the expiry date compared against the event date (not today's date), the named insured matching the exact entity renting from you, and the limits meeting your contract minimum. A valid-looking certificate that expires before the event, or that names a different LLC, provides no protection.

Want the full playbook?

Get a demo and see these tactics on your business.

We’ll show you how to launch conversion-ready pages, fix checkout drop-off, and automate review + SMS flows.

Get a demo ->See pricing

Ready to rule your rental business?

Get a personalized demo. See your business on GRS in 30 minutes.

Get a demo ->

No credit card required - 14-day free trial - Cancel anytime