Kadlah guide
Digital wedding invitation checklist before you publish
Use this practical checklist to review names, dates, venue links, itinerary, RSVP settings, mobile readability and the final share message.
The short answer
Before publishing a digital wedding invitation, verify names, dates, times, venue, map links, itinerary, RSVP limits and the public URL. Confirm the Free or Premium design rule, test the guest actions on a phone and ask someone else to review the details.
Event details
Compare each value with the latest confirmed information from the venue and family.
- Names and titles are spelled correctly
- Day, date and year agree with the venue booking
- Start and end times use one format
- Each event has the correct venue
- The public contact information is current
Guest actions
Every button should make sense when opened by someone who has never seen the editor.
- Google Maps opens the intended destination
- Waze opens the same arrival area
- RSVP accepts a test response
- Pax and notes settings match what you need
- Any phone or WhatsApp action reaches the right number
Mobile readability
Open the preview on a small phone and check the first screen before scrolling. Names, date, venue and the next action should be readable without zooming. Check that image backgrounds do not hide text and that controls are easy to tap.
Ask for an independent review
Give the checklist to someone who did not enter the content. Ask them to find the couple names, date, venue, map actions and RSVP without prompting. Their questions are more valuable than a quick confirmation from someone who already knows the details.
Repeat the review after a late edit. A small change to a date or event name can create an inconsistent heading, itinerary entry or share message elsewhere on the page.
Publish when the key actions are proven
You do not need to make every decorative detail perfect before publishing, but the guest path must work. Names, date, time, venue, directions and RSVP should be correct and usable. Keep optional copy or gallery changes separate from urgent operational corrections.
Once published, save the public URL and the date of your last review. This gives the family one reliable reference when sharing the invitation or checking whether an update has already been made.
Keep a plan for late changes
Confirm the venue, time and access route before publishing because the invitation is locked afterward. If an important change happens later, contact affected guests directly and ask Kadlah support whether administrative maintenance is appropriate.
After changing an essential detail, repeat the map, RSVP and mobile checks that could be affected. Save the updated public link in the family message rather than creating a second invitation for the same event.
Keep the public checklist separate from private data
The checklist can mention the actions you need to test without copying a guest list, phone numbers or RSVP notes into a shared planning document. Keep personal information in the appropriate account and share only what a helper or vendor needs.
When the invitation is ready, ask the reviewer to confirm the guest experience rather than asking them to export or forward the entire response list.