Give every guest two tags as you add them: a group and a side. Those two tags are what turn three hundred names into something you can ask questions of, because the question is never “show me everyone”. It is “who from his office has not replied”, and a flat list cannot answer that.
The questions a guest list has to answer
You open your guest list for a reason, and the reason is almost always a slice of it rather than the whole thing. In the weeks between sending and the wedding, the same handful of questions come round again and again:
- Who from his office still has not opened their invitation?
- How many people on her side have accepted, because the top table has to balance?
- Which family members have we not sent the link to yet?
- Who are the neighbours, so we can seat them together?
- His mother is asking about her own relatives. Can you get down to just those in a moment?
A flat list answers none of them. It gives you one control, which is scrolling, and one skill, which is remembering. That works at forty names. At two hundred and fifty it does not, and it stops working in the week you are chasing replies and have the least patience for it.
Group and side are two different questions
The group says what these people are to you: family, friends, office, neighbours and so on. The side says whose people they are, the bride’s or the groom’s or both. They are separate fields on the guest, and neither one interferes with the other.
That independence is the point, and it is the thing couples most often undo without meaning to. Given one label, people invent compound ones: His Office, Her Office, His Family, Her Family. The vocabulary doubles, every new guest becomes a two-part decision, and you still cannot ask for every colleague across both families. Tag someone as office and as the groom’s side instead, and three questions open up: his office, everyone on his side whatever their group, and every colleague on both sides. Two tags, no compound labels.
Tag as you add, not afterwards
This is the only discipline that matters here, and it is worth more than any clever scheme. Setting a group and a side while you add a guest costs a second, because you already know the answer. You are adding them because you just thought of them, and you thought of them as your cousin, or as somebody from work. Doing it later costs the same second plus finding the guest, opening them and saving them, one at a time. There is no way to retag fifty rows in one go.
So add in batches that share a tag. Sit down once and put in his office, all of them, then do her family later the same way. The add page takes as many rows as you need in one sitting, and each row carries its own group and side dropdown. Nothing is copied down from the row above, so you set the pair on every line, but setting it while your head is already inside one group takes no thinking. Setting it name by name, weeks apart, is where wrong tags come from.
Decide once what each group means at your wedding, and tell whoever else is adding names. Does a former colleague you now count as a friend go in office or in friends? There is no correct answer. There is only an answer the two of you both use. Tagging that quietly changes meaning halfway down the list is worse than no tagging at all, because it looks reliable.
What the tags buy you later
Sending is the first payoff. The invitation goes out one chat per guest, one tap each, and three hundred of those is an evening with no edges. Filter to one group and the sitting has a shape: his office is the office, you work down it, and then it is finished for the night. Side splits the evening between the two of you the same way. One of you works down his side while the other works down hers, and neither has to remember where the other stopped, because each guest carries a sent marker that flips as the chat opens.
Chasing is the second. Set the group to office, add the delivery and reply state you are after, and the follow-up list is on screen. Delivery is one choice at a time rather than a stack, so “not opened” also catches the guests you never sent to; the sent marker on the row is what tells the two apart. This matters because the message differs. What you write to his aunt who has not replied is not what you write to her colleagues, and keeping the two lists apart means you write each message once.
Then seating. The seating screen filters the guests you have not placed yet by side, by group and by reply state, which is roughly how tables get built anyway. A table is usually a group. The neighbours near the door, the university friends together, the aunts where they can see everything.
And counting, with one caution. The head count above the list follows whatever filters are on, so narrowing to her side gives you the heads invited on her side. Read it as heads invited, not heads coming. The response tiles higher up the page count the whole list and do not narrow with the group and side filters, so if you want accepted numbers for one group, take the export. The downloadable list covers exactly the rows you filtered to and carries the group and the side as columns, so a coordinator or a venue gets the structure rather than a wall of names.
When two tags are not enough, and when they are too many
Both happen, and it helps to know which one you are.
If your list is sixty people and you know every one of them by heart, the tagging will not earn its keep. Search for a name, find the person, carry on. Tag the sides if the two families are chasing separately, and leave the groups at their defaults.
At the other end, some weddings divide along a line that is neither group nor side. Village and city. The people you owe an invitation to and the people you want there. Your father’s colleagues as distinct from your own. Two tags cannot express a third axis, and bending the group vocabulary to fake one will cost you more than it returns, because from then on the groups mean two things at once. If that is your situation, be plain about it. Use group and side for what they describe, keep the third division in a spreadsheet of your own, and do not force it into a field that was not built for it.
Frequently asked questions
Which side do mutual friends go on?
Both, for most of them, and it is worth knowing what that means when you filter. Both is its own value, so a guest tagged both does not appear when you ask for the bride's side alone. If a friend will genuinely sit with one family on the day, tag them to that side instead, because seating is where the tag does its real work.
Can I make up my own group names?
No. The groups are a short fixed list, which is what stops the vocabulary drifting when two or three people are adding names to the same list. If none of them fits a set of guests, put those guests in the catch-all group and use the side to separate them, or accept that this particular division lives in your head rather than in the list.
Do guests see their group or side?
No. Both tags are for you. A guest opening their invitation sees the invitation, not how you have filed them, so you can be as blunt as you like when you tag.
Related: The guest list manager