Catering Contracts: Deposits, Guarantees and Cancellations

The kitchen part of catering I can teach in an afternoon. The part that puts a caterer out of business is almost never the food. It is the booking that shrinks, the client who pays late, the wedding that gets called off in a family argument three weeks out, and the caterer who has no signed page to point at when the money conversation turns cold.

Good catering contract terms are not lawyerly decoration. They are the difference between a bad event costing you a bruised evening versus costing you a month's margin. This is a working chef's guide to the clauses that matter — the guaranteed guest count, the deposit schedule, the tiered cancellation fee, and the handful of others that quietly protect your food order. It is general practice from years of running events, not legal advice; get a local lawyer to bless your template once, then reuse it.

The clause that pays for your food: the guaranteed guest count

Every other number in a catering contract hangs off one figure: the guaranteed count. This is the number of guests the client commits to pay for, regardless of how many actually walk through the door. It is not a forecast. It is a floor.

The mechanism is simple and it is the single most important line in the whole document. You bill the greater of the guaranteed count or the actual attendance.

Read that carefully, because it cuts both ways. If the client guarantees 100 and 90 show up, you still bill 100 — you bought and prepped for 100, so you are made whole. If they guarantee 100 and 115 arrive, you bill 115 — because you fed 115. The client never pays for fewer than they promised, and never pays for fewer than they consumed. That is fair, and clients accept it once you explain it in exactly those terms.

The guarantee deadline is the whole point

A guarantee with no deadline is worthless. The deadline is the moment the number locks, and it exists so that when you place your food order, the client is already financially committed to that headcount. Standard practice is 72 hours before the event for most catering, tightening to a firm number by the point you cannot cancel your own supplier orders.

The clause reads roughly like this: "Client shall confirm the guaranteed guest count no later than 72 hours prior to the event. If no confirmation is received, the guaranteed count shall default to the number stated at booking." That default line is not optional — without it, a client who goes quiet leaves you guessing, and guessing on a 200-cover job is how you lose $900 in wasted protein.

Here is the worked case from the lede. A client books 120 at $85 per head. The guarantee deadline is 72 hours out. The day before the event — inside the deadline — they call: only 80 are coming now.

The $3,400 gap between the first two rows is not a windfall. It is the food you already bought, the staff you already rostered, and the other Saturday booking you turned away. The guarantee is what stops the client's last-minute change from becoming your loss. Note the third row too: the contract should let them reduce the number before the deadline, within reason (say, no more than 10% below the booking figure). A guarantee that never lets the client breathe reads as a trap and loses you the job at the quoting stage.

The deposit schedule: getting paid before you spend

A deposit is not a booking formality. It is you refusing to finance the client's event out of your own cash flow. The rhythm that works, and that clients recognise as normal:

The booking deposit must be non-refundable and the contract must say so in plain words. That is what makes it a deposit rather than a pre-payment you might have to hand back. It protects the date you are holding — a Saturday in June you cannot re-sell at three weeks' notice is worth real money.

The line I care about most: the final balance is due before service, not invoiced after. The day you cater an event and leave without full payment is the day you have handed the client a 30-day interest-free loan they may decide not to repay. Chasing money after the plates are cleared is the worst position in this business — the leverage is gone. Corporate clients on purchase orders are the one common exception, and even they should be on defined net terms in writing, not a vague "we'll sort it".

The US Small Business Administration's guidance on managing business finances makes the same point in duller language: a small business lives or dies on cash flow timing, not on the size of the invoice. A staged deposit schedule is cash-flow management written into the contract.

Tiered cancellation fees: the closer to the date, the more it costs

Cancellations are not a single event with a single fee. The cost to you rises as the date approaches, because your ability to re-sell the slot and unwind your supplier commitments falls. A single flat cancellation fee is either too harsh far out (and scares off bookings) or too soft up close (and leaves you exposed). Tier it against calendar distance.

Those percentages are a starting point, not gospel — a high-volume corporate caterer with re-sellable weekday slots might run gentler tiers than a wedding specialist who books one Saturday a season. The principle holds regardless: the fee tracks your actual sunk cost and lost opportunity at the moment of cancellation, and the client can see the logic. A tier they understand is a tier they pay without a fight.

