Group trips don't die because people stop wanting to go. They die at the dates stage, months before anyone argues about Airbnbs. Someone says "we should do a weekend away", everyone agrees enthusiastically, someone asks "when works?", and the thread produces four maybes, two conflicting preferences and a "let me check with work". Then it goes quiet forever.
I've watched this happen to my own friend groups repeatedly, and the fix turned out to be less about tools and more about doing the decisions in the right order. Here's the method, tool-agnostic first, with the shortcuts at the end.
Why trip dates are so much harder than dinner dates
Three reasons. First, the ask is bigger: a weekend costs annual leave, money and family negotiation, so people genuinely need to check before answering. Second, the search space is huge: "sometime in autumn" is ninety days, and no one wants to type out ninety opinions. Third, commitment is asymmetric - the person who books flights first carries all the risk, so everyone waits for someone else to commit first, and nobody does.
A group chat makes all three worse, because every partial answer scrolls away and the state of play lives in nobody's head.
Step 1: Decide who's deciding
Trips need an owner. Not a boss - just the person who will actually call it. Groups that skip this step orbit politely forever because no one feels entitled to say "right, it's the 14th". If you started the thread, congratulations, it's you.
Step 2: Narrow the window before you ask anyone anything
Do not ask "when is everyone free?" against an open horizon. The owner should unilaterally cut the space down: "a long weekend in September or October" is a good ask; "sometime this year" is not. People can hold sixty days in their head next to their calendar. They cannot hold three hundred and sixty-five.
Step 3: Collect availability as data, not conversation
This is where trips die, so treat it mechanically. You want, from each person, the days in the window they could travel - collected somewhere that doesn't scroll away. A shared spreadsheet works. A poll works. (Happening was built for exactly this: share one link, friends tap the days they can do, nobody needs an account - and you see the counts per date instead of a pile of messages.) Whatever you use, the rule is the same: answers go into the tool, chat stays for jokes.
Give it a deadline. "Mark your days by Sunday night" converts politeness-procrastination into action, and it gives the owner permission for step 4.
Step 4: Pick the best date, not the perfect one
With any group bigger than four, some weekend will work for everyone maybe a third of the time. The rest of the time, the real decision is "the 14th works for six of seven - do we go without Priya, or move to a worse-but-complete weekend?" That's a values call only a human can make, and it's the owner's call to make quickly. A trip that happens with six people beats a perfect trip that never happens with seven. (If someone's presence is the point - it's their birthday, it's their stag - weight accordingly. Happening lets a host mark up to three must-attend people for exactly this.)
Step 5: Announce, then book something non-refundable
Announce the date as a decision, not a suggestion: "We're going 14th-16th. Flights are £60 right now." Then the owner books their own travel and says so. Nothing converts a plan into a real trip like one person being financially committed. Everyone else books within the week; it's social physics.
The 48-hour version
- Friday: owner picks the window, sends one link, sets a Sunday deadline.
- Weekend: friends tap their available days - thirty seconds each, on their phones.
- Sunday night: owner looks at the ranked dates, picks the winner, announces it, books their travel.
Two days from "we should do a trip" to a date in everyone's calendar. The group chat stays for the important stuff, like arguing about who has to share the sofa bed.