A useful catering count must answer two questions: how many of each dish are needed, and which guest requested each one. MealReply keeps those views together and updates them whenever a guest uses their private receipt to revise a response.
Use one list for one event or order
Keep separate events for separate service times or venues. A focused list gives every total a clear deadline and prevents lunch, dinner, and companion orders from becoming one ambiguous count.
Make mutually exclusive options
Each participant selects exactly one option. Write choices so they do not overlap, and include portion or course differences in the title when they affect what the provider must prepare.
Keep guest details private
Participants see the menu but not other guests or aggregate counts. The organiser link contains names, choices, and dietary notes, so it should be stored and shared like private event information.
Use receipts for corrections
After submitting, each guest receives a private receipt link. It changes or withdraws only that response, avoiding duplicate entries and reducing manual corrections for the organiser.
Lock the count at a clear deadline
Close responses before ordering and record the totals at that moment. If changes are accepted later, reopen intentionally, review the new version, and send an updated order rather than relying on memory.
Reconcile with attendance and provider rules
Meal counts do not replace the attendance list, minimum-order rules, staff meals, or contingency portions. Treat the collected totals as a clean input to the final catering decision.