Agree the money first,
then design the weekend to fit.

The instinct is to start with ideas — a city, a house with a hot tub, something with a theme. Resist it for one conversation. The person being celebrated already has a version of this in their head, and it is usually smaller and quieter than the one you are about to build. Ask them in private, and take the answer at face value even if it disappoints you.

Two questions settle almost everything else. How long: one evening, one night, two, three. And roughly what each person can spend without it becoming a problem — not what they would spend themselves, but what the least comfortable person on the list could manage. The destination, the size of the group and the shape of the whole thing follow from those two answers.

Ask a third thing while you are there: who must be on the list, and who they would rather was not. That is much easier to hear now than to explain later. Write it down, because you will drift from it.

A weekend half the group cannot afford does not become a smaller weekend. It becomes a split group: the ones who came, the ones who were suddenly busy, and a quiet resentment that outlasts the event. Nobody tells you the real reason they dropped out. They say work, or a wedding, or the dog.

So set the number first. Decide what one person pays, all in — travel, bed, food, the activity, and their share of the celebrated person's costs — then design something that fits inside it. This is the reverse of the usual order: book the house, add the meal, add the thing on Saturday afternoon, and discover in week six that you have built a month's rent.

Two habits keep the number honest. Include what people pay on the day: a figure that leaves out drinks and taxis is not a figure, it is an opening offer. And carry a small buffer, because someone will drop out after the deposit and the rest of you will absorb it. Hand back what is unused at the end.

The list is not yours. It belongs to the person being celebrated, which means names go on it that you would not have chosen: the sibling-in-law, the friend nobody has seen in years, a parent. Ask about each of them rather than deciding for them. In some families a mother who was never asked is a far bigger problem than a mother who came for dinner on the Friday and went home.

That is also the right shape for anyone who cannot do the whole thing. Some people cannot take two days off, or spend the money, or leave a small child, and would still like to be there. Build the trip so one part stands alone — the Friday dinner, say — and invite them to it properly, with the same detail and the same cost line as everyone else.

Say the number when you extend it. An offer with the cost in it, and no obligation to stay over, is something a person can accept or decline in one message. "Come along if you fancy it" hands the work back to them, and most people will not do it.

Whatever it looks like, this invitation is asking people to commit money on a date, and it has to carry everything that decision needs: the dates, including when it starts and when it ends on the last day; where, precisely enough to book travel to; the cost per person; what that covers and what it does not; when the money is due; and a reply deadline.

The deadline is the part organisers soften, and the part that has to be hard — because it is not really your deadline. It belongs to the house, the restaurant, or the deposit. Say so. "The house needs the deposit on the twelfth, so I need to know by the ninth" is a sentence nobody argues with. "Let me know when you can" produces answers in March.

It is also the argument for sending a link rather than a picture. Details on a weekend away move: the pick-up time changes, the restaurant swaps, a second night is added. An image is frozen the moment it lands in the group chat; a live invitation page is edited once and everyone sees the current version, including the people who opened it a month ago. The party invitation wording guide has openings you can adapt.

Chasing eleven people across three group chats is the part that makes organisers swear never again. The fix is structural, not personal: one place where everyone replies, so you are not reconstructing a headcount from thumbs-ups and "probably". An online RSVP hands you a list — who is in, how many, what they do not eat — instead of a chat you read backwards.

Money follows one rule: nothing is booked until the money is in. Not until people confirm — a confirmation costs nothing, and people mean it sincerely right up to the moment the payment would leave. Put a single due date on the invitation, set it earlier than the day you actually need it, and expect two stragglers.

Then chase once, lightly: one message in the group saying what is still outstanding, no names, and a private nudge two days later to the people it applies to. Be honest about anyone who misses the date — if the number does not work without them, the trip does not work, and week three is a better time to learn that than week nine.

The most useful thing you can produce is a running order. Not a list of secrets — just times and places, from arrival to departure, with an address against each one. Put it where everyone can open it on a phone, and point at it every time you are asked.

It absorbs the same twelve questions asked eleven times each: what time on Friday, where do I go first, should I eat before, can I get a train back at six. A page carrying the schedule, the directions, hotel suggestions and a short answers section takes all of that off you, and the messages stop arriving at eleven at night.

If the trip has distinct parts, ask about them separately rather than as one yes. A guest can reply for the Friday dinner, the Saturday activity and the Sunday lunch as three answers, so you book the restaurant for the nine who are eating rather than the fourteen who said yes to the weekend in general. The person coming for one evening is then counted properly.

A surprise works when the person likes surprises, the group is small enough to keep one, and what is hidden is the content: the restaurant, who flew in, the afternoon. It fails when it is really a surprise for the organiser, pushing someone into a weekend they would not have chosen on dates they cannot spare.

Two things are never a surprise. The cost, because asking somebody to pay a number they have not seen is not a gift. And the dates, because adults have jobs, childcare and other people's weddings, and the kind thing is to let them protect the weekend rather than discover it.

You can still keep the good part hidden. "Hold the weekend of the fourteenth, here is roughly what it costs, bring shoes you can walk in" is a complete invitation, and it leaves everything that actually delights someone unopened.

Plenty of people do not want a weekend away. They want an evening, a table for twelve and their own bed. That is not a lesser version, and it is what to propose whenever the two answers you started with were one evening and not much.

It needs exactly the same invitation. A dinner has an arrival time the restaurant will hold for fifteen minutes, often a set menu chosen a week ahead, a cost per person, and a number that has to be confirmed. So it still carries the date, the address, the arrival time, the cost, the deadline, and a reply that collects meal choices and allergies rather than leaving you to message everybody the day before. The dinner invitation page covers wording for that shape.

What changes is timing. A weekend away realistically wants three or four months, so people can book travel and take days off; an evening can go out four to six weeks ahead. In both cases the reply deadline belongs to whoever holds the deposit, not to you.