Two families meeting,
not a small wedding.

An engagement party has one job and it is a social one: the people who will spend a long day together in a year's time meet each other first, in a room where nothing is riding on it. Your parents meet their parents. Your oldest friend meets the sister who will stand next to you. Nobody has to walk anywhere or say anything in particular, and that is the point.

Treated as a small wedding, it goes wrong in a predictable order. A colour scheme appears, then a running order, then a seated three-course meal, then a budget that quietly borrows from the wedding. Guests can feel a rehearsal when they are in one, and by the second time they put on the same outfit for the same two families, the evening has lost the quality that made it worth holding.

The test is simple. Take away the food, the room and the plan, put everyone in a garden with something to drink, and ask whether the evening still works. For an engagement party the answer is yes, which is why it can be modest without being disappointing. For a wedding the answer is no, which is why that one costs what it costs.

Common practice is a few months after the proposal, while it is still news. The party is a reaction to something; held a year later it becomes an event in its own right and has to justify itself. If your engagement will be a long one, and two-year engagements are ordinary now, hold the party early rather than saving it up.

The trap at the other end is holding it close to the wedding. Guests who travel, book a room and buy an outfit twice in one season begin to feel asked twice, and the people most likely to feel it are the ones with furthest to come, which is to say the people you most want at both. Leave a clear gap. A season is the minimum and six months is comfortable.

It also helps to put the party before the save the dates, which usually go out eight to twelve months ahead. Then the sequence a guest lives through is news, party, save the date, invitation: four separate moments, each with its own reason to exist. Compress any two of them and the wedding invitation arrives as the third request in a row.

One rule is worth more than all the etiquette around it: everyone at the engagement party is also invited to the wedding. No exceptions, no assuming they will understand. Someone who has raised a glass to your engagement, met your mother and gone home with the date in their head does not read a missing wedding invitation as a budget decision. They read it as a decision about them, and it is the most reliable source of lasting hurt around a wedding.

The rule is painless while both lists are the same size. It bites when the wedding will be much smaller — a short ceremony, forty people, a room that seats what it seats. The honest answer is the one nobody wants to hear: keep the party small too. A hundred-person engagement party followed by a forty-person wedding asks you to un-invite sixty people by saying nothing for several months, and they will work it out long before the invitations go out.

If you want the big, loose celebration, hold it after the wedding rather than before. A party for everyone who was not in the room is a genuinely good event: there is nothing left to be invited to, so nobody is waiting. Either way, settle the wedding's rough number before you write the party's list. The guide to who to invite to a wedding draws those circles in a way that survives contact with a family.

In many families the bride's parents host and pay for the engagement party, which is the older form of the tradition. In many others the couple host and pay for their own. Often the two sets of parents split it, or one side takes the engagement and the other takes something later in the year. None of these arrangements is more correct than the rest, and no guest can tell from the evening which one you chose.

What guests can tell, and what matters, is who is inviting them. Put it in the first line: the Ferreiras would like you to join them, or Ana and Tom would like you to join them. That single line answers a dozen quiet questions — whose house this is, who to thank on the way out, who will make the toast, who to reply to. The engagement invitation wording page has both versions written out to copy.

Then settle the money before it is a bill. The host sets the budget, the budget sets the number, and the number sets the shape of the evening, in that order. When the couple are paying and a parent would like to add ten names, the sentence that keeps everyone in a good mood is the plain one: this budget carries sixty people, here is what sixty-five would cost, and we are happy to talk about it.

A drinks party is the workhorse: two or three hours, something on trays, no seating, people moving. It carries the largest list for the least money and it is the best shape for two families meeting, because nobody is trapped between the same two neighbours all evening. The risk is that it ends with each family having talked mostly to itself, which is the one thing the hosts are there to prevent.

A long lunch suits small children and older relatives who would rather not drive home in the dark; daytime venue hire is usually cheaper, and it finishes at an hour that leaves the day intact. A dinner is the warmest of the three and the most expensive per head. It caps the list at whoever fits round the tables, which is a limitation if your list is ninety and exactly the right instrument if it is thirty.

Decide in that order — number first and then shape, or shape first and let it cap the number. The version that goes wrong is choosing a seated dinner because it sounds nicer, then trying to make ninety people fit inside it. Every problem after that, the venue and the cost per head and the parents who each want six more names, is really that first decision arriving late.

In most places an engagement party is not a gift occasion. Flowers, a bottle, a card: that is the level, and plenty of guests will bring nothing at all, correctly. The difficulty is never the custom, it is the uncertainty — a few people will worry about it, and one of them will ring your mother to ask what everyone else is doing.

So say it once, quietly, and then leave it alone. One line at the foot of the invitation, or in the notes on the reply page, is enough: no gifts, please, your company is the present. Do not repeat it, and do not name a wedding gift list at an engagement party, because a list named here reads as a bill for an evening nobody was charged for. If somebody brings something anyway, thank them and put it aside rather than opening it in front of the room.

Speeches deserve the same restraint, and there is a good case for exactly one. Whoever is hosting stands up, welcomes everyone, says in two sentences why these two families are in the same room, and proposes a toast. Two minutes and it is done. A round of speeches turns a mixing room into an audience, which is the opposite of what the evening is for, and it spends material that belongs at the wedding. The father who has been writing his speech since March should be encouraged to keep writing it.

Here is the practical case for an engagement party, set apart from the celebration: everyone you will need for the wedding invitations is in one room, in a good mood, months before you need anything from them. Six months later you will be trying to extract a postal address from a cousin over a group chat, at the exact moment the printer wants the final list. On the night it takes an hour of ordinary conversation.

Make it someone's job. One person, one file, five columns: the guest's name, the name of whoever they came with, an email address, a phone number, and a full postal address including the country. Ask while you are talking to them rather than passing a sheet round at the end, which produces half a page of handwriting nobody can read. Anyone you miss, get from the parent who invited them that same week, while the evening is still recent enough to be interesting.

That file is the wedding's guest list, so none of the work is spent twice. If the engagement invitation went out as an online one, part of it is already built: replies come back with the guest's name, how many are coming and the names of the people they are bringing — the detail envelopes get wrong when they fall back on 'and guest'. A spreadsheet then imports into the wedding with the columns mapped by hand and duplicates caught by name or email, so the aunt who is in the file twice does not receive two invitations.

The other thing you collect is not written down anywhere. An hour of watching the room teaches you more about the seating plan than an afternoon with a diagram: who found each other, who did not, which uncle stayed at the far end of the garden. Write that down the next morning, before you decide it is the sort of thing you are bound to remember.

When the two families come from different countries, the party is doing something harder: half the room has never met the other half, and not everyone in it shares a language. It still works, but it is not an evening you can leave to run itself. Introduce people by their relationship and not by name alone — this is Ana, Marco's aunt, she has come from Porto — because a name on its own gives a stranger nothing to say next.

Mix them physically. If there is seating, do not seat by side; if there is not, the hosts' job for the first hour is to walk people across the room and leave them there. Keep the music low enough that a second language can be heard, because background noise is what finishes off a language somebody learned at school. Give any welcome in both languages, two minutes each, rather than one long one while a third of the room waits politely.

The information side is easier than the social one. An invitation page each guest reads in their own language answers the questions — what time, what to wear, which station, where to stay — before they become somebody's job on the night; Vowly's guest page carries the schedule, directions and hotel tips in nine languages, and adds the calendar file and confirmation email that turn a date in someone's head into a date in a diary. If both celebrations are coming, there is a separate piece on running the engagement and the wedding side by side in one app, which is mostly about not typing the same hundred names twice.