Guest List Management in 2026: How to Build, Split and Track Guest Lists by Function (Free Tracker)

Most guest list advice assumes one list, one party, under 50 people. It works right up until your event has a ceremony at 2 p.m. and a reception at 6 p.m. with different people in the room, or until the list crosses 150 names and "who did I already ask?" stops being a joke.

This guide handles both. It gives you the arithmetic for how many invitations to send, the A-list and B-list method for cutting a list without insulting anyone, the per-function split that turns one messy list into two or three real headcounts, and an actual tracker you can copy out of this page into a spreadsheet. Not a paragraph telling you a tracker would be a good idea. The tracker.

Key takeaways

• Invites needed equals your target attendance divided by (accept rate × show-up rate). For a casual party at a 60 percent accept rate and an 85 percent show rate, hitting 20 bodies takes about 39 invitations, not 30.
• A flat "over-invite by 50 to 60 percent" rule is safe for a casual party and dangerous for a wedding. At an 85 percent accept rate, 194 invitations produce roughly 165 acceptances for a room that seats 125.
• One event with three functions is three headcounts, not one list with footnotes. Track ceremony, reception and brunch in separate columns from the first name you write down.
• Capture "number in party" per household rather than counting names. A four-person household is one invitation, one address, one reply and four chairs.
• Never send a B-list invitation less than three weeks before a formal event. Inside that window the timing itself is the message.
• Your reusable guest list is an asset, not a memory. On Lumhe you find guests by name, phone number or email inside the app and connect with them, so your circle carries into the next event instead of living in a phone note you retype.

The four jobs of guest list management

Guest list management is four separate jobs most people try to do in one place, which is why it falls apart.

Sizing and selecting are decisions. Splitting and tracking are systems. If your guest list is stressing you, work out which of the four is failing before you shop for a tool, because a tool only fixes the last two.

How many people to invite, by event type (including 150 to 600 guests)

Pick your target attendance before you write a single name, because it sets your venue, your budget and your menu, and changing it later breaks all three. Here is the range per format, and what actually changes at each size.

Notice where most guides run out. Mixily's guest list post tops out at a 30 to 50 person house party, and its own published plans list a free tier capped at 50 invites and 40 RSVPs per event (Mixily's pricing page as of 21 January 2026; re-verify before relying on it). Fine for a house party. Not the range where guest list management gets hard. That starts at about 120 guests and two functions, where the list stops being something you can hold in your head.

What to do first at 150 guests and up

Three moves, in this order.

1. Get the capacity number for every function before you list anyone. Ceremony seats, reception covers, brunch table count. These are hard ceilings.
2. Decide the function structure. Two functions, three, five. Write them down as columns, today.
3. Build the list by household, not by person. A 300-guest wedding is usually 130 to 170 households. That is the number of invitations you send and the number of replies you chase.

The invite formula: over-inviting without blowing your capacity

The rule you have read everywhere is "over-invite by 50 to 60 percent." Mixily states it directly: to get 20 people, invite 30 to 32. The problem is visible in their own next paragraph, which says that of 30 invitations, about 20 say yes and 15 to 18 actually turn up. So the rule is calibrated to produce 20 acceptances, not 20 guests in the room. You wanted 20 in the room.

Use two rates instead of one, because two things happen in sequence.

For 20 people at a casual weekend party, at a 60 percent accept rate and an 85 percent show rate: 20 ÷ (0.60 × 0.85) = 39 invitations. Not 30.

Planning assumptions by event type

These are planning assumptions for sizing an order, not survey data. Use them until you have two events of your own history, then use your own numbers.

Where a flat over-invite rule becomes expensive

Take a reception room that seats 125 and apply a blanket 55 percent over-invite: you send 194 invitations. At an 85 percent accept rate, normal for a wedding where save-the-dates went out months earlier, that is roughly 165 acceptances. You are 40 people over a hard cap, and there is no polite way to withdraw an invitation. Over-inviting works for events where people decline freely and the room absorbs the variance. It fails on capacity-constrained events.

The guardrail: never send more invitations than your maximum capacity, unless you can honestly plan for the room to be full. If your formula says to send more than the room holds, tier the list instead. That is what the B list is for.

The A-list and B-list method

Tier your list before you cut it, because a tiered list can be released in waves and an untiered list can only be argued about. Write every household into one of three tiers.

How to release a B list without anyone noticing

The B list gets a bad reputation because people run it badly. Four rules make it invisible.

