When to Send Wedding Invitations: The Only Deadline That Matters Is in Your Venue Contract
In short
- The standard answer: save the dates 6 to 8 months out, invitations 6 to 8 weeks out, 12 weeks if there is no save the date or guests are travelling, RSVP deadline about a month before.
- Those numbers are a printing and postal schedule, not an etiquette rule. They exist because paper takes weeks to make, days to travel, and days to travel back.
- The date that actually governs you is your venue’s final guaranteed count, usually two to three weeks out and written into your contract. Every other date should be derived from it, backwards.
- Going digital does not shorten the timeline as much as people expect. What it removes is production and post; what it does not remove is the four weeks of chasing that every guest list needs.
- The number the conventional advice gets wrong is not the send date. It is the RSVP deadline, which is usually quoted a month before the wedding and should sit four weeks before your venue’s count.
Search this question and every answer agrees, which is usually a sign that nobody has checked recently. Six to eight weeks for invitations, six to eight months for save the dates, RSVPs a month out. The numbers are repeated so consistently that they read like etiquette.
They are not etiquette. They are manufacturing and logistics, inherited from a process most couples are no longer entirely using.
The standard wedding invitation timeline, and where it comes from
Work backwards through what a paper invitation has to do.
Letterpress, foil and engraved stationery run 10 to 14 weeks from artwork approval to delivery. Digital printing is faster but still counted in weeks once proofs and a reprint for the inevitable typo are included. Then addressing and assembly, which on 90 households is a full weekend. Then transit to your guests. Then the guest has to decide, find the card, find a stamp, and post it back, and that return leg is the slowest and least reliable part of the whole chain.
Six to eight weeks is what that pipeline needs to complete before your caterer starts asking questions. It is a good answer to the question “how long does the process take”. It was never an answer to the question “when should my guests know”.
That distinction matters, because if you are not doing the paper part, you have inherited a deadline structure built around constraints you do not have.
Work backwards from your venue’s final headcount date
Somewhere in your venue or catering contract is a line requiring a final guaranteed count by a specific date. In most US contracts that is two to three weeks before the event. From that moment the number is locked: you pay for every cover you guaranteed, whether or not the person arrives, and adding people afterwards is usually possible and usually surcharged.
That is the only date in this entire article that has money attached to it. So build the timeline backwards from it, not forwards from a blog post.
Here is a standard wedding invitation timeline, working backwards from your venue’s final headcount date, for a wedding on 12 September:
| Working backwards | Date | Why |
|---|---|---|
| Venue final count due | 29 August | It is in the contract. Everything else is derived from this. |
| Your internal cut-off | 25 August | Four days to reconcile the list and count children and vendor meals. |
| RSVP deadline printed to guests | 1 August | Four weeks before the venue’s date. That gap is your chasing window, not the venue’s margin, and you will use most of it. |
| Reminder to non-responders | 25 July | A week before the deadline, while it is still in the future. |
| Invitations sent | 27 June | Five weeks to decide, if nothing needs printing. |
| Invitations sent, if printing | mid-May | Add production and both postal legs. |
| Save the dates | March | Only if people are booking travel or time off. |
Notice what happens if you take the generic advice instead and set the RSVP deadline “a month out”, on 12 August, with a final count due 29 August. You have left yourself seventeen days to chase where you needed four weeks, and they fall in the three weeks you can least afford to spend them. We put numbers to why the chasing window has to be that wide in how many wedding guests actually show up.
When to send save the dates (and do you really need them?)
Six to eight months before the wedding, eight to twelve for a destination. But the more useful question is whether to send them at all.
A save the date carries no information a guest can act on beyond a date and a place. Its whole job is to reserve a weekend that would otherwise be booked. So it earns its cost when guests need to arrange flights, accommodation or time off work, when you are marrying in peak season and competing for your friends’ calendars, or when your date lands on a holiday weekend. For a local guest list on an ordinary Saturday, it adds a mailing without adding anything the invitation will not say better eight weeks later.
One rule with no exceptions: a save the date is a promise. Anyone who receives one must receive an invitation. That is what makes it incompatible with the next section.
The wedding B-list: sending invitations in waves
Almost everyone has a second tier of guests, and almost nobody says so. It is not cruel, it is capacity: the venue holds 120, the list starts at 150, and some people are going to be invited only if others decline.
The mechanics are chronological and unforgiving. Wave one goes out on the schedule above with the real RSVP deadline. As declines land, wave two goes out with its own, later deadline, which is why the second wave needs its own printed or configured cut-off rather than the first one crossed out. And a wave-two guest must never have received a save the date, because taking that promise back is the part people never forgive.
We wrote the full mechanics, including how to time the waves so nobody can tell, in the wedding B-list.
Digital wedding invitations: what changes and what does not
Three of the delays disappear: production, outbound transit, and the return post. On a printed timeline that is five or six weeks of pure logistics, and it is genuinely gone.
What does not disappear is the part that actually costs you the calendar. People are slow to answer regardless of the medium. The four weeks of chasing in the table above are not a paper problem, they are a human one, and no format removes them. So if you were hoping digital would let you send invitations six weeks out instead of twelve, it will not, or rather it will and you will pay for it in August.
What it does buy you is three things, and only the first is usually mentioned:
- You can decide later. Your design, your wording, even a late addition to the list can be settled weeks after a printed invitation would have had to be signed off. The send date moves less than you would like. The commit date moves a lot.
- You can see who has seen it. A paper reply card is silent until it comes back. A digital invitation distinguishes has not opened it, opened it and has not answered, and answered. Those three states need three different follow-ups, and chasing someone who has not seen the invitation at all is a completely different conversation from chasing someone who has read it twice and is quietly hoping to be forgotten.
- Chasing becomes one action instead of forty. The four-week window is survivable when a reminder to everyone who has not answered is a single message rather than a weekend of phone calls that you were dreading anyway.
The catch worth stating: if you are printing beautiful stationery because you want the object, none of this shortens your printing timeline. Print for the object and collect the responses digitally. Those are two separate decisions and most couples make them as one.
How to handle guests who will not click a link
This is the part that generic timelines never mention, and it is the one that actually costs you evenings.
Some proportion of your list will not RSVP online. Not because they are unwilling, but because they do not use email much, distrust links, or would simply rather tell someone. Depending on your family this can be five percent or it can be thirty, and it correlates almost perfectly with the guests you most want at the wedding.
The workable answer is not to fight it. It is to decide, before you send anything, who those people are, and route them through someone else: an adult child, a niece, a sibling who is already speaking to them weekly. Then their response lands in the same list as everyone else’s rather than in a note on your fridge.
For the timing of the follow-up itself: chase once, before the deadline, not after. A reminder that arrives while the deadline is still in the future reads as helpful. The same message afterwards reads as an accusation, and gets a worse response rate.
Do not read a non-response as a no, either. Attendance and confirmation diverge in both directions, and we put numbers to the gap by guest segment in how many wedding guests actually show up.
How our app helps
Digital RSVPs & Guardian is on the free tier, and the second half of that name is the part worth explaining.
The RSVP side is what you would expect: each household gets its own invitation link, responses land in one list as they arrive, and the reply carries the things you actually have to tell a caterer, including base menu choice, dietary needs and severe allergies, plus how many children are coming and which of them need a seat. The Eco-RSVP step goes one further and asks guests which courses they will actually eat, which is a smaller final order and a slightly less guilty conscience.
The Guardian is our answer to the previous section. For any guest you can assign another guest as their Guardian, who manages that person’s RSVP on their behalf. Your grandmother does not need an email address, a smartphone or an opinion about the internet. Her nephew answers for her, in the same list as everyone else, and your headcount is complete without a spreadsheet of exceptions.
There is a reminder message you can send to exactly the guests who have not responded yet, with an RSVP deadline token you can drop into the text so the date is correct in every copy. And the guest list is unlimited on the free tier, which matters more than it sounds when your list is still a negotiation.
While the responses come in, two things are worth reading in parallel: how many guests fit at a wedding table and in your venue, and, once the count settles, how many tables for 100, 150 or 200 guests.
Frequently asked questions
When should wedding invitations be sent?
Six to eight weeks before the wedding is the conventional answer, twelve weeks if guests are travelling or there was no save the date. Then check it against your own venue contract, because if you want a full four weeks to chase non-responders the send date usually has to move earlier than the convention suggests, whether or not you are printing anything.
How do we set the RSVP date from our venue contract?
Find the date the final guaranteed count is due, then put the RSVP deadline four weeks before it. On a contract that wants the count two weeks out, that lands your deadline about six weeks before the wedding. Those four weeks are your chasing window, not a margin for the venue.
When should you send save the dates?
Six to eight months before the wedding, eight to twelve for a destination. Send them only if guests need to book travel, accommodation or time off, and never to someone you might not end up inviting, because a save the date is a promise you cannot take back.
Can we send wedding invitations by email or a link?
Yes, and it removes production and both postal legs entirely. It does not remove the time guests take to answer, so keep the chasing window. Print for the guests who would be genuinely hurt without a card, and collect every response in one place regardless of how the invitation was delivered.
What do we do about guests who do not use email?
Assign somebody who does to respond on their behalf, and decide who those people are before you send anything rather than after the deadline passes. It is far quicker than chasing, and it keeps your headcount in one list instead of two.