Booking a group trip without one martyr
In most groups, one person does about 90% of the work of organising the trip. Everyone knows who it is. Often it is the person reading this.
The usual explanation is that the others are lazy. That explanation is wrong, and it is worth abandoning early, because it leads to the wrong fix — nagging, sighing, and eventually a pointed message about how nobody helps.
The real reason is that the work is invisible and unassignable. Nobody can volunteer for a task they cannot see the shape of. So fix the structure, not the people.
What counts as a task
“Someone should sort the cars” is not a task. It is an observation that a problem exists. It cannot be completed, refused, chased or ticked off.
“Book the two hire cars for the 14th, by 30 April — Sam” is a task.
A task needs exactly three things:
- A verb. Book, confirm, pay, choose, ring. Something with an end state. “Look into” is not a verb for these purposes; it is a way of agreeing to nothing.
- A deadline. An actual date.
- Exactly one name. Not two. Two people own nothing.
Write the trip down as a list of things in that form, before you write anything else. Ten to twenty tasks is normal for a week away with eight people. Seeing the list is half the work — most groups have never seen it, which is precisely why they assume it is small.
Deadlines need reasons
An arbitrary deadline does not get met. A deadline with a cause behind it does.
“Book the flights by 1 May” invites negotiation. “Book the flights by 1 May, because the low fare bucket on that route usually goes around then” does not, because there is nothing to negotiate with. The date belongs to the world, not to the person who set it.
Real reasons are easy to find. Prices step up. The ferry sells out in June. The attraction releases tickets 90 days ahead. The villa’s free-cancellation window closes. The deposit is due. Attach one to every date, and if you genuinely cannot find a reason, consider whether the task needs a deadline at all.
Let people claim, then assign the rest
Publish the list. Let people pick.
Volunteering is markedly more reliable than allocation, because someone who chose the restaurants has an opinion about restaurants and will actually enjoy doing it. Someone assigned the restaurants has a chore.
What is left over after claiming is always smaller than you feared, and small enough to hand out without anyone feeling put upon. Assign it directly and by name — “Priya, can you take the airport transfers?” — rather than posting it back to the group and hoping.
Give the claiming a window. Twenty-four hours in a chat is enough. Beyond that people stop reading.
The order things have to happen in
The commonest planning failure is booking something non-refundable before the dates are fixed. It is expensive and entirely avoidable, and the fix is to work down a spine.
- Dates. Nothing can be priced until these are settled. Settle them first, settle them properly, and stop discussing them.
- Accommodation. It is the largest sum, the most constrained supply for groups, and it determines where everything else has to be.
- Long-haul transport. Flights, long trains, the car ferry. These fix arrival and departure times.
- Internal transport. Hire cars, local trains, island ferries, transfers. These depend on the arrival times you have just fixed.
- Timed tickets. Attractions with release windows and hard sell-outs.
- Restaurants. Last, and closest in, because they are the most changeable and the easiest to move.
Some things jump the queue. If a specific attraction is the reason for the trip, and it releases tickets 90 days out, that ticket may have to be booked before the flights. Say so explicitly, so nobody thinks the spine has broken.
Decisions and bookings are different things
Groups conflate these constantly, and it is why settled questions keep reopening.
A decision is collective. Which island, which week, hotel or villa, hire cars or trains. A group can vote, and a vote can be a straight majority, a ranked list or a simple veto count. Whatever you use, run it once and announce the result.
A booking is individual. It requires one person, one card, one confirmation email. It is an execution step, not a discussion.
Once a decision is made, the booking that follows is not an invitation to reopen it. If somebody wants to reopen it, that is a new decision with a new vote, and it needs to happen before the person with the card is standing at the checkout with a held rate expiring.
The non-responder, and the default
There is always someone who does not reply. Usually they are not being difficult; they are waiting for the conversation to resolve so they do not have to have an opinion.
The structural answer is a default, agreed in advance:
“If nobody objects by Friday, we’re booking the Tuesday flights.”
Silence becomes consent — but fairly, because everyone agreed to that rule up front and because the default was stated, in specific terms, with a date. This is very different from someone unilaterally booking and announcing it.
Use defaults liberally. They convert the group’s most common behaviour, which is not replying, into a functioning decision procedure.
Don’t keep everything on one phone
If one person holds all the confirmations, all the booking references and all the host contact details, the group has a single point of failure — and it fails on the day that person’s phone dies at an airport, or they get delayed and everyone else is standing outside a locked flat.
Put every confirmation somewhere everyone can reach: a shared folder, a shared board, a pinned message. Booking reference, address, contact number, check-in time, what is due on arrival.
It also has a second effect, which is that the invisible work becomes visible. When people can see thirteen confirmations, they understand what was done.
Match the task to what people actually have
Not everyone can do every task, and pretending otherwise is how the wrong person ends up with the villa deposit.
The person with real credit-card headroom takes the deposit-heavy booking. The person with airline status or a company travel account takes the flights. The one who drives — and whose licence is clean, and who is over 25 — takes the hire car and is the named driver. The one who speaks the language rings the restaurant. The organised one holds the timed tickets.
This is not favouritism. It is matching the task to the resource, and it lowers the total effort for everyone.
Group size changes the answer
Three to five. No structure needed. A chat and a shared note is fine, and imposing process on five people is more annoying than the problem it solves.
Six to ten. This is where it breaks without structure. Enough people that nobody feels individually responsible, not enough that anyone thinks to organise it properly. Tasks with owners and dates are not optional here.
More than ten. Sub-groups. One person per household, flat or car, who is responsible for their own people, and one coordinator who deals only with those representatives. Trying to run twenty people in a single conversation produces a chat that everybody mutes, which means nobody sees the deadlines.
Whatever you use to hold the list — a shared document, a spreadsheet, Voyade’s booking board — the requirement is only that every task has a verb, a date, one name, and a place everyone can see it.