
A monthly team pizza lunch should get easier to organise, even when the guest list changes. The useful distinction is between information you can carry forward and information you must confirm again. For a team based in Canary Wharf or Canning Town, a reusable brief can save repeated explanations without turning last month’s attendance into this month’s order.
Keep one standing brief, create a short update for each lunch, and make clear when an enquiry becomes a confirmed order. This is about managing a recurring decision, not building another delivery checklist.
Separate the standing brief from the monthly update
Your standing brief should describe how the team wants the lunch to work. Treat it as background for an enquiry, not permission to repeat a previous order automatically. Add a ‘last reviewed’ date and give one person responsibility for keeping it accurate.
| Keep in the standing brief | Reconfirm for each lunch |
|---|---|
| Main organiser, backup contact and approval process | Who is organising and approving this occasion |
| Usual office or proposed lunch setting | Actual location, date and requested lunch time |
| Preferred format, such as a shared team lunch | Confirmed attendees and unresolved replies |
| How dietary requirements are collected | Requirements reported by this month’s attendees |
| How quotes and order confirmations are recorded | The agreed selection, quantities and any changes |
Label anything that is merely a preference as ‘usual’ or ‘requested’. A usual lunch time is not a confirmed service arrangement, and a previous menu selection is not evidence of current availability.
Count people, not calendar invitations
Use a fresh attendance question each month: ‘Will you be joining the pizza lunch on this date, at this location?’ An accepted recurring calendar invitation may not answer that question. Ask people to respond specifically for the lunch rather than assuming everyone working that day will eat.
Keep three simple categories: confirmed, not attending and awaiting reply. If visitors or colleagues from another office are invited, name who is responsible for confirming them. Avoid quietly counting an unresolved reply as either a definite yes or a definite no.
For example, in a hypothetical month with 24 invitees, 17 might confirm, four decline and three remain undecided. The useful enquiry is ‘17 confirmed, with three outstanding’, not simply ‘a team of 24’. Ask how that uncertainty should be handled before agreeing quantities.
Use two deadlines, with different purposes
Set an internal reply deadline so you have time to chase missing answers and obtain approval. Separately, ask Zzetta what confirmation point and change arrangements would apply to the proposed lunch. Do not assume that your internal deadline is also the restaurant’s deadline.
- Gather replies: ask for attendance and current dietary requirements together.
- Resolve uncertainty: contact outstanding respondents and identify any requirements needing discussion with staff.
- Request or update the quote: provide the confirmed count and clearly flag anything unresolved.
- Record agreement: save the final selection, quantities and arrangements expressly confirmed for that lunch.
If your team cannot confirm early, explain that when enquiring. Ask what can be agreed provisionally and what must be settled before an order is accepted. Do not treat a provisional quote as an automatic recurring booking.
Carry forward preferences, not dietary assumptions
A previous preference for a particular pizza can be a useful starting point. Dietary requirements need a fresh check with the people actually attending. Someone may join for the first time, skip a month or report a change; last month’s totals should not become a permanent label for the team.
Zzetta offers Halal, Vegan and Gluten-Free options from one flame-fired kitchen. Specific ingredients and suitability must be discussed with staff. Those options do not establish that every dish is halal, that food is allergen-safe or that there is no cross-contamination.
Use the menu to prepare questions and proposed selections, rather than assuming previous choices remain available. Keep individual dietary information out of a widely shared attendance sheet; pass on the details needed for the enquiry through an appropriate private channel.
Send a short monthly update, not a copied old order
The following reusable enquiry template keeps the background consistent while making changes visible. Replace every bracketed field before sending.
Subject: Monthly team pizza lunch — [date] — quote request
Standing brief: Our team is based at [location]. Our usual lunch format is [format]. The organiser is [contact], with approval from [role]. This brief was last reviewed on [date].
This month: We request lunch on [date] at [time/location]. We have [number] confirmed attendees and [number] outstanding replies. We expect to resolve those replies by [date].
Food discussion: This month’s reported requirements are [details for staff discussion]. Our proposed selections are [choices], subject to availability and suitability discussions.
Please confirm: The proposed quantities and quote, when final numbers are needed, how later changes would be handled, and what is required to confirm this order. Please do not treat the standing brief as an instruction to repeat last month’s order.
Make next month easier with one small review
After lunch, record actual attendance, whether quantities felt appropriate and which preferences people volunteered. Use these observations to inform the next enquiry, not to create a fixed order regardless of headcount. Update the standing brief only when something genuinely lasting changes.
Ready to discuss your next team lunch? Visit Zzetta’s Catering Hub and Get a Quote via WhatsApp. Send the reusable brief alongside this month’s confirmed numbers and outstanding questions.
Zzetta – Soul Fired Pizza · 110 Barking Road, Canning Town, London E16 1EN · 020 3904 7074 · WhatsApp +44 7852 272312 · ciao@zzetta.co.uk
