A final guest count is more than a number on an event sheet. It sets the point when the client’s estimate becomes a planning commitment: you use it to size recipes, revise purchase orders, schedule staff and calculate the expected balance. A clear clause explains the deadline, what counts as the guaranteed number, whether late increases are possible and how late decreases affect billing. It also tells both sides when dietary and allergy counts must be confirmed.

There is no universal deadline or minimum guarantee. For example, Café Pacific’s published catering terms request a final guaranteed count 14 business days before an event and do not allow decreases after that deadline; its terms also set an earlier cutoff for increases. Grazing Theory’s event agreement sets a 10-day final-count deadline and an 80% minimum billable count, while allowing reductions within its stated limit. These are examples of market practice, not industry standards or legal advice. Check the current terms and make your own language fit your service, supplier lead times and local rules.

Six copy-ready final-count clause options

Use these as starting points, not legal boilerplate. Replace every bracketed detail, make the clause consistent with the rest of your agreement and state whether “days” means calendar or business days. Have a qualified local professional review contract terms when needed.

1. Set the final-count deadline

Example: “Client must provide the final guaranteed guest count, including the number of meals for each agreed menu selection, by [time and time zone] on [date], which is [X] business days before the event. Caterer will use this count to plan food, supplies and staffing.”

When it helps: Use a definite date or a clearly calculable deadline. A specific date is easier to administer than “about two weeks before.” If vendor cutoffs differ, set the deadline early enough for the slowest essential order.

2. Make the confirmed count the billing minimum

Example: “After the final-count deadline, the guaranteed guest count is the minimum number of guests billed at the contracted per-guest rate, even if fewer guests attend. Any separately priced fixed services or items remain subject to their own line items.”

When it helps: This links a late decrease to the buying and labor commitments you have already made. Be explicit about the billing basis and avoid suggesting that the guarantee changes unrelated fixed charges.

3. Allow late increases only when feasible

Example: “Requests to increase the guaranteed count after [deadline] are subject to Caterer’s written confirmation of food, supplier and staffing availability. Approved additional guests will be charged at [amount] per guest [plus any applicable taxes or agreed charges], and must be confirmed by [final cutoff]. A request is not accepted until Caterer confirms it in writing.”

When it helps: A headcount increase can require more than food: it may affect venue capacity, service equipment and staff. Name the last point at which you can consider a request, and do not promise availability before checking.

4. Set a minimum percentage of the original contracted count

Example: “The final guaranteed count may not be reduced below [X]% of the original contracted count of [N]. The minimum billable count is therefore [calculated number] guests. If the submitted final count is lower, billing will be based on the greater of the submitted count or the stated minimum.”

When it helps: Write the actual minimum number alongside the percentage so no one has to do deadline-day arithmetic. State whether the minimum applies to the original contracted count or another clearly named baseline. Confirm the language is lawful and consistent with your pricing and other terms in your jurisdiction.

5. Require dietary and allergy counts with the final number

Example: “With the final guaranteed count, Client must provide the number of meals for each agreed dietary requirement and identify known food allergies and the affected guests or meals. Caterer will review the information and confirm in writing which requests can be accommodated. Caterer will not infer or guarantee an allergy accommodation that has not been specifically discussed and confirmed.”

When it helps: A headcount is not enough to plan special meals. Ask for clear details and time to review ingredients, substitutions and preparation procedures. Never guess what an allergy note means or promise that a meal is allergy-free without being able to support that claim. For a process to manage ingredient or recipe changes, see this café and catering allergen change-control checklist.

6. Explain how day-of overages are handled

Example: “Guests above the confirmed guaranteed count on the event day can be served only if Caterer has sufficient food, supplies, staff and venue capacity. Any accepted overage will be charged at [amount] per guest [plus applicable charges] and recorded on the event-day change sheet. Caterer cannot guarantee service for unconfirmed guests.”

When it helps: Distinguish a request from an accepted change. Choose a practical process for recording who approved an overage and how the final charge is calculated. A day-of clause should not imply that extra portions are always available.

Four client emails to make the deadline easier

14-day final-count reminder

Subject: Final guest count due [date] for [event name]
Send: About 14 days before the event, or earlier if the contract deadline or supplier cutoff comes first.

Hi [Client name],
We’re preparing the food, staffing and purchase plan for [event] on [event date]. Your agreement calls for the final guaranteed count by [deadline, including time and time zone]. Please reply with the total number of guests and the count for each menu choice, plus the dietary and allergy details we discussed. After the deadline, the confirmed count and the terms in your agreement will apply. If anything is unclear, please contact me before [date].
Thank you,
[Name]

Three days before the deadline

Subject: Reminder: guest count due in three days for [event name]
Send: Three days before the written final-count deadline, if a complete count has not arrived.

Hi [Client name],
A quick reminder that your final guaranteed count is due [deadline]. Please send the guest total, menu-choice breakdown and dietary/allergy information by then so we can finalize our prep and supplier plan. If you expect a change or are waiting on RSVPs, let me know today; I can explain what the signed terms allow, but I can’t extend the deadline unless we confirm that change in writing.
Best,
[Name]

Reply to a decrease received after the deadline

Subject: Re: Guest-count update for [event name]
Send: Promptly after a client requests a late reduction.

Hi [Client name],
Thanks for letting me know. The final guaranteed count we received by the deadline was [count]. Under the guest-count clause in our agreement, [briefly state the agreed billing rule, such as “that count remains the minimum billable count after the deadline”]. We’ll keep the billing basis at [count or contract minimum] and plan service using the latest information we can safely and practically accommodate. Please send any updated dietary details by [time]. If you’d like, I can confirm the expected balance and payment date from the agreement.
Best,
[Name]

