Destination
Rooms, arrivals, who paid
With the rest of This wedding. Same Base RSVP as a wedding in town.
What this wedding holds
Who’s landing when
Flights and arrivals in one view.
Who sleeps where
Rooms on-site and off, plus hotel blocks with group codes.
Who still owes
Lodging collections — Venmo or mark paid. What’s outstanding stays visible.
What they need to know
One destination guide you write. If the app is on, the website shows basics; polls and lodging stay on the site.
Same RSVP as everyone
QR and a shareable link on Base RSVP, at rsvp.dueaplanning.com. A guest website is separate. The guest app sits after that.
The list, the rooms, who paid.
In This wedding. Same QR as a wedding in town.
RSVP first
Destination still starts with the yes.
The same RSVP flow can collect attendance, meals, addresses, song requests, and custom weekend questions.
Guest guide
Then add the weekend guide.
When travel matters, the guest website can carry schedule, FAQ, travel, and RSVP details in one place.
Also on this weekend
Welcome dinner, brunch, extras
Mini RSVPs after the main yes — so headcounts stay with the rest of the weekend.
The day itself
Run sheet and Packet ZIP for vendors. Same handoff as a local wedding.
More than one calendar day
Guests see the weekend by day. That’s the usual destination shape.
Local weddings — travel stays off.
Launching November 1. Join the early list.
See the planning home before public launch: RSVPs, guests, budget, vendors, seating, and day-of in one place.