Catering for a Multi-Day Conference Team: Count Each Day Separately

Illustrative pizza catering banner

For a multi-day conference team around ExCeL London and the Royal Docks, yesterday’s attendance should not become today’s catering order by default. People may join for one session, leave before lunch or work different shifts. The useful starting point is a separate count for each meal, not one total copied across the conference.

This guide focuses on keeping that count accurate: who is actually eating, what remains uncertain and how to communicate changes before an order is confirmed. It is for people feeding a working team, rather than individual visitors choosing somewhere to eat.

Count people eating, not people registered

Define whose meals your team is covering. Exhibitors might need food for stand staff; crew may need separate meal groups around shifts; organisers should distinguish their own team from delegates. Visitors making their own lunch arrangements should not enter your catering count unless you have explicitly agreed to include them.

Ask each person a meal-specific question: “Will you need a team-provided lunch on Tuesday?” That gives you a clearer answer than “Are you attending the conference?” Repeat it for each relevant day and meal.

Use four statuses: confirmed eating, pending, not eating and cancelled. A person who has not replied is pending, not automatically included or excluded. If someone joins after lunch, record their attendance without counting them for that meal.

Build a daily attendance view

Keep one shared record with a row for each person and meal. Useful fields are date, meal, team or shift, attendance status, dietary request, last update and person responsible for confirming. Restrict access to personal dietary information to those who need it.

Then create a short daily summary. This hypothetical three-day example shows why a repeated order could miss the actual pattern:

Meal Confirmed eating Pending Attendance range
Day one lunch 12 3 12–15
Day two lunch 18 2 18–20
Day three lunch 9 4 9–13

The range describes uncertainty; it is not an instruction to order for the highest number. Ask the supplier how they would plan quantities against confirmed attendance and whether any allowance for unresolved guests is possible. Agree that allowance explicitly rather than adding an unexplained percentage.

Separate the forecast from the confirmed order

Your attendance sheet and the supplier’s accepted order are different records. Keep both visible. A useful summary shows latest expected attendance alongside headcount used for the confirmed order, with a difference column.

For example, if day two’s order was agreed against 18 people and two pending colleagues subsequently confirm, the sheet should show a difference of two. That flags a conversation; it does not mean the order has automatically changed.

  • Forecast: your current estimate, with pending people shown separately.
  • Submitted request: the numbers and requirements you have sent for confirmation.
  • Accepted order: what the supplier has explicitly agreed to provide.

Give each submitted revision a clear version label and timestamp. Ask for acknowledgement of the latest version so that an older message is not mistaken for the final instruction.

Agree when each day can change

Before committing, ask whether each day can have its own confirmation point or whether the whole conference order must be settled together. Also ask how additions, reductions, cancellations and dietary changes would be handled. Do not assume that a change possible on day one will also be possible later.

Set your internal reply deadline earlier than the supplier’s agreed deadline, leaving time to chase missing answers and resolve questions. Appoint one person to submit changes and a deputy for absences. Colleagues can update their attendance, but only the nominated contact should authorise an order revision.

After each meal, record how many people actually ate and any useful feedback about quantities. Use that to question the next day’s assumptions—not to overwrite its separately confirmed attendance.

Track dietary requests by day too

A dietary count should change when the people attending change. Record requests against each meal, and avoid simply carrying Monday’s totals into Tuesday. One person may have overlapping requirements, so category totals should not be added together as though they represent different people.

Zzetta offers Halal, Vegan and Gluten-Free options from one flame-fired kitchen. Discuss specific ingredients and suitability with staff; these options are not a promise of allergen-safe food or universal suitability. Share the relevant daily requirements before an order is agreed, and ask staff to clarify what can be accommodated.

Send an enquiry that makes the differences clear

Zzetta is an independent stone-oven pizzeria established in 2018 in Canning Town. Explore the Catering Hub and use the menu as a starting point for questions, rather than assuming every item is available for your proposed arrangement.

Suggested enquiry template: “We are arranging meals for a conference team around ExCeL London / the Royal Docks on [dates]. For each meal, our confirmed and pending counts are [daily breakdown]. Dietary requests by meal are [details]. Please quote against the confirmed counts and explain how pending attendees could be handled. Can each day be confirmed separately? Please confirm change deadlines, quantity recommendations and any conditions before we agree the order. Our authorised contact is [name].”

Get a Quote on WhatsApp with your daily breakdown. Any proposed arrangements at the conference site also need checking with your venue or organiser; a catering enquiry does not establish permission.

Zzetta – Soul Fired Pizza · 110 Barking Road, Canning Town, London E16 1EN · 020 3904 7074 · WhatsApp +44 7852 272312 · ciao@zzetta.co.uk

Scroll to Top