# Event dietary request and caterer handoff worksheet

Event: ______  Service period / meal: ______  Food lead: ______  Provider: ______  Current revision/date: ______

## Public form copy (adapt to the actual food offered)
“For the meals described on this event page, do you need to discuss a food allergy, intolerance or other dietary requirement? If yes, tell us which food or ingredient and which meal is affected. We will pass relevant details to the food team and contact you if we need to clarify or cannot confirm an option. Update your request at [private contact route] by [operational date, if any]. A submitted request is not a guarantee of a suitable meal.”

Do not require a diagnosis. If no food is provided, remove the question. For group orders, identify the specific attendee. Explain who receives the data and the approved privacy/retention route for this event.

## Restricted handoff log
| Attendee reference (not public) | Meal / service | Current food or ingredient request | Clarification needed? | Provider owner / response date | Confirmed option or limitation | Guest informed / date | On-site contact | Revision |
|---|---|---|---|---|---|---|---|---|
| Example-001 | | | | | | | | |

## Check before food service
- [ ] Current attendee request is linked to the correct meal and person.
- [ ] Only authorized food and event staff can see the detailed request.
- [ ] Provider checked ingredients, preparation and any cross-contact question within its own food-safety process.
- [ ] Guest received a clear response; “request received” was not presented as confirmation.
- [ ] Changed requests superseded old lists; all teams know the current revision.
- [ ] An on-site contact can answer a guest’s question without exposing the full attendee list.
- [ ] Unmet or unverifiable requests were communicated plainly before service.
- [ ] Retention and deletion owner recorded under the event’s approved rules.

Food lead sign-off/date: ______  Provider sign-off/date: ______  Open issue and owner: ______