Allergy tracking for retreat kitchens

The riskiest handoff at a retreat is not the schedule or the rooms. It is the moment a guest's food allergy has to travel from a registration form to the person holding the serving spoon. This guide covers how to make that handoff reliable.

Why retreat kitchens are different

Retreat kitchens are usually run by volunteers who cook for a crowd, often from a donated or shared space, with a menu that changes by meal. Guests live there for a weekend, so every meal matters. That mix makes allergy mistakes easy: the person who read the sign-up form is rarely the person cooking.

Step 1: Ask the right questions at registration

Do not rely on a single "dietary restrictions" box. Ask separately:

• Do you have any food allergies? Which foods?
• How serious is the reaction, as far as you know, and do you carry medication such as an epinephrine auto-injector?
• Do you follow a special diet (vegetarian, gluten-free, diabetic-friendly, and so on)?
• Is there anything else the kitchen should know, such as a texture issue or an access need?

Ask this when guests register, while they are thinking about the event, rather than weeks later by email.

Step 2: Get the list to one accountable person

Choose a kitchen lead who owns the allergy list. Everyone else on the team should be able to ask them, not hunt through the registration records. The kitchen lead needs to see allergies and diets. They do not need to see payments or private notes unrelated to food. Keeping that separation also protects your guests.

Step 3: Plan the menu around the list

Once registration closes, count how many guests have each restriction and plan meals so that most guests can eat most of the meal. A few ideas:

• Choose a base meal that is naturally free of the most common allergens in your group, and add extras on the side.
• Label every dish with its main ingredients.
• Avoid shared serving utensils across dishes.
• Keep ingredient labels from packaged foods so you can check them if a guest asks.

Step 4: Make it visible on the day

Before the first meal, hold a short briefing with everyone who will cook or serve. Review the list aloud. For serious allergies, agree on how the guest will be identified and served, for example with a place card or a separate plate prepared first. Then make sure volunteers know who to ask when they are unsure. Guessing is never an acceptable answer.

Step 5: Keep a record

Afterwards, keep a simple record of what was served and any reactions or near misses. It helps next year's team and shows you took reasonable care.

What software can and cannot do

Software can collect the answers consistently, put them in front of the kitchen lead, and keep private details limited to the people who need them. It cannot cook the food or replace a conversation with a guest who has a severe allergy. Treat it as the safety net under your process, not the process itself.

Common mistakes to avoid

• Collecting the information late. Allergy answers collected by email weeks after registration are often missed.
• Trusting memory. A volunteer who "remembers" a guest's allergy is not a system.
• Assuming a label means safe. Recipes and packaged foods change. Check labels each time.
• Embarrassing the guest. Handle serious allergies privately and discreetly.
• Treating "no nuts" as the whole policy. Allergies vary widely, so plan from your actual list.

Write it down

A written policy helps volunteers follow the same steps. See our food allergy policy template for an outline you can adapt, and our retreat planning checklist for where allergy planning fits in your timeline.

More guides