Christening invitations for out-of-town guests: the fine print

Your cousin opens the invitation on the 07:12 train and sends one question: 'Do I get off at the village, or is the lunch somewhere else?' If the answer isn't already on the page she's reading, you'll be typing it out six more times before Friday. That's the test every out-of-town christening invitation has to pass.

The invitation carries the logistics so you don't have to. Church at one address, lunch at another, some guests driving three hours, some on a train, and one link that holds the times, the maps and the replies. Get that right and the day runs on the invitation instead of on your phone.

One christening, two addresses

Ceremony and celebration often sit forty minutes apart. A single 'view location' pin that lands on the church is worse than no pin at all when the meal is in the next town. Give each place its own label, its own map and the full name an outsider would actually type into their phone.

• Start and finish time for every part, including the gap between ceremony and lunch if there is one.
• A map or directions link for each separate place, with the full name and address as a visitor would search it: 'St Michael's Church, Plaza del Ayuntamiento', not 'the church in the village'.
• The dress code translated into something useful: comfortable shoes because the square is cobbled, shade at 15:00, a jacket for the evening.
• A cover photo they recognise from a distance - the church, the square, the house - so they know they're in the right place before they read a word.

Out-of-town christening invitations need real times

Your start time is somebody's train ticket. 'Ceremony at 12:00, lunch at 14:30' lets a family four hours away pick a train that works. 'Midday' makes them guess, then apologise when they walk in late. Put the same detail at the other end: 'we finish around 20:30' tells whoever is driving home whether they can make it or should book a bed nearby.

If some of your guests don't read your language, the invitation content can be set per language - it's available in seven - so the times and the addresses arrive in the language each guest reads, not in yours.

When the invitation already says when and where, the group chat has nothing left to ask.

Your RSVP list, and changes that don't need a resend

Confirmations arrive inside the same invitation, in one ordered list, so you can see who's coming and how many without chasing anyone. The form questions are yours to set. If lunch moves to 15:00 or the map points somewhere new, edit it and the link stays the same: no second message, no reprinting, no calling round. Guests don't install anything - they open the link in a browser and reply from their phone. If a few people want something to keep, they can print the page; everyone else reads it on a screen. Write yours, try it free, and publish with one button once the times are confirmed.