A single-event catering contract only has to survive one date. A recurring program — weekly office lunch, a biweekly all-hands, a standing Friday team meal — has to survive fifty of them, plus every holiday, offsite, and slow week in between. Program managers who reuse a one-time catering agreement for an ongoing schedule usually discover the gap the first time they need to skip a week or the headcount drops by half the day before a long weekend. The fix is a written cancellation and change policy built for a recurring relationship, not a single booking.
Why a Recurring Program Needs Its Own Cancellation Policy
Standard catering cancellation terms are written around a wedding or a one-off party: a sliding scale where cancelling 30 or more days out returns most of a deposit, cancelling in the 7-to-14-day window forfeits a large share of the food, beverage, and staff cost, and cancelling inside 24 to 72 hours can mean paying close to the full quoted price because the caterer has already bought ingredients and scheduled staff. That structure makes sense for an event that happens once. It breaks down for a program that repeats weekly, because "cancel this instance" and "cancel the whole relationship" are two very different things, and most standard contracts only account for the second one.
A recurring-program addendum should separate three distinct actions: skipping a single occurrence (a holiday week, an office closure), permanently changing the standing order (fewer people are coming every week now), and ending the program outright. Each deserves its own notice window and its own consequence, spelled out before the first delivery — not improvised over email the week a problem comes up.
Setting a Headcount Change Deadline That Actually Works
Every caterer needs a final-count cutoff to buy food and schedule staff, and for most programs that cutoff lands one to two weeks before delivery, with some vendors asking for RSVP-style tracking two to three weeks out so they have time to follow up on stragglers. Two details matter more than the exact day:
- Increases and decreases usually aren’t treated the same. Most vendors stay flexible on adding people up to 48-72 hours before a delivery, sometimes at a small per-head premium, because more portions is a simpler problem than fewer. Cutting the count is often locked earlier, since food and staff are already committed once the cutoff passes.
- Build in a standing buffer instead of chasing an exact number every week. A small cushion — commonly cited around 5-10% over the RSVP'd count — absorbs normal week-to-week swings (a few people out sick, a last-minute guest) without triggering a change request every single time. Some vendors will accommodate a similar variance inside their own contract before charging extra.
For a recurring program specifically, the deadline should be a fixed day of the week — "final count due by noon Wednesday for Friday delivery" — not a floating number of days, since that’s what actually gets tracked and enforced week after week.
Handling Holidays and Skipped Weeks Without Damaging the Relationship
Because federal law doesn’t require private employers to offer paid holidays, every company sets its own calendar — which means the caterer has no way of knowing your office is closed the week of a holiday unless the recurring-program agreement says so explicitly, or someone remembers to tell them in time. Two practices keep this from becoming a recurring source of friction:
- Share the skip calendar up front, in writing, for the full contract term. A list of observed holidays and any known office closures, handed over at signing, lets the vendor plan staffing and ordering around it instead of treating every skip as a surprise cancellation.
- Distinguish a planned skip from a late cancellation. A week that’s skipped with reasonable notice — before the caterer has bought ingredients or committed labor for that specific delivery — typically shouldn’t carry any charge at all, since no cost was actually incurred. That’s a different situation from cancelling a delivery that’s already in motion, which falls back under the standard late-cancellation terms.
Some vendors will also reschedule a delivery within the same week — moving Monday’s lunch to Tuesday because of a holiday — without a fee, as long as the notice comes early enough that no purchasing has happened yet. That kind of flexibility is worth asking for explicitly rather than assuming it’s included.
What to Put in Writing With Every Recurring Vendor
The specific numbers will vary by vendor and program size, but the categories below are what a recurring-program addendum should cover, regardless of who’s cooking:
| Notice given | Typical treatment |
|---|---|
| Weeks in advance (holiday calendar shared at signing) | No charge — treated as a planned skip, not a cancellation |
| Several days before a specific delivery | Headcount changes accepted; decreases may be capped near the buffer |
| 24-72 hours before delivery | Full or near-full charge — ingredients and staff are already committed |
| Same-day | Full quoted price in almost every case |
Put the exact cutoffs, the buffer percentage, and the holiday list into the same document the vendor signs — not a side conversation with whoever answers the phone that week. A program that runs for a year will eventually test every one of these edges, and the version that’s in writing is the version that holds up.
Conclusion
A recurring catering program lives or dies on the boring parts of the contract: what counts as a skip versus a cancellation, how late a headcount can move, and who has to remember the office holiday calendar. Getting a written catering cancellation policy in place before the program starts — one built around a repeating schedule rather than a single event — turns what would otherwise be a monthly negotiation into a routine that both sides can rely on.