Search for an invitation timeline and you get a number of weeks with nothing behind it. No workings, no way to tell whether it meant a wedding for two hundred or a curry for eight.
So this one shows the workings: four gaps, each with a reason, that add up to your own number. Do it once and you will not need a chart again.
Everything counts back from your numbers day
Not from the party. From the day you must give a headcount to somebody who charges you for it: the caterer, the venue that wants a minimum spend, the restaurant, the coach hire. That is your numbers day. Write it down first.
If nobody is charging you per head, you do not have one, and your timeline collapses to almost nothing. Drinks at home, a picnic, a pub garden: nobody is committed to a number, so extra notice buys nothing. Which is why a borrowed timeline feels absurd for a small party. Its gaps are not the ones you have.
The four gaps
Your lead time is the sum of whichever of these apply.
Gap one, your admin. Between your RSVP deadline and your numbers day. It exists so you can count replies, sort plus-ones, collect dietary requirements and follow up holdouts. On a list of twenty that is an evening. On a hundred and fifty it is not, and squeezing it costs you the buffer.
Gap two, their decision. Between sending and your RSVP deadline. Not politeness: it is the time it takes an adult to check a shared calendar, ask the person they would be coming with, and find out whether anyone can have the kids. In most households that conversation happens when both people are in the same room, unhurried, which gives the gap a floor. It wants one full weekend inside it, two if childcare or leave is involved.
Gap three, their booking. Only if money or time off must be committed before anyone can commit to you. Its length is not a rule. It comes from whatever they have to organise, which makes it a question about trains, hotel rooms and rotas rather than etiquette. Birthday announcement cards works through how to find it.
Gap four, the competition. Only for dates that compete: December, bank holiday weekends, a summer of other people's weddings. It buys no decision time, only position in a filling diary.
Add up the gaps that apply to you. If the timeline you were about to copy assumes all four, check that you have four.
Lead times by event type
- Dinner or drinks at yours. No numbers day, no booking gap. One decision gap: one weekend.
- Kids' party. A numbers day if there is a venue or an entertainer, no booking gap, but other parties competing for the weekend. Two weekends, plus your admin.
- Milestone birthday, everyone local. A numbers day if it is catered, nothing else. Two weekends, plus your admin.
- Milestone birthday, guests travelling. A numbers day, and a booking gap your guests set the length of. That gap first, then all the above.
- Engagement party. Often a numbers day, sometimes a booking gap, usually a competing date. That gap if any, plus two weekends and your admin.
- Wedding. An immovable numbers day, the longest booking gap here, every competing date going. Split it, below.
That last one is why save the dates exist. When gap three is long, holding the invitation back until every detail is settled means either sending it half-finished or leaving guests to book flights on a rumour. A save the date splits the problem: it carries the booking gap alone, and the invitation follows with the decision gap and your admin. Any event with a long gap three can borrow that.
The countdown
Two runs. The first counts backwards from your numbers day and fixes every date. The second runs forwards from send day, and ends where the first began.
Backwards, fixing the dates:
- Numbers day. Fixed by somebody else. Everything is measured from here.
- RSVP deadline, one admin gap earlier. A specific date on the invitation, ideally a weekday, so the chase that follows misses the weekend.
- Send day, one decision gap before the deadline. One condition: do not send until you can answer every question it raises, or you get questions instead of replies.
- Save the date, as soon as the date is confirmed, and only if gap three applies. It goes to guests you have no doubt about, since it commits you to inviting them.
Forwards, from the day you send:
- First chase, while the deadline can still be met. Late enough that people have had their weekend, early enough that replying is easy. A reminder, nothing more.
- Second chase, once the deadline has passed. A different job. The first asked people to remember; this one asks them to decide, individually, because a deadline going by is information. The wording for both, and for the final call nearer the party, is in how to chase party RSVPs.
- Numbers day, arriving. Anyone unaccounted for is a no. That is what the deadline was for.
- The day before, which is not a chase. A logistics message with the time, address, parking and anything to bring, and it goes to the yeses only. Send it to people who never replied and you have reopened an RSVP you closed.
Worked through for a catered 40th with nobody travelling: numbers day is the Monday before the party, your admin gap a week, so the RSVP deadline is the Monday before that, and two weekends of decision gap puts the invitation out about four weeks ahead. Change an input and the four weeks moves, which is the point.
Two failures are worth naming. A deadline sitting on the numbers day leaves the second chase nowhere to go. And an invitation carrying no reply date reads as news rather than a question, which is how a guest list goes quiet without meaning to.
Letting something else hold the dates
You can run all this from a notes app. The alternative is to set the dates once and let them fire.
With The Card Genie's Invite and RSVP, the RSVP deadline is a field on the event, each guest gets their own reply link and never signs up, invitations carry a calendar attachment, and reminders to non-repliers are scheduled. Three go out by default, at 14, 7 and 3 days ahead, and you can set up to three of your own anywhere from 1 to 90 days out, or none. Worth knowing: those intervals count back from the event date, not from your RSVP deadline, so if your deadline falls earlier, move them to match it.
Events are one flat fee, £9.99 up to 50 guests, £19.99 up to 100, £39.99 up to 300 and £79.99 up to 1,000. If you need one card rather than a guest list, an online invitation is £1.79 with an RSVP link built in, or £3.49 animated with sound, preview free and watermarked.
FAQs
How far in advance should I send party invitations?
Long enough to cover the gaps that apply, which for drinks at home is one weekend and for a catered event with travelling guests is considerably more. Find your numbers day, subtract the time you need to count and chase, then the time guests need to decide. That total is your answer, and beats any borrowed figure.
When should the RSVP deadline be?
Far enough before the day you confirm numbers that you can chase stragglers, sort dietary requirements and hand over a figure calmly. A few days on a short list, a week or more on a long one. Never the same day, or one late reply breaks it.
Is it better to send invitations earlier?
Only up to the point where you can answer everything the invitation raises. Past that, sending earlier does not get replies sooner, it gives people longer to forget. An early invitation with no deadline produces the same silence as a late one, and you will have burnt your notice for it.
What if guests reply after the deadline?
Take them if you can, and say so warmly. The deadline is not there to punish anyone, it exists so you can give a number to somebody on a fixed day. Once that number has gone in, "I would love to, but the count is locked" is a kind and complete answer.