One reference, several local clocks
The same call can begin in the morning for one person and in the afternoon for another. UTC is an international time reference; local time is expressed relative to that reference. UTC+2 means two hours ahead of UTC at that moment. It does not mean a clock has accidentally been set fast. It is a way of representing the same instant using a convention followed in a particular region.
The difference may change during the year
Daylight saving rules and transition dates vary between territories. A difference observed today should therefore not automatically be reused for a meeting several months away. Even places that both change their clocks may do so on different days. For a real appointment, check both cities on the intended date and confirm the calendar display. An old example can explain the method without remaining a valid schedule.
Convert using a complete date
Imagine a fictional meeting at 18:00 UTC. In a place using UTC+1 on that date, it will be 19:00; in one using UTC−3, it will be 15:00. If adding or subtracting crosses midnight, the day changes too. Write the complete result before sending an invitation. These are hypothetical offsets: the relationship between a city and an offset needs checking for the meeting date, rather than being inferred from longitude.
Make arrangements everyone can check
An invitation can state the date, time and reference city, alongside a calendar entry that converts the instant for each participant. Avoid ambiguous abbreviations and messages such as “tomorrow at eight” when the conversation crosses borders. For recurring activities, explain whether you intend to keep the organiser’s local time or a fixed UTC time. These choices may produce different results when clocks change.
