How to manage catering order changes and final guest counts

A customer message is a request, not yet an approved order

A changed guest count can affect food, packaging, labour, pricing and delivery capacity. Keep the request separate from the current approved order until the appropriate person has checked the consequences and the customer has confirmed the revised scope. This makes it possible to answer two different questions: what has been requested, and what has the restaurant committed to produce?

Choose a change-confirmation process before the event. Tell the customer who can approve revisions and when you need a final count for planning. Your deadline should reflect actual capacity and your agreed terms; there is no universal cut-off that works for every restaurant. Nebraska Extension’s catering checklist also treats final counts, coordination and client confirmation as distinct operating checks.

Record the proposed change in specific units

Keep the order reference, request time, requester, previous value and proposed value together. “Add eight guests” is not a complete menu instruction. Clarify whether the customer wants eight additional individual meals, larger shared trays or a different menu mix. Ask how any dietary request should be reviewed under the restaurant’s established process.

Make time changes equally precise. An event start, a kitchen ready-by time, a departure time and a delivery arrival window are different milestones. If the arrival window changes, review the other milestones rather than overwriting one vague “event time” field.

Check the impact before saying yes

Assign one person to coordinate the decision with the kitchen and fulfilment team. Check ingredients, preparation capacity, packaging, staffing and the delivery plan. Recalculate the agreed quote where the scope changes; do not silently assume the original price covers the new request. Follow your existing commercial and tax policies instead of treating this guide as contract advice.

• Which menu quantities or units change?
• Can the kitchen meet the revised ready-by time?
• Do packaging, equipment or staffing requirements change?
• Does the new address or access instruction affect dispatch?
• Does the customer need to approve a revised quote?
• Who is responsible for confirming the decision?

Worked example: an office lunch changes from 40 to 48 guests

This is a fictional operating example. Version 1 of an order has 40 individual meals and an agreed delivery window. The customer asks for 48 and specifies that the eight additions should match the existing meal mix. The catering manager checks production and packaging capacity, prepares the revised quantities and quote, and obtains confirmation before marking Version 2 approved.

The kitchen receives Version 2 with eight additional meals explicitly allocated by menu item. Packing staff receive the revised container or meal count. The delivery receiver and arrival window are checked again. The old prep sheet is marked superseded or removed according to the restaurant’s process. Nobody should have to infer the approved quantity from a group-chat message.

Use a short revision record the whole team understands

Copy these fields into your order record: order reference; revision number; requested by and time; previous quantities or timing; proposed quantities or timing; price impact; capacity decision; approved by and time; customer confirmation; teams notified; acknowledgements outstanding. An approval should make clear exactly which version is accepted.

Send each team the operational change it needs to act on, together with the current order reference. Confirm acknowledgement with the responsible person when a change affects production or dispatch. “Sent” and “understood” are not interchangeable, especially when the kitchen is working through normal service.

If a late change cannot be accepted, make the remaining plan explicit

Explain the constraint and the options the restaurant can actually deliver. Record the agreed outcome, including any part of the original order that remains unchanged. Do not mark a request confirmed merely to make the workflow look complete. Keep unresolved questions visible until the responsible person closes them.

After the event, review whether the change caused repeat calls, duplicated preparation or a missed handoff. Improve the order template and confirmation process using the actual incident. This guide covers information and team coordination; staff training, food safety, allergen handling and your contractual obligations remain governed by the restaurant’s approved procedures.