How to vote on restaurants with different dietary needs

A restaurant vote works only after the options are suitable for the people eating. Asking a person with a dietary requirement to accept the majority’s favourite is not a compromise. It is a shortlist failure.

In this guide: Filter for requirements first, then vote among suitable choices.

1. Ask about requirements privately if needed

Collect the practical requirement without demanding a diagnosis or personal history. Distinguish a preference from a requirement that affects whether someone can eat there.

2. Verify suitable choices before voting

Check the actual menu and ask the venue about the relevant preparation or service arrangements. A label such as vegan-friendly does not answer every allergy, cross-contact or accessibility question. Treat unanswered questions as unresolved, not as reassuring.

3. Vote on the remaining trade-offs

Once suitability is confirmed, compare price, location, noise, timing and atmosphere. Have a backup in case the selected venue cannot seat the group. Do not book an unsuitable restaurant and hope the kitchen will improvise.

Worked example: what this looks like

Fictional scenario—not a real customer story or executed AI result.

A fictional crew shortlists a tasting menu and two casual restaurants. One cannot confirm a required dietary arrangement, so it is removed before the vote. The remaining two both work; the group then chooses between a shorter walk and a quieter setting. Nobody has to disclose why the requirement exists to justify staying in the plan.

Make the decision bookable, not merely popular

A proposal needs a stable meaning from the moment people read it to the moment someone acts on it. Keep the dates, people, total-cost basis and important conditions together. If those facts change, explain the new version instead of silently editing the commitment beneath an earlier response.

Do not confuse three separate stages: an idea is worth considering, the group supports a specific proposal, and the affected people have authorised the booking and their contribution. A ballot helps with the middle stage. It does not verify supplier availability or move money.

Before closing the discussion, write the next action as a sentence with an owner: “Jordan will confirm the exact room arrangement by Thursday, then ask the crew to approve the current booking total.” That is more useful than “sorted”.

A message or brief you can copy

Replace the bracketed fields with your own details. Read the complete text before sending it; copying it here does not send a message or perform an action.

Dinner shortlist for [date]: [options]. Confirmed requirements: [practical needs only]. Still awaiting venue confirmation: [questions]. Please vote only after those questions are resolved. We’ll compare [price, location, atmosphere] among suitable choices.

Before you call it settled

• The proposal means the same thing to everyone reading it.
• Hard constraints are handled before preferences are compared.
• Each person chooses their own response; silence is not a payment instruction.
• The actual ballot result and settings are understood.
• A named person owns the next supplier or booking check.

Keep the final written confirmation with the reservation. Reconfirm directly with the venue if menus, group size or requirements change.

Put the decision somewhere useful

Keep the proposal, current terms and next action with the trip in Limbo. Use the relevant help guide below for the actual workflow; the examples above do not create a booking or determine your configured ballot outcome.

Sources and further reading

• Limbo: current voting guidance

Product guidance was reviewed against the local Limbo help content and voting implementation on 19 September 2026. The suggested group process is separate from the actual configured ballot rules.

Keep planning

• Build an AI trip plan you can actually use
• Group-trip planning guide