Somebody asks the same question every time there is a potluck: does anyone have allergies we should know about? Somebody answers it from memory, out loud, in a hallway, three days before the meal. It works, mostly, until the person who remembers is out of town, or the meal is run by someone new, or the fellowship dinner has grown from thirty people to ninety and nobody can hold all of it in their head anymore.
The problem is not that people forget to ask. It is that the answer never gets written down anywhere it will still be found the next time it matters. Here is where that note should actually live.
The note belongs to the person, not the event
A dietary restriction is a fact about a person, not a fact about a single potluck. If you write it on this Sunday's sign-up sheet, it dies with this Sunday's sign-up sheet. The next meal, the next small group dinner, the next youth trip that involves food — someone has to ask again, because the only place the answer existed was a piece of paper that is now in a recycling bin. Attach the note to the person's own profile instead, the same place you would keep a phone number or a birthday, and it shows up every time that person shows up.
Separate the emergency from the preference
Not every dietary note carries the same weight. A peanut allergy that can send someone to the emergency room is a different category of information than a preference for less spice or a choice not to eat meat on Fridays. Write the safety issue first, in plain words, somewhere it cannot be skimmed past — “severe allergy: tree nuts” reads differently than “prefers no nuts.” The preference still matters and still deserves a note, but it does not need the same urgency attached to it.
Write it once, well
The goal is not a long paragraph. It is a short, specific line that a volunteer who has never met this person can read and act on: what to avoid, how serious it is, and anything relevant about why (a recent diagnosis, a pregnancy, a child's condition, a religious practice). “No dairy — lactose intolerant, not an emergency” tells a cook everything they need. A vague note like “has some food things” tells them nothing and just moves the re-asking down the road.
Keep it visible to whoever is cooking, not the whole church
This is medical and personal information, even the mild version of it. It does not belong on a printed roster taped to the kitchen wall where anyone can read it. It belongs somewhere the small group leader, the hospitality coordinator, or whoever is actually buying groceries for Wednesday night can look it up when they need it, and nobody else has a reason to. Restricting who sees it is not bureaucracy — it is the same discreetness you already extend to other private information in your church directory.
Update it when you hear about it, not at the next intake form
People do not announce dietary changes on a schedule. Someone mentions a new diagnosis in passing after service. A parent tells the children's ministry leader about a nut allergy the week before a party. A member starts a new diet for health reasons and mentions it once, to one person. Whoever hears it first should be the one who writes it down, immediately, on that person's record — not a mental note to bring it up at the next committee meeting, which is exactly how these notes get lost.
Households complicate this in a specific way
A family signing up for the Wednesday dinner is not one dietary profile — it is however many people are in that household, each with their own note or none at all. The parent with the gluten sensitivity is not the same person as the child with the egg allergy, and a note attached at the household level blurs both. This is the same reasoning behind keeping households and individuals distinct in your records generally: the household is useful for mailing and RSVPs, but health information belongs to the individual it describes.
Let the note follow the person past this one meal
The real payoff of writing this down properly shows up months later, at a meal nobody planned yet. A guest who mentioned an allergy in March is still a guest with that allergy in October, whether or not they have become a member yet — the note should already be waiting on their record however far along their path from guest to member has gotten. In SundayBridge, that note lives on the person's own profile alongside their groups and their care history, so whoever is planning the next meal is reading the same record everyone else already reads — not hunting down last spring's sign-up sheet.
None of this requires new software discipline you do not already have. It requires one habit: when someone tells you what they cannot eat, write it where the next cook will actually look.