Two refinements worth writing in. First, define postponement separately from cancellation — a client moving a date is different from one walking away, and letting them roll the deposit to a new mutually agreed date (once) earns enormous goodwill at almost no cost to you when the slot is re-sellable. Second, state that cancellation must be in writing and that the fee is calculated from the date you receive it, not the date of the event the client claims they meant to cancel.

The clauses people forget until they need them

Overtime and extension charges

The event was contracted to end at 23:00. At 23:15 the host asks your team to stay another hour because the speeches ran long. Without an overtime clause, you are now working for free and your staff are on unplanned pay. Write it in: service beyond the contracted end time is charged at a stated per-hour rate — often 1.5× the standard staffing rate, billed per half-hour or hour started. Say it up front and the host makes an informed call at 23:15 instead of assuming your time is a gift.

Payment terms and late fees

For the rare cases where money is owed after the event (corporate net-30, mostly), spell out the term and a late fee — commonly 1.5% per month on the overdue balance. The late fee is rarely about the money. It exists so that "the invoice is overdue" is a contractual fact with a defined consequence, not an awkward phone call where you sound like you are begging.

Force majeure

The clause that seemed like boilerplate until 2020 taught everyone what it was for. Force majeure covers events genuinely outside anyone's control — a venue fire, a government shutdown, a flood — and defines what happens when neither party is at fault. The fair version does not hand the client a full refund (you still incurred costs) and does not let you keep everything (you did not deliver). It typically retains costs actually incurred and deposits already spent on their behalf, refunds the rest, and offers a rebooking window. Decide this in the calm of contract-signing, not in the panic of a cancelled event.

Liability and insurance

State what you are responsible for and what you are not. You carry public liability insurance and food safety responsibility for what leaves your kitchen — that is non-negotiable and clients expect it. But you are not liable for guest behaviour, for a venue's faulty wiring, or for a client who insists you serve food they supplied. A cap on total liability (frequently the contract value) keeps a single bad night from becoming an open-ended claim. This is the clause most worth having a lawyer draft to your jurisdiction; the rest you can template.

Why the signed BEO is the other half of the safety net

The contract governs the money. The Banquet Event Order governs the event — the timeline, the menu, the headcount, the room setup, the service style, the dietary flags. On their own, each has a gap. Together they close it.

Here is the failure the pair prevents. Your contract says 120 guests at $85. Two weeks out, the client emails asking to "add a canapé course and push dinner to 20:00". You say yes on the phone. On the night, they insist the canapés were always included and dinner was always at 20:00 — and that the extra course should not cost more. Without a signed document capturing that change, it is your word against theirs, and you will usually eat the difference to protect the relationship.

A signed BEO, re-issued and re-signed whenever the details change, is the running record of what was agreed and when. The contract sets the framework — guarantee, deposit, cancellation. The BEO carries the specifics that move week to week. When the two disagree, you have a problem; when they agree, you have proof. Any material change should update the BEO and get a fresh signature, even if it is just an email reply saying "confirmed". Digital acceptance counts.

If you are not already building one for every event, start with the eleven sections that belong in a proper BEO — it is the operational document that turns a contract's numbers into a plan the kitchen and floor can actually run.

Putting it together

A catering contract is not there for the 95% of events that go smoothly — those never test it. It is there for the 5% that go sideways: the shrinking headcount, the cancelled wedding, the corporate client who forgets to pay, the night that runs three hours long. On those events, the contract is the only thing standing between a difficult evening and a genuine loss.

Build the template once. Guaranteed count with a hard deadline and a sensible floor. A staged, non-refundable deposit schedule with the balance due before service. Tiered cancellation fees that track your real exposure. Overtime, payment terms, force majeure and a liability cap. Then pair every booking with a signed BEO and keep it current. Have a lawyer read it once for your jurisdiction, and reuse it for years.

Do that and the awkward money conversations mostly disappear — because the answers were agreed, in writing, back when everyone was still friends.

"They cut the numbers the night before. I only got paid for the 80 who came. That was the last event I ran without a guarantee clause."

Every caterer has a version of that sentence. The good news is it is the most preventable loss in the business. One clause, agreed at booking, and it never happens to you.