Events and catering: headcounts, allergens and late changes

It's 11pm on a Thursday. Saturday's wedding had 142 confirmed guests on Monday; now the bride messages to say it's 138, her aunt is coeliac "but not severely", and the cousin from Valencia is bringing his son after all, who can't eat nuts. Three messages, a voice note and a screenshot from a family group chat. If you run an events or catering business, this piece is about how to stop chasing those changes by hand, which parts an agent can take on, and where a person still has to stay in charge, especially when allergens are involved.

Where the time really goes (hint: not the kitchen)

Ask any catering production manager and you'll hear the same thing: the kitchen gets planned; the conversation with the client doesn't. A typical event produces a steady drip of messages over the three or four weeks before the day:

• Headcount confirmations. The client gives one number when booking, another when paying the deposit, and the final one, if you're lucky, 72 hours out.
• Allergies and intolerances. They arrive in pieces, badly spelled and sometimes uncertain ("I think it's lactose, or maybe egg").
• Logistics changes. Set-up time, van access, moving drinks from the garden to the hall because rain is forecast.
• Extras. An open bar that runs an hour longer, one more kids' menu, a dessert table nobody quoted for.

None of this is hard. The trouble is that it comes in through four channels, at any hour, and a wrongly noted detail doesn't show up until the day itself, in front of 140 people. If you coordinate ten or fifteen events a month, that admin can easily eat a full working day a week from someone who should be closing quotes.

The case: a 12-person caterer, before and after

Take a realistic example: a caterer with a central kitchen, twelve staff and eight to fifteen events a month across weddings, first communions and corporate lunches. The events coordinator holds everything in her head and in a spreadsheet.

Before. Clients message the business WhatsApp or the coordinator's own phone. She copies each change into the event spreadsheet by hand, forwards allergies to the kitchen in a separate group, and phones every client who hasn't confirmed numbers a week out. Monday mornings go entirely on "catching up" the following weekend's events. When she's off sick or on holiday, nobody knows exactly where each wedding stands.

After. An agent handles the same WhatsApp number and inbox. It doesn't decide anything with consequences, but it does the collecting:

1. Asks for confirmation on schedule. At 15, 7 and 3 days out, it messages the client with the current number and asks them to confirm or correct it. No reply? It nudges once, then flags the coordinator.
2. Collects allergies in a structured way. Instead of "any allergies?", it asks for the guest's name or table, which allergen, and whether it's an allergy or an intolerance. Vague answers ("he doesn't eat weird stuff") get a follow-up question.
3. Logs every change on the event record, with who asked and when. Nothing lives only in the chat.
4. Separates anything that changes the price. An extra kids' menu or another hour of bar goes onto a separate list the coordinator reviews and approves before the client sees a new total.
5. Freezes the event at 72 hours. After that point, headcount or allergen changes are no longer applied automatically: they go straight to a person, marked urgent.

The coordinator still makes every decision that matters. What she stops doing is copying, forwarding and chasing. In a setup like this it's reasonable to expect Monday mornings to shrink to a half-hour review, but measure your own before-and-after numbers: your volume and your clients aren't anyone else's.

Allergens: a person is in charge, not the agent

This is where you need to be most careful. In Spain, anyone serving unpackaged food, restaurants, institutional kitchens and caterers included, must provide information on the 14 allergens that are mandatory to declare, under Royal Decree 126/2015. Spain's food safety agency, AESAN, has a summary page worth keeping handy.

An agent can help a lot with the information side: recording accurately which guest has which allergy, cross-checking that list against the allergens you've already mapped for each dish, and flagging when a coeliac guest is seated at a table whose menu includes a dish with gluten. That's exactly the kind of tedious check that slips at 11pm.

What the agent should not do:

• Tell a guest "yes, you can eat that" on its own authority.
• Change a menu or suggest substitutions without the kitchen signing off.
• Accept an uncertain allergy at face value without someone on the team speaking to the client.

The working rule: the agent asks, organises and flags; the head chef decides and signs off. If your per-dish allergen sheet isn't up to date, fix that before automating anything. An agent cross-checking against stale data only gives you a false sense of safety.

Last-minute changes: where it all goes sideways

Friday afternoon, the client writes that there are ten more after all. Or the keynote speaker at the corporate lunch is vegan. Or the venue has moved the access time. These messages share three traits: they arrive out of hours, they affect purchasing and staffing that are already locked in, and the client expects an instant reply.

The useful thing an agent does here isn't solving the problem; it's replying fast and clearly. Something like: "Got it, 148 instead of 138. I'm passing this to the coordinator now to confirm whether we can accommodate it and what it costs. You'll hear from us before 10am tomorrow." The client relaxes, the coordinator gets a clean alert with the exact change, and nobody has to read a forty-message thread on Saturday morning to work out what moved.

It helps enormously if you write your cut-off rules down first: until when you accept headcount changes at no charge, how many extra guests you can absorb without buying more, and after what time only emergencies get handled. If those rules only exist in your head, the agent can't apply them and you'll keep answering from the sofa.

When it isn't worth it

To be fair, there are cases where this is overkill:

• If you run two or three events a month, a good spreadsheet and a calendar reminder will probably do. The volume doesn't justify building anything.
• If most of your events are corporate with a single contact who emails you the final list, collection isn't your problem.
• If your kitchen team won't actually review the alerts, don't set up the allergen cross-check. An alert nobody reads is worse than none, because everyone assumes someone checked it.

One detail people forget: allergy data is health data. Keep only what you need, delete it after the event, and make sure whatever tool you use is GDPR-compliant. That part isn't optional.

Where to start

Take the events in the next six weeks and try just one piece: headcount confirmations at 15, 7 and 3 days. It's the easiest thing to measure (how many clients confirm without you having to call?) and the lowest-risk. If it works, add allergy collection, with the kitchen's allergen sheet already reviewed. Last-minute changes always come last.

Asking, following up and filing each detail in the right place is exactly what an operations agent does. You approve anything that changes the menu or the invoice; it makes sure nothing lands on you by surprise on a Thursday night.