Make the shortlist before you spin
Start with restaurants the whole group could genuinely visit or order from now. Randomly selects from the Entries you provide; it does not search nearby venues, check menus, verify allergy information, compare prices, or know whether a restaurant is open.
Ask for hard constraints before preferences. A severe allergy, medical dietary requirement, wheelchair access need, fixed budget, closing time, travel limit, or reservation requirement is not something to leave to chance. Check the restaurant’s current information directly and remove any place that fails a requirement.
Next, ask each person for one or two places they would actually accept. Remove duplicate suggestions and confirm the final shortlist aloud. A smaller list of valid options produces a more useful result than a long list padded with places someone plans to veto later.
Keep every Entry at the same level
Use restaurant names when the question is “Where should we eat?” Use cuisines only when the question is “What kind of food should we choose?” Mixing a cuisine such as Thai with a specific venue such as Corner Café makes the result ambiguous.
If the group has not chosen a shortlist of venues, run a cuisine round first. After selecting a cuisine, stop the Wheel and find restaurants that satisfy the group’s real constraints. Do not treat the first round as evidence that any nearby restaurant in that category is safe or suitable.
Keep labels short enough to read on a phone or shared screen. When two places have the same name, add a neighborhood or suburb. Do not paste addresses, order details, loyalty numbers, phone numbers, allergy records, or other personal information into an Entry.
Use this five-minute restaurant rule
The simplest routine is filter, shortlist, confirm, select, and verify. Agreeing to the rule before the Selection prevents the Wheel from becoming a performance that continues until the host gets a preferred answer.
- Filter for dietary, allergy, accessibility, budget, distance, time, availability, and reservation requirements using current first-party restaurant information.
- Shortlist only places everyone affected says they could accept tonight.
- Enter each distinct restaurant once, remove duplicates, and read the list back to the group.
- Agree to honor the first Selection unless the shortlist contains a genuine factual or setup error.
- Select once, then verify the final practical details and make the booking or order.
Equal chances, weighting, and vetoes
One Entry per restaurant gives every listed place the same chance. Adding the same restaurant several times weights the result toward that place. Randomly does not present duplicate Entries as a formal weighting system, so use one Entry per place for a transparent group choice.
Resolve vetoes before the Selection. A person does not need to justify a private medical or accessibility detail to the room, but the facilitator should remove an unacceptable venue. A “veto after the spin” rule invites strategic re-spins and makes the process feel less fair.
Preferences are different from constraints. If everyone can accept all five places but two people strongly prefer one, decide openly whether equal chances are still the rule. Do not hide that preference by quietly duplicating an Entry.
What to do when the selected place does not work
Pause when new information makes the selected restaurant unavailable or unsuitable. Explain the factual problem, correct the whole shortlist, and begin a new Selection. Do not call an ordinary disappointment a setup error.
A restaurant closing early, losing a reservation, exceeding the agreed budget, or being unable to meet a confirmed access requirement can justify rebuilding the list. The group should apply the same rule no matter which restaurant was selected.
If the result reveals that someone never accepted the venue, the useful outcome is the newly stated preference. Discuss it directly. A Wheel can break a tie among acceptable options, but it cannot manufacture agreement or take responsibility for the consequences.
Use the Wheel on a shared screen
Prepare the shortlist before screen sharing, switch to Presentation Mode, and repeat the selected restaurant aloud. The large visual reveal can make a small group decision feel conclusive without asking anyone to click an advertisement or interact with anything except the Tool.
A Shared Setup can carry the list in the URL fragment, which is not sent to the Randomly server as part of the page request. Anyone with the complete link can still read its Entries, so use ordinary restaurant labels and share the link deliberately.
For a recurring lunch group, save a clean local list and review it each time. Restaurants change hours, menus, prices, access arrangements, and ownership. A saved Entry is a convenience, not a current recommendation or verification.
Related Randomly guidance
Read how Randomly handles fairness and browser randomness, review the privacy approach, or choose a practical starting point from the Template library. Continue with everyday decision Tools.
Quick answers
Frequently asked questions
How do I make a random restaurant picker?
Confirm the group’s requirements, make a shortlist of restaurants that satisfy them, enter each place once in the Wheel, agree to the correction rule, and make one Selection. Verify current restaurant details before booking or ordering.
Does Randomly find restaurants near me?
No. Randomly selects from the Entries you type. It does not use your location, search restaurant databases, check menus, verify allergy safety, or confirm opening hours and reservations.
Should everyone get a restaurant veto?
Remove any place that fails a real requirement or that an affected person cannot accept before the Selection. Agree on that shortlist openly rather than allowing strategic vetoes only after a result appears.