1. Send the first wave early. A-list invitations go out at the front of your normal window: 6 to 8 weeks for a party, 8 to 12 weeks for a wedding after save-the-dates.
2. Set the A-list reply deadline early enough to leave a release window. If your caterer needs numbers 14 days out, set the A-list deadline at 5 to 6 weeks out. The gap is where wave two lives.
3. Never send a B-list invitation inside three weeks of a formal event. Inside that window the timing itself tells the guest what happened. For a casual party, one week is the floor.
4. Keep the invitation identical. Same wording, same design, same channel. Nothing gives away a second wave faster than a different-looking invitation.

Release math for a 125-seat reception

You end at 124 for a 125-seat room, with the decision made in three controlled steps instead of one hopeful send. Our step-by-step party planning guideapplies the same tiering logic to smaller gatherings.

Splitting one guest list into per-function lists

If your event has more than one part, it has more than one guest list, and treating it as one list with a verbal footnote is the most common cause of a wrong headcount. A function is any part of your event with its own date, time, venue and guest list. Most celebrations have between two and five.

Common function structures

The three-list pattern that covers most events

Almost every multi-function celebration resolves into three groups.

• The all-functions inner circle. Present at everything, usually 15 to 30 percent of the list. They need the full schedule and the most logistics.
• The main-function list. The reception, the party, the big room. Your largest number, and the one your budget hangs on.
• The single-function guests. Invited to exactly one part. They need one date, one time, one address, nothing else.

Write those three groups as columns and the ambiguity disappears. A guest on the reception list and not the ceremony list is not a difficult conversation. It is a cell.

Why an invitation with a note in it does not work

"Ceremony is family only, reception starts at 6" inside one invitation asks every guest to work out which category they are in, and some will guess wrong. It also gives you one RSVP for two events, so a yes tells you nothing about who is standing in the ceremony room.

This is the mechanic Lumhe is built around. You add each function as its own sub-event inside one event, with its own date, time, venue and guest list, and each function has its own RSVP. Different guests are invited to different functions, so the ceremony list and the reception list are two lists and two live headcounts, not one list with an asterisk. The guest sees only what they are invited to.

Plus-ones, families and household invitations without ambiguity

Decide the plus-one policy before you send anything, then write it into the invitation, because ambiguity always resolves into a text you have to answer 24 hours before the event.

The policy by event size

Plus-one etiquette for hosts: four rules

1. Name the plus-one when you know the name. "And guest" is a placeholder that invites a person you never agreed to. A named invitation also reaches the right person.
2. Be consistent inside a group. If three of five friends get plus-ones and two do not, that will be discussed. Draw the line by relationship status or by tier, never by convenience.
3. Apply the same rule to kids, explicitly. "Adults only, and we completely understand if that makes it hard" is kinder than silence. If children are welcome, ask for names and ages, because that is a high chair and a different meal.
4. Ask for the number, not the intention. "How many in your party?" produces a number you can cook for. "Are you bringing anyone?" produces a maybe.

Track households, not names

One row per household, with a "number in party" column. A four-person household is one invitation, one address, one reply and four chairs. Counting names instead of households is how hosts end up sending four invitations to one mailbox and chasing four replies that were always going to arrive together.

Building a guest list you keep instead of a note on your phone

The best idea in most guest list articles is also the one they leave you to do by hand: keep a running list so your next event starts from a built list rather than a blank page. Mixily's version says it plainly, and the recommended method is a note on a phone with event name, date and who came, growing into a list of about 60 reliable people over a year (Mixily states this as personal practice, not data).

The idea is right. The implementation is the problem. A phone note is not a guest list, for four reasons.

What a persistent guest circle does instead

This is where Lumhe works differently by design. Lumhe has a built-in people network: you find guests by name, phone number or email inside Lumhe, send a connection request, and invite them directly from the app. Nothing is retyped. Your celebration circle compounds across every event you host, so the graduation party you plan next spring starts from the list your engagement party built, with the contact details already attached. Every invitation also generates a shareable link for WhatsApp, iMessage, Instagram or email, which is the right tool for the cousin who is not on the app yet.

What to record after every event

Whatever tool you use, capture five things while the event is fresh. Ten minutes now saves an hour next time.

Field 2 is the one people skip and the one that pays. Two events in, you know your own accept and show rates, and you can stop using anyone else's planning assumptions, including the ones in this article.

Tracking RSVPs per function in real time

A guest list becomes a headcount only when replies land in one place, per function, and update themselves. Everything else is transcription.

The three states, and the fourth column that matters

Every household sits in one of three states per function: invited and not replied, yes with a number, or no. The fourth column is the one hosts forget: counted as. That is your decision about the household, not their status. A guest who has ignored three contacts across two channels has a status of "no reply" and a counted-as of zero, and the caterer needs the second number.

Nudge non-responders only

Send your reminder to the people who have not answered, per function. Almost nobody does it, because a group email cannot segment. A guest who already replied yes and gets a third "are you coming?" learns that your messages do not require reading, which is the behavior you cannot afford in the final week.

