Scheduling a meeting becomes surprisingly hard the moment people are in different time zones. A simple "let us talk at 3 PM" can land in the middle of the night for someone halfway around the world. The good news is that most scheduling mistakes come from a few predictable habits, and once you fix them, cross-border calls become routine.
Always Anchor to One Clear Reference
The single biggest cause of confusion is ambiguity about which clock you mean. When you write "3 PM," whose 3 PM is it? The safest habit is to state the time, the city, and the offset together. For example, write "3 PM in London (UTC+1)" rather than just "3 PM." Naming a real city is better than naming an abbreviation, because city names map to a known location with known rules.
If you work with people who are comfortable with it, UTC is the most neutral anchor of all. UTC does not shift for daylight saving time, so "16:00 UTC" means the same instant everywhere on Earth. Each person then converts that single instant to their own local time.
Send Invitations Through a Calendar, Not Just Text
Calendar systems such as Google Calendar and Outlook store events as an absolute moment in time, then display that moment in each attendee's local clock automatically. This is the most reliable way to avoid errors, because the conversion happens on every device without anyone doing mental math.
When you create the event, double-check the time zone field on the event itself. Many tools default to the organizer's home time zone, which is usually what you want. But if you are traveling, your laptop clock may have changed, and an event you create could silently shift. Setting the event's time zone explicitly removes that risk.
Respect Working Hours, Not Just Availability
A time slot that is technically open on everyone's calendar may still be a terrible idea. Asking a colleague in Sydney to join a call at 11 PM their time is a fast way to burn goodwill. Before proposing a time, look at the local hour for each participant, not just whether the slot is free.
When no slot works comfortably for everyone, rotate the inconvenience. If one recurring meeting always falls early for the Americas, alternate it so the discomfort is shared rather than always landing on the same region. Fairness over time matters more than any single perfect call.
Watch Out for Daylight Saving Time
The trickiest scheduling errors happen around clock changes. Countries shift into and out of daylight saving time on different dates, and some do not observe it at all. For a few weeks each spring and autumn, the usual offset between two cities can be one hour different from what you expect.
This is exactly why anchoring to a city rather than a fixed offset helps. If you schedule "9 AM in New York," your calendar follows New York's rules through every DST transition automatically. If you instead hard-code "UTC-5," that offset becomes wrong the moment New York switches to daylight saving time and moves to UTC-4.
A Simple Checklist Before You Hit Send
- State the time with a city name, not just an abbreviation.
- Use a calendar invite so each device shows the correct local time.
- Confirm the event's time zone field, especially if you are traveling.
- Check the local hour for every attendee, not only free slots.
- Be mindful of upcoming daylight saving time changes between the cities involved.
Build Habits That Scale
The teams that handle time zones gracefully are rarely the ones with the fanciest tools. They are the ones with shared conventions. Agree as a group on a default reference, such as UTC or a primary office city, and use it consistently in every message and document. When everyone follows the same convention, confusion drops sharply.
It also helps to keep a small reference of where your collaborators are and roughly how many hours separate you. After a few weeks, you will start to feel the offsets intuitively, and proposing a workable time becomes second nature. Until then, lean on calendar tools and clear references to do the conversion for you, and reserve your mental energy for the actual conversation rather than the math behind it.