Owner Resources

What Your Customers’ Contracts and COIs Actually Demand

A run of pallet racking filled with wrapped pallets and cartons on several levels above floor-level stock

Nobody in a warehouse looks forward to the insurance exhibit.

It arrives late in the onboarding, usually as an appendix nobody read while the commercial terms were being negotiated. It is a page or two of requirements written in a register that does not appear anywhere else in the contract. It has almost certainly been copied from a template. And it is now the thing standing between you and a start date, which is how a document nobody wanted to think about becomes the most urgent item on your desk.

This post is not about what those requirements mean. Our post on umbrella limits, additional-insured status, and the certificate covers the substance — what the limit request is really asking for, what additional-insured status changes, and the sentence that matters most in the whole subject: a certificate is evidence that coverage exists; it is not coverage. That post owns that line, and we are not going to re-teach it here.

This post is about the operations of it. What actually happens when the exhibit lands. Who chases the certificate. Why onboarding stalls. And the one thing most exhibits leave out that should worry a warehouse more than anything they put in.

The exhibit arrives at the wrong end of the process

Here is the shape of the failure, and it repeats almost exactly every time.

The commercial conversation goes well. Rates are agreed, a start date is set, the space is being cleared. The contract comes across for signature and there is an insurance schedule attached to it. Somebody skims it, sees familiar words, and forwards it to the broker with a note that says “can you send them a cert.”

And then one of two things happens, and which one depends on a piece of policy structure that has nothing to do with your customer.

If your policy extends additional-insured status by function — to any party you have agreed in a written contract to add — the certificate can generally be issued the same day. The status already attaches to the person you just signed with, because you signed with them. Nothing needs to be requested.

If instead your status attaches only to parties specifically added to the policy one at a time, then nothing can be issued yet. An endorsement has to be requested, the insurance carrier has to grant it, and it has to actually be on the policy before a certificate can honestly describe it. That is not a broker being slow. That is the mechanism.

Onboarding does not stall on coverage. It stalls on that difference. And the time to find out which one you have is not when a customer’s compliance portal is emailing you daily — it is at renewal, in a quiet room, with the endorsements on your policy in front of you.

Somebody owns the certificate. Make it deliberate.

In most warehouses, nobody owns it. The exhibit lands with sales or with the owner, the request goes to whoever is nearest a keyboard, and over a couple of years the operation accumulates certificates issued from three different people’s assumptions about what the policy says.

Give it to one person. And give that person two things that are usually withheld from them:

  1. Authority to say no. Not to the customer — to the request. If an exhibit asks for something your policy does not do, the correct response is to say so and negotiate it, not to route around it. The person handling certificates has to be allowed to escalate rather than improvise.
  2. A calendar. Because certificates expire, and the expiration is the part everybody forgets.

That second one produces more grief than any coverage question in this post. Your policy renews. Your customer’s compliance system knows the old expiration date and will begin flagging you as non-compliant — often while your renewal is still being marketed and there is genuinely nothing to send yet. Nothing is wrong with your coverage. But a stop-work notice or a withheld invoice does not distinguish between “has no insurance” and “has not sent us the new certificate.”

Renewal is not finished when the policy binds. It is finished when every party who needs a certificate has one. Keep the list. Work it as part of the renewal.

The path an insurance exhibit takes — and the line it usually leaves out A top-to-bottom flow diagram. A customer’s insurance exhibit arrives attached to a contract and reaches one owner inside the warehouse, who reads it against the actual policy. The path forks in two: additional-insured status that attaches by function to any party agreed in a written contract allows a certificate to issue at once; status that attaches only to individually added parties requires an endorsement first, and onboarding waits. An emphasized band below states that the exhibit asks loudly for liability limits and rarely asks at all for coverage on the customer’s own goods. A closing note observes that certificates also run downstream to staffing agencies, freight carriers, and contractors, and that every certificate expires at renewal. No figures appear in the diagram.
<rect x="250" y="18" width="200" height="42" rx="8" fill="#ffffff" stroke="#C3DEDE"/>
<text x="350" y="36" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" font-weight="600" fill="#0F4C5C">The exhibit arrives,</text>
<text x="350" y="52" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" font-weight="600" fill="#0F4C5C">attached to the contract</text>

<path d="M350 60 L350 80" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>

<rect x="250" y="84" width="200" height="42" rx="8" fill="#ffffff" stroke="#C3DEDE"/>
<text x="350" y="102" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">One owner reads it against</text>
<text x="350" y="118" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">the actual policy</text>

<path d="M350 126 L350 144" stroke="#0F4C5C" stroke-width="2" fill="none"/>
<path d="M350 144 L160 144 L160 166" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>
<path d="M350 144 L540 144 L540 166" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>

<rect x="42" y="170" width="236" height="92" rx="8" fill="#ffffff" stroke="#C3DEDE"/>
<text x="160" y="192" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" font-weight="600" fill="#0F4C5C">Status attaches by function</text>
<text x="160" y="214" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" fill="#3F5B64">Anyone you agreed in writing</text>
<text x="160" y="229" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" fill="#3F5B64">to add is already covered</text>
<text x="160" y="251" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" font-style="italic" fill="#3F5B64">The certificate issues today</text>

