Common event catering mistakes and how to prevent them

Most event catering mistakes start before anyone serves a plate. You order against the wrong headcount, choose a menu the venue can't support, or give the caterer a service window that doesn't match the programme. Prevent them by agreeing who gets fed, when they get fed, what the full service costs, and who makes decisions when something changes.

So you've sold tickets, booked the programme, and found a caterer whose food you like. Then lunch runs late. People miss a session, your crew starts buying emergency meals, and the invoice includes equipment you thought was covered. The food might taste great. The catering still failed.

For a paid event, food is part of the experience you've sold. It also creates costs that can move after the ticket revenue is already committed. You need a plan that protects both. This guide walks through the common mistakes, how to catch them before service, and what to check afterwards so you don't pay for the same problem again.

The examples below are illustrative planning exercises, not industry benchmarks. Replace their quantities, prices and service times with your bookings, supplier quotes and tests. Food safety requirements also depend on where you operate. Your caterer and the relevant local authority need to confirm the rules for your event.

1. Ordering food against the wrong headcount

The first thing you want to do is separate attendance from meal demand. They aren't the same number.

A ticket might include lunch, offer an optional meal, or include admission only. Some people arrive after lunch. Others attend both days. Meanwhile, your speakers, technicians, security staff and volunteers may need food even though they never bought a ticket. If you tell the caterer your total ticket count and leave it there, you're asking them to guess.

Build a meal count for each service. Record the ticket groups entitled to that meal, confirmed add-ons, crew requirements and any other agreed allocations. Then show which numbers are confirmed and which are forecasts. Don't let an expected late sales figure look like a paid meal order.

Here's an illustrative example. You have 260 tickets sold for a one-day conference. Of those, 180 include lunch and 40 buyers have separately purchased lunch. The other 40 tickets don't include it. You also need 25 crew meals. Your confirmed requirement is 245 meals, before you discuss any additional allowance with the caterer. Ordering 260 automatically would confuse the ticket count with the food commitment.

Now check the awkward bits. Does a group ticket represent one person or several? Can a buyer transfer their ticket? Does a refunded booking still appear on the list somebody exported last week? Are staff meals the same menu and service time as attendee meals? Answer these before quantities go into production.

Give the final count an owner and an agreed cutoff. Ask what the caterer can change after that point, what it costs and how late additions get communicated. A late ticket sale doesn't automatically mean the kitchen can provide another meal.

An allowance for uncertainty can make sense. But decide what uncertainty you're covering. Walk-up buyers, unconfirmed crew and unusually large appetites are different problems. Ask whether a reserve can stay unprepared until needed, whether it suits the menu, and whether safe storage permits that approach. Buying extra finished meals isn't the only possible answer.

For a multi-day event, repeat the calculation by day and by meal. A full-event admission total won't tell you whether Tuesday lunch is oversupplied while Wednesday breakfast runs out. Keep your ticket offer, meal entitlement and catering count consistent throughout the booking journey.

2. Treating the cheapest menu as the cheapest service

A lower per-person price can hide a larger event bill. Before you compare quotes, make sure they describe the same job.

Ask each supplier to price the actual menu, quantities, service hours, staffing, delivery and equipment. Include setup, clearing, collection, crockery, disposables and waste handling where they apply. Check taxes, service charges, minimum orders and overtime too. You need to see what you owe for the service you've planned.

Imagine two illustrative lunch quotes. One lists food at $18 per person and leaves staff and equipment outside the price. Another lists $24 per person with those items included. You can't call the first cheaper until you add the missing costs. Equally, the second isn't automatically better. It may include a service you don't need.

Bring the catering total into your event budget, rather than keeping it in a supplier email. Separate the amount you owe regardless of turnout from the amount that changes with meal orders. That tells you what happens if ticket sales finish below your forecast.

There's another easy mistake here. A quote may say it serves your whole audience, while the staffing only covers delivery and setup. You were imagining an attended buffet. The caterer was imagining a drop-off. Ask what staff actually do during service, who replenishes food and who clears afterwards.

Name every item the venue provides. Then get the venue to confirm it. Tables, sinks, refrigeration and bins don't become available because the caterer's quote assumes them. If something is missing, price it before you approve the offer.

Keep the quote comparison readable. One row for each cost is enough. When a supplier excludes an item, mark who will supply it and the confirmed amount. A blank cell isn't a saving.

Don't bargain away the parts that let the service work. If the budget is tight, ask for a simpler menu, a different format or fewer service periods. Cutting replenishment staff while keeping a complicated buffet can leave you paying for food that never reaches the people who bought it.

3. Choosing the menu before checking the venue

A tasting tells you what a caterer can produce in their own kitchen. It doesn't tell you what they can deliver in yours.

