Template

Allergen Management: Menu Labeling, FOH Intake & Incident Report (Interactive Template)

Ready-to-adapt menu labels and FOH scripts plus an interactive, timestamped incident / near-miss form and FOH checklist. Use this pack to standardize intake, prevent cross-contact, and record incidents so you can learn, report, and reduce risk.

Interactive Tool

Allergen Management: Menu Labeling, FOH Intake & Incident Report

Purpose

Use this interactive pack to standardize how your team communicates allergen risk, captures allergy intake, and records incidents or near-misses. The form below collects consistent, timestamped records that are searchable and can be linked to locations, shifts, and staff. Follow local law and adapt wording to your POS and brand voice.

Quick menu labeling & FOH intake reminders

Menu labels: Use clear short labels such as "Contains: MILK, EGG" or an icon + short text. Include a single legend/footnote: "If you have a food allergy, please notify your server. Despite our efforts, cross-contact is possible."

FOH intake script (short): "Do you or anyone in your party have a food allergy we should know about?" If yes: "Please tell me exactly what you are allergic to — I will note this on your order and speak with the kitchen manager."

The form below contains an FOH checklist, a structured incident / near-miss report, and fields to assign follow-up. Convert this pack into your POS/incident system so submissions are timestamped and retained.

Name of the staff member completing this form.
Select the staff role of the reporter.
Use local format (e.g., 2026-09-14 18:32). Submissions will also receive a server timestamp.
Where the incident or order was handled (e.g., Main Dining, Takeout Window, Line 2).
Capture if the guest shared their name or contact details.
Record the guest's exact words (e.g., "severe peanut allergy").
Include how the dish was modified (if at all).
Select or note the POS allergy option used, or paste the POS note.
Check all that apply.
If you stored a plate or took photos, note filenames or links to where they are saved.
What was done right away to reduce harm and prevent repeat in the same shift?
Longer-term fixes such as recipe changes, new POS flags, or retraining. Assign owners below.
Use local date format (YYYY-MM-DD recommended).
Rate the event to help prioritize follow-up.
1.0 10.0
This checklist supports consistent FOH behavior and training follow-up.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.