The 4 roles every group trip needs (and the one that's always missing)

Quick answer: every group trip needs four roles filled — decider (breaks ties, enforces decision rules), scout (surfaces ideas from links), local (verifies against ground truth), treasurer (tracks expenses and runs settlement). One person can hold two roles; nobody should hold three. The role groups always forget is the decider — it's invisible work, looks bossy, feels arbitrary. Name it on day one anyway. Without one, every vote gets relitigated.

Every group trip has the same four people. Sometimes they're four different humans. Often, they're one person wearing four hats and slowly losing their mind by day six of planning.

You can't avoid these roles. You can only choose whether they're held by different people or by the same exhausted person.

This piece names the four roles, says what each one actually does, and tells you which one your group is almost certainly failing to fill — because in the early beta crews of 4–9 people we've tested with, the most common gap by a wide margin has been the same one: the decider.

The four roles

1. The decider

Job: breaks ties. Enforces the decision rule the group set up front (e.g. the 80% consensus rule). Calls things when calling is needed.

Not: the planner. Not the PM. The decider's whole job is to unblock — they don't propose ideas, they don't track expenses, they don't book anything. They just resolve the moments when the group is stuck on something for the third time.

Who's good at this role: the quietly opinionated friend. The one who doesn't volunteer first but whose judgment everyone secretly trusts. Often not the loudest in the chat.

Who's wrong for it: the friend who wants everyone to be happy. They'll refuse to call ties to avoid disappointing anyone, and the group will stall.

This is the role groups forget to fill. Because there's no obvious task, nobody volunteers — and yet without one, every disagreement turns into an open thread. "Should we do X or Y?" becomes a forty-message debate when it could have been a thirty-second call.

2. The scout

Job: surfaces ideas. Sends the TikToks, the Maps pins, the Reddit threads, the friend-of-friend recommendations. Builds the shortlist.

Not: booking, voting on their own ideas with extra weight, or insisting on inclusion. A scout proposes; the group disposes.

Who's good at this role: the friend with the algorithm. They saw the place on Instagram in February. They've been quietly bookmarking the destination for months. Their phone is full of screenshots.

Who's wrong for it: the friend who only weighs in once a week. Scouting is a continuous job — you need someone surfacing fresh ideas as planning progresses, not a one-off "here's a list" three weeks out.

This role is rarely missing — there's almost always someone who naturally scouts. The trouble starts when the scout also becomes the decider, because they start lobbying for their own ideas. That's why the two roles should be different people.

3. The local

Job: verifies. Has been to the destination, knows someone who has, or has done enough research to function as the institutional knowledge. Vetoes the things that look good on TikTok but won't work — wrong neighbourhood, closed Tuesdays, 90 minutes from where the group will actually be.

Not: the decider. The local has expertise; that doesn't mean they get final say on activities outside their expertise.

Who's good at this role: the friend who lived there, or who has a cousin who did, or who reads /r/travel on their lunch breaks. The point isn't credentials — it's caring enough about ground-truth to push back on plausible-sounding bad ideas.

Who's wrong for it: the friend who's confident but hasn't done the homework. False confidence is worse than no expertise, because it gets things vetoed that shouldn't be and approved that shouldn't be.

If no-one in the group has been to the destination, the local role gets distributed across whatever sources you have — a friend who's been, a guide you trust, a chatbot you've cross-checked. The role still exists; it just doesn't have a single owner.

4. The treasurer

The treasurer is the role that quietly determines whether your group will travel together again.

Their job is small — log expenses as they happen, settle once at trip-end, post the simplified transfer list. But the consequences are large: a treasurer who avoids friction will let a balance go unpaid for six weeks, and by week seven, two friends aren't speaking. A treasurer who's pedantic without warmth will turn every receipt into an audit, and the trip starts feeling like a tax return.

So the treasurer needs an unusual mix: calm enough to be ignored when they ask once, comfortable enough with friction to ask twice. Not the conflict-avoidant friend (the chase doesn't happen). Not the friend who'll take a missed payment personally (the chase happens, but it's hostile).

Two firm rules: the treasurer should never also be fronting the money — that compounds the social contract into something most friendships can't carry. And the treasurer should use a tool that does the math automatically (Splitwise, Wendir's Moneybags agent), because their actual value isn't arithmetic — it's owning the human side. Deciding whether a custom split is fair. Reminding the friend who hasn't paid without making it weird. The tool handles the spreadsheet; the human handles the friendship.

If both fronting and treasuring fall to the same person, read the expense fronting piece before booking anything else.

The math on combinations

There are four roles and roughly n people. The combinatorial reality:

• n = 4: ideal — one role per person, no overlap. Each person owns one piece and can rest from the others.
• n = 3: unavoidable doubling. One person holds two roles. Pick the least conflicting doubling: scout + local works (both about ideas + ground truth), treasurer + decider works (both about enforcement), but scout + decider is asking for trouble.
• n = 2: not really a group trip; the framework's overkill. Just communicate.
• n = 5 or 6: add a deputy scout. Don't add a deputy decider — having two deciders is the same as having none.
• n = 7+: you're at the size where a single trip splits into sub-groups for activities. Each sub-group needs its own scout + local, but the trip still has one treasurer and one decider for whole-group calls.

The hard rule: no one person holds more than two roles. The moment someone is decider + scout + local, you're back in unpaid PM territory and the system has already failed.

Why does nobody volunteer to be the decider?

In every group we've worked with, the decider is the role that ends up unassigned. Here's why:

• It's invisible. The scout shows their work (here are ten places!). The local shows their work (this one's closed Tuesdays!). The treasurer shows their work (here's the math!). The decider's work is not having a 90-minute debate — which leaves no artefact and feels like doing nothing.
• It looks bossy. Nobody wants to be "the one who decides," because in a friend group that reads as a power move.
• It feels arbitrary. People assume good calls require expertise; deciding doesn't, so people assume it doesn't need to be anyone's job.

All three are wrong. The decider's job is the highest-leverage of the four — without it, the others can't function. The scout proposes infinitely if nothing ever lands. The local vetoes infinitely if nothing ever ships. The treasurer logs an infinite expense list if no plan ever gets executed.

Name the decider on day one. It doesn't have to be a power move. It can be: "I'll call ties this trip — if you don't like a call, push back once and we'll re-vote; otherwise we move on." That's it. Quiet, low-key, totally functional.

How to assign the roles

The five-minute version, in the planning workspace:

1. Post the four roles with one-line descriptions.
2. Ask everyone to claim one (and at most one). Whoever doesn't claim gets assigned by the group.
3. If two people claim the same role, the decider role (already filled by whoever's hosting this conversation, often by accident) decides. Mildly recursive but functional.
4. Write the names + roles into the workspace header so they're visible all trip.
5. Anyone can swap with consent. Once a trip, not three times.

This takes less time than the average group's argument about restaurants. It saves the trip.

The counter-take

There's a harder case where this framework backfires: groups where the trust is already thin.

Naming a decider in a friend group with smouldering resentments doesn't prevent conflict — it surfaces it. Now there's a person whose calls can be objected to as "well, of course they decided that." The role becomes the lightning rod. Same for treasurer: someone who already feels they're carrying the friendship will read "you're tracking the spreadsheet" as further unpaid emotional labour. If the underlying relationship work hasn't been done, the framework gives the resentment a new shape rather than a solution.

For experienced, high-trust groups, the answer is simpler: skip the formal step. Travelled together six times? Your roles are deeply implicit and naming them feels insulting. "Of course I'm the local for Tokyo, why are we even having this conversation." Just go.

The framework matters most for: first-time-together crews, mixed travel styles, 5+ people who haven't all travelled together. Not for groups where the issue isn't role distribution but trust.

The shortest version

If you only take three things from this:

1. Four roles: decider, scout, local, treasurer. Name them on day one.
2. No-one holds more than two. If someone is, redistribute or shrink the trip.
3. The decider is the role groups forget. Name it explicitly even if it feels low-status — without it, every vote gets relitigated.

Where this fits

This piece is the team-shape complement to the main planning manual. The manual sets up the system; the four roles distribute the load. The 80% consensus rule is what the decider enforces. The expense fronting piece is what the treasurer owns.

Wendir's seven specialist agents are roughly mapped to the human roles: Scout proposes places from links, Local verifies, Moneybags runs the treasurer's math. The decider role stays human — for good reason. Some calls shouldn't be automated. iOS-first, closed beta. Waitlist.

More from the Group Trip Operating Manual

• How to plan a group trip without becoming the unpaid PM — the system the roles plug into.
• The 80% consensus rule — what the decider enforces.
• How to split travel expenses when one person fronted everything — what the treasurer owns.
• Group trip Slack vs WhatsApp vs Discord — what actually works — workspace vs chat, tested.

---

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