Event Reminders: What to Send the Week Before and Day Of

You sent invitations three weeks ago. Half the guest list replied within days. The other half went quiet, and now the event is close enough that food, seating and setup all depend on a real headcount you don't have.

A reminder isn't a nag if it has a clear job to do. The week-before message should close the loop on RSVPs and hand out logistics. The morning-of message should get confirmed guests out the door on time. They're different messages with different jobs, and mixing them up is why so many reminders get ignored.

What the Week-Before Reminder Should Do

This message goes out five to seven days before the event. It has two audiences at once: people who haven't answered yet, and people who have. For the first group, it's a gentle push to reply. For the second, it's the logistics they'll actually need on the day.

• Date, start time and end time, even if it was on the original invite
• Address or link, since some guests will have deleted the first message
• Parking, entrance or building-access notes if the venue is tricky to find
• What to bring, if anything, so nobody shows up empty-handed to a potluck
• Dress code or theme, if there is one
• A soft deadline: "if we haven't heard from you, please let us know by [date]"

If you're using a capacity limit or a waitlist, this is also the moment to check the numbers against your food and drink plan. The party food calculator can turn a confirmed headcount into actual quantities so you're not guessing three days out.

Sample Wording for the Week-Before Message

Hi everyone, we're one week out from [event name] on [date] at [time]. If you haven't had a chance to RSVP yet, we'd love to get a final count by [date] — here's the link: [invitation link]. For those already coming: parking is on the side street, and the party runs until about [end time]. See you soon.

Notice the message does two things in two short parts: a direct ask for the still-undecided, and useful details for the already-confirmed. You don't need to write two separate emails if the invitation tool lets you send one message to everyone, though some hosts prefer splitting it so non-responders get a shorter, more direct nudge.

What the Morning-Of Message Should Do

This one is shorter and has a single job: reduce no-shows and answer any last question before someone leaves the house. It goes out a few hours before start time, not the night before, since people forget overnight.

• A one-line restatement of time and place
• Anything that changed since the week-before message — weather plan, room switch, a moved start time
• A note on where to park or which door to use, especially for a venue guests haven't visited
• A phone number or contact for last-minute questions or a guest running late
• For outdoor or weather-dependent events, the rain-plan decision if you've made one

Sample Wording for the Morning-Of Message

Today's the day. [Event name] starts at [time] at [address] — use the side entrance, parking is in the lot behind the building. Text me at [number] if you're running late or can't find the door. See you soon.

Deciding Who Gets Which Message

Not every guest needs every reminder, and sending the wrong one to the wrong group is how reminders start to feel like noise. A simple rule: guests who haven't replied get the week-before nudge with the RSVP ask front and center. Guests who already said yes or maybe get the logistics version, without the ask, since repeating a question they already answered reads as inattentive.

The morning-of message goes to everyone who said yes or maybe, since a maybe often turns into a yes once the day arrives. Guests who declined don't need either message unless plans changed and you're reopening a spot from a waitlist.

If you're managing this by hand across texts, emails and a group chat, it's easy to lose track of who's in which bucket. Sending reminders through the same tool you used for the invitation, and filtering by going, maybe or not-replied, keeps the two messages from getting crossed. It also means you're not typing the same update into five different threads.

Where This Varies

How firm you should be about the RSVP deadline in a reminder depends on the event. A dinner party for eight with a fixed number of seats can afford a direct "please reply by Thursday so I can shop." A backyard birthday party with a flexible headcount can be looser. Formal events like weddings usually build the deadline into the invitation itself rather than the reminder, and reminders there tend to focus on logistics — attire, timing, parking — rather than chasing a reply. Large, casual gatherings sometimes skip the week-before message entirely and rely only on a morning-of text, since a soft RSVP deadline was never realistic to begin with. If you're still deciding how many days of lead time to build in before you start reminding people, the RSVP deadline calculator can help you back into a schedule from your event date.

Family and cultural norms around punctuality also shape how strict a reminder should sound. In some households, a start time is a suggestion and guests arrive on their own schedule; in others, five minutes late is notably late. Match the tone of your reminder to how your specific guest list actually behaves, not to a generic rule.

If you're still working out invitation wording for the event itself, wording examples for different occasions can help you keep the tone of the reminder consistent with how the invitation read in the first place. A reminder that suddenly sounds much more formal or much more casual than the original invite can read as odd, even if the content is right.

The most useful habit is picking your two send times before the event, not scrambling to remember on the day. Put the week-before reminder and the morning-of message on your own calendar the same day you publish the invitation, so neither one depends on you remembering under pressure later.