Reply to a late increase: can or cannot accept

Subject: Re: Request to add [number] guests to [event name]
Send: As soon as you have checked stock, supplier timing, staffing and venue capacity.

If you can accept:
Hi [Client name],
We can accommodate [number] additional guests, subject to the details below. The revised count will be [new total], at [rate] per additional guest, for an added [amount] [plus any applicable agreed charges]. Please confirm in writing by [cutoff]. We’ll treat the increase as accepted once we receive your confirmation and send our written acknowledgment. The updated balance is [amount], due [date] under the agreement.
Best,
[Name]

If you cannot accept:
Hi [Client name],
Thanks for asking. After checking our food and supplier availability, staffing and service capacity, we can’t safely or reliably add [number] guests this close to the event. We’ll keep the confirmed count at [count] and proceed under the agreed terms. I’m sorry we can’t make this change; please let me know if there is another adjustment within the confirmed plan that you’d like us to review.
Best,
[Name]

What to do when the final count arrives

1. Lock and verify the record. Save the count, timestamp, who supplied it and the version of the agreement that governs it. Check that menu selections add up to the total, and ask about missing dietary or allergy details. Keep the billable guarantee separate from the number of meals you currently expect to prepare.

2. Re-scale recipes by yield, not by guesswork. For each recipe, divide the new planned number of portions by the recipe’s base yield, then multiply each ingredient quantity by that factor. For example, a batch that yields 24 portions scaled to 104 portions uses a factor of 104 ÷ 24, or about 4.33. Apply your own portion size, tested yield, trim loss and production buffer; do not assume every ingredient scales perfectly in real kitchen conditions. The USDA’s Food Buying Guide explains how yield data can help estimate purchase amounts and distinguishes as-purchased quantities from edible portions. Use relevant product-specific yields and round purchase units to practical package sizes.

3. Revise the purchase list and supplier orders. Convert recipe quantities into what you actually buy, check pack sizes and minimum orders, and identify orders that can still be changed before the supplier cutoff. Update quantities and written confirmations; do not assume a supplier has accepted a reduction until it confirms. A lower guest count may reduce variable ingredients but leave fixed minimums, delivery fees, disposable supplies or other line items unchanged.

4. Recheck staffing and service capacity. Review prep hours, service coverage, equipment, delivery and venue limits against the new count. A lower count may not reduce setup or travel work; an increase may need another server or additional equipment. Record any staffing or service change separately rather than applying the food-count percentage to every cost.

5. Update the expected balance and dates. Calculate the revised expected amount using the written pricing rule: the confirmed count or contractual minimum, plus approved additions and any separately priced services. Record when payment is due and when supplier or labor cash must leave the business. A revised invoice expectation is not cash received; keep the scheduled due date and actual receipt distinct in your cash plan. For an event-by-event view of supplier bills and event balances, see the holiday catering cash-flow planning guide.

Worked example: 120 quoted, 104 confirmed, 90% minimum

Illustrative example only. Suppose a caterer quoted 120 guests at $48 per person, and the signed terms set a minimum billable count of 90% of the original contracted count. The minimum is 120 × 0.90 = 108 guests. The client’s on-time final count is 104, so the caterer bills 108 guest equivalents: 108 × $48 = $5,184 for the per-guest portion. At 104 guests, the same rate would total $4,992; the difference is $192, before any separate charges, taxes or other contract terms.

For production, the caterer’s starting meal plan is 104 portions, not automatically 108, because the confirmed attendance count and the billable minimum serve different purposes. Compared with the original 120-portion plan, that is 16 fewer portions, or 13.3% less on the variable per-portion recipe quantities before practical buffers, yield adjustments and pack-size rounding. A 24-portion recipe, for example, scales to 104 ÷ 24 = about 4.33 batches. If a tested recipe needs 0.15 kg of edible-portion vegetables per guest, the 120-guest plan uses 18 kg EP and the 104-guest plan uses 15.6 kg EP, a reduction of 2.4 kg EP. The as-purchased amount may differ because of trimming and supplier pack sizes; use your own yield records or a relevant yield reference, then round to an orderable quantity.

The minimum billable count protects the contracted revenue floor; it does not mean you should automatically order food for 108 when the confirmed meal count is 104. Decide any additional service buffer from your event’s real uncertainty and food-safety plan. Review fixed costs separately, and document the 108-person billing basis, 104-person meal plan, supplier changes, staff plan and balance date so the client and team are working from the same version.

Keep the records connected without assuming automation

Ququ Quotes can hold reusable per-guest line items, which can help you prepare consistent event quotes. For food operations, Ququ Food supports menu products and recipes, recording purchases and sales as Movements, and reviewing income, expenses and margin in Finances; Food purchases and sales flow into the Finance budget. Treat those as records you update as your event plan changes: do not assume the guest count automatically scales recipes, updates supplier orders or revises a quote. A simple dated count log and written supplier confirmations still matter.

Keep the signed agreement, count emails, recipe version, purchase changes, staffing notes and revised balance together. Contract terms and consumer-protection rules vary by location, so this guide is practical information, not legal advice. For related background, see the event services quote template and worked recipe-cost and yield example. A reliable count process makes it easier to explain what the client owes, what the kitchen needs and which costs can—and cannot—shrink when the headcount changes.