Tokyo for friends with three different food tolerances

Quick answer: for groups with mixed dietary restrictions (vegetarian, coeliac, allergies) in Tokyo, pick a food-decider before booking flights — give them veto rights on every restaurant. Stay on the Shibuya/Harajuku/Omotesando spine (highest density of vegetarian + gluten-conscious options). Book the two hardest meals from home (one safe group dinner + one tourist-district lunch). Carry laminated Japanese allergy cards. Use split-and-converge days — don't force all meals together.

The hardest part of planning Tokyo with a mixed group isn't the language. It isn't the booking. It isn't even the prices.

It's the moment, on day two, when one of you realises the only place open within walking distance has bonito flakes in the broth, soy sauce on everything, and shellfish in the dashi — and the rest of you are starving.

This piece is for groups where at least one person has a non-trivial dietary restriction. Vegetarian. Vegan. Coeliac. Shellfish allergy. Whatever the constraint, the answer is the same: planning has to happen before the trip, not at the restaurant door.

The template here is the same as the Kyoto planning doc — pick the shape, name the roles, vote on the candidates, book the fixed points. The difference is one extra rule and one extra role.

The crew (same as Kyoto, different constraints)

For continuity, let's say it's the same four-person crew from the Kyoto trip — but this time we're going to Tokyo and the constraints are sharper:

• A — pescatarian, no allergies.
• B — coeliac (genuine; not a preference). Soy sauce is the silent villain.
• C — strict vegetarian (no fish, no dashi). Veganism would be even harder; vegetarian is the workable case.
• D — shellfish allergy (anaphylaxis-grade). One trace of prawn ends the trip.

Realistic mix. The kind of group most people are part of without realising.

The extra role: the food-decider

The four roles all still apply. But for a trip with multiple food restrictions, one of those four people also takes on the food-decider role. Their job:

• Vet every dinner booking against everyone's restrictions before it goes to a vote.
• Maintain the shortlist of restaurants known to be safe for the whole group.
• Carry the allergy cards (in Japanese) — one per restriction.
• Veto a place that seems risky, even if it would be popular otherwise.

This is delegated authority. You're explicitly saying the food-decider's veto on a restaurant is final, because the cost of being wrong is too high. They don't have to argue.

In our Kyoto trip, this role was loose — the local handled it informally. For Tokyo with anaphylaxis-grade allergies and a coeliac, it has to be explicit.

Pick the food-decider before booking flights. Not before booking dinner. Before the trip exists.

The neighbourhood logic for mixed needs

Like Kyoto, the neighbourhood matters more for transit than aesthetics — but in Tokyo, mixed-needs groups also need to think about which districts have the right restaurant density.

The pattern:

• Shibuya / Harajuku / Omotesando spine — highest density of vegetarian, vegan, and gluten-conscious places. Western expat influence, modern Tokyo café culture. Easy to find safe options.
• Ebisu — has emerged as Tokyo's gluten-free ramen district. Multiple dedicated spots. Worth a dinner pilgrimage if you have a coeliac in the group.
• Daikanyama / Nakameguro — adjacent to the Shibuya spine. Higher-end, slower-paced, plenty of mixed-cuisine cafés.
• Shinjuku — works, but you have to know specific places. The neighbourhood is too dense to "wander into something safe."
• Asakusa — postcard Tokyo, but harder for restrictions. Traditional places, fewer accommodations for special needs. Visit in the day for the temple; eat elsewhere.

The accommodation rule: stay within 10 minutes' walk of a station that gets you to the Shibuya spine in under 20 minutes. This gives you the "safe restaurant" district at arm's length without insisting you eat there every meal.

We picked an Airbnb in Daikanyama — quieter than Shibuya, walkable to it, A$210/night for a 4-bed apartment.

The booking strategy

For Kyoto, we made one rule: book one nice dinner from home, treat it as a fixed point. For Tokyo with restrictions, the rule expands:

Book the two hardest meals from home, leave the rest flexible.

The "two hardest" are:

1. The one safe-for-everyone group dinner. Probably ¥10,000–15,000 per person. Worth the booking. Worth the splurge.
2. One safe lunch in a tourist district. Where the alternative options are limited or risky. Asakusa is the classic case — if you want to visit the Senso-ji temple, you need a planned lunch nearby, not a "we'll figure it out."

Everything else stays flexible — breakfast at the apartment, lunches on your own schedule, dinners with one of two pre-vetted backups if the booking falls through.

The actual day structure

Two specific examples — Day 1 and Day 3 of a 4-day trip — to show how mixed-dietary scheduling actually works.

Day 1 (arrival, Shibuya, all-safe)

Time	Stop	Note
14:00	Airport → apartment, drop bags	Narita Express, 90 min
16:30	Shibuya wander, coffee	Loose group time. Everyone re-orients.
18:00	Group dinner — booked from home	Vegetarian shojin-ryori or similar safe-for-all.
21:00	Walk back, sleep	Light first night.

The Day 1 dinner is the icebreaker dinner for a mixed-needs crew. Everyone eats at the same place, everyone's restrictions are pre-cleared, nobody is stressed. Sets the tone.

