Three events, three spreadsheets, one Friday
A wedding couple sends their RSVP export with a column called 'Anything we should know?'. A charity dinner organiser forwards eleven separate emails from guests. A law firm sends a PDF of names with codes in brackets that nobody has explained, like (V), (GF) and (NN).
Your events coordinator retypes all three into your usual sheet, tidying up as they go. 'Pescatarian but eats chicken' needs a phone call. 'Nut allergy, severe' goes in bold. Two names appear twice with different requirements. By the time it reaches the head chef, it is a printed list with handwritten corrections, and the version the front of house supervisor has on the night is from before the last round of edits.
Why the list never arrives clean
You cannot control how clients collect information from their own guests. They use whatever they have, and most of those tools let guests type anything into a box.
- Free text mixes preferences, intolerances and allergies with no way to tell which is which.
- Guest names are not linked to a table or seat, so service has to match them up on the night.
- Updates arrive as a new full list, and nobody checks what changed from the old one.
- The kitchen needs counts per dish; service needs names per table. The same list is reformatted twice.
The retyping step is where meaning gets lost. It is also the step that only one or two people know how to do well, which makes busy weeks risky.
What the gaps cost on the night
The first cost is at service. A guest says they told the organiser about their requirement, the supervisor cannot find them on the list, and a chef has to make something at the pass while the rest of the table waits. It is stressful for your team and it is the moment the client remembers.
The second is time. Hours go on retyping, chasing unclear entries and reconciling versions, often late in the week when the kitchen is also busiest. And when a list is wrong, it is hard to show whether the error came from the client's information or your handling of it.
One structured list that everyone works from
What we build turns whatever the client sends into one structured list for the event, and sends anything unclear back to be confirmed.
- Clients get a link to a form built for your events: guest name, table if known, and dietary needs chosen from your own categories, with a free-text note for anything else.
- If a client insists on sending their own spreadsheet or emails, we import it and use AI extraction to map entries onto your categories. Anything ambiguous is flagged for your coordinator, never guessed.
- Each entry records whether the guest described it as an allergy, an intolerance or a preference, using the client's words, so your team can apply your own procedures.
- When a new version arrives, the system shows only what changed since the last one.
- The kitchen view gives counts per dish variation for each course. The service view gives names by table with their requirements.
- Unclear entries generate a short list of questions to the client, and the event shows as not final until they are answered.
| Client sends | What we do with it | What your team checks |
|---|---|---|
| RSVP spreadsheet | Map columns and entries to your categories | Flagged ambiguous rows |
| Forwarded emails | Extract names and needs into draft entries | Every draft before it is accepted |
| Coded PDF list | Ask the client what the codes mean once | The code mapping |
| Your own form | Nothing to convert | Late changes only |
The system never decides what is safe to serve. It gets the information in front of the people who make that call, in a consistent format, with the client's own words attached.
The kitchen and the floor on the same page
The head chef sees how many of each variation to prepare for each course. The supervisor prints or opens the table view on a tablet and knows who is where. If a late email arrives on the Thursday, the coordinator sees only the two changes, not a whole new list to re-read.
It also changes the conversation with clients. A form that asks clear questions gets clearer answers, and when something is uncertain, the client is asked in writing and their answer is kept with the event.
A quick self-check
- Someone in your office retypes dietary lists for most events.
- Kitchen and front of house work from different versions of the same list.
- You have had a guest at service whose requirement was not on your list.
- New versions of a list arrive and nobody can quickly see what changed.
- Clients use their own codes and abbreviations that you have to decode.