Catering contract: the operational clauses that cause disputes

A catering contract has two halves, and only one of them is what you will find if you search for a template. The legal half — parties, payment schedule, cancellation, liability, insurance — is well covered by the form sites, and you should get that half from a lawyer rather than from me. The other half is operational: guest count guarantees, the final number and when it locks, setup and strike windows, room flips, and what the floor plan attached to the contract actually has to say. That half is where the arguments happen, and it is missing from every template I have read. I’m Daniel Pitner, Director of Sales at EventDiagram, twelve-plus years in the event industry, and this is the half I can write honestly.

This is not legal advice and it is not a contract template. Nothing here substitutes for a lawyer in your state reviewing what you sign. What follows is what to make sure the operational clauses say, and why, from the load-in side of them.

The guarantee: the clause that decides what you get paid

The guarantee is the guest number the client commits to pay for regardless of who actually walks in. Three things need to be explicit, and in most disputes I have seen, at least one of them was not:

• The deadline, as a date and a time in a named timezone. “72 hours prior” is ambiguous for a Saturday evening event — is that Wednesday evening or Wednesday close of business? Write the actual timestamp.
• What happens if the guarantee is never given. The standard answer is that the expected count on the contract becomes the guarantee. Say so, or you are negotiating it on the Thursday.
• The overset. Most caterers set and prepare some percentage above the guarantee — commonly three to five percent. If you do it, the contract should say you do it, and say whether the client pays for those covers if they are used.

The guarantee is also the number that drives the room. It is worth knowing that a guarantee moving by ten guests can change the table count, and a table count change can move the dance floor, the buffet lines and the aisles with it — which is why the next clause matters.

The floor plan attachment, and what it has to state

Most catering contracts reference a floor plan as an exhibit and then attach a picture of one. A picture is not a specification. If the plan is contractual, it should carry, on its face:

Attach the version, not “the latest.” Contracts that reference a living document are contracts that reference whatever it says the day someone looks.

Access: setup, flip and strike windows

Three separate windows, and they get collapsed into one line far too often:

• Setup. When can you get into the room, through which door, and with what lift access? A two-hour setup is a different price from a six-hour one, and a loading dock on the far side of the building is a real cost.
• The flip. If the same room goes from ceremony to dinner, or from general session to banquet, the flip window is the most expensive fifteen minutes of the day. The contract should name the window and the headcount doing it. If the plan changes the number of tables, the flip time changes with it, and that is a re-price, not a favour.
• Strike. When does the room have to be clear, and what happens if the client’s own vendors are still in it? Whoever is last out gets blamed for the condition of the room, so define who owns it and when.

Changes, and what a change costs

Every contract has a changes clause and most are useless, because they say changes must be “mutually agreed in writing” and stop there. Useful versions name a cutoff after which a change is billable, and give examples: adding a bar, moving from rounds to long tables, adding a stage, changing the service style. Those are all layout changes as much as menu changes, and they are the ones clients think are free.

My rule from the operations side: if a change alters the floor plan, it alters the labour, and the contract should make that connection explicit. Going from twenty rounds to sixteen long tables is not a neutral swap; it is a different number of linens, a different setup time, and often a different server count.

The clauses I would read twice

• Exclusivity and outside food. Especially cake, and especially who cuts it.
• Corkage, if the client is bringing wine — per bottle, and whether it applies to unopened bottles.
• Service charge versus gratuity. They are not the same thing, they are taxed differently in many states, and clients routinely believe the service charge is the tip. Say plainly which is which.
• Weather and outdoor calls. Who makes the call to move indoors, by when, and what the indoor plan is. The indoor plan should be an attached, drawn plan, not “the ballroom.”
• Force majeure. Post-2020 these are longer and worth reading properly.

Where the floor plan and the paperwork disagree

The BEO is the document that turns the contract into instructions for the day, and it is the one the kitchen and the captains actually read. The places a BEO and a floor plan contradict each other — and the twelve I keep seeing — are in what a BEO is, section by section. If you are working out what the room can physically hold before you commit to a guarantee, the room capacity calculator does the floor arithmetic, and how many people fit at a 60-inch round table does the per-table half.

Where we obviously stand

We build EventDiagram, which is floor plan software, not legal software — so read this accordingly. My interest is the exhibit, not the agreement: I think most catering contracts attach a drawing that cannot be checked, and that this is the cause of a surprising share of the arguments that follow. Drawing the room to scale, versioning it, and attaching that version is most of the fix, and our tools for caterers exist to make that the easy path. The free tier will draw and date one room for you.

And once more, because it matters: this is not legal advice. Have a lawyer in your state review any contract before you sign it or send it.