An event catering allergen checklist should connect menu versions, supplier ingredient information, staff instructions and the person authorised to resolve uncertainty. An organiser may receive a beautiful menu PDF weeks in advance and still discover that the supplier substituted a garnish, changed a sauce or moved food between service stations. The risk is not simply missing paperwork; it is that the information attendees receive may no longer describe what is served.

Four catering allergen evidence handoffs from approved menu to pre-service tabletop

Use this guide as a coordination workflow for events, not a substitute for a caterer’s professional food-safety management system. Local rules differ, so the food business and the event’s responsible safety lead must confirm which declarations and controls apply.

Start with an approved menu version

For each catering service—breakfast buffet, speaker lunch, VIP dinner, kiosk or staff meal—assign one current menu identifier and a named caterer contact. Record each dish, approved recipe or ingredient specification, the source of allergen information and the date the caterer confirmed it. Keep a separate change log for substitutions and kitchen variations.

The UK Food Standards Agency allergen checklist addresses accurate information and cross-contamination prevention for food businesses. Its specific legal requirements apply to the relevant UK jurisdictions and must not be presented as a universal worldwide rule. For US events, apply the applicable state and local requirements and involve the qualified food-service operator.

Make supplier evidence traceable rather than decorative

Ask the caterer for current allergen information and a method to refresh it when ingredients change. The organiser should know where the authoritative record lives and who can answer a guest-service question. A useful document register includes Menu version, Food service area, Caterer owner, Ingredient information received, Cross-contact procedure confirmed, Staff briefing completed, Signage reviewed, Open questions and Human approver.

Do not assume that an attachment named “allergen list final” is necessarily final. Log its effective date, any changed dishes and who reviewed the revision. If multiple contractors prepare and plate food, clarify which supplier owns each handoff. The UK technical guidance on allergen information notes the importance of staff knowing where accurate information is held.

Confirm practical cross-contact controls

An allergen declaration identifies ingredients; it does not by itself prove that unintended contact is prevented. Ask the qualified caterer to explain how food is stored, prepared, transferred and served under its approved controls. Shared utensils, buffet replenishment, late substitutions and staff unfamiliar with the menu can create gaps between the written record and actual service.

The CDC’s food-allergy practices guidance highlights staff training and, where feasible, separate equipment and work areas. Event production staff should not reinterpret those controls or promise a meal is safe. Instead, confirm that the caterer’s designated professional has reviewed the service plan and that the front-of-house team has a clear escalation contact.

Run a timed evidence check before the event

At contract confirmation, establish who owns the menu and evidence. Ahead of print deadlines, check whether printed menus, digital screens and place cards use the same current version. During the kitchen or venue briefing, confirm how requests reach the caterer’s qualified contact. Immediately before the relevant service, confirm whether any substitutions occurred and how approved changes reached serving staff.

A hypothetical conference lunch illustrates the failure chain: the vegetarian option changes from one sauce supplier to another after menu cards are printed. A vendor follow-up flags the substitution. The organiser marks “revised ingredient evidence pending”, removes the outdated sign from use and asks the caterer to validate new information before service. The automated check does not decide whether the new dish is safe.

Five questions for a short catering-vendor follow-up

Keep each call brief and refer to a specific menu and service period: (1) Is the current approved menu version still accurate? (2) Have ingredients, suppliers or preparation methods changed? (3) Where is the updated allergen record available? (4) Have all serving supervisors received the current instructions? (5) Which unresolved item needs your food-safety lead’s decision before service? Document the answer against the correct catering task.

Avoid asking the AI to interpret a free-text statement as an allergen clearance. If the supplier reports “mostly confirmed” or “waiting for the chef”, save that uncertainty as an exception. Do not use automated calls to collect attendee health histories; guest accommodation requests should use the event’s private, approved process.

Design an escalation path that stops unsupported assurances

The event producer can chase documentation, but the caterer must authorise ingredient declarations and controls. Assign the duty manager for inconsistent labels, the caterer’s food-safety lead for uncertain recipes or substitutions, and the venue or event safety lead for a significant service concern. A product not cleared for its intended service should remain on hold under the approved procedure, rather than being moved to “ready” after a generic vendor call.

Document the human response and the new evidence version. If the food-service plan is changed, ensure all affected locations receive the approved instruction. An acknowledgement from one booth should not be treated as a confirmed briefing across every buffet line.

Conduct a pre-service tabletop handoff

A useful final exercise involves the organiser, caterer, service captain and venue representative walking through an unexpected ingredient substitution. Each participant should be able to explain where the authoritative menu record is, who updates the signage, how service staff are notified and who can instruct the team to hold an item. Record any unresolved communication gap as a real task with a named owner. The point is not to practise medical treatment or promise a particular food is safe; it is to confirm that the approved professional decisions reach every serving station before guests arrive.

Connect supplier follow-up to the project board

A monday.com board can hold each service task, responsible vendor, due date, evidence link, latest response and review state. Autoza AI can support scheduled check-in calls and mapped updates under its approved configuration. It cannot independently verify ingredients, make medical judgments or certify food handling. Build a clear handoff to human food-safety owners before using automated follow-up at scale.

For a wider supplier coordination pattern, see Event Weather Contingency: Task-Owner Check-Ins. The common lesson is that a reported status is useful evidence, not the final safety decision. To design a permissioned follow-up cadence for your caterers, request a workflow review.

Explore Autoza AI for monday.com or browse more workflow guides.

Frequently asked questions

What documents should an event caterer supply before service?

Depending on jurisdiction and service format, obtain the current menu and allergen declarations, ingredient or recipe change records, the caterer’s approved management procedure, service-contact details and any other evidence required by the venue or food-safety lead.

Can an organiser accept a verbal “allergen free” promise?

Avoid treating an unsupported verbal assurance as safety proof. Ask the qualified caterer to provide the relevant written information, explain cross-contact controls and refer uncertain requests to its designated food-safety professional.

What happens if a menu item changes on event day?

Keep the old version identifiable, request updated allergen information, review signage and service-team briefing, and obtain the responsible caterer’s approval before the revised item is offered. Escalate unresolved uncertainty rather than guessing.

Should an AI check-in ask guests about food allergies?

Routine vendor calls should ask suppliers about menus, controls and approved evidence—not collect attendees’ medical information. Guest requests should be handled through a privacy-aware accommodation and food-service process.

Can monday.com automatically approve an event menu?

A project board can track documents, dates, owners and reviews, but menu safety and allergen declarations must remain with authorised food-business and event professionals. A reported “done” status should not trigger automatic approval.

Related reading