Setting your RSVP deadline

Your RSVP deadline is the date the form stops accepting replies. After it passes, guests opening your link see that replies have closed.

Set it before you publish

This is the ordering that matters, and getting it backwards has caused real problems on real sites.

If you publish first and set the deadline afterwards, there is a window where guests can reply — and a later mistake in the deadline can close the form without anything on your dashboard drawing attention to it. One published site sat with a closed form for around eight weeks while the wedding was still ahead.

Nupta now checks this at publish time and asks you to confirm if your deadline would close the form well before your wedding. Setting it first means you never see that prompt.

Choosing the date

Work backwards from your caterer, not from your wedding.

• Two to four weeks before the wedding is the normal range, because that is when caterers and venues want final numbers.
• A deadline more than about six weeks early will prompt a confirmation, because it is more often a mistake than a choice.
• Leave room for the people who always reply late. Every wedding has them.

A useful pattern: set the deadline about a week before the date you actually have to give the caterer. The gap absorbs the stragglers without eating into your own margin.

After the deadline

The form closes, but nothing is deleted. You keep every reply, and you can still add or change replies yourself on your guest list — which is where the late ones end up anyway.

You can also move the deadline later at any time, which reopens the form.

The sentence guests read

Your RSVP section tells guests when to reply by, and that sentence is written from the deadline itself, so it always matches the date the form enforces. Do not type the date into the section's subtitle as well: that text is yours and will not follow a later change.