<rect x="422" y="170" width="236" height="92" rx="8" fill="#ffffff" stroke="#C3DEDE"/>
<text x="540" y="192" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" font-weight="600" fill="#0F4C5C">Status attaches one at a time</text>
<text x="540" y="214" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" fill="#3F5B64">The endorsement has to be</text>
<text x="540" y="229" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" fill="#3F5B64">requested and granted first</text>
<text x="540" y="251" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" font-style="italic" fill="#3F5B64">Onboarding waits</text>

<path d="M160 262 L160 282 L350 282" stroke="#0F4C5C" stroke-width="2" fill="none"/>
<path d="M540 262 L540 282 L350 282" stroke="#0F4C5C" stroke-width="2" fill="none"/>
<path d="M350 282 L350 300" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>

<rect x="130" y="304" width="440" height="60" rx="9" fill="#C8935A" stroke="#0F4C5C"/>
<text x="350" y="330" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#1A1A1A">The exhibit asks loudly about liability.</text>
<text x="350" y="352" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#1A1A1A">It rarely asks about their goods in your care.</text>

<text x="350" y="390" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" font-style="italic" fill="#3F5B64">The same discipline runs downstream — to the staffing agency, the</text>
<text x="350" y="405" text-anchor="middle" font-family="Inter, sans-serif" font-size="11" font-style="italic" fill="#3F5B64">freight carrier, the contractor. Every certificate expires at renewal.</text>
The exhibit stalls onboarding on a mechanical question, not a coverage one. And the thing it usually forgets to ask for is the thing a warehouse most needs.

The line the exhibit forgets — and this is the one that should worry you

Now the part that belongs to warehousing specifically, and that we have never once seen a customer’s template get right on its own.

Read a stack of insurance exhibits and you will see the same list, over and over: general liability, commercial auto, workers’ compensation, an umbrella sitting over the top of them, additional-insured status, a waiver of subrogation, primary and non-contributory wording. It is a coherent list. It is also, unmistakably, a contractor’s list — a template written for a vendor who comes onto your premises and might damage your building or injure your people.

You are not that vendor. You are a bailee. The thing your customer is trusting you with is not access to a site — it is their inventory, sitting on your racks, in your care.

And a general liability policy is not built to pay for damage to property in your care, custody, or control. That is the point of the care, custody, or control problem, and it is the reason warehouse legal liability exists as a separate line at all.

Which produces a genuinely strange result, and it is worth sitting with:

A warehouse can satisfy a customer’s insurance exhibit completely — every limit met, every endorsement in place, every certificate accurate — and still have no coverage whatsoever for the customer’s goods.

The exhibit did not ask. The customer assumed. And nobody discovers the assumption until there is a fire, at which point the customer’s own property policy pays them and their insurer comes looking at you for the recovery.

So do the thing that feels counterintuitive: tell them. When an exhibit demands a great deal of liability coverage and never once names coverage for goods in your care, raise it. That conversation costs you nothing, because you are not creating an obligation — you are demonstrating that you understand precisely what you are holding, which is exactly the impression you want a customer to have of the business they are about to hand their inventory to.

If your customers are distributors who own the goods you ship for them, or if you own inventory yourself, the goods-in-transit and goods-in-storage picture runs through stock throughput instead — a different answer to the same underlying question of whose goods, and where.

The certificates that run the other way

One more, because warehouses consistently do to their vendors what they resent their customers doing to them — which is to say, nothing.

You are not only a party who provides certificates. You are a party who should be collecting them:

  • The staffing agency supplying your peak-season labor.
  • The motor carrier whose driver is at your dock every morning.
  • The contractor working on your racking, your dock levelers, your sprinkler system.
  • The maintenance vendor on your material-handling equipment.

If one of them causes a loss and their coverage turns out to be absent, lapsed, or narrower than everyone assumed, the claim does not evaporate. It looks for the next available party with a policy — and that party is standing in the building, holding the keys.

The discipline is the same in both directions: collect the certificate, know what the underlying agreement says about indemnity, and track the expiration. The only difference is that when you are on the receiving end, nobody sends you a compliance portal reminder. You have to build the habit yourself.

What to actually do before the next exhibit lands

  1. Pull your own policy and find out how additional-insured status attaches. Not what your coverage type usually does — what your endorsements say. This single fact determines how fast you can onboard.
  2. Name one person as the certificate owner and give them the authority to escalate a requirement rather than route around it.
  3. Build the renewal certificate list — every customer, landlord, and lender who needs one — and work it as part of the renewal itself.
  4. Read the next exhibit for what it does not say. If it never mentions goods in your care, that is not good news.
  5. Collect certificates from your own vendors, and diary their expirations the way your customers diary yours.