Walk the venue together before you settle the menu. Follow the delivery route, inspect the preparation and holding areas, and confirm the equipment the service needs. Ask about power, water, ventilation, handwashing, waste collection and access restrictions. The menu should fit the site you've actually booked.

The practical questions really aren't glamorous. Can the delivery vehicle reach the loading area? Will a lift take the equipment? Who unlocks the kitchen? Does the refrigerator have usable space once other suppliers arrive? Where can staff wash their hands? These are the questions that stop your polished lunch plan becoming an expensive improvisation.

For events in Great Britain, the Health and Safety Executive's gas safety guidance for catering and hospitality explains responsibilities around gas equipment, maintenance and competent work. Have the supplier and venue confirm the arrangements for your installation. Don't treat a portable appliance as permission to put it wherever there's space.

Outdoor catering needs a workable weather plan. Decide what happens to the service point if wind or rain changes conditions. Confirm sheltered preparation space, safe routes for staff and suitable storage. A gazebo in the equipment list doesn't prove the whole service can keep operating.

Use your event logistics plan to connect catering access with the rest of the build. A supplier arriving during soundcheck may share the only loading entrance with production. A waste collection crossing the attendee queue may create a problem neither team expected.

Choose food that survives the real journey. If the caterer needs to transport it, hold it and serve a large group quickly, test that sequence. Ask how the dish tastes at the point of service, not just when it leaves the kitchen. Sometimes the better menu is the less delicate one.

4. Giving everyone a break the catering can't serve

This is where a lot of apparently good plans fall apart. The programme sends everyone to lunch at once, but the service was priced as if they would arrive gradually.

Start with the number of people likely to seek food during the busiest period. Then test how quickly a complete service point can serve them. A complete point includes everything they need to leave with their meal. If everybody still queues at one payment terminal or one collection desk, adding another food table won't solve the problem.

Here's a simple illustrative capacity calculation. Suppose 240 people need lunch within a 30-minute service window. Each independent serving point completes a meal every 30 seconds in a test. That's two meals per minute, or 60 meals per point over the window. Two points provide theoretical capacity for 120 meals. Four provide 240. Five provide 300.

This estimates total service capacity. It does not predict individual waiting times, which depend on arrivals and queue management.

Four points match the demand on paper, with no room for uneven arrivals, questions, spills or replenishment pauses. That doesn't mean five is always the answer. It means you need a better plan than assuming the arithmetic will perform perfectly. Test the actual setup and agree how much time people need to eat and return.

Your service window also differs from the whole break. People need time to walk to lunch, find a seat, eat and get back. If the session ends late, that remaining window gets smaller. Coordinate the programme and caterer before you advertise a break that nobody can use comfortably.

You have several options. Stagger the release of attendee groups, simplify the meal assembly, create independent service points or lengthen the break. Choose the change that fits your programme and venue. Don't make attendees solve it by skipping the session they paid to attend.

Check the queue layout too. Keep exit routes clear and leave space for people who need assistance or can't stand in a long line. Put clear meal information before the service point so basic questions don't all land on the person serving.

Time a rehearsal with the actual containers, utensils and menu. If your test uses empty plates and staff who already know every choice, it won't show what happens when buyers arrive hungry and confused.

5. Collecting dietary requests without a delivery plan

Asking about dietary requirements is useful only if the information reaches the people preparing and serving the food.

Separate preferences, religious requirements, intolerances and allergies. They can need different arrangements. Don't turn them into one checkbox labelled special meal and assume the caterer knows what that means. Give people a clear way to describe their requirement and explain who will respond.

The Food Standards Agency's allergen guidance for food businesses covers information for prepacked and non-prepacked food and management of allergens in preparation. It recommends written information supported by a conversation for non-prepacked food. Use the guidance relevant to your UK location and food format; elsewhere, confirm the requirements with the local authority.

Ask your caterer to confirm what they can safely provide. A vegan dish isn't automatically suitable for someone with a milk allergy, and gluten-free ingredients don't settle how food is prepared or handled. The person answering questions needs verified ingredient and preparation information.

Decide how a guest gets the agreed meal. Will they collect it from a staffed point, identify themselves to a server or receive it at their seat? Who checks that the meal matches the request? How do you stop reserved meals going to people who simply prefer that option?

Keep the information current. If a supplier changes an ingredient or substitutes a dish, the allergen information and staff briefing need to change with it. Don't let yesterday's printed sign make today's meal look safe when nobody has checked the replacement.

Protect the person's privacy. Share the information with the staff who need it to deliver the meal, and avoid displaying personal health details on a public list. You can make the collection process clear without asking somebody to explain their medical history in front of a queue.

Send the collection instructions before the event. Loopyah's attendee email tools let you send event updates to ticket holders. Use an update to explain meal times, where guests can get ingredient information and how to contact your team. Your caterer still needs to assess individual requests and manage the food service.