On Lumhe, RSVP tracking is per function and in real time, and nudge reminders go to non-responders only, for the function they have not answered. So the guest who confirmed the reception but never answered the welcome dinner gets one nudge about the welcome dinner, and nothing about the reception.

For the full escalation sequence, the segmentation by stage and 24 copy-paste reminder scripts, we have a dedicated guide on how to get people to actually RSVP. This section stops at the tracking mechanic on purpose.

Reducing no-shows: the 7-day, 3-day, morning-of sequence

Three timed touchpoints cut no-shows more than any wording change, and the standard sequence for a casual event is 7 days, 3 days and the morning of. Mixily recommends exactly this cadence and it is sound for a party. It is not enough for anything with a deposit attached.

Why the morning-of message earns its place

It converts a soft yes into an arrival, and it catches the two failures that have nothing to do with intent: the wrong date and the wrong address. Keep it to one line with the time and the place, and send it per function so brunch guests are not reading about last night's dinner.

Plan for the gap, and be gracious about it

Some acceptances will not arrive, at every event. Put the buffer in the order, not in your feelings about the list. For food, order for counted-as plus roughly 10 percent, rounded to whatever unit your caterer sells. For seating, set only the number you confirmed, because empty chairs read worse than a slightly full room. When someone cancels, answer with one warm line and nothing else. A guest who feels judged for cancelling stops replying altogether, which costs more than one empty seat.

Your free guest list and headcount tracker

Here is the tracker. Copy it out of the page and use it as-is. It is split into two linked tables sharing the household name as a key, because a table past about eight columns is unreadable on a page, while a single wide row is perfect in a spreadsheet. If you are using Sheets or Excel, skip to the CSV block and paste one row per household.

Table 1: who is on the list

Table 2: functions, RSVPs and logistics

Use a fixed vocabulary in the function columns so you can filter and count: Yes n, No, No reply, or n/a for not invited. Do not write sentences in these cells.

Table 3: the per-function rollup

This is the table you send to a caterer or a venue. Recount it weekly, and again at your deadline.

Response rate is (yes + no) ÷ people invited. It tells you how much of your list is still unknown, a different and more useful question than how many are coming.

The copy-paste CSV

Paste this into Google Sheets or Excel. In Sheets, paste into cell A1 and choose Data, then Split text to columns. One row per household, one column per function. Add or remove function columns to match your event.

How to use it without it becoming a second job

• Fill columns A to E for everyone in one sitting. Identity and tiering before contact details. This is the hour that makes the rest fast.
• After that, only touch the function columns and "last contact." Everything else is static.
• Sort by tier before your first send, then by function column before every nudge. Sorting by a function column groups your no-replies together, which is your nudge list.
• Recount the rollup weekly. A stale rollup is worse than none, because you will believe it.
• Keep the address column even for a digital invitation. It is your thank-you list, and finding 90 addresses in November is a miserable afternoon.

Where a spreadsheet stops working

A spreadsheet is a record of what you were told. It cannot collect a reply, it cannot tell you who has not answered without you checking it, and it cannot be two people's copy at once without a version argument. The break point is around 40 households or the second function, whichever comes first. After that the tracker becomes the backup and something live becomes the source of truth. On Lumhe the per-function RSVP count is the live number, and the tracker above holds the dietary needs, addresses and notes that no RSVP system captures for you.

Guest list tools compared

Judge every option on the same five questions. The two columns that matter most are the ones comparison posts leave out: whether the tool tracks RSVPs per function, and which invitation formats it accepts.

Third-party prices and caps change. Treat every figure above as a starting point to verify, not a current quote. For a longer breakdown of tracking tools, see our guide to the best RSVP tracking tools for weddings and events.

After the event: photos, thank-yous and what your list becomes

Your guest list has two jobs left after the last guest leaves, and both expire quickly.

The thank-you list. Within 48 hours, message everyone who attended, one line each. Within a week, written notes to anyone who brought a gift and to whoever set up or cleaned up. This is why the address column exists.

The photo list. This is where most events lose the evening. The pictures scatter across a group chat that scrolls away, fourteen camera rolls, and a Story that expires in a day. On Lumhe, Moments is a shared photo timeline for the event. Guests upload their photos and everything collects in one organized place. It is not a group chat and not a Story, it does not expire, and it is still there after the event ends. For a multi-function event the same timeline holds the welcome dinner, the ceremony and the brunch, so guests who came to one part can see the rest.

If money gifts are part of your occasion, Digital Lifafa handles them without you posting bank details in a group chat. You add your payment ID, whether that is Venmo, Zelle, Cash App, PayPal or a bank transfer. The guest pays from whichever app they already use and uploads the receipt, and it arrives wrapped in an occasion-themed digital envelope you open. Lumhe never touches the money.

