Weddings
Two-City Wedding Invitations: Mistakes That Confuse
Two cities, two clocks and one link: here's where two-city wedding invitations go wrong, and how to set yours up so nobody has to ask which one to come to.
Send The Joy · October 6, 2026 · 3 min read
It's 11pm and your phone has three messages. One guest wants to know if the ceremony is in Madrid. Another asks what time dinner starts in Lisbon. A third asks which of the two links is the real one. You sent one invitation. Two-city wedding invitations go wrong in the same few places, and the cover is where it starts.
A wedding in two cities isn't hard to plan. The invitation is the part that goes wrong, usually because the city and the time sit somewhere guests don't look. Put them where they can't be missed and the questions stop before anyone writes them.
Two-city wedding invitations start with the city on the cover
The cover is the first thing anyone sees, often on a phone, often standing in a queue. Put the city and the date on the first line: "Ceremony in Madrid, 12 July" or "Dinner in Lisbon, 13 July". That line decides whether your guest starts looking at flights or closes the link.
- City and date on the first line of the cover, not saved for scene five.
- "We marry in Madrid and celebrate in Lisbon" only works with a date next to each city. Without them, that sentence becomes three different questions before lunch.
- Two separate celebrations get two separate links, each with its own city, time and address.
- Write the date the way both countries read it: 12 July, not 12/07.
A time without a city next to it is a lost time
18:30 on its own doesn't say which clock. Write "18:30, local time in Lisbon" instead of a bare number. If the two cities sit in different time zones, keep each time glued to its city: Madrid 18:00 · Lisbon 20:30.
Check that the time is on the first screen of the link, not only at the end. Someone opening it at midnight on a phone shouldn't have to scroll to find out when to be where.
A dress code per city, not one for the whole weekend
If Saturday is a city dinner in Lisbon and Sunday is a long lunch outside Madrid, one dress code for the whole weekend helps nobody. Write one line per celebration, next to the time and the place, so people pack the right shoes. If your guests speak different languages, the invitation can be set up so each group reads theirs, without a second version to keep track of.
If the city and the time are on the first screen, half your questions never get written.
The RSVP, the map and the change you don't want to resend
An RSVP with only yes and no gets you confirmations, then messages asking where to go. Add a field for the city, and keep the answers apart: on the Madrid link you want the names of everyone coming to Madrid, not a mixed list. One map pin per celebration, with the full venue name and the city beside it, or someone drives to the wrong town. And when the Lisbon dinner moves half an hour, change it in the link: the same page shows the new time to everyone who opens it. Set it up once, open it on a phone that isn't yours, and send one link per city.