If a request arrives late, acknowledge it and get the caterer's answer. Don't promise a safe alternative because you want the buyer to feel reassured. A clear limitation before travel is more useful than a confident promise your kitchen can't keep.

6. Treating food safety as somebody else's vague responsibility

You can hire specialists and still need to know who is responsible for each part of the service. The problem starts when everyone assumes the next person has checked it.

Ask your caterer for the food safety arrangements relevant to transport, receipt, storage, preparation and service at your event. Confirm who checks food on arrival, who monitors holding conditions and what happens if the checks fail. The plan should name a person who can stop service.

The US FDA's current Food Code is a model offered for adoption by relevant jurisdictions. It isn't a universal event rulebook. For a US event, establish which requirements your local authority has adopted. For events elsewhere, use the applicable local guidance. Copying a temperature or time allowance from another country's article isn't a food safety plan.

You don't need to become the chef. You do need to ask whether the equipment can hold the planned volume safely, whether staff can check conditions during the rush and whether records will be kept. Agree the response to failed refrigeration or delayed delivery before either happens.

Keep safety decisions separate from pressure to avoid waste. Food that can't be confirmed safe doesn't become acceptable because it cost money or the programme is running late. Tell the service team that they can escalate a concern without waiting for someone to argue about the invoice.

Also check the supporting basics. The food team needs appropriate handwashing, cleaning materials and a safe way to keep raw and ready-to-eat work apart where relevant. A beautiful service table can't compensate for missing facilities behind it.

Work with your event's medical and incident leads on escalation. Staff should know how to report a suspected reaction or illness, who contacts emergency services when needed and how to preserve relevant information. This is an operational briefing, not an invitation for an untrained crew member to diagnose a guest.

Ask what evidence you'll receive after service. Delivery checks and incident records can help investigate a problem, but they need to exist when the event runs. Reconstructing them from memory afterwards gives everyone less to work with.

7. Forgetting to feed the people running the event

Crew catering usually fails because it gets bolted onto the attendee plan. Your crew don't necessarily have the same breaks, access or food needs.

Build their meals around shifts. Security may need food before the doors open. Technicians may be working through lunch. Speakers may need a meal near the stage rather than across the venue. Ask each team lead for numbers and workable collection times, then include them in the confirmed order.

Don't make a single crew runner responsible for finding everyone during the busiest part of the event. Decide whether teams collect meals, receive deliveries or rotate through a staffed point. Check where they can eat without abandoning their responsibilities.

This is also a budget issue. If people end up buying meals because the promised food isn't available, reimbursement costs appear after the event. If the team misses breaks entirely, you have a staffing problem that the caterer can't solve by leaving another tray on a table.

Keep attendee allocations and crew allocations visible to the kitchen. If the crew arrives first and takes meals reserved for ticket holders, you can create a shortage even when the overall food count was correct. Labels and separate collection arrangements are usually easier than fixing the argument afterwards.

Include dietary requests for crew through the same careful process. Someone working backstage shouldn't have to accept a meal they can't eat because the form only went to ticket buyers.

Finally, plan the late shift. The event ending for attendees doesn't mean the work is over. If the team stays to dismantle the site, confirm whether their meal is available after public catering closes and how it will be held safely until then.

8. Letting changes happen through scattered messages

You've agreed the plan, then the programme moves, a sponsor adds guests and somebody requests another service point. If those changes live in different chats, the caterer can arrive with a perfectly correct version of an outdated plan.

Keep one approved service brief. It should show meal times, quantities, menu, dietary arrangements, venue requirements and the people authorised to approve changes. Give it a clear version date. Share the updated version with everyone affected when a change is accepted.

A useful change record is simple. Write what changed, who approved it, what it costs and which parts of the event need to respond. If lunch moves, the catering team isn't the only audience. Attendee communications, room scheduling, crew breaks and cleaning may need updates too.

Don't let an enthusiastic team member order extras without knowing the cost. Give the onsite lead clear spending authority and an escalation contact. Decide what requires approval and what they can fix within an agreed allowance.

Confirm receipt of the final brief. Sending a document isn't proof that the supplier accepted its contents. Ask them to flag anything they can't deliver and settle those points before the event.

During service, use one contact for the caterer and one backup. Otherwise several people may issue contradictory instructions while each assumes they're helping. The contact should be reachable without disappearing from the role they were meant to cover.

After a verbal emergency decision, record it when practical. You don't need a committee meeting while lunch is failing. You do need a reliable account of what was authorised when the final bill arrives.

9. Planning surplus disposal instead of preventing surplus

Nobody wants to run out of food. But buying too much without a reason can quietly eat the event's profit.

The US Environmental Protection Agency's food waste prevention guidance recommends measuring wasted food and comparing purchasing with customer orders. That's a useful starting point for an event too. You need to know what went uneaten and why before changing the next order.

