Anaphylaxis Risk and Allergy Protocols at Australian Wedding Receptions

A wedding reception combines nearly every condition that turns food allergy into a life-threatening event: a large number of guests, food prepared by strangers, shared or buffet-style service, and a celebratory mood that makes people reluctant to flag a medical concern in the middle of a party. Most severe allergic reactions in Australia happen when people eat food prepared by someone else, which is the definition of a catered reception. Buffet and shared-food formats compound the risk because cross-contact between dishes is hard to prevent and even harder to trace back to its source once a guest starts reacting. A reaction can also be mistaken for something else. Anxiety, a few drinks, the heat of a crowded room: all of these can mask the early signs of anaphylaxis, and a guest who is standing, dancing, or working the room is slower to be noticed and slower to sit down, both of which delay the one thing that matters most, getting adrenaline into them fast. None of this scales with how severe someone's past reactions have been. A guest who has only ever had mild symptoms before can have a fatal reaction the next time, so there is no such thing as a low-risk allergy guest based on history alone. Every one of these factors is structural to how receptions work, not a freak coincidence, so the risk is manageable: name the structure, and you can build a protocol around each part of it.

Food allergy rates among Australian adults and their implications for a guest list

Food allergy is not rare among Australian adults, and it is common enough that ignoring it at the planning stage is a genuine gamble rather than an overabundance of caution. Allergy rates are highest in infancy and fall with age, but even in adults the rate is around 1 in 50, and Australia has some of the highest rates of allergic disease of any country in the world. At the scale of a typical wedding guest list, that rate becomes an operational fact: a reception of any meaningful size will almost certainly include at least one guest carrying a real risk of a serious reaction. The ingredients that trigger those reactions are not exotic, either. The list of priority allergens declared under Australian law includes peanuts, tree nuts of every common kind, milk, egg, fish, crustacea, mollusc, sesame, soy, lupin, added sulphites, and gluten-containing cereals, which together touch almost every course on a typical menu. A standard three-course wedding meal, prawns to start, pasta for the main, a nut-topped dessert to finish, will likely carry several of these allergens without anyone intending it. Knowing that the risk exists somewhere in the room is only the beginning. Couples still need to know exactly which guests are affected, by exactly which allergen, and that information does not arrive on its own. It has to be asked for, and the RSVP is where that question first gets asked.

What Australian law now requires caterers to disclose

Caterers in Australia now operate under a clearer legal obligation to disclose allergens than at any point before, but that obligation stops well short of guaranteeing a safe reception. The Food Standards Code was amended on 25 February 2021 to introduce Plain English Allergen Labelling (PEAL) requirements, and that regime was formally in full effect from 25 February 2026, requiring clearer and more consistent mandatory allergen declarations across food labels. Separately, updated food safety regulations under Standard 3.2.2A took effect for all Australian food businesses from 8 December 2024, and that includes caterers working private functions like weddings. Together, these rules mean a wedding caterer sourcing packaged or pre-labelled ingredients has a legal duty to declare the priority allergens present in what they serve. That is a genuine floor, and it did not exist in this form before.

The allergen labelling regime that came into full force in Australia in February 2026 sets a mandatory floor for caterers, but it governs ingredients and labels, not the real-time communication that keeps a specific guest safe on the day. The law says what a caterer must declare about what is in the food. It says nothing about how that information gets from a guest's RSVP card to the kitchen, and nothing about how the right plate finds the right person during service. That gap is not a loophole so much as a boundary: legislation can force disclosure of contents, but it cannot build the communication chain that connects a guest's allergy to the meal placed in front of them. Filling that gap is left entirely to the couple and their caterer, and it does not happen automatically just because the caterer is compliant with the law. It has to be built, deliberately, starting well before the wedding day.

Collecting allergy information at the RSVP stage, the first link that determines every link after it

The RSVP is the only point in the entire planning process where a couple can collect accurate, voluntary allergy information from every guest at once, and how that question gets asked decides whether the answers are actually useful later. Allergen management works as a shared responsibility that runs the length of the service chain, from the guest's own disclosure through the kitchen to the person carrying the plate, and that chain starts with whatever gets written down before the event even begins. Simply giving guests a place to list food allergies on the RSVP, with enough lead time before the big day, is what makes it possible for the couple and caterer to actually plan around specific needs rather than reacting to them at the last minute.

What gets asked matters as much as whether something gets asked. A single "dietary requirements" box invites guests to lump preference, intolerance, and allergy together, but these are not the same thing and do not call for the same response. Vegetarian preference is a menu choice. Lactose intolerance is a comfort issue. An allergy with anaphylaxis risk is a medical emergency waiting to happen if it is missed, and the RSVP needs to separate these clearly enough that the caterer knows which entries demand a completely different level of care. The format of the RSVP itself changes how usable that data is. A structured field built for allergy disclosure produces information the couple can act on immediately. A free-text comments box, or an allergy mentioned in a separate email weeks apart from the RSVP itself, produces a pile of scattered notes that someone has to manually sort and cross-reference before it is any use to a caterer at all. The RSVP stage is where the entire safety chain either starts clean or starts messy, and everything downstream inherits whichever one it gets.

Getting allergy data from the RSVP to the caterer before the menu is finalised

Collecting allergy information at RSVP accomplishes nothing on its own. It has to reach the caterer while there is still time to act on it, and that window closes earlier than most couples expect. Allergy data has to land with the caterer before the final menu and preparation plan are locked in, because once a menu is finalised and ingredients are ordered, changing it is difficult, and sometimes it simply cannot be done in time. Couples who treat the caterer briefing as a logistical detail to sort out a few weeks before the wedding are, in practice, treating it as though it happens after the point where it can still change anything.

The briefing needs to happen in writing, not as a verbal aside during a tasting session, and it needs to answer three specific questions: which guests have which specific allergens, whether any of those allergens is serious enough to warrant removing the ingredient from the entire menu rather than just from one plate, and how each affected guest's meal will be identified, prepared, and served differently from everyone else's. On that middle point, the standard guidance is direct: if a guest has a severe nut allergy that carries a risk of anaphylaxis, the safer move is pulling nuts from the whole menu rather than trying to isolate one nut-free plate among a hundred others. Buffet service carries extra risk and deserves its own conversation. A dedicated, individually prepared meal for the guest with a food allergy is a safer option than expecting that guest to navigate a shared buffet line, because preventing cross-contact across dozens of shared serving dishes is close to impossible to guarantee. Whatever the format, the caterer should confirm in writing how allergen-specific meals will be labelled and tracked from the kitchen to the table, because that written confirmation functions as both a safety measure and a record if anything goes wrong later.

Caterers, understandably, sometimes push back on major menu changes requested close to the event. Raising allergy requirements when the contract is being negotiated, while the menu is still flexible, keeps the couple's ability to insist on real accommodations intact. Waiting until after the menu is set turns a planning conversation into a difficult negotiation.

What best-practice allergen training requires of wedding catering staff

A caterer can get the menu exactly right and still put a guest at risk if the staff serving that menu do not know how to recognise or respond to a reaction. Couples need a way to judge whether a caterer's team is actually prepared, and a national benchmark now exists for exactly that. The National Allergy Council published minimum content standards for food service allergen training, and those standards require staff to understand food allergy as distinct from other dietary needs, know the common food allergens in Australia, recognise what an allergic reaction looks like, and know what to do if a customer has one. That is the floor any wedding caterer's staff should be able to clear, and it is reasonable for couples to ask about it directly.

The broader framework backs this up. The Australia and New Zealand Consensus Statement on Best Practice Food Allergen Management 2025, led by the National Allergy Council and the Allergen Bureau and endorsed by 16 bodies including ASCIA, the Australian Culinary Federation, and the Restaurant & Caterers Association, treats allergen management as a responsibility shared across the entire service chain, not something that lives in the kitchen alone. Wait staff carrying plates to tables are as much a part of that chain as the chef preparing the food. Couples vetting a caterer can put this to a practical test with three direct questions: has the serving staff completed allergen management training, is there a written procedure for handling allergen-specific meals from kitchen to table, and who is the named person responsible for allergen management on the day. A caterer with clear answers to all three has done the work. One without clear answers has not, regardless of how the food tastes.

Guests themselves have a tool available too. Chef Cards, published by Allergy & Anaphylaxis Australia, are recommended for use at function venues including wedding receptions. A guest fills out the card with their specific allergy, hands it to the serving staff, staff pass it to the chef, and the card comes back with the completed meal as confirmation that the right dish reached the right person. Couples can suggest these cards to guests with severe allergies as an extra layer of verification on top of whatever the caterer already has in place.

Connecting allergy data to the seating chart so the right meal reaches the right person

A caterer with trained staff and a correctly prepared allergen-free meal can still send it to the wrong guest if the kitchen's information is not connected to where that guest is actually sitting. This is where most allergy protocols quietly fail, not in preparation, but in the last ten metres between the kitchen door and the table. Guidance from the Food Allergy Aware platform recommends that guests check again with serving staff as each course arrives, but that check is a backstop for a service plan that has already linked the guest's seat to their meal, not a replacement for having that plan in the first place.

The structural fix is straightforward to describe, even if it takes real coordination to build. A guest's allergy information, their table and seat assignment, and their meal specification must exist as a single connected record, not three separate lists that must be manually cross-referenced during service. On the morning of the wedding, the caterer and every serving staff member should be working from a printed run sheet organised by table, not by guest name alone, showing which seats at which tables have allergen-specific meals, what the allergen is, and how that meal is labelled so it cannot be mixed up with the seat next to it. That run sheet is the one physical object standing between a correct kitchen and a service mistake made under the pressure of getting a hundred hot plates to a hundred tables at the same time.

Some will object that this level of coordination is unrealistic for a reception of any real size. The coordination cost, though, is meant to happen in the planning phase, not during service. By the time guests are seated, the run sheet already exists, the seating chart is already linked to it, and service becomes a matter of following a system rather than improvising decisions on the fly.

Briefing the morning of: staff, adrenaline devices, and the emergency plan

The morning of the wedding is the last point where every piece of the protocol built over the preceding months gets tied together into something the venue staff can actually execute. That briefing needs a named person responsible for allergen management, not a vague sense that "someone" is handling allergies. One individual, clearly identified to the couple, the venue, and the catering team, should be responsible for allergen management on the day, with the authority to make a call if something looks wrong. That person needs the run sheet in hand, needs to know which guests carry anaphylaxis risk and where they are seated, and needs to know where any adrenaline device on site is kept and how to use it if a guest needs to reach for their own.

Anaphylaxis is always a medical emergency, and delayed treatment with adrenaline is what turns a serious reaction into a fatal one, so the morning briefing has to include a clear, simple action plan: recognise the signs, get the adrenaline device, call emergency services, keep the guest seated or lying down rather than upright, and do not wait to see if symptoms pass on their own. None of this replaces medical training, and none of it substitutes for a guest's own action plan and their own device if they carry one. This breadth means a standard three-course wedding menu, entrée with crustacea, pasta main, dessert with nuts, is likely to contain multiple priority allergens by default.

Every link in this chain, the RSVP question, the caterer briefing, the staff training, the seating record, and the morning-of plan, exists to close the same gap: the space between what the law requires a caterer to declare and what actually keeps one specific guest safe at one specific table. Building that chain deliberately turns a wedding reception into what every couple wants it to be, a room full of people who came to celebrate, and went home safely.