The usual advice is two to eight weeks ahead, which is true and not very useful. What matters is the type of event and how much your guests have to arrange in order to say yes.
The short answer
| Event | Send |
|---|---|
| Casual dinner or drinks | 2 to 3 weeks |
| Kids birthday party | 3 to 4 weeks |
| Adult birthday | 3 to 4 weeks |
| Baby or bridal shower | 4 to 6 weeks |
| Graduation party | 4 to 6 weeks |
| Holiday party | 4 to 6 weeks, and by early November for December |
| Wedding | 6 to 8 weeks, with a save the date 6 to 12 months out |
| Destination or weekend event | 8 to 12 weeks |
| Formal or black tie | 6 to 8 weeks |
The rule underneath the table: the more a guest has to arrange in order to attend, the earlier you send. Travel, childcare, time off work and formal dress all push the date earlier.
Why sending too early backfires
There is a real ceiling. Send a casual party invitation three months out and it drops off people's mental radar long before the date. They do not decline, they simply forget, and you get silence instead of numbers.
Sending too late has the opposite problem. Below about two weeks you are competing with plans people have already made, and your yes rate drops for reasons that have nothing to do with your event.
Holiday parties are the exception
December is the one month where you are competing with everyone else's calendar. Send by early November for anything in December, and by late October if you want first pick of a weekend. Thanksgiving and Friendsgiving invitations want to go out in the last week of October.
This is the single most common timing mistake. A holiday invitation sent on December 1 is landing in a calendar that filled up two weeks earlier.
Save the dates
A save the date earns its place when guests need to book travel or take time off. For a local birthday party it is noise. For a destination wedding it is the difference between people coming and not.
Send them six to twelve months ahead for weddings, and two to three months ahead for anything else that involves travel. A save the date does not need full details. It needs the date, the city, and a promise that details are coming.
Build the reminder in from the start
Set your RSVP deadline about a week before you actually need numbers. That gap is your buffer for the people who will not reply on time, and there will be some.
Then plan on two nudges: one a few days before the deadline, and one a few days after for anyone still silent. Two is the standard. Three starts to feel like pressure.
The practical version of this is being able to see who has not replied without scrolling through a message thread. On Easy Evite the dashboard shows replied, opened and not yet opened separately, which tells you whether someone is ignoring you or never actually received the link. Those two problems need different fixes, and the second one is more common than people expect.
If you are already late
Sending late is recoverable, and better than not sending. Three things help:
Say it is short notice, once, without apologising repeatedly. "Short notice, but we would love to see you" is enough. Extended apology makes people feel they are being asked for a favour.
Ask for a faster reply and give a reason. "Can you let me know by Thursday so I can order food" gets a much better response rate than a vague ask when time is tight.
Use the channel people actually check. At two weeks out, email works. At five days out, a text gets read and an email may not. This is the one situation where switching channel matters more than the invitation itself.
If you are planning ahead, the holiday, graduation and wedding collections are free to browse and customize before you commit to a date.