Household invitations, done properly

One envelope, several people

For most of history, invitations went to households. An envelope addressed to a family carried an unspoken understanding about who was included, and the host trusted that understanding to hold. It mostly did, until the reply card came back with a number on it and nobody was quite sure which names the number meant.

Digital invitations make it tempting to abandon households and invite every person individually. That solves the counting problem and creates a new one: you now send four messages to one family, three of them to people who share a phone, and you lose the sense that these guests arrive, sit and leave together. The better approach keeps the household as the unit of invitation while recording every person inside it.

Decide what a household means for your event

Before you build a list, agree what a household is. For a wedding, it is usually the people you would address on one envelope: a couple, a family with children, flatmates you know as a pair. For a school event, it might be a student and the adults who will accompany them. For a community banquet, it may be a family table.

Customs differ, so make the rule fit your guests rather than a rulebook. In some families an adult child living at home is naturally part of the parents’ invitation; in others, any guest over eighteen expects their own. Neither is wrong. What matters is that you choose deliberately and apply the choice to everyone.

Write the rule down and apply it consistently, because inconsistency is where awkwardness comes from. If one cousin is invited with a partner and another is not, the reason should be a decision you made, not an accident of how the list was typed.

• Who counts as part of a household for this event?
• Are adult children invited with their parents or separately?
• Are partners named, or invited as an unnamed plus-one?
• Are children invited, and up to what age do they need a child meal or a booster seat?
• Who in the household receives the invitation and manages replies?

Name every person you can

An invitation to "the Mensah family" is warm but imprecise. It does not tell you whether the grown-up son who lives abroad is included, or whether a new baby needs a high chair. Wherever you can, list each person by name inside the household, even if the invitation itself still reads as a family greeting.

Named guests make every later step easier. Meal choices attach to people rather than to a number. Seating can place a grandmother next to her daughter rather than seating "two from the Mensah party" wherever there is space. Check-in staff can greet people by name. And when someone asks whether a particular relative is invited, you can answer clearly.

If you genuinely do not know a name, for example a partner you have not met, record a placeholder such as "guest of Kofi" and ask for the name in the reply.

Let each person answer for themselves

A household invitation should produce individual replies. One person may be coming while another is travelling. A teenager may join the reception but not the ceremony. An elderly parent may need a step-free route while the rest of the family does not.

The practical design is simple: one link or card goes to the household, and inside it every named person has their own answers. One family member can fill the whole thing in, which is how most households actually reply, but the record you receive says exactly who is attending, what each person will eat and what each person needs.

The question to design around is not "how many of you are coming?" but "which of you are coming, to which parts, and what does each person need?"

Multi-day and multi-function events

Many celebrations have more than one part: an introduction ceremony and a reception, a civil service and a party, a welcome dinner the night before. Not every guest is invited to every part, and not everyone invited will attend every part.

Record invitations per function, then collect replies per person per function. A worked example makes this concrete. Suppose the Adeyemi household of four is invited to a traditional ceremony on Saturday and a reception on Sunday. On Saturday all four attend. On Sunday the two adults attend and the children stay with relatives. A single headcount for the household would say four; the honest numbers are four on Saturday and two on Sunday, with two adult meals and no child meals on Sunday. Your caterer, your seating plan and your door list each need the per-function figure.

Plus-ones without confusion

Plus-ones are where household invitations most often go wrong, usually because the rule was never stated. Decide in advance who receives one, and say so in the invitation rather than leaving guests to guess. A clear line such as "We have reserved two seats in your name" prevents the uncomfortable conversation later.

When you do offer a plus-one, ask for their name and the same details you ask everyone else, such as meal choice and access needs. A plus-one is a guest, and treating them as an anonymous extra seat leads to wrong meal counts and awkward place cards.

1. Decide which guests are offered a plus-one, and record the reason.
2. State the number of seats reserved in each invitation.
3. Ask for the plus-one’s name, meal and any access needs.
4. Decide whether you will approve plus-ones before they are confirmed.
5. Set a date after which plus-ones cannot be added.

Children, ages and safety

If children are invited, you usually need a small amount of information about them: whether they need a child meal, a high chair or a booster seat, and sometimes whether they will be in a supervised area. You rarely need exact dates of birth, and collecting less is better. An age band such as "under 4", "4 to 12" or "13 and over" is usually enough for catering and seating.

Keep information about children visible only to the people who need it. A caterer needs the number of child meals. A venue may need to know about high chairs. Nobody needs a list of children’s ages circulating in a group chat.

Who receives the invitation

Choose a primary contact for each household: the person most likely to reply and to read updates. That person receives reminders and changes. For large families, it can help to record a second contact, especially if the primary contact is less comfortable with messages or email.

Respect how people actually communicate. In some communities, invitations travel through a family elder or by phone; in others, a single family group message is the norm. The household model works with both, as long as each person’s reply ends up recorded individually.

Keeping the list clean

Large guest lists collect duplicates: the same aunt entered twice by two different planners, a couple listed once together and once separately. Review your list for duplicates before invitations go out, merging records rather than deleting them so that nothing already answered is lost.

Once replies start arriving, avoid editing households by hand in several places. Keep one list as the source of truth, and let changes flow from it to seating, catering and the door list. Attergo is built around exactly this: one invitation per household, a reply for every person and every function, and every downstream plan updated from those replies. Whatever tool you use, the principle is the same: record the decision once and let everything else read from it.