A florist's truck at the loading dock at six in the morning, with no certificate of insurance on file, is a small emergency dressed up as a delivery. The flowers are beautiful. The event is in twelve hours. And I cannot let that crew into the building until the paperwork clears, because the moment they walk into my ballroom, whatever happens to them, or to the guest they trip, becomes the hotel's problem. So we stand at the dock and make phone calls while the clock runs. That scramble is entirely avoidable, and avoiding it is most of what working with outside vendors is about.
Every real event brings in people who do not work for me. Florists, bands and DJs, photographers and videographers, audiovisual companies, rental and decor houses, and often a wedding or corporate planner sitting above all of them. They are essential. They are also strangers in a building I am responsible for, and the job is to let them do excellent work without ever losing control of the space, the timeline, or the liability. That balance runs on three things: the insurance, the load-in, and a clear map of who owns what.
The certificate of insurance is the gate, not paperwork
The certificate of insurance, the COI, is the single document that decides whether a vendor gets into the building. It is easy to treat it as bureaucratic box-checking. It is not. It is proof that if the vendor damages the property, injures a guest, or injures one of their own people on my floor, their insurance answers for it instead of the hotel's. Without it, every risk that vendor creates lands on the property.
A proper COI names the hotel as an additional insured, carries the liability limits the property requires, and covers the actual dates of the event including setup and teardown, not just the event hours. Vendors who work hotels regularly know this cold and send it without being asked. New vendors, or the friend-of-the-family photographer at a wedding, often have no idea what I am asking for, which is why I ask early and in writing, weeks out, not at the dock.
The limits themselves are set by the property and its risk team, so I will not quote a number that varies from hotel to hotel. The rule that never changes is simpler: no valid COI, no access. I would rather have an awkward conversation two weeks out than an uninsured crew in my building on the day.
This is also where the hotel's own team has to be aligned, because vendor requirements usually originate with the person who sold the event. Understanding what the sales and catering office does helps here, since the contract they wrote is where the COI requirement, the approved vendor rules, and the load-in terms all live. If it was not put in the contract, it is much harder to enforce at the dock.
Load-in is a schedule, not a scramble
The second thing that separates a calm event from a chaotic one is how load-in is handled. Load-in is the window when vendors bring their gear and setups into the building, and left unmanaged it becomes five trucks at one dock, a freight elevator nobody reserved, and crews stacking on top of each other in a room that is not ready for any of them.
Managed, it is a schedule. I want to know, before the day, who is arriving, when, with how much, and needing what. The florist needs dock access and a cart. The band needs the stage built first and power where the stage is. The audiovisual company needs the room clear and often the most time of anyone. The rental company needs to drop before the decor crew arrives to dress what they dropped. Sequencing those arrivals so they build on each other instead of colliding is the actual craft of load-in.
The physical facts of the building drive the plan. How many loading docks, how big the freight elevator, which corridors the gear can move through without going past guests, and where crews can stage boxes without blocking a fire exit. None of that is glamorous, and all of it decides whether load-in runs smoothly. A load-in schedule shared with every vendor in advance, with arrival windows and a contact name, prevents most of the problems before a single truck shows up.
Teardown deserves the same discipline and rarely gets it. It happens late, everyone is tired, and vendors want to be gone. But their gear has to leave on the timeline the contract set, especially if the room turns for another event. I plan the load-out as deliberately as the load-in, including who is responsible for removing what and by when, so the room does not sit hostage to a crew that decided to come back for their equipment tomorrow.
Who owns what
Most vendor friction is not really about the vendor. It is about an unspoken assumption over who was responsible for something. The cure is a clear, shared map of ownership, and the place that map lives is the banquet event order. The BEO is the single source of truth for the event, and every vendor's role, timing, and responsibility should trace back to it.
Broadly, the hotel owns the building and everything structural: the space, the power, the base tables and chairs and house linens, the food and beverage, and the safety of everyone in the room. The vendors own their specialty and their gear: the flowers, the music, the photography, the specialty rentals, the decor. The planner, when there is one, owns the client relationship and the creative vision and is often my main point of contact for coordinating the rest. When those lines are drawn clearly and written down, vendors do great work inside them. When they are fuzzy, two crews both assume the other one is handling the dance floor and neither does.
A few boundaries are worth stating out loud with every vendor, every time:
- Food and beverage is almost always the hotel's. Most full-service hotels do not allow outside catering, because the kitchen and the liquor license are the property's responsibility and its revenue. Outside desserts sometimes get an exception. A vendor showing up with their own bar setup usually does not.
- Anything touching the building's systems is the hotel's to approve. Power, rigging, anything hung from the ceiling, anything drilled or taped to a wall. A vendor does not get to decide what my building can safely carry.
- The guest experience is the hotel's, always. A vendor can be brilliant at their craft and still behave in a way that reflects on the property, because to the guest, everyone in a hotel uniform or not is part of the event. I set expectations for conduct up front, and I do not apologize for it.
Engineering owns the building
The one boundary I never blur is anything that touches the building's systems, and that is where I bring in engineering early and often. An audiovisual company that needs significant power, a lighting vendor that wants to hang fixtures, a band with a stage plot that draws more amperage than the room's circuits carry, a decor crew that wants to suspend something from the ceiling. Every one of those is an engineering decision before it is a creative one.
Engineering knows what the room can actually carry: the circuits, the rigging points, the load ratings, the connections. A vendor knows what they want to plug in. Putting those two together before the day, rather than discovering the mismatch when the breaker trips during the first dance, is the entire reason to coordinate early. I would rather have engineering tell a vendor no two weeks out than have the room go dark mid-event.
That last risk is not hypothetical. A room full of vendor equipment on circuits nobody load-checked is exactly how the power goes out in a full building. Coordinating vendor power and rigging through engineering is not me being territorial. It is me keeping the lights on during the moment the client will remember for the rest of their life.
The handoff and the relationship
Two things make vendor coordination sustainable past a single event.
The first is the handoff. Events run long, and the person who briefed the vendors at load-in is often not the person on the floor when the band arrives or teardown starts. So vendor status has to pass cleanly across shifts: who has arrived, who is behind, what was promised, what changed. This is the same discipline as any good warm handoff between shifts. The vendor should never feel the seam where one manager left and another took over. If the incoming manager does not know the florist is running an hour late, that hour becomes a surprise instead of a managed adjustment.
The second is the relationship. The best vendors are repeat vendors. A florist who knows my dock, my freight elevator, and my house rules is faster and cleaner every time they come back, and they make my events better. So I treat vendors as partners, not as a risk to be managed, even while I hold the insurance and safety lines firmly. Clear expectations, a fair load-in window, a place for their crew to eat, and honest communication earn a vendor who wants to work my building again. That roster of trusted vendors, built over years, is quietly one of the most valuable things an events operation has, and it is worth protecting.
Working with outside vendors comes down to a posture, not a checklist. I want them to do the best work of their careers in my building, and I want to control the space, the timeline, and the risk while they do it. Those two goals are not in tension. The insurance, the load-in schedule, and a clear map of who owns what are exactly what let a stranger walk into my ballroom and help me make someone's day unforgettable.
The takeaway
Outside vendors are not a threat to manage or a favor to grant. They are partners who make your events better, as long as you hold three lines without apology: valid insurance before anyone enters, a load-in schedule instead of a scramble, and a written map of who owns what. Draw those lines clearly and communicate them early, and a building full of strangers will run like a team that has worked together for years.
Questions from the desk
Why do hotels require a certificate of insurance from vendors?
Because the moment a vendor enters the building, the risk they create, damage to the property, injury to a guest, or injury to their own crew, would otherwise fall on the hotel. A COI naming the hotel as additional insured shifts that liability to the vendor's insurance. No valid COI, no access, and I ask for it weeks out, not at the dock.
Can I bring my own caterer or bar to a hotel event?
Usually not. Most full-service hotels own food and beverage because the kitchen and the liquor license are the property's legal responsibility and a significant part of its event revenue. Outside desserts sometimes get an exception, but an outside bar or full caterer almost never does. Always confirm with the sales and catering office, since it is written into the contract.
What is load-in and why does it need a schedule?
Load-in is the window when vendors bring their equipment and setups into the building. Without a schedule you get multiple trucks at one dock, an overbooked freight elevator, and crews colliding in a room that is not ready. A sequenced load-in plan, shared in advance with arrival windows and a contact name, sequences vendors so each one builds on the last instead of blocking it.
Who is responsible if a vendor damages the hotel or a guest is hurt?
This is exactly what the certificate of insurance exists to answer. With a proper COI in place, the vendor's insurance responds. Without one, the hotel is exposed, which is why access is gated on the paperwork. The banquet event order and the contract also document who owned what, which matters when something goes wrong.