LunchLink workplace catering guide
How to handle last-minute catering headcount changes
Handle late catering headcount changes by confirming the count, protecting dietary meals, and checking same-day fallback options.
LunchLink Editorial Team
Research and writing
LunchLink Catering Planning Team
Operational review
Direct answer
The short answer
Treat a last-minute headcount change as an exception workflow, not a casual text update. First confirm the new count and when food is actually needed. Then separate increases from reductions, review the selected provider's written cutoff and current terms, and ask what is still possible for that exact order. Do not assume extra meals, substitutions, credits, or reduced charges are available. If the accepted order cannot absorb the change, send a complete same-day request immediately with the revised headcount, timing, address, dietary needs, and acceptable formats.
At a glance
Key takeaways
- Confirm the real count, eating time, and who owns the revision before calling the caterer
- Treat added guests and reduced guests as different commercial and operational problems
- Ask what is still possible for the exact order instead of assuming extras, credits, or substitutions
- Protect labelled and dietary meals before redistributing food to the wider group
- Use a same-day fallback only when the original order cannot absorb the change
Confirm the change before you escalate it
Late count changes create confusion when different people are reporting RSVP updates, room attendance, and executive additions at the same time. Name one person as the count owner and record the revised guest total, the number of protected or labelled meals, the actual eating time, and the latest moment the provider can still act on the information.
Avoid vague requests like 'a few more people' or 'less than expected.' The provider needs a real number, the full address, the room or handoff point, the current order reference, and the acceptable fallback if the exact menu cannot be expanded.
| Field | What to confirm | Why it matters |
|---|---|---|
| New total count | Exact number added or removed | Drives quantity, packaging, labels, and fees |
| Eating time | When people need food, not just meeting start | Determines what can still be produced and delivered |
| Protected meals | Named, dietary, or reserved portions | Prevents accidental reassignment of critical meals |
| Fallback format | What alternatives are acceptable | Helps the provider offer a workable same-day option |
Handle increases and reductions differently
An increase is a capacity and logistics problem. Ask whether the selected provider can add meals, scale a shared format, send a supplementary drop, or switch part of the group into another format without breaking the dietary or delivery plan.
A reduction is a terms and waste problem. Ask which quantities, charges, or packaged items were already committed and whether the provider allows any reduction, credit, or repurposing. Do not promise the wider team that the bill will fall just because attendance did.
| Change | Primary question | Typical risk |
|---|---|---|
| More guests | What can still be added for this exact order? | Kitchen capacity, driver timing, and missing labels |
| Fewer guests | Which quantities or charges are already committed? | Assumed credits, waste, and over-ordering |
| Mixed change | Can the provider rebalance protected and shared portions? | Dietary meals getting reassigned incorrectly |
Protect dietary meals and reserved portions first
Do not solve a shortage by redistributing labelled meals before checking the dietary list. Vegetarian, halal, allergen-related, gluten-related, or named individual meals may already be fully allocated even if the general count has changed.
Hold protected meals in a separate zone until the final attendee list is reconciled. If a labelled meal is no longer needed, confirm whether it can be reassigned safely and truthfully before handing it to another guest.
- Count protected meals before opening general distribution
- Keep labelled meals separate from shared extras
- Escalate a missing or unclear dietary meal immediately
- Document any approved substitution before service starts
Use a same-day fallback when the original order cannot stretch
If the accepted order cannot absorb the change, send a complete fallback request at once. LunchLink accepts urgent requests with at least four hours' notice, but suitability still depends on current kitchen capacity, route timing, the exact address, the revised count, and the acceptable formats for that moment.
The fallback should be simpler than the original plan when time is tight. A flexible format, broader cuisine range, or reduced customization can widen the set of options the team can check, but none of those changes guarantee acceptance.
| Send now | Include |
|---|---|
| Order reference | What was originally ordered and what changed |
| Revised headcount | Exact total plus added or removed guests |
| Timing | Eating time and latest workable arrival window |
| Format flexibility | Individual meals, platters, shared extras, or other acceptable fallback |
| Dietary needs | Protected meals that cannot be dropped or guessed |
| Access | Address, room, receiver, and delivery constraints |
Close the loop after service
Once the delivery arrives, reconcile the count before broad distribution. Confirm shortages, supplementary items, serviceware, labels, and the placement of protected meals. Record any unresolved issue while the provider can still respond.
After the meal, update the internal planning brief with what changed, what the provider allowed, and which assumptions failed. That creates a better cutoff and contingency plan for the next order instead of repeating the same scramble.
- Reconcile total quantity before general pickup
- Check labels, serviceware, and supplementary items
- Record shortages or substitutions while the provider is reachable
- Update the planning brief for the next order
