Loading Forever Farrah…
A tiered method for cutting a wedding guest list, the rules that make the cuts feel fair, and what to say when someone asks why they weren't invited.
Sort everyone into three tiers (must invite, want to invite, would be nice), then cut from the bottom tier up using rules that apply to everyone, such as no plus-ones for single guests or no colleagues. Rules are easier to explain than individual decisions, and they stop the cutting turning into a debate about each person. Agree the rules with both families before anyone sees a list.
Weddings are feeling expensive on both sides of the invitation. In a 2024 LendingTree survey of 2,025 US adults, 89% of wedding guests agreed that weddings and wedding-related events are getting too expensive. For couples, guest count is usually the single biggest cost driver, because food, drink, chairs, tables and invitations all scale with it.
Guest list tiers: A: must invite, Immediate family, grandparents, wedding party, closest friends, You'd rather not have the wedding than not have them; B: want to invite, Extended family you're close to, good friends, partners of A guests, You'd notice if they weren't there; C: nice to have, Colleagues, parents' friends, distant relatives, plus-ones for single guests, You'd invite them if space and budget allowed.
Rules apply to everyone, so they're easy to explain and hard to argue with. Start with the one that removes the most C-tier names:
"If we invite one cousin we have to invite them all." Then apply a rule to the whole group. Consistency matters more than who's in it. A parent insists on a guest. If they're contributing to the budget, give each set of parents a fixed number of names, and let them choose within it. A friend group of eight where you're close to five. Groups compare notes. Either invite the whole group, or invite the five and be ready to explain the line you drew. Someone invited you to their wedding. It doesn't oblige you, especially if theirs was years ago or much bigger.
A second wave of invitations can fill spaces left by early declines, but only if it's invisible. Send the first wave eight to ten weeks ahead and the second no later than six weeks, with a reply-by date that still makes sense. Never send a second-wave invitation with a reply-by date that has nearly passed, and never send one to someone who is friends with first-wave guests who might compare notes.
Keep it short, true and not about them:
Your guest list will change several times before the invitations go out. Keeping it in one place, with each guest's household and tier, stops the version-control problem of three spreadsheets and a notes app. In Forever Farrah the guest list itself is unlimited on every plan, including the free one. Plan limits apply to how many guests you seat on the seating chart, not how many you can list.
Sort guests into must-invite, want-to-invite and nice-to-have tiers, then cut from the bottom tier using rules that apply to everyone, like no plus-ones for single guests or no colleagues.
No. It's one of the most common and accepted cuts. Apply it to everyone equally, and make exceptions only for guests who won't know anyone else.
Not if they can't tell. Send second-wave invitations early enough that the reply-by date is still several weeks away.
Loading Forever Farrah…