A 14-person team is ordering dinner before an off-site workshop. The organiser adds four set-menu choices and sends one MealReply link in the team channel.
One list matches one restaurant order
The title includes the dinner date and the note names the restaurant. Anyone not joining can choose the explicit “Not attending dinner” option so the organiser can distinguish absence from no response.
Descriptions prevent avoidable questions
Each menu title includes the main dish and each description clarifies the side. The dietary field remains separate for restrictions that need personal follow-up.
Private receipts absorb normal changes
The list stays open until noon the day before. Two colleagues revise their own choices through receipt links, so the organiser does not have to edit a spreadsheet or reconcile duplicate messages.
Closing freezes a clear final count
The organiser closes responses, checks totals against expected attendance, follows up on one allergy note, and sends the four quantities to the restaurant.