Then close the loop on the list. Mark attended, note the real number in each party, add the line of context, and connect with anyone new inside the app. That last step is the difference between a guest list and a celebration circle. One is work you redo every time. The other compounds.

The guest list cheat sheet

Twelve rules with a number attached. This is the whole method on one screen.

Seven mistakes that cost real money

Each of these has a dollar or a chair attached.

1. Counting names instead of households. Duplicate invitations, duplicate chasing, four envelopes to one mailbox.
2. Inviting before you know your capacity. You cannot un-invite. Every decision after this one is damage control.
3. One flat list for a multi-function event. One RSVP for three functions means guessing at two of them, and catering guesses cost the most.
4. "And guest" instead of a name. You are inviting an unknown person to a meal you pay for per head.
5. Nudging everyone instead of the silent ones. Trains your whole list to ignore your messages in the week you need them read.
6. No dedicated dietary column. Allergy information arrives by text in April and is not in front of you in September.
7. Losing the list afterwards. You rebuild the same 80 names next time, and forget three who should have been on it.

The printable version

Frequently asked questions

How do you manage a guest list for an event with multiple parts?

Give each part its own list from the beginning and track a separate RSVP for each. One invitation carrying a note like "ceremony is family only" produces a single reply that cannot tell you who is standing in the ceremony room, which is exactly the number you need. Per-function tracking, whether as a spreadsheet column or live in an app, is the only version of this that produces real headcounts.

How many people should you invite to a party?

Divide your target attendance by your accept rate multiplied by your show-up rate. For a casual local party, that usually means inviting 1.6 to 2 times the number of people you want in the room: about 39 invitations to get 20 guests. For a wedding where save-the-dates have gone out, acceptance runs much higher, so the multiplier drops to 1.1 to 1.3, and over-inviting on the casual ratio will put you well over your venue cap.

What is the A-list and B-list method?

It is tiering your list into an A list that is always invited, a B list released in waves as A-list declines arrive, and a C list of courtesy invitations sent only if the numbers still allow. It lets a capacity-capped event fill the room without sending more invitations than the room holds. Done properly it is invisible: identical invitations, same channel, and nothing sent inside three weeks of a formal event.

How do you handle plus-ones as a host?

Set one rule by relationship status or by tier, apply it consistently inside every friend group, and write it into the invitation. Name the plus-one whenever you know the name, because "and guest" invites a person you never agreed to feed. Then ask for a count rather than an intention: "how many in your party?" returns a number you can cook for.

How do you deal with no-shows?

Assume some acceptances will not arrive and put the buffer in your order, not your expectations. Order food for counted-as plus about 10 percent, and set seating only for guests you confirmed. Reminders are the biggest lever: three touchpoints for a casual party, five for a wedding, with a day-before confirmation per function. When someone cancels, reply with one warm line, because a guest who feels judged for cancelling stops replying altogether.

What should a guest list tracker include?

Household name, number in party, relationship, group or side, tier, contact, mailing address, invite-sent date, one column per function, plus-one name, kids and ages, dietary needs, last contact with channel, a counted-as decision and notes. The two hosts leave out and regret are mailing address, which becomes the thank-you list, and counted-as, which is your decision rather than the guest's status. The tracker and CSV above include all of them.

Can you reuse a guest list for the next event?

Yes, and it is the highest-leverage habit in hosting, but only if the list holds contact details rather than names alone. A note listing who came is a memory aid, because you still have to find each person in your contacts again. Lumhe's built-in people network is the alternative: find guests by name, phone number or email, connect with them, and your celebration circle carries into every event you host afterwards.

What is a realistic RSVP response rate to plan around?

Track response rate as (yes plus no) divided by people invited, and expect 80 to 95 percent of a well-run list to answer by your deadline. The silent remainder is a decision, not a mystery: after three contacts across two channels, count them as zero. Every rate here is a planning assumption for sizing an order, not survey data.

Planning a celebration with more than one function? Upload the invitation you already made to Lumhe, whether that is an image, a video, a PDF or typed text, then find and connect with your guests by name, phone number or email inside Lumhe and send it to them directly. Add each function separately, so the ceremony and the reception have their own guest lists and their own RSVPs, and you always know the headcount for each one. Reminders go only to the guests who have not answered, for the function they have not answered. After the event, everyone's photos collect in Moments, a shared timeline that does not expire. Guests who want to send money instead of a gift can do it through Digital Lifafa: you add your payment ID, they pay from whichever app they already use and upload the receipt, and it arrives wrapped in a digital envelope you open. Lumhe never touches the money. You can also share your invitation link on WhatsApp, iMessage, Instagram or any other platform. Explore Lumhe.

SEO Keyword Map