The whole warehouse insurance program is built around the difference between the goods you own and the goods you merely hold, because that difference is what a customer’s contract is really about even when the contract never mentions it. If you would like someone to read your customers’ exhibits against your actual policy — before you sign the next one — that is the conversation.

The bottom line

A customer’s insurance exhibit is an operations document before it is an insurance document. It arrives late in the onboarding, it holds up a start date, it asks for things in language that was usually copied from a template written for a different kind of vendor, and somebody in your building — usually somebody with no insurance training and no authority — ends up owning it. The two things that matter most are structural rather than technical: first, whether your additional-insured status attaches by function to anyone you have agreed in writing to add, or has to be requested one customer at a time, because that single difference determines whether onboarding takes an afternoon or a fortnight; and second, whether the exhibit even asks for the coverage that protects the thing the customer actually cares about, which for a warehouse is their goods in your care — and very often it does not, because general liability exhibits are written for contractors who damage buildings, not bailees who damage inventory. A certificate proves nothing on its own; the sibling post on additional-insured status and the certificate covers why. This post is about the desk the exhibit lands on, and what to do before it lands.

Frequently asked questions

A customer sent an insurance exhibit and our start date is next week. What now?

Send it to your broker the day it arrives, not the day before the start date — and send the whole exhibit, not a summary of it. Most of what holds up an onboarding is not a coverage gap, it is a mechanical one: your additional-insured status may attach only to parties specifically added to the policy, which means an endorsement request has to be made and processed before an accurate certificate can be issued. That takes as long as it takes. If instead your policy extends that status by function to anyone you have agreed in a written contract to add, the certificate can usually be issued immediately. Which of those you have is set by the endorsements actually on your policy, and the time to find out is before a customer is waiting.

Who in a warehouse should actually own the certificate process?

One named person, and it should not be whoever happens to be at the desk. In practice the exhibit arrives with the contract, the contract sits with sales or the owner, and the certificate request gets forwarded to whoever answers first — which is how a warehouse ends up with certificates issued from three different assumptions about what the policy says. Give it to one person, give them the authority to say “this requirement is not something our policy does,” and give them a calendar. That last part matters more than it sounds.

Why does the certificate keep expiring in the middle of an account?

Because a certificate describes a policy as of a moment, and your policy renews. Your customer’s compliance system knows your expiration date and will start emailing about it, usually to the wrong address, usually while your renewal is still being marketed. The failure is procedural, not substantive: coverage is fine, nobody sent the new certificate, and the customer’s system flags you as non-compliant. Some customers escalate that to a stop-work or a withheld payment. Keep a list of every party that needs a certificate at renewal, and treat sending them as part of the renewal, not as an afterthought to it.

Our customer’s exhibit never mentions coverage for their goods. Should we tell them?

Yes, and it is worth doing plainly. A great many insurance exhibits are written from templates aimed at contractors and service vendors — they demand general liability, auto, workers’ compensation, and an umbrella, and then stop. But a general liability policy is not designed to pay for damage to property in your care, custody, or control; that is what warehouse legal liability is for. So an exhibit can be fully satisfied by a warehouse whose bailee exposure is uninsured. Pointing that out is not creating a problem for yourself. It is showing the customer you understand what you are actually holding.

Can we just sign the contract and sort the insurance out after?

You can, and it is the most common way warehouses acquire obligations they cannot meet. A signed contract is a promise about your insurance program; it does not change your insurance program. If the exhibit demands something your policy does not provide, signing does not create it — it creates a gap between what you owe your customer contractually and what your policy will actually do, and that gap only ever surfaces at a claim, when it is far too late to fix. Read the exhibit against the policy before signature, every time. This is exactly what a broker is for.

We hire staffing agencies and freight carriers. Do we need their certificates too?

Yes, and this is the half of the process that warehouses routinely neglect. The certificate discipline you are subjected to by your customers runs downstream from you as well: the staffing agency supplying temporary labor, the motor carrier picking up loads at your dock, the contractor working on your racking. If one of them causes a loss and their coverage turns out to be absent, expired, or narrower than you assumed, the claim looks for the next available party — and you are standing there. Collect the certificates, track the expirations, and know what the underlying agreement says about who indemnifies whom.

About the author

Nate Jones, CPCU

Nate Jones, CPCU, is the founder of Wexford Insurance and Warehouse Guard Insurance, a specialty insurance agency placing warehousing, distribution, and wholesaling coverage in 48 states through a 25-market specialty panel. He reads customers’ insurance exhibits alongside the warehouse policies they are aimed at, and the recurring finding is not a limit problem — it is a structure problem: exhibits copied from templates written for a different kind of vendor, additional-insured mechanics that cannot keep pace with an onboarding calendar, and a customer demanding a great deal of general liability while never once naming the coverage that would actually respond to their pallets burning. Reach him via the Warehouse Guard Insurance quote form or call 317-942-0549.

Let a CPCU-led agency read your program

Tell us what you store or sell and who owns it — the customers’ goods in your care, or your own inventory on the move — and we will market it to the markets that write this class.