What should a chef do when a daily special has no written allergen record?

Why specials are the weakest link in allergen control

A special is built from whatever is on hand: yesterday's braise, a sauce from the walk-in, a garnish improvised at the pass. That is exactly what makes it good, and exactly what makes it dangerous. Purchased components carry allergens the chef may not have read the label for, sauces made earlier in the week contain ingredients no one remembers adding, and the dish itself often changes at four in the afternoon when something runs short. The core menu has a matrix that took weeks to build. The special has a description that lives in the chef's head. Related: How QR Menus Changed the Game

Servers learn about the special verbally at pre-shift, usually in a sentence or two focused on selling it. When a guest at table twelve asks whether the special is safe for a shellfish allergy, the server repeats what they heard, or worse, reasons from the dish name. Nobody wrote anything down, so there is nothing to check. Many of the allergen near-misses operators describe to us involve a dish that was not on the printed menu that day, and the common thread is not carelessness but the absence of any record to consult. Related: Why a Printed Allergen Card Goes Out of Date

Keep reading: Allergen Labeling Basics Every Restaurant Should Know, Why a Printed Allergen Card Goes Out of Date, Building a Menu That Is Safe and Appealing. See how MenuAegis helps you live allergen and nutrition menus with an auto-updating qr.

The rule: no written record, no service to a declared allergy

Set a hard line and say it out loud to the team. If the kitchen cannot produce a written component list for a special, the answer to any allergen question about it is that the kitchen cannot confirm it is safe, followed immediately by the dishes that are documented and would work instead. Losing one special sale is trivial compared to the alternative. Guests with allergies are used to hearing an honest no, and they trust a restaurant more for saying it than for guessing. Related: Allergen Labeling Basics Every Restaurant Should Know

The rule also shifts the incentive in the right direction. Chefs who want their special to sell will write the record, because a special that cannot be recommended to a meaningful share of the dining room is a special that sits. Managers should back the rule at the pass and on the floor, and should never override it under pressure from a busy service. The moment one exception is made, the rule is gone.

A five-minute special card that actually gets filled in

The card has to be quick or it will not happen. One page, filled in before pre-shift: dish name, date, and a line for every component on the plate. For each component, note whether it is made in house or purchased, the brand and product for anything purchased, and which of the nine major allergens it contains. House-made components reference their recipe card if one exists, or list their ingredients if not. The chef signs and writes the time. It takes about as long as plating the first one.

Post the card at the pass and at the server station, and read the allergen line out loud during pre-shift so every server hears the same words. If a component changes mid-shift, the card is amended with a new time and the floor is told immediately, not at the end of the night. Cross out nothing; write the new version below the old so the history is visible. Keep the cards in a binder or a folder by date, because a guest who calls two days later asking what was in the special deserves an answer.

Getting the special in front of guests without a reprint

A printed menu cannot keep up with a dish that exists for one evening, which is why specials are usually announced rather than shown. A live QR menu solves this cleanly: add the special as a dated item, flag its allergens from the card, and the guest scanning the code sees exactly what the server has. When the special sells out or changes, the item is edited or removed and every table sees the change at once. MenuAegis was built around this kind of same-day edit, but the principle holds for any live menu.

Over a few months, the archive of special cards becomes something more useful than a compliance record. Specials repeat, and a card that already lists components, brands, and allergens is a head start on the next time the dish runs. Some operators promote a well-documented special onto the core menu precisely because the allergen work is already done. Treating the special card as the first draft of a permanent record, rather than a chore, is what makes the habit stick. Related: Building a Menu That Is Safe and Appealing