Guest List Etiquette

The guest list is where budget, family dynamics, and venue capacity all collide at once, which is exactly why it's worth building deliberately rather than just writing down everyone you can think of and seeing what the number comes to.

Start with a cap, not a wish list. Decide your realistic maximum - based on budget and venue capacity - before you start naming people, not after. Building an aspirational list first and cutting it down later is genuinely more painful than starting from a number and filling it in, because every cut then feels like a rejection rather than a plan.

A tiered approach helps with fairness questions. Group potential guests into rough tiers - must-invite, would-like-to-invite, invite-if-numbers-allow - agreed jointly between both of you and, if they're contributing financially or the list includes their side heavily, both families. This gives you a structured way to trim from the bottom tier if numbers run over, rather than making it up ad hoc under pressure.

On splitting the list between families and friends: an even split by side isn't a rule, just a common starting point - the right split depends on your actual circle and relationships, not a fixed formula. What matters more is agreeing the approach explicitly with both families early, especially if parents are contributing financially and have their own must-invite names in mind.

On evening-only guests: inviting a wider group to the evening reception but not the full day (see the wedding breakfast for how this affects catering) is a well-established and genuinely useful way to include more people without inflating your formal-meal budget. Be clear and consistent in how you communicate this - see invitation wording - since inconsistent messaging about who's invited to what is the single most common guest-list etiquette complaint.

On plus-ones and children: decide these as blanket policies, not case-by-case exceptions, for the same reason as splitting by family - consistency reads as fair even to guests who don't get the answer they wanted, while visible exceptions read as favouritism regardless of your actual reasoning.