Editorial review: · Kalenderwoche.info
Schedule across time zones without guessing local times
“Tuesday at 3 pm” is not a complete agreement for an international meeting. At least the specific date and time zone are missing. A calendar invitation checked in each participant's local display is more useful than mental arithmetic based on an assumed permanent time difference. The process below focuses on the agreement rather than the buttons in a particular app.
Specify the date, time zone and duration together
Write out the full appointment first. For example: “15 January 2027, 15:00–15:30, Europe/Berlin”. This is a deliberately fixed example, not a current meeting proposal. Include the purpose and the location or agreed joining details.
A week number may provide extra orientation but does not replace these details. For a deadline, distinguish a single shared instant from a date in someone's local calendar. Otherwise, “by Tuesday” can finish at different moments for different people.
Use a location-based zone, not a guessed offset
An identifier such as Europe/Berlin describes more than the offset currently displayed on a clock. Time-zone rules can change, and IANA maintains a database reflecting those changes. Do not use today's observed difference as a permanent rule for future appointments.
Short abbreviations can also be confused. Select the appropriate location-based time zone in your calendar and inspect the resulting invitation. Settings vary between products; the important outcome is a confirmed local display, not a supposedly timeless sequence of menu clicks.
Check the invitation from the participants' perspective
During the initial arrangement, ask participants to confirm their local date and time. Check whether their calendars use the intended display zone. A screenshot without a visible zone is less informative than a complete appointment specification.
Keep one authoritative invitation. If several participants recreate the same event, competing versions can emerge. Name the person responsible for changes and update the existing invitation through the agreed channel.
Decide which local time a recurring series should preserve
A recurring meeting can follow the local time at one location or a fixed UTC time. These are not necessarily equivalent throughout the year. Decide which rule suits the collaboration before creating the series instead of letting the first displayed time become an accidental permanent requirement.
Inspect multiple occurrences, particularly around clock changes at the locations involved. The local time can change for some participants. If this creates a conflict, agree an explicit exception rather than adding a second, similarly named series that obscures which one is correct.
Include travel and changes in the checking process
Anyone travelling should recheck the date and display zone before the meeting. A device or calendar zone change can alter the displayed time without rescheduling the event itself. Tell the others if you actually need to agree a different meeting time.
The template below records the agreement clearly. It is not a time-zone converter and does not promise a permanently valid conversion between two places.
Appointment and purpose:
Date and start–end time:
Authoritative time zone or UTC rule:
Confirmed local date and time at each location:
Recurrence rule and checked exceptions:
Who updates the invitation and communicates changes?