How to build your wedding guest list
The guest list is the first wedding decision that moves real money: venue size, budget, even the date all derive from it. It is also the most loaded one — behind every row there is a person, and sometimes an offended aunt. Here is an orderly way to build it: two circles, a clear frame with the parents, and one file structured right from day one.
How many guests do you start from?
You don't start from names — you start from the budget. Every guest on the list is a plate the venue bills for, so the guest range derives from what you are willing to spend, not the other way around. Set a target range before writing the first name, and build the list into it — once you touch the upper bound, every new name that enters means another name leaves.
What are the must circle and the joy circle?
One exercise that sorts the entire list into three clear groups. Sit down just the two of you, before the parents send their lists, and run every name through it:
- The must circle — the people the wedding simply cannot happen without: close family, the friends who would be there in any scenario. They go in first, no discussion.
- The joy circle — the people you love imagining on the dance floor: army friends, close colleagues, favorite cousins. They go in as long as the range has room.
- Everyone else — the "it would be awkward not to" invitees: neighbors from a decade ago, acquaintances you haven't spoken to in years. A name that fits neither circle probably doesn't need a row.
Who decides — you or the parents?
You set the frame, and the parents get a defined place inside it. At most Israeli weddings the parents have a list of their own — extended family, friends, work — and the conversation about it turns dramatic mainly when it starts from names. Start from numbers:
- Frame first, names later — close the overall range between the two of you, and only then sit with each set of parents on their share.
- A quota, not a veto — each side gets a defined number of seats and decides on its own who fills them. You don't delete names from your mother's list — she prioritizes within her quota herself.
- The same test for everyone — the parents' lists go through the two-circles exercise too: who is a must, who is joy, and who is "it would be awkward".
- Principles close once — plus-ones and kids are rules of the whole wedding, not a negotiation per name (more on that below).
Why does a B-list backfire on WhatsApp?
Because people talk — and an invitation that arrives two weeks after everyone else's gives away exactly where you stood on the list. "A-list now, B-list when seats free up" looks clever on paper, but your guests share WhatsApp groups, and the invitation is discussed the day it goes out. Whoever receives it late works out on their own that they were waiting in line — a bigger insult than not being invited at all. Instead of a B-list: close a list slightly below your target, keep a margin for genuine additions, and send everyone in the same wave.
How do you structure the file from day one?
One row per household — that is, per invitation — not per guest. A family with kids is one row with one phone number, not five rows. And every row carries four columns that will work for you all the way to the wedding day:
- Mobile phone — where the invitation with the personal link will be sent. A row without a phone is a guest who receives nothing.
- Side — his side, her side or shared. That is how you see at any moment how each side is progressing, and who chases whom with reminders.
- Group — family, army, work, studies. This is the column that will build the seating chart: a table is, in the end, a group that sits together.
- Expected party size — how many people stand behind this invitation. That is the gap between the number of invitations and the number of guests — exactly the number the venue bills for.
These columns are not tidiness for its own sake: invitations need a phone, reminders need a status, seating needs groups and meal counts need party sizes. One file serves every stage — if it is built right from the start.
What spreadsheet hygiene keeps the file usable?
One mobile number per row, and every number appears exactly once. The rest of the rules follow from that:
- No duplicates — an uncle who appears on your list and on the parents' list will get two invitations and be counted twice. A duplicate sweep by phone number before sending saves embarrassment and money.
- Mobile numbers only — a WhatsApp or SMS invitation doesn't reach a landline. A landline number is a row that will never answer.
- Real names, not nicknames — "Yuval's mom" looks fine today and becomes impossible on the seating chart six months from now. Full name, as it should appear on the invitation.
- Consistent values — in the same column, "work" is always written the same way, not "work" in one row and "from the office" in the next. That is the only way to filter and count.
When is the list finally closed?
Never completely — which is why you build it so an addition breaks nothing. Another name always turns up: a new partner, a colleague who just joined, friends back from abroad. The goal is not to prevent additions but to plan for them — a small margin inside the range, new rows entered in exactly the same structure, and a clear eye on the truly binding moment: closing the final number with the venue. Until then the list lives and breathes; after it, every addition is a conversation with the venue.
What do you decide about plus-ones and kids?
Decide once, phrase it in one sentence, apply it to everyone. These two decisions produce more hurt feelings than any single name on the list — precisely because every exception feels personal:
- Plus-ones — a rule by type of relationship, not by person: for example, long-term partners are always invited, a one-evening date is not. Once decided, the rule applies to your niece and to your colleague alike.
- Kids — three common options: no kids, family kids only, or everyone. Pick one, phrase it gently on the invitation — and it translates straight into the expected-party-size column.
How does the list become invitations, seating and meal counts?
If the file is built right — it is already prepared for all of it. In Weddigo you upload the Excel as it is, and the system detects the columns on its own: phone, side, group and party size. From that moment, that exact list is the one that sends a personal link to every household, reminds only those who haven't answered yet, drags onto tables by the groups you defined and closes the meal counts with the venue. A file built right in one evening works for you until the end of the wedding.
A good guest list is not a page of names — it is the foundation the whole wedding sits on. Build it right once, and it works for you until the last dance.
Questions and answers
How do you start building a wedding guest list?
Start with a target range derived from your budget — every guest is a plate the venue bills for. Then sort the names with the two-circles exercise: the must circle, people the wedding simply cannot happen without, and the joy circle, people you love imagining on the dance floor. A name that fits neither circle probably doesn't need a row.
Who decides who is on the guest list — the couple or the parents?
The couple sets the frame: the overall range and the rules, such as the plus-one and kids policy. Within it, each set of parents gets a defined quota of seats and decides for themselves who fills it — a quota, not a veto. That keeps the negotiation about numbers and principles rather than specific names.
Is a wedding B-list a good idea?
Usually not. Guests share WhatsApp groups, and the invitation is discussed the day it goes out — anyone who receives theirs two weeks after everyone else works out they were on the waiting list. Close a list slightly below your target instead, keep a small margin for genuine additions, and send everyone in the same wave.
How should you structure the guest list spreadsheet?
One row per household — that is, per invitation — with one mobile number and no duplicates. Give each row a side (his, hers or shared), a group such as family, army or work, and an expected party size. That exact structure later drives the invitations, reminders, seating and meal counts — and an RSVP system can import it as it is.