How do you plan a stag do without the cringe?

The bachelor party has a reputation problem, and most of it comes from two things: a plan built around what the organiser finds funny, and a price nobody agreed to. Both are fixable in the first conversation.

This article covers who plans it, when to hold it, what the usual formats cost per head, and how to run a weekend that a mixed group of ages actually enjoys. Bachelor party and stag do are used interchangeably throughout; the American version is more often a weekend away, the British more often a mix of both.

The best man leads and the groom stays out of the logistics, but four things are his call and should be settled in one conversation, early.

• Who is invited. Including the awkward ones: brothers-in-law, fathers, a colleague who assumes he is coming.
• The ceiling. The most he is willing to see his friends spend.
• The no list. Anything he genuinely does not want, and this is the question that most often goes unasked.
• The shape. A night out, a full day, one night away or a weekend.

Ask about the no list directly rather than hoping it comes up. Most grooms will not volunteer that they hate surprises, cannot swim, do not drink much any more or would rather not be tied to anything. Asked plainly, almost all of them will say so.

A surprise activity inside a known weekend works well. A surprise date, destination or price does not, because those are the three facts the rest of the group needs in order to commit. Anyone with young children, shift work or a long journey needs them earliest.

Cost is the main reason people decline, and almost nobody says so. Publishing an all-in figure before anyone commits solves more problems than any activity ever will. The figures below are per person and indicative, for the US.

Three practical rules. Quote the total including the groom's share if the group is covering it. Collect the money before booking, not after, so a dropout is not the organiser's debt. And keep a simple record of who has paid what, because the person chasing four payments by text at eleven at night is the person who stops enjoying the weekend first.

If two or three people go quiet when the price lands, that is feedback about the price. A cheaper version that everyone attends beats an expensive one that half the group misses.

Four to eight weeks before the wedding. Far enough out that a rough Sunday has no consequences, close enough that it still belongs to the wedding.

Not the weekend before, whatever the films suggest. The last week holds suit fittings, deliveries, family arrivals and a hundred small errands, and the cost is not the hangover but the lost Saturday.

On length, shorter is usually better than the group thinks. A pattern that works:

1. Friday evening: arrival, food, drinks. No activity. People are travelling and tired.
2. Saturday morning: nothing booked before ten. Breakfast that can absorb latecomers.
3. Saturday afternoon: the main activity, two to three hours.
4. Saturday evening: a booked table, then one optional plan afterwards.
5. Sunday: a late breakfast and out. Do not book anything.

Two hours of unstructured time on the Saturday is not a gap in the plan, it is the part people remember. Groups that are scheduled hour to hour spend the weekend being herded.

The typical bachelor party group spans twenty years, several fitness levels and at least one person who knows nobody. Three habits do most of the work.

Pick an activity with a low floor. Anything requiring skill, nerve or stamina divides the group into participants and spectators. Go-karting, clay shooting, a brewery tour, golf, a boat, a long lunch: all of them work because nobody is excluded and nobody is embarrassed.

Make the drinking optional in practice, not just in theory. Someone will be driving, someone in recovery, someone on medication and someone simply not in the mood. A plan that only works drunk loses them by nine o'clock.

Introduce people. The best man is the only person who knows everybody, and a group chat two weeks out with names and a one-line description of each person does more for the weekend than any activity.

Then there is the tradition question. Handcuffs, forfeits, nudity, anything involving strangers, and the whole genre of humiliation are all in decline for a reason: they are funny to the group and rarely to the groom. If the no list did not rule them out, the room test still applies. If you would not describe it to his mother, do not build the weekend on it.

Bachelor weekends fail on logistics far more often than on planning. The recurring ones:

• Passports. Someone will discover theirs expires within six months. Ask in writing, twelve weeks out.
• The wedding is in three weeks. No activity that can break a wrist, an ankle or a nose. This is not caution, it is arithmetic.
• Accommodation by room, not by head. Who shares with whom changes the price per person, so decide it before quoting.
• One person holding every booking. Confirmations in the group chat, not in one inbox.
• The groom paying for nothing. Standard, and it should be stated, otherwise he spends the weekend trying to buy rounds.
• Nobody appointed to be sober. On any weekend with an activity, one person needs to be able to read a booking confirmation at three in the afternoon.

Finally, the tone. A bachelor party that ends with a genuinely good story does not need a casualty. The best ones tend to be unremarkable on paper: a group of men in a house or a pub with enough time to talk, doing one thing they would not otherwise have done.

If several people are travelling in for the wedding as well, this is the moment the group discovers who is coming from where. That information is worth keeping, because it is the same list the couple will need for their wedding website when accommodation questions start arriving.