The 80% consensus rule: why majority-vote group decisions break trips

Quick answer: majority vote (51%) is the wrong rule for group trips because the losers can't walk away — they're on the same flight. Use 80% as the threshold for activities and restaurants; below 50% retires the idea silently. Before any vote, define three things: quorum (75% of crew, 72-hour window), neutral weight (counts as nothing, not half), and veto rights (non-negotiables only — allergies, accessibility, religion). Use 50% for dates and flights, not 80% — flight prices move.

The argument always starts the same way. Someone proposes a restaurant. Three people thumbs-up it. One person says "I mean, sure, I'd go." Another person doesn't reply. By Wednesday it's a 90-minute group chat thread about whether "sure" counts as a yes, whether the silent person gets a vote, and whether the original proposer should propose somewhere else "to be fair."

This is what happens when you don't have a consensus rule.

This piece is short and explicit because the rule is short and explicit. 80% lands a decision. Below 50% retires it quietly. Between is for one round of conversation, not three. And before any of that, you write down three things — quorum, neutral weight, and veto rights — so no-one can re-litigate the rule mid-vote.

Why is majority vote the wrong rule for group trips?

Majority vote — 51% wins — works in democracies, juries, and friend groups deciding between two bars. It does not work for group trips because the structure is wrong:

• The decisions aren't binary. You're not picking between two restaurants; you're picking from twelve.
• The minority can't walk away. They're booked on the same flight as the majority.
• The decisions compound. Three majority-wins-in-a-row leaves the same group of friends consistently outvoted on every choice. By day three, they're a passenger on someone else's trip.

The unpaid PM's instinct — "let's just put it to a vote" — is what creates the silently resentful traveller. The fix isn't to vote less. It's to set a higher bar.

The 80% rule, in one line

An idea lands on the day if it gets thumbs-up from everyone who voted, with at most one neutral and no thumbs-down — or, more crudely, an 80% approval rate across the engaged crew.

That's it. Below the threshold, the idea goes to a shortlist for one more round. Below 50%, it's retired silently — no second debate. The PM doesn't relitigate; the workspace just moves on.

The number matters less than the existence of a number. Some groups use 75%. Some use a flat "no thumbs-down" rule. Whatever you pick, write it down before the first vote.

The three things to define before voting starts

People disagree about rules less when the rules were set before the stakes were known. Define these on day one of the trip's planning, ideally in a pinned message in the workspace.

1. Quorum

How many people have to vote for the result to count?

• Too low: a 2-of-4 vote becomes a "decision" while half the group missed it. Resentment.
• Too high: every vote stalls waiting for the friend who hasn't opened the app since Tuesday.

Workable: 75% of the crew, within 72 hours of the vote going up. On a 4-person trip, 3 votes is enough. On a 6-person trip, 5. Anyone silent at the deadline opts into whatever the voted majority decided.

2. Neutral weight

What does a 🤷 mean? You'd be amazed how much trouble this causes.

• Counts as a yes: the bar to land an idea is much lower. Conflict-avoidant friends end up implicitly approving things they didn't want.
• Counts as a no: every neutral is effectively a veto. Few ideas pass.
• Counts as half: clean but mathematically annoying.
• Counts as nothing — the idea must clear 80% of the votes that aren't neutral. This is the rule we use. A 3-yes, 1-neutral vote is "100% of engaged voters approved" → lands.

Pick one, write it down. Don't decide mid-vote.

3. Veto rights

Can any one person kill any idea?

For group trips, vetoes exist — but only for non-negotiables:

• Dietary needs (allergies, religious requirements, medical)
• Accessibility (mobility, sensory, mental health)
• Hard "no" categories agreed in advance (e.g. one person hates haunted-house tours; they say so before the trip; "haunted-house tour" is on their veto list)

"I don't like ramen" is a downvote. "I'm coeliac" is a veto. Make the categories explicit so vetoes don't get inflation-pressured into "I just don't feel like it." If everyone with a veto has agreed it's only for the listed categories, you can challenge a stretched veto politely — "is this on your list?" — without it being personal.

What this rule actually changes

People wildly underestimate the social load of a single un-named vote.

Without the rule, every 3-yes-1-meh vote becomes a re-litigation: should we go anyway? Are we ignoring her? Should I propose somewhere else to make it up? That happens in a chat, in real time, while the proposer feels bad for having floated the idea.

With the rule:

• The vote either passes the threshold or doesn't. No ambiguity.
• The "meh" voter doesn't feel singled out — the rule didn't ask them to elaborate.
• The proposer isn't punished for proposing.
• The PM doesn't have to be the heavy.
• The group moves on faster.

A trip-planning workspace can run a dozen votes in a week without anyone feeling outvoted, because the rule was set, applied, and the outcome was procedural rather than personal. That is the single biggest delta between a group trip that ends well and one that ends in three angry texts.

When 80% is the wrong rule

A few cases where consensus thresholds aren't the right tool:

• Dates, flights, and any logistics where prices move. Use the 50% rule from the main planning manual — lock the moment half the crew confirms. Waiting for 80% costs hundreds of dollars in flight inflation.
• Decisions that need a single decider. Restaurant reservations the night-of. Driver pick. Designated drinker-checker. Some calls need a human to just call it, not a vote.
• Trips with one obvious local. If you're going to my home town, I'm not voting on the bagel place. I'm telling you. Defer to expertise when it exists; vote on the rest.

A consensus rule isn't a substitute for judgment. It's a substitute for repeated low-stakes arguments.

The shortest version

If you only take three things from this:

1. Use 80% as the bar for activities, ideas, and restaurants. Below 50%, retire it. Between, one more round.
2. Define quorum (75%, 72 hours), neutral weight (count as nothing), and veto rights (non-negotiables only) before the first vote.
3. Use 50% for dates, not 80%. Different decisions need different thresholds.

Where this fits

The 80% rule is one piece of the larger system in the planning manual — decisions in a workspace, feelings in a chat. The threshold matters because it stops votes from leaking back into feelings. The workspace counts the thumbs-up; the chat doesn't have to.

Wendir's idea board enforces the rule by default: vote in the workspace, the threshold is enforced procedurally, the conversation in the chat stays a conversation. It's currently iOS-only, in closed beta. Join the waitlist if you want an invite.

Or use any tool that lets you define the rule and stick to it. The tool matters less than the rule.

More from the Group Trip Operating Manual

• How to plan a group trip without becoming the unpaid PM — the larger system this rule fits inside.
• How to split travel expenses when one person fronted everything — the math behind the most-disputed votes.
• The 4 roles every group trip needs — the rule works better when each role is named.

---

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