A B-list only works if the second wave can be mailed, answered and counted before your caterer's final headcount is due — and with the common ten-day final count, the last day you can post it is 34 days before the wedding, just under five weeks. Because the second wave cannot go out until your A-list reply-by has passed, that reply-by has to sit at least five weeks before the wedding for a mailed B-list to be possible at all: the standard four-week reply-by leaves no road left. Past that date, do not mail a card that will arrive looking last-minute — invite the second wave by phone or text instead.
Work it out from one number: the day your caterer needs a final count. Subtract 24 days and you have the latest date a second wave can be posted. Then find your row.
Set the A-list reply-by six weeks before the wedding, not four. This is the only row where you have real control. Take the caterer's final-count date, subtract 24 days for the latest mailable date, then put the A-list reply-by a week before that so a slow week of post cannot sink it. Mail the A-list ten to twelve weeks out to keep the answer window comfortable.
Post the second wave tomorrow morning. You have room. Mail it the day after the reply-by date with a reply-by two weeks out, which still lands well clear of the caterer's count. Every day you spend deciding comes off the guest's answering window, not off the caterer's deadline.
Check the exact date before you buy stamps. This is the borderline. The card has to be posted, delivered, opened, answered and returned, and two of those five steps are the post office's problem rather than yours. If the latest mailable date is inside a week, hand-deliver locally and phone everyone else.
Treat six weeks as the cutoff, not five, and check the contract first. A long vendor lead time eats the second wave's window from the other end. At a 21-day count the latest mailable date is 45 days before the wedding, so even a six-week A-list reply-by can miss it by a few days. Read the clause before you plan any of this.
Do not mail. Call them, and do not explain. A printed invitation arriving three weeks out announces itself. A warm phone call at the same distance does not — plenty of people are invited late for perfectly ordinary reasons. Say you would love them there, give the date and the time, and ask them to let you know within the week.
Send nothing. Four free seats is two couples, and inviting two couples out of a held list of fifteen is where B-lists get discovered — the fourteen who never heard from you all know each other. If the freed seats will not cover a coherent group, keep the seats empty and spend the money on the bar.
Four complete schedules where the arithmetic works. Each one runs A-list reply-by → declines → seats freed → mail date → B-list reply-by → the caterer's count, and shows how many days of slack are left over. Copy the shape and swap your own dates in.
Mixed guest list · caterer needs the count 10 days out · Wedding day: September 12 · A-list reply-by: August 1 (6 weeks before the wedding) · Declines in hand on August 1: 14 households · Seats freed: 31 · Mail the second wave: August 2 · B-list reply-by: August 16 · Caterer's final count: September 2 · Latest mailable date: August 9 Verdict: mailable, with 7 days of slack. Address and stamp the envelopes in July so they can go in the box on the 2nd.
Mostly local list · caterer needs the count 7 days out · Wedding day: June 20 · A-list reply-by: May 16 (5 weeks before the wedding) · Declines in hand on May 16: 9 households · Seats freed: 19 · Mail the second wave: May 17 · B-list reply-by: May 31 · Caterer's final count: June 13 · Latest mailable date: May 20 Verdict: mailable, but only 3 days of slack. A local list is the one case where you can hand-deliver the stragglers instead of trusting the post.
Mostly traveling list · caterer needs the count 14 days out · Wedding day: October 3 · A-list reply-by: August 15 (7 weeks before the wedding) · Declines in hand on August 15: 22 households · Seats freed: 44 · Mail the second wave: August 16 · B-list reply-by: August 30 · Caterer's final count: September 19 · Latest mailable date: August 26 Verdict: mailable, with 10 days of slack. A traveling list declines more, so more seats free up — and it needs the earlier reply-by anyway, which is what created the room.
Destination wedding · caterer needs the count 21 days out · Wedding day: February 13 · A-list reply-by: December 5 (10 weeks before the wedding) · Declines in hand on December 5: 26 households · Seats freed: 52 · Mail the second wave: December 6 · B-list reply-by: December 20 · Caterer's final count: January 23 · Latest mailable date: December 30 Verdict: mailable, with 24 days of slack. Destination weddings have the most comfortable B-list window of all — but give the second wave three weeks to reply rather than two, because they are booking flights on shorter notice than everyone else.
The B-list decision needs one number on one day: how many seats are free the morning your reply-by passes. Text My Wedding keeps the yes, no and silent counts current as replies land, so the answer is on screen instead of somewhere in a shoebox.
Declines arrive as households; seats free up as people. A household of four declining is not the same event as two couples declining, and the B-list you hold has to be shaped like the seats you get back — not like a ranking of your friends.
Sizing a mixed list of 120 guests across 55 households · Planning estimate: about 18% decline, so roughly 22 seats come back · Average invited party: 2.2 seats per household · So expect around 10 households to say no · B-list to hold: 10 to 12 households, not 20 · A-list reply-by: June 6 (6 weeks before a July 18 wedding) · Mail the second wave: June 7 · B-list reply-by: June 21 · Caterer's final count: July 8 · Latest mailable date: June 14 Verdict: mailable. Hold roughly as many households as you expect declines, and accept that some of the second wave will decline too.
When one household frees six seats · Wedding day: May 16 · caterer's count 12 days out · A-list reply-by: April 4 (6 weeks before the wedding) · Declines: 7 households, one of them a family of six · Seats freed: 17, but 6 of them are in a single block · Mail the second wave: April 5 · B-list reply-by: April 19 · Caterer's final count: May 4 · Latest mailable date: April 10 Verdict: mailable, 5 days of slack. Fill a six-seat block with a family or three couples who already know each other — a table of strangers assembled from the leftovers is the version guests notice.
When fewer decline than you planned for · Wedding day: August 29 · caterer's count 10 days out · A-list reply-by: July 18 (6 weeks before the wedding) · Expected declines: 11 households · Actual: 4 · Seats freed: 9 · B-list held: 14 households — far more than the seats justify · Mail the second wave: July 19 to 4 households only · B-list reply-by: August 2 · Caterer's final count: August 19 Verdict: mailable, but send four, not fourteen. The ten you do not send to are the risk, so pick the four with the least overlap with the rest of the list.
Matching the wave to the seat shapes you got back · Wedding day: April 25 · caterer's count 14 days out · A-list reply-by: March 7 (7 weeks before the wedding) · Declines: 12 households — 8 couples, 3 singles, 1 family of four · Seats freed: 23 · Second wave posted March 8: 7 couples, 3 singles, 1 family of three · Seats invited in the second wave: 20 · Held back: 3 seats of headroom · B-list reply-by: March 22 · Caterer's final count: April 11 Verdict: mailable, 10 days of slack. Invite slightly fewer seats than you freed — a second wave that overshoots leaves you telling someone there is no room after they have already said yes.
These are the three ways the window closes. In every one of them the honest answer is that the arithmetic no longer works — so the schedule ends in a phone call, not a stamp. A late card is what makes a B-list visible; a late phone call almost never does.
The standard four-week reply-by — the most common miss · Wedding day: May 9 · caterer's count 10 days out · A-list reply-by: April 11 (4 weeks before the wedding) · Earliest you could post the second wave: April 12 · Latest mailable date: April 5 · Caterer's final count: April 29 Verdict: too late by 7 days, before a single decline arrived. A four-week reply-by is perfectly good advice for a wedding with no B-list, and it forecloses a mailed second wave entirely. Invite by phone from April 12.
You had the room and spent it deciding · Wedding day: September 19 · caterer's count 10 days out · A-list reply-by: August 15 (5 weeks before the wedding) · Latest mailable date: August 16 — one clear day · You finished counting declines and agreed the list: August 28 · A card posted August 28 would want a reply by September 11 · Caterer's final count: September 9 Verdict: too late by 12 days, and the reply-by would have landed after the count. Decide who is on the B-list before the A-list reply-by, not after it.
A long vendor lead time closes the window early · Wedding day: August 22 · caterer's count 21 days out · A-list reply-by: July 11 (6 weeks before the wedding) · Earliest you could post the second wave: July 12 · Caterer's final count: August 1 · Latest mailable date: July 8 Verdict: too late by 4 days, even at six weeks. When the count is due three weeks out, the A-list reply-by has to sit seven weeks out for the post to work. Phone the second wave on July 12 and ask for an answer by the 26th.
A B-list is a scheduling decision you make before the invitations are printed, not a rescue you attempt afterwards. These three schedules show the stagger that creates the window, how to run two small waves instead of one big one, and what to do when a table empties nine days before the count.
Planning the stagger backwards, before anything is printed · Wedding day: November 7 · caterer's count 10 days out · Caterer's final count: October 28 · Latest mailable date: October 4 (the count minus 24 days) · So: A-list reply-by September 26 (6 weeks out), a week of slack · Mail the A-list: August 15 (12 weeks out) — a 6-week answer window · Mail the second wave: September 27 · B-list reply-by: October 11 Verdict: mailable with 7 days of slack, designed in from the start. Note the A-list still gets six weeks to reply — the stagger costs them nothing, it just moves the whole chain earlier.
Two small waves instead of one big one · Wedding day: October 17 · caterer's count 10 days out · A-list reply-by: August 29 (7 weeks before the wedding) · Wave two posted August 30 to 8 households · reply-by September 13 · Declines from wave two: 3 households, 6 seats back · Wave three posted September 13 to 3 households · reply-by September 27 · Caterer's final count: October 7 · Latest mailable date: September 13 Verdict: both waves mailable, with wave three going out on the last possible day. Two small waves fill more seats than one large one, but only a seven-week reply-by buys you the second turn.
A family drops out nine days before the count · Wedding day: June 13 · caterer's count 10 days out · A-list reply-by: May 2 · second wave already posted May 3 · May 25: a household of four cancels — 4 seats back · Caterer's final count: June 3 · Latest mailable date was May 10 Verdict: nothing to post. Ring two couples the same evening, tell them plainly you would love them there and that you need to know by Friday, and give the caterer the number on June 3 either way. Never say a space opened up — say you are so glad they can come.
The reason B-lists fail is almost never etiquette. It is that couples treat all five of these as one flexible deadline, when three of them are imposed from outside and cannot move at all.
You do, and it decides everything else · five to seven weeks before the wedding if you want a mailed B-list, versus the usual three to four. Set it too late and there is no B-list to have — the second wave cannot leave before this date has passed, so a four-week reply-by kills the option before a single reply arrives. This is the one date on the page you should choose deliberately.
Your catering contract, not you · typically seven to twenty-one days before the wedding. Every other date here is measured backwards from this one, and it is the only genuinely hard deadline in the chain. Read the clause before you plan a second wave: a 21-day count costs you eleven days of B-list window compared with a ten-day one.
Nobody — it is arithmetic · 24 days before the caterer's final count. Post after it and the reply physically cannot get back to you in time to count. The 24 days is a two-week reply window plus ten days for the post in both directions and an evening to tally. Miss it and the answer is a phone call, not a later card.
You do, but you have almost no room · two weeks after the second wave is posted. Give them longer and it crosses the caterer's count; give them less and you will spend the difference chasing. Two weeks reads as completely normal to a guest — plenty of invitations arrive five weeks out.
Your guests, as their declines arrive · mostly in the last ten days before the A-list reply-by. You cannot invite against seats you do not have yet, and you cannot un-invite. Count the freed seats once, on the reply-by date, and invite slightly fewer than you counted.
Two numbers on this page come from elsewhere in the cluster. How many declines a list your size should expect — and therefore how many seats a second wave has to fill — is worked out on the wedding attendance rate page, and the vendor deadline every date here is measured backwards from is set out in when the final headcount is due. Tiering the list in the first place — deciding which households are A, B and C before anything is mailed — is a different job from timing the second wave, and it is worked through on cutting the wedding guest list down. Once the second wave is in the mail, chasing it is the same job as chasing the first, so use automatic RSVP reminders rather than inventing a separate follow-up. The card itself must repeat the first round's copy word for word with only the date changed — see RSVP card wording — and if the A-list replied by scanning a QR code on the reply card, the second wave has to carry the same code to the same page, because a different reply route is the detail guests compare.
B-lists are common and there is nothing wrong with holding one. Every problem people attribute to B-lists is actually a problem of being found out, and being found out is a logistics failure rather than a moral one.
Order 20–25% more invitations than the A-list needs, at the same time, from the same print run. A reprint is a different paper batch and a visibly different ink weight, and it takes two to three weeks you no longer have.
Addressed, stamped, sealed, sitting in a drawer. The second wave has to be capable of going in the mailbox the morning after the A-list reply-by, because the days you spend addressing come out of the guest's answering window.
Same suite, same enclosures, same envelope, same handwriting, same reply mechanism. If the first round had a printed reply card, so does this one — a second wave that says “just text us” when everyone else got a card is the mismatch that gets discussed.
No “we had a cancellation”, no “a space opened up”, no “we finally got the numbers”. There is no version of that sentence that reads well, and none of it is necessary — invitations arrive at different times for a hundred boring reasons.
The fastest way for a B-list to be discovered is a bridesmaid, a parent or a group chat, not the postmark. Two people should know it exists, and neither of them should mention it at the rehearsal dinner.
Holding a second wave is normal and it is fine. It stops being fine when a guest can tell, and there are only a handful of ways they ever can. Here is what gives it away, and one thing that genuinely is a bad idea rather than just a risk.
This is the single most common tell. Guests talk, and “ours said reply by the 16th” against “ours said the 1st” is a two-second conversation. It is unavoidable — the compressed window is the whole mechanism — which is why nothing else about the card may differ.
A second print run, a leftover envelope in a slightly different cream, a plain stamp where the first round had a custom one. People keep wedding invitations on the fridge for months and compare them at the shower.
“We had a cancellation and thought of you” tells the guest exactly where they stood, in writing, forever. Say nothing about timing at all. If someone asks outright, “the list took us ages to finish” is true of every wedding.
At that distance the invitation is racing the save-the-dates other people posted eight months ago, and the guest has already seen the wedding mentioned online. Past the latest mailable date, phone instead — a call at three weeks reads as warm, and a card at three weeks reads as an afterthought.
If you are holding twenty households against an expected ten declines, half of that list will never hear from you, and they all know each other. Hold roughly as many as you expect to free up, not as many as you wish you could invite.
This is the one that is not just a visibility risk. If a household would be awkward at the table, they are not a B-list, they are a no. The second wave is for people you genuinely wanted and could not fit, which is also why it almost never reads as an insult when it stays invisible.
Freed seats are not filled seats. Second waves decline at least as often as first waves and often more, because they are answering on short notice. Give the caterer the number you have actually confirmed, never the number you hope to confirm.
Enter your wedding date, your A-list reply-by and the day the caterer needs a final count. It returns the last date you can post a second wave, the reply-by that wave gets, and a straight yes or no on whether there is still time — including an honest “too late to post” when there is not.
Check whether there is still time to mail a second round of invitations, and the last date you can post them.
Leave it blank and every answer below still works — you just get “four weeks before the wedding” instead of a printed date.
The common case: a local core plus a scattering of guests who need a flight or a hotel.
A mix lists usually sit around 4 weeks.
Read it off your catering contract — 7 to 14 days is typical.
Private by design: every date and number here is worked out in your browser, and the dates and counts you enter never leave this page. We count anonymous usage — which mode people pick, nothing they type. Close the tab and it's gone, so copy your dates somewhere safe.
Your second wave
Second wave
Every B-list date hangs off the first reply-by date, and the last one is set by your caterer.
The second wave cannot move until this date has passed and you know how many declines you have.
Same suite, same wording, new reply-by date. Never mention that a first round went out.
A shorter window is fine and does not read as rushed — plenty of invitations arrive four weeks out.
Later than this and the reply cannot land before you have to give the caterer a number.
Have the second-wave envelopes addressed and stamped before the first reply-by date so they can go out the next morning.
Decline, reply, and no-show rates here are planning estimates built from the ranges wedding vendors publish — useful for sizing a list, not a survey result.
No, and it is far more common than anyone admits — venues have fixed capacity and guest lists do not. The etiquette failure is not holding a second wave, it is letting a guest work out that they were on it. Keep the stationery, wording and reply method identical, change only the reply-by date, and never explain why the invitation arrived when it did.
The morning after your A-list reply-by date, and no later than 24 days before your caterer's final count. With a ten-day final count that puts the last mailable date 34 days — just under five weeks — before the wedding. Past that, the reply cannot get back to you in time to be counted, so invite by phone or text instead of posting a card.
Roughly the number of households you expect to decline, not the number you wish you could invite. On a mixed list of about 120 guests you might expect around 18% to decline — 20-odd seats, or about ten households at an average party of just over two. Holding twenty households against ten expected declines means half of them never hear from you, and they usually all know each other.
Only if you let them compare notes and find a difference. The reply-by date is the one thing that has to differ, so everything else must match exactly: same print run, same envelope, same enclosures, same reply route. The other common leak is people, not paper — keep the list between the two of you.
Two weeks from the day the invitation is posted, or three for guests who need flights. A shorter window does not read as rushed — plenty of invitations legitimately arrive four or five weeks out — and anything longer will collide with your caterer's final count.
Phone them. A call three or four weeks out sounds warm and slightly informal; a printed invitation at the same distance announces that it is late. Say you would love them to come, give the date, the time and the place, and ask for an answer within the week so you can make the caterer's deadline.
Yes, and there is no way around it. The second wave is posted after the first reply-by has passed, so it needs its own compressed date roughly two weeks out. That single difference is the only thing about the card that should change — matching it to the original date would leave guests with a deadline that has already gone.
Text My Wedding sends the invitation by text, records every RSVP against the right household, and nudges the ones who go quiet — so your caterer gets a number instead of a guess.
