Weddings
Sunrise Wedding Invitations: Time, Brunch and RSVPs
Two times, one meeting point and a brunch headcount: how to set up a sunrise wedding invitation that gathers confirmations without a single follow-up message.
Send The Joy · October 3, 2026 · 3 min read

It's 5:40 in the morning. The ceremony starts at 6:30 at the viewpoint, brunch is at 8:00, and you're scrolling a group chat trying to work out who is actually coming. Three replies say 'we'll see'. Two people want to know where to park. One never answered. A sunrise wedding invitation has to survive this hour.
None of that is your guests' fault. A wedding at sunrise has two fixed times, one exact meeting point and a headcount for brunch, and a chat thread can't hold any of it. Better to put all three in the same place before you send anything.
At 6:30, the time is the design
Ceremony time and brunch time are two different pieces of information, so don't write them on one line. Each detail gets its own field in the editor: one for the ceremony, one for the wedding brunch. If the meeting point is a viewpoint, give the real reference — the gravel car park, the wooden gate, the path on the left — and add the map. Nobody should arrive when the sun is already up. And if you move the time later, the same link shows the new one.
- Ceremony time and wedding brunch time in separate fields of the same invitation.
- A dress-code line for 6:30: light coat, shoes that cope with wet grass.
- The exact meeting point and a map, so nobody arrives after sunrise.
- One RSVP question that asks the real thing: 'Are you staying for the wedding brunch?'
The wedding brunch isn't a lost WhatsApp thread
Give the wedding brunch its own scene. Time, place and what you're serving — coffee, bread, whatever your family actually eats at that hour. Keep the type, the colours and the photos consistent with the rest of the invitation, so brunch reads as part of the celebration instead of a note stuck on at the end.
Confirmations land inside the invitation, in one ordered list. The RSVP questions are configurable, so the answer about brunch sits next to the name and you're not rebuilding the guest list from screenshots. Guests reply from their phone, in the browser. Nothing to install.

A sunrise wedding invitation isn't decoration. It holds two times, one meeting point and the list of who's staying for brunch.
Sunrise wedding invitations: an RSVP that doesn't live in your chats
Guests open the link in any browser — phone, tablet or laptop — and confirm there. Answers stay in the confirmation list, in order, instead of arriving as stickers and voice notes at midnight. If someone can't find the button, send the same link again. It doesn't change and it doesn't break.
Change the time and the link stays the same
Clouds at 6:30? Move brunch from 8:00 to 9:00 and edit the scene. The link, the QR code and the message you already sent stay as they are, and everyone sees the updated time. Same for the venue, the map, the dress code or a line you want to rewrite. You can swap a photo or mark a different cover after sending, and the link keeps showing the new version.
The invitation is a web page, not a PDF. It doesn't print or post anything, and guests need a phone, tablet or computer with a connection to open it. If you also want paper for the people who keep things in a drawer, the sensible combination is a link for everyone and a few printed copies for whoever will actually hold on to one. Pick a design, try it free and publish it before the sun comes up.



