Who Pays for Dinner — Two-Wheel Guide

Why two wheels for dinner decisions?

Friend groups rarely stall on one question. They stall on two: where are we eating, and who covers the check? A single generic decision wheel forces you to merge those jobs — paste restaurants and friend names on the same circle, spin once, and land on "Alex" when you needed "Thai food." The fix is two separate spins with two clear labels: wheel one picks the restaurant, wheel two picks the payer.

Name Spinner does not ship multi-wheel sync in one product view yet. This guide uses two embeds in sequence — the same pattern you would run on two phones or two browser tabs at the table. Spin restaurant options first; commit to the meal; then spin payer names. Both wheels use crypto-backed fair picks and run free in the browser.

If you only need the payer spin, read who pays the bill spinner. If you only need cuisine type, try what to eat spinner or restaurant roulette wheel. This page is for groups that want both decisions settled in one ritual.

Step one — lock the restaurant

Before you spin: Remove closed venues, places someone cannot eat (allergies, dietary rules), and options outside tonight's budget. One spin = one restaurant — no re-spin because someone wanted tacos unless everyone agreed on a mulligan rule upfront.

Display the spin on a shared phone in the center of the table. Secret spins invite "you rigged it" jokes even among friends. Screenshot the result when your group uses Venmo later — same habit as logging who paid last week.

Hybrid planning: Send the homepage link with your real restaurant list before anyone leaves work. By the time you meet, wheel one is pre-loaded; you only spin payer names after menus arrive.

Fast food vs sit-down: Use the demo meal types below for broad categories, or paste specific chains from the restaurant roulette template on the homepage when the group wants "Chipotle" not "Mexican."

Step two — spin who pays for dinner

After the group commits to the restaurant choice, open the payer wheel. Remove anyone not at the table, anyone who paid last outing (if you track rotation manually), and the birthday guest when the social contract says they eat free. Define tip and tax before the spin — does the winner cover everything including gratuity, or only entrees?

Two embeds, one flow: You do not need a special product feature — two tabs or two sequential scrolls on this page work. Build both lists on the Name Spinner homepage, save two share links labeled "Dinner — where" and "Dinner — who pays," and bookmark them for your regular crew.

Building both lists on the homepage

Restaurant wheel: Paste specific restaurant names when the group always chooses among the same six spots. Paste cuisines when you want broader variety. Payer wheel: First names only unless duplicates force last initials.

Weighted tickets: Name Spinner supports per-name weights on the homepage when one person volunteered for double odds because they missed last three outings — use sparingly and announce weights aloud.

Compassionate groups: Skip the payer spin when someone is explicitly budgeting this month — remove their name without debate, or cover them as a group decision before randomness starts. Randomness serves friendship when everyone can absorb a typical meal cost.

When two wheels are overkill

Same restaurant every Friday: Drop wheel one; only spin payers. Venue already booked: Jump straight to payer wheel. Solo diner: Neither wheel applies — use yes or no wheel for dessert instead.

Itemized split meals: When the social contract is forensic accounting per dish, apps that divide line items beat "one person treats." Use payer wheels when the norm is rotation, not spreadsheet precision.

Linking to other decision spinners

Still arguing about appetizers after both spins? Yes or no wheel for shared plates. Chore rotation the next morning? Chore picker wheel. Weekend recovery: Weekend activity spinner when dinner leads to plans.

Common questions

Do I need two devices? No — one phone, two spins in sequence, or two browser tabs from the same homepage links.

Is spin order rigged if payer wheel is second? Restaurant choice does not affect payer odds — independent lists, independent crypto-backed spins.

Can both wheels share one link? URL codec holds one list. Use two links or re-paste between spins on the homepage.

Fairness details? Read how fair is a random name picker — same engine for names and meal labels.

Sample Friday night script

Read aloud while friends watch: "First spin picks cuisine — we eat there unless someone has a veto we agreed on pre-spin. Second spin picks who pays entrees; tip split by headcount." Following the script prevents retroactive rule invention when the wheel lands on sushi and the usual payer is broke this week.

Document in chat: Post both screenshots with caption "June outing — locked" so the social ledger survives memory gaps. Next week: Same links, edit restaurant list if one place closed, keep payer rotation transparent.

Corporate and team dinner variants

When the company card pays, label the payer wheel "who submits the expense report" — random admin duty, not personal hundreds out of pocket. Client dinners skip payer wheel entirely; use wheel one for cuisine negotiation only. Intern welcome meals: Spin cuisine publicly, manager pays by policy — announce before spinning so randomness applies only to food choice.