A bachelor or bachelorette weekend lasts two days. What wears the organiser down is the six weeks before it: forty messages a day, four people who reply "works for me" to everything and one who never replies at all, a budget nobody dares name, and the constant worry of getting it wrong for the one person it is actually for. Almost all of that stress comes from three decisions people keep postponing. Make them early, write them down once, and most of the messages simply stop.
The weekend is not the hard part
Ask anyone who has organised a stag or hen weekend what was hardest. They will not mention Saturday night. They will mention the moment they put 780 euros of accommodation on their own card without knowing whether everyone would actually come, or the week two guests pulled out because they found out the real price too late.
Three decisions settle nearly everything: what it costs, who is invited, and what the schedule looks like. While those stay vague, every small detail turns into a negotiation. Once they are fixed, the group stops debating and starts booking flights.
Step 1: one conversation with the guest of honour
Tradition says it should be a surprise. In practice the surprise should cover the details, never the frame. Ask four questions, once, about three months out:
- "A full weekend, or one long day?"
- "Somewhere abroad, or something within three hours of home?"
- "Is there anyone you really do not want on the list?"
- "Is there one thing you flatly refuse: a humiliating outfit, a skydive, karaoke?"
Two minutes of conversation, and you avoid the worst possible outcome: a beautifully organised weekend designed for somebody else. The city, the activity, the Saturday wake-up call all stay a genuine surprise. You have only removed the four ways to miss the point entirely.
Step 2: name a price cap before you invite anyone
This is the step almost everyone skips, and it is the number one reason people drop out. A hen weekend at 320 euros is not a problem. A hen weekend whose price only becomes clear three weeks before departure is, because by then anyone short of money has two options left: borrow it, or look like the friend who bailed.
Here is a worked example: two nights in Porto for nine people, flying in from Dublin and Amsterdam.
- Return flights: around 110 euros each (85 from Dublin, 135 from Amsterdam, booked two months ahead)
- Apartment for nine, two nights: 780 euros, so 87 euros each
- Saturday afternoon activity, river boat with a skipper: 40 euros each
- Saturday dinner, set group menu with drinks: 42 euros each
- Groceries, breakfasts, taxis and a night out: 45 euros each
- The guest of honour's share, split across the other eight: 26 euros each
Announced total: 350 euros per person, flights included. That figure goes in the very first message, the one asking whether people are free. Not in the tenth message, after the apartment is already booked.
One small thing matters more than it looks: quote a cap, not an estimate. "350 euros maximum, flights included" is a commitment. "Around 300" commits to nothing, and quietly becomes 420 once taxis, brunch and the second round are added.
The per-person price belongs in the first invitation, never in the message after the first booking.
Step 3: the guest list is not yours
This is the touchiest subject, and it is settled in one sentence: the guest list belongs to the person being celebrated, the logistics belong to you. You should not be deciding whether the work colleague comes, or whether the brother who knows nobody will feel out of place.
One rule covers most cases: invite the people who will be at the wedding and who the guest of honour sees at least once a year. Everyone else gets the wedding, and that is plenty. A group of eight who actually know each other works far better than a group of eighteen where four spend the weekend on their phones.
And when somebody invites themselves, which happens more often than you would think, the answer is not "no". It is "let me ask, it is their list". You are not the bouncer, you are the messenger.
Step 4: three blocks, not twelve time slots
The schedule that fails always looks the same: a timed grid from 9am to 2am with fifteen minute transitions. Nobody follows it, the organiser spends the weekend herding people, and goes home more tired than after a working week.
Build three blocks instead:
- One headline block: the activity people will still bring up in two years. Exactly one, on Saturday afternoon, booked and paid in advance. It is what gives the weekend its identity.
- One social block: Saturday dinner, one long table, a set menu with drinks included so nobody has to divide a bill between ten people at midnight. This is where the weekend actually happens.
- One empty block: Sunday morning. Nothing planned, late brunch, whoever wants to sleep sleeps. An empty block is not a hole in the schedule, it is what makes the rest bearable.
Friday evening needs no plan at all. People land at different hours, they are hungry, they want to see each other. Groceries and something to cook are enough, and it is often the best part of the weekend.
Plan it without the forty messages a day.
Kobidi keeps the whole weekend in one place: everyone proposes dates, stays and activities, the group votes, and the per-person price updates with every expense added. Free, and nobody needs to install anything to join.
What ruins these weekends
The bad ones fail in remarkably predictable ways:
- Humiliation. Making somebody who hates it walk through a city in a ridiculous outfit does not create a memory, it creates a politely buried grudge that lasts years.
- Fourteen hour days. Three activities on Saturday is two too many. The group ends up enduring two of them to enjoy one.
- A price revealed late. See above. It is the single biggest cause of dropouts two weeks out.
- Groups of twenty with no sub-groups. Past twelve people, book two tables and two taxis, or half the group will not speak to anyone all night.
- Drinking as the entire plan. A Saturday afternoon that opens with shots ends with three people asleep at 9pm and a half empty dinner table.
Activities that actually work
The good ones share a trait: they give people something to do together without requiring anyone to be funny on demand. Rough prices per person, in a group of nine:
A cooking class with a chef, around 55 euros. A skippered boat on a river or a bay, about 40 euros. An escape room, 26 euros. A surf lesson on the Atlantic coast, 45 euros including the wetsuit. Go-karting, 38 euros a session. A vineyard tasting with transport, 45 euros.
The test to apply before booking: will the shyest person in the group have a good time? If the answer is no, the activity is for you, not for them.
Who covers the guest of honour
In most groups the bride or groom to be pays for nothing across the weekend. In practice that means their accommodation, activity and meals are split across everyone else. In the Porto example that is roughly 210 euros divided by eight, so 26 euros more each.
The part people forget is travel. Say clearly in the first message what the pot covers. "Everything is covered except your flight" is a perfectly reasonable position, as long as it is said upfront and not at the airport.
And if someone in the group is genuinely stretched, the way to handle it is not a group announcement. It is a private message, a quietly adjusted share, and no further mention of it all weekend.
The timeline, in six steps
- Three months out: the four questions to the guest of honour, and a guest list they have approved.
- Ten weeks out: the invitation, with dates, city and the price cap. A yes or a no within a week, not a "let me get back to you".
- Two months out: accommodation booked. Whoever fronts it gets paid back within 48 hours, not "before we leave".
- Six weeks out: Saturday activity booked and paid, restaurant reserved with a set menu.
- Two weeks out: a reminder with times, the meeting point, and who is bringing what.
- Two days out: one recap message with the address, the time and the door code.
Six messages across three months. That is very little compared with the forty a day a group with no frame produces, and it delivers exactly the same weekend.
Once the group passes eight people
Beyond eight, tracking all this by hand gets painful fast. Two people suggest different dates, three reply privately, somebody joins late, the activity changes and every share changes with it. The organiser spends their evenings recalculating numbers nobody reads.
That is the point where a shared space earns its place: everyone proposes a date, a place to stay or an activity, the group votes instead of arguing, and the per-person share updates itself every time an expense is added. Everybody sees the same number at the same moment, and nobody has to ask "so where are we at?" again. That is exactly what Kobidi does, and it is free.