Day 3 (split-and-converge day)

Time	Group?	Stop	Note
09:00	Together	Breakfast at apartment / nearby café	Easy.
10:30	Together	Asakusa, Senso-ji temple	Visit only — eat later.
12:00	Together	Booked safe lunch in Asakusa	Pre-vetted by food-decider.
13:30	Split	Individual afternoon	A → Tsukiji outer market (fish). B → gluten-free ramen in Ebisu. C → Yanaka café crawl. D → museum (shellfish-free).
18:00	Reconverge	Shibuya spine	Drinks, walk-in dinner at one of the pre-vetted backups.

The split afternoon is the single biggest unlock for mixed-needs groups. Trying to find a single museum/shop/lunch combo that works for all four restrictions in one walking distance is exhausting. Splitting for 4 hours and reconverging for dinner is the cheat code. Everyone gets what they want; no-one has to compromise the whole day.

The food-decider's pre-trip checklist

If you've been delegated the food-decider role, the work happens before the trip:

1. Get the allergy cards translated into Japanese. One per person with restrictions. Laminated. Carry copies.
2. Build a Google Maps list of pre-vetted places. Aim for 8-10. Each one cross-checked against everyone's restrictions, with notes ("safe for coeliac, vegetarian options, no shellfish in kitchen").
3. Book the two hardest meals at least 2-3 weeks ahead.
4. Identify 2-3 walk-in backups in each likely neighbourhood. These are restaurants you've vetted but not booked — they're the "if-the-plan-breaks" fallback.
5. Read each booking's reply email carefully. Some places, when you ask about restrictions, will pre-prepare alternatives. Others will silently downgrade your meal. The reply tells you which.
6. Carry a power bank and a translation app. Both. The food-decider is also the de facto translator at restaurant doors when something unexpected comes up.

This is maybe 4-6 hours of pre-trip work. It saves the trip.

What we'd do differently (and what worked)

For a 4-day Tokyo trip with this constraint profile:

Worked:

• Booking the two hardest meals from home — both delivered.
• Daikanyama as base — every Shibuya-spine option was 10-15 min walk.
• Split afternoons (Day 2 and Day 3) — everyone got the day they wanted.
• The food-decider role being explicit. C had veto authority on a place A wanted to try; A accepted it. Without the explicit role, that would have been an argument.

Would change:

• Booked three hard meals from home, not two. We had one walk-in dinner that took 35 minutes to find a place safe for B (coeliac). On a tired night, that's brutal.
• Added a third pre-vetted backup per neighbourhood. We had two; one was closed.
• Got the allergy cards earlier. D's shellfish card was a printout we did the night before flying. Should have been laminated, in a wallet, weeks ago.

The math (briefly)

Same shape as the Kyoto piece — log expenses as they happen, settle once at trip-end using debt simplification. For Tokyo with restrictions, one specific tweak: the food-decider doesn't pay more than anyone else. The role is service to the group, not a cost. If they end up eating somewhere expensive because of the constraints (e.g. specialised vegan kaiseki at ¥18,000pp), that gets equal-split — everyone pays for the privilege of safe-for-all dining, not just the person whose restrictions drove the choice.

This is a social contract point. Write it down before the trip.

The template, abstracted

Strip Tokyo and what remains is a planning template for any destination with a mixed-restriction group:

1. Pick the food-decider before flights. Delegated veto on restaurants.
2. Choose accommodation by restaurant-district proximity, not just transit.
3. Book the two hardest meals from home. Group dinner + one tourist-district lunch.
4. Build a vetted shortlist + 2-3 backups per neighbourhood.
5. Carry translated allergy cards. Laminated. Per restriction.
6. Split-and-converge days. Don't try to find one venue that works for everyone every meal.
7. The constraint-driven cost gets equal-split. Always.

Works for Tokyo. Works for Lisbon (vegetarian and coeliac in a meat-and-bread-heavy country). Works for Mexico City (allergens are different but the framework is the same).

Where this fits

This is the second Destination Deep-Read, deliberately pitched on the hardest variant — mixed restrictions. The next two destination pieces (Sydney hens, Mexico City for non-Spanish-speakers) will use the same template with different complications.

The Manual pieces this trip ran on:

• The main planning manual
• The 4 roles (plus the optional food-decider role on top)
• The 80% consensus rule — note: the food-decider's veto is the exception that proves the rule. Some calls aren't votes.
• How to split travel expenses
• Group chat tooling

Wendir's Local agent is built for exactly this verification job — cross-checking a place against constraints, hours, and recent reviews — but a human food-decider is still the right call when allergies are anaphylaxis-grade. We don't want an LLM having final say on whether prawn appears in a kitchen. Closed beta, iOS-first.

More from the Destination Deep-Reads

• Kyoto in 3 days for 4 people: the real planning doc — the format template.
• Sydney long-weekend for a hens — the spreadsheet that worked — coming next.
• Mexico City for 5 people, 4 days, no Spanish — later in the year.

---

Written by the Wendir team. Last updated: 15 May 2026.