How to organise an outing for twenty people without losing your mind
Somewhere around fifteen people, organising an outing stops being a social task and becomes an administrative one. The methods that worked for six actively fail. Asking everyone what they would like produces forty opinions and no date. Waiting for confirmations produces a group that is still eighty per cent maybe the day before. Splitting the bill at the end produces a scene.
The shift is this: with a small group you are hosting, and with twenty you are running an operation. The job is now deciding, informing and collecting money, in that order. Do those three things well and the day mostly runs itself.
Set the date first, and refuse to reopen it
Pick the date before you pick the activity, announce it as a decision rather than a proposal, and then hold it against all subsequent lobbying.
This feels autocratic and it is the single kindest thing you can do for a large group. There is no date that suits twenty people. There is only a date that suits fourteen of them, and your job is to find it quickly rather than to discover, over three weeks of polling, that it does not exist.
Reopening the date is the classic large-group death spiral. Someone cannot make it, you move the date to accommodate them, and now two people who could make the original date cannot make the new one. You have traded one absence for two and spent a fortnight doing it.
So: choose, announce, and when someone cannot make it, say that you are sorry and that you hope to see them at the next one. That is the whole script.
One person decides
Consensus does not scale. At twenty people, every additional opinion in the decision loop costs more than it adds, and a committee of three organisers is somehow slower than one.
Be the decision-maker, or appoint one and then get out of their way. The role is not glamorous: choose the thing, book the thing, tell everybody about the thing. Consultation is fine before the decision and useless after it.
Two ways to keep this from feeling heavy-handed. Ask for information rather than for preferences, since anything I should know about is a much better question than what would you like to do. And give people one real choice inside a fixed frame, because choosing between two options you have already vetted is participation, whereas an open field is homework.
Choose an activity that splits
This is the most important structural decision you will make, and most organisers make it accidentally.
Activities that split into small teams scale almost indefinitely. Twenty people become four teams of five, everyone is doing something, everybody talks to the four or five people nearest them, and the whole group reconvenes at the end with something to compare. Add another six people and you add another team. Nothing breaks.
Activities built around a single unit do not scale at all. A table of twenty means you speak to the three people beside you and shout at nobody else for two hours. One guide talking to twenty people means the back half hears nothing. One booth, one bowling lane, one anything, means a queue.
So the test for any candidate is simple: at twenty people, does this become four groups of five, or one group of twenty pretending to be a group? A puzzle trail or an outdoor game is the clearest example of the first kind, because the format is teams of a handful racing the same route, which means the size of the whole party is nearly irrelevant. City Sleuth is built that way, and a group of twenty is four teams and a leaderboard rather than a logistical problem.
If the day has to include a meal for everyone, put the splitting activity first and the meal second. People who have already been on a team with each other sit down as a group that knows one another, and the table works far better for it.
Collect the money before the day
Never on the day, never afterwards, and never in cash at a table while a server waits.
State the amount in the first message, alongside the date. Set a payment deadline about a week before, and be clear that paying is what confirms a place. This does two jobs at once: it gets your money in, and it converts your maybes into a real number, which is the thing you actually need.
A large group also contains a wide range of budgets, and nobody wants to announce theirs. Naming the figure early and plainly lets a person decline quietly, weeks in advance, without an explanation. That is far kinder than an ambush at the till.
Refunds: decide the policy before anyone asks, say it once in writing, and apply it identically to everyone. A stated rule is easier for everybody than twenty individual judgements about how good someone's excuse was.
Build a plan that survives four no-shows and two latecomers
Assume it. Not as pessimism, just arithmetic. Out of twenty confirmed people, expect a few to drop out in the final week and a couple to arrive after the start.
Design accordingly.
- Book for the number who have paid, not the number who said yes with an emoji.
- Prefer per-person pricing where you can, so a drop-out costs one share rather than reshaping the whole booking.
- Keep team sizes flexible. Four teams of five absorbing two absences becomes four teams of four and a bit, which is nothing. A plan requiring exactly twenty is a plan waiting to be ruined by a head cold.
- Have a plan for latecomers that is not the group waiting. Either they join at a known point, or they miss the first part. Decide which, and say so in advance, so nobody has to make a ruling on the pavement while eighteen people watch.
- Leave a slack hour. Everything with twenty people takes longer than it does with six. Arrivals, ordering, moving between places, all of it.
One source of truth and one arrival instruction
The organiser's real workload is not the booking. It is answering the same six questions twenty times in twelve separate conversations.
The cure is one message that contains everything, sent to everyone, and then pointed at whenever someone asks. Date. Meeting point, described so precisely that a person who has never been there cannot get it wrong. Arrival time and the latest useful arrival time. What it costs and how to pay. What to wear and how much walking is involved. When it ends. Your phone number.
Send it twice: once when you announce, once the day before. The day-before message is the one people actually read, and it prevents almost every individual question you would otherwise field on the morning.
Be specific about the meeting point in particular. Not the name of a place, but where exactly, on which side, and what it looks like. Vagueness here is what produces six people standing round a corner from the other fourteen.
When the group splits anyway
It will. After the main activity, some people go home, some go for one drink, and a third contingent goes off to do something else entirely. Organisers often experience this as a failure of the plan.
It is not. It is a large group behaving like a large group, and letting it happen is usually correct. Twenty people cannot stay together indefinitely without someone being bored or overtiring themselves, and a day that ends in three contented smaller groups is a better outcome than one that ends with everybody trapped together being polite.
What you can do is make the split graceful. Have a clear end to the official part, so leaving then is normal rather than an early exit. Announce the optional next thing loosely and let people opt in. And do not treat the after-party attendance as a scorecard for the day, because the people who went home were, in many cases, the ones who had the best time.
Your next move
Pick the date this week. Send one message with the date, the cost and the payment deadline. Choose an activity that splits into small teams. Then send the details message twice and let the day happen.
If a format that splits twenty people into competing teams is what your day needs, talk to us about a City Sleuth group booking and we will tell you how it works for a party your size.