Separate food prepared but never served from food left on plates. The first may point to inaccurate counts, the wrong service window or too much production. The second may point to portions, menu suitability or quality. Putting both into one total loses the explanation.

Ask the caterer whether service in smaller batches makes sense for your event. It may help match replenishment to actual demand, provided safe holding and preparation arrangements allow it. You can't make that choice independently of the menu, staffing and equipment.

Discuss any donation or recovery arrangement before the event. Confirm who can accept the food, what safety and handling conditions apply, when collection happens and who records the transfer. A charity contact in your phone doesn't create a reliable collection plan.

Don't count a possible donation as a reason to overorder. Your first job is to buy a sensible quantity and deliver the meals you've sold. A recovery plan deals with remaining safe surplus; it doesn't fix a forecast that nobody checked.

For a food festival with independent traders, the organizer's role changes. You may not buy their stock, but you still coordinate service times, facilities and waste arrangements. Our guide to organising a paid food festival covers that wider model. Agree what information traders will share so your next event improves without pretending you control every kitchen.

10. Reviewing the invoice without reviewing the service

Paying the final bill closes the transaction. It doesn't tell you whether the catering worked.

Compare the agreed order, actual service and final charges. Identify extra meals, overtime, equipment replacements and emergency purchases. Check that each addition has a clear reason and approval. Query unexplained differences while everyone still remembers the event.

Then review what guests experienced. Did the service open on time? Were the promised choices available? Could people get food within the break? Did dietary meal collection work? Were crew meals delivered around shifts? A supplier can meet its food quantity and still leave you with an unusable service.

Ask the kitchen and floor team what constrained them. You might discover that the menu was fine but the room release overwhelmed the queue, or that a missing key delayed access. Fix the actual cause. Switching caterers won't help if your programme recreates the same problem.

Use the review to change specific catering purchasing decisions for the next event. Revise the meal forecast, allow more setup time, simplify a dish or adjust the service layout. Put the financial effect into your event budget review. The lesson should change a future order or operating plan, not sit in a document nobody opens.

Keep what worked as well. If a reserved collection point handled dietary meals well, keep the instructions and staffing arrangement. If a meal format moved people through comfortably, record the conditions that made it work. Good delivery becomes repeatable when you know why it succeeded.

Run one final service walk-through

Before the event, get the catering lead, venue contact and your operations lead together. Walk the meal journey in order. Start where the delivery arrives and finish where the last dirty plate goes. You'll catch gaps that don't appear when each supplier reviews only their own part.

Give somebody the role of a guest collecting an agreed dietary meal. Can they find the right point without asking several people? Can the server identify the meal and answer questions using current information? Now try the same journey for someone who needs assistance. The ADA National Network's temporary events accessibility guide provides a US reference for planning accessible temporary events. Confirm the applicable arrangements for your site and audience.

Next, rehearse a disruption. In this illustrative scenario, the session before lunch overruns and the caterer reports that one serving point can't open. Your event lead needs to decide whether to delay the next session, change the release of groups or use a confirmed alternative. The kitchen lead decides what can safely be served. The communications lead updates attendees. Nobody should have to discover their responsibility in the queue.

Check the fallback against your original promise. If you sold a hot meal, switching to a snack isn't a harmless operational change. Decide how you'll explain the difference and handle requests for a remedy. Keep a record of what you offered and what the buyer received.

Then check the recovery time. An extra service point isn't useful if its equipment takes longer to arrive than the remaining break. A backup menu isn't available unless the supplier can produce it under the actual conditions. Ask when each alternative could start and what it needs from your team.

Finish with a short briefing the service staff can use. Explain meal times, entitlement checks, dietary collection, who answers ingredient questions and who can authorise a change. Put the contact information where they'll have it during service, rather than inside a document on somebody else's laptop.

If the walk-through exposes a problem, change the plan while there's still time. You don't need to rehearse every possible disaster. You need to find the weak decisions that would otherwise land on a busy server with hungry guests in front of them.

What to check before you approve catering

Before you commit, read the plan as if you're the attendee arriving hungry and the team member trying to run the service. Can both people understand what happens next?

• Your meal count separates confirmed orders, forecast demand, crew and other allocations.

• The quote includes the service, equipment and hours your plan needs.

• The caterer has checked venue access and facilities against the menu.

• Your busiest service window has been tested against likely demand.

• Dietary requests have confirmed meals and clear collection instructions.

• Safety checks, incident escalation and authority to stop service have named owners.

• Crew meals fit working shifts and remain separate from attendee allocations.

• The final approved brief reaches every team affected by changes.

• Surplus arrangements are practical and comply with relevant requirements.

• Your review will compare cost, delivery and the experience guests actually received.

The food is only one part of the decision. Buy a service your venue can support, your programme can accommodate and your team can manage. When the count, timing and responsibilities are clear, you give the caterer a much better chance of delivering what your buyers paid for.