There's a certain kind of optimism that arrives with being elected trips coordinator for a club.
You've been on enough of the club's trips to know roughly how they work, you have ideas, and you're going to be more organised than last year's coordinator, whose filing system appeared to consist of a folder called "MISC" and a significant amount of institutional knowledge stored entirely in their own head.
Three months later you understand why the folder was called "MISC".
The scale problem
Planning a trip for eight friends is hard. Planning a trip for thirty club members is categorically different — not harder in the same way, but harder in new ways.
With friends, you know everyone. You know who's experienced and who isn't, who has a car, who's vegetarian, who always runs late, who can be counted on to confirm early. With a club, you have a sign-up sheet. You know names, and you might know a few people well, but you're coordinating with members you've met once or twice. New members may never have been on an overnight trip before and genuinely don't know what to expect. You're building a shared experience for people who, in some cases, are strangers to you and to each other.
The logistics scale linearly, but the people complexity doesn't. Thirty people means thirty different experience levels, dietary requirements, fitness levels, and expectations for what the trip will actually be.
The institutional knowledge problem
Most outdoor clubs run on a one or two year handover cycle. The trips coordinator does the role, accumulates a huge amount of knowledge about how things work, and then hands over to whoever ran for the position at the AGM.
The handover, in practice, is rarely adequate. There's usually a conversation, maybe some documents, possibly a shared drive that was last updated properly two years ago. The new coordinator is then largely on their own.
They don't know which campsites the club has used before and why, or which ones to avoid. They don't have contacts at the huts or lodges. They don't know about the local route that looks straightforward on the map but has a tidal crossing that catches people out. They don't know how many members typically drop out in the last week before a trip, which matters enormously when you're booking accommodation for thirty people.
Every year, clubs partially reinvent the wheel. Every year, new coordinators make mistakes their predecessors already made.
Safety and risk: the weight nobody talks about
Taking a group of friends into the hills carries informal responsibility. Taking club members, including people you barely know and new members who may have overstated their experience, carries something heavier.
Trip leaders for clubs are often volunteers with no formal training. They're students or working adults doing this in their spare time, but they're making decisions that affect people's safety. Is this route appropriate for everyone who signed up? Does anyone have a medical condition that matters in an emergency? Who are their emergency contacts? Is the weather acceptable or is this a genuinely marginal call?
These are serious questions. Clubs that handle them well have checklists, briefing templates, and a culture of asking them out loud. Clubs that handle them less well are hoping the questions won't become relevant.
The admin side of this — emergency contact details, experience assessments, risk acknowledgements — is genuinely important for club trips in a way that doesn't quite apply to informal friend groups. It's also exactly the kind of admin that gets done poorly when it lives in a spreadsheet that gets emailed around the week before departure.
The money problem gets bigger with scale
For a friend group, splitting costs can be handled in a WhatsApp message and sorted via bank transfer — informal, but workable.
For a club of thirty, this breaks down fast. You need deposits to secure bookings, and you need people to pay before you can confirm numbers, but people won't pay until they're sure the trip is happening, and the trip can't be confirmed until you have enough paying members. Then there's the dropout problem. A club trip has more financial exposure than a friend group trip — the bookings are larger, the deposits are higher, and the cancellation policies are less forgiving. When six people drop out in the last fortnight, the remaining members end up covering costs that weren't in the original price per head.
The treasurer and the trips coordinator often find themselves in awkward negotiations. Members sometimes dispute what they owe. Club funds occasionally end up subsidising last-minute dropouts. None of this is rare.
Mixed experience levels: the brief matters more than you think
A club trip will almost always span a wider experience range than a friend group outing. An experienced member who's been coming on club trips for three years has a very different baseline from a fresher on their first ever overnight hike, and the gap between their expectations can catch both of them off guard.
A route can be appropriate for both, but only if the less experienced members have an accurate picture of what they're actually signing up for. This is where pre-trip communication matters more than most clubs appreciate. A brief that just says "moderate hike, bring waterproofs" is either doing real work or failing to do it, depending on how it's read. "Moderate" is subjective. Waterproofs can mean anything from a full waterproof shell to a pac-a-mac from Primark.
Newer members often don't ask questions even when they're uncertain, because they don't want to look inexperienced in front of people they've just met. The burden falls on the trip leader to give them enough information to genuinely self-select, or to ask the right questions at sign-up.
The committee knows, but the club doesn't
One pattern that plays out in almost every club: the people planning the trip become so embedded in the details that they consistently underestimate how little everyone else knows.
An update posted in the club's Facebook group or Slack is seen by a fraction of members. An email to the mailing list gets opened by maybe half. A WhatsApp message in a group of forty quickly gets buried under other chat. The result is that on the day of the trip, there are always members who didn't know the meeting point had changed, or who thought kit would be provided, or who show up at 8am when it was always an 8:30 start.
This isn't negligence — it's the inherent fragility of using general-purpose communication tools for structured, time-sensitive information that a specific group of people needs to have actually received.
What actually works
The clubs that run smoothly tend to have a few things in common.
One place for trip information, rather than a Facebook event and a WhatsApp group and a spreadsheet and an email thread all running in parallel. Somewhere every member can see the current state of the plan without needing to scroll back through a week of chat to piece it together.
Structured sign-up, rather than just a name on a list. Experience level, emergency contact, dietary requirements, medical information — collected once, stored properly, not reconstructed from memory the night before departure.
Clear ownership of specific pieces of logistics, so the trips coordinator doesn't personally own everything. Food, transport, gear, safety brief, communications — these can each be owned by different people, which makes the whole thing more resilient.
And some form of document preservation, so the decisions and lessons from this trip are findable by next year's coordinator. Not in someone's inbox, not in a shared drive with a password nobody has written down, but somewhere accessible and maintained.
None of this requires special technical expertise. It requires tools that actually match the shape of the problem — structured sign-up, shared information, distributed ownership, searchable history. The difference between that and a collection of group chats is considerable.