Event teams often face the task of changing from one meal format to another within a single day while keeping dietary details accurate for every attendee. This requires mapping the programme first, then building communication steps that stay consistent when plated service gives way to a standing reception or when a networking lunch replaces a seated dinner. The current independent publication of De Poort van Antwerpen produces these guides separately from any earlier operators of the domain. All references to rules draw on the Federal Agency for the Safety of the Food Chain (FASFC) and the European allergen labelling requirements that apply in Belgium.
Clear records reduce the risk of an allergen reaching the wrong plate. Staff need one reliable channel for updates rather than separate notes passed between kitchen and floor. The method begins with a programme review that shows exactly where and when each format change occurs, followed by a system that carries the same dietary list through every switch without loss of detail.
Reading the programme for meal-format changes
Begin by listing every segment that involves food or drink and note its duration, location and expected movement of people. A morning plenary that ends with coffee can shift to a working lunch served at tables, then to a drinks reception where guests stand. Each change alters how dietary requests reach the service team. Fixed seating periods allow one central list, while periods of free movement require the list to travel with each station. Programme mapping also shows the time available between segments for any list updates. When movement is high, the list must be split so that staff at different points hold only the entries they need. The same map reveals whether a single update moment exists or whether updates must happen in sequence. This step prevents the common error of assuming one format will cover the entire day when the schedule shows otherwise.
Judgment on format suitability rests on two conditions: the number of guests who submitted requests and the physical distance between service points. If more than ten requests involve strict avoidance, plated service with table numbers is preferable because it limits handling. When the programme places two formats within thirty minutes of each other, the list must be prepared in duplicate beforehand. A frequent mistake is to record only the main meal and forget that coffee breaks or welcome drinks may also contain allergens. The programme review therefore includes every refreshment point, however brief, so that the dietary list covers the full sequence rather than the largest single meal.
Collecting and updating dietary details before the day begins
Send a short form that asks only for the medical or religious reason behind each request and the exact items to avoid. Record the date the information was received so that later changes can be tracked. Store the list in a shared document that both the kitchen and the service supervisor can open on a tablet. Two days before the event, send a confirmation message to every attendee who submitted a request. Ask them to reply only if the details have changed. This step reduces the number of last-minute alterations that reach the kitchen during service. The form itself should use plain language and avoid open text boxes that invite vague answers such as “no nuts” without naming the specific nut or preparation method.
Applicable conditions for this method are events with more than twenty attendees or with at least one overnight stay, because both increase the chance of a request being forgotten. A common error is to accept verbal additions at registration without entering them into the shared document at once. The correction is to keep a printed copy of the blank form at the registration desk so that any new request is written down immediately and photographed into the digital record. European labelling rules require that the kitchen knows the exact composition of every dish served, so the collection process must capture not only the guest’s restriction but also the dish they will receive in each format.
Dividing the list for different service points
When the programme moves from plated lunch to a standing reception, split the master list into two shorter lists. One stays with the plated service team and shows table numbers; the second travels with the reception stations and shows only names or coloured badges. Colour coding on badges or lanyards lets staff check requirements without asking guests again. Print the lists on waterproof paper and place one copy at each service point. Update any change by crossing out the old entry and writing the new one by hand, then photograph the page so the kitchen receives the same update within minutes. The division must be checked against the programme map to confirm that no guest appears on both lists at the same time.
Judgment criteria include the number of service stations and the speed of guest movement. If stations are more than twenty metres apart, separate lists reduce the time staff spend walking between points. A frequent error is to divide the list by meal type rather than by location, which leaves one station without the full set of names it needs. The correct approach is to divide first by physical station, then within each station by the order of service. This keeps the list short enough to read quickly while still covering every request that applies to that point in the programme.
Briefing service staff on format switches
Hold a ten-minute briefing at the start of each new service period. Read the current list aloud, point to the locations where those guests will stand or sit, and confirm the route the list will follow if the format changes again. Staff who move between stations need to know they must carry the list with them rather than leave it at the previous station. The briefing also states the agreed response to an unlisted request that appears on the day: offer a plain option already prepared for another guest and log the new request for the post-event record, without promising future adjustments on the spot.
Conditions that make the briefing necessary are events lasting more than four hours or using more than two distinct meal formats. A common mistake is to rely on a single morning briefing that staff later forget when the second format begins. Repeating the key points at each switch prevents this. The briefing must also cover the physical path the list will take, including who carries it during any gap between services. This detail is often omitted, yet it is the point at which information is most easily lost.
Keeping records during service
Use a simple tick sheet next to each name or table number. A tick shows the meal was served; a cross shows it was returned or refused. At the end of each segment, photograph the sheet and send the image to the person maintaining the master list. This creates a running record that can be checked against the original requests. When a guest leaves early or arrives late, note the time beside their name. These notes help later when deciding whether a continuous service station would have been more suitable than fixed slots.
The method applies whenever the programme contains three or more meal-related segments or when the number of dietary requests exceeds five. A frequent error is to record only the final outcome and omit the time of service, which removes the ability to see whether a request was handled at the correct station. The photograph step ensures that any handwritten change is captured before the next format begins, preserving the chain of information across the entire day.
Closing the loop after the event
Within 24 hours, compare the tick sheets with the original dietary list and note any mismatches. Record only the facts: number of changes received on the day, number of meals returned, and any station where the list arrived late. Keep the file for the next event that uses the same venue or the same suppliers. This record stays with the current operators and is not transferred to any previous domain management. It supplies the factual basis for adjusting communication steps when a similar programme appears again.
The review is useful when the same group or venue is booked within six months, because patterns in late changes become visible. A common error is to skip the review when the event ends smoothly, yet the absence of recorded mismatches does not prove the system worked; it only shows that no mismatch was noticed. Completing the comparison within 24 hours keeps the memory of each segment fresh and produces a document that can be read in under ten minutes before the next planning meeting.
