Keep a destination wedding in the venue's time zone

A wedding has a local clock even when the people planning it live in several countries. Decide which timezone belongs to the event, and show that context whenever a date or appointment could be interpreted differently.

A practical sequence

1. Store the venue timezone by its regional name rather than a fixed offset.
2. Show local event times consistently across the timeline and guest information.
3. For remote meetings, show the meeting instant in each viewer's own zone.
4. Review dates near midnight and daylight-saving transitions explicitly.

Work through an example

A planner in California schedules a call with a couple in London about a wedding in Italy. The call is one instant with two viewer-local displays; the ceremony remains a local Italian event time. Treating both as an unlabelled 16:00 creates avoidable confusion.

Where judgement matters

Travel days and event days may differ for a guest crossing a date boundary. Do not assume that a date in an airline itinerary is the wedding venue's date. Ask the transport provider or traveller to confirm the relevant local times.

Make it usable

Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.

Work the decision

A practice case

An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.

A planner in California books a call with a couple overseas, then writes 10:00 into a note without a timezone. Each person can reasonably interpret it differently. Store the meeting’s date and timezone, display the resolved local time and avoid assuming the same offset applies throughout the year.

Three decisions and why each matters

Decision	Why it matters
Use a named timezone for the event location.	A fixed UTC offset cannot express all seasonal clock changes.
Keep arrival dates in the destination’s local calendar.	An overnight flight can land on a different date than the departure itinerary suggests.
Verify the actual date in calendar invitations.	A screenshot of a previous meeting time is not evidence that a later call resolves the same way.

Make one usable artifact

Create a sample call and a multi-day event itinerary with timezone, local date, local time and the corresponding participant view. Check a date near a seasonal clock change.

Then test the difficult case

Reschedule the call by two weeks across a clock change in one location. Confirm both participants’ displayed times before sending the revised invitation.

Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.