Why 'just convert the hours' goes wrong
Doing time zone math in your head usually means adding or subtracting a fixed number of hours — "Vietnam is 12 hours ahead of New York" — and that shortcut works fine right up until one side of the conversation shifts its clocks for daylight saving and the other doesn't. The gap between two time zones isn't always a constant; it changes on different calendar dates in different countries, or doesn't change at all in countries that don't observe daylight saving, which is exactly the kind of detail a rough mental calculation misses.
Convert a specific meeting time
The daylight saving trap
Whether a country shifts its clocks, and when, varies more than most people realize. The UK moves to British Summer Time in late March and back in late October. Canada observes daylight saving on similar North American dates (with a few regional exceptions). Vietnam and China don't observe daylight saving at all — China abolished it in 1991, and Vietnam has never used it — so their offset from UTC stays fixed year-round. Brazil suspended its daylight saving practice in 2019 and hasn't reinstated it as of this writing, after decades of observing it. The practical upshot: a meeting time that's correctly converted in January can be an hour off by July if one side of the call is in a daylight-saving country and the other isn't — worth double-checking specifically around March and late October/November, when most Northern Hemisphere shifts happen.
A simple process that scales to any team
The most reliable habit for a team spread across several countries is to agree on one shared reference — usually UTC — and state meeting times against it in calendar invites, rather than assuming everyone will correctly convert from whichever time zone the organizer happened to use. Most calendar tools convert UTC or a named time zone into each attendee's local time automatically, which removes the manual math (and the chance of getting it wrong) entirely. For a one-off call rather than a recurring meeting, converting the exact proposed date and time — not just "3 PM my time" — avoids the daylight-saving trap above, since the tool accounts for whichever offset actually applies on that specific date.
Common scheduling mistakes
Beyond daylight saving, a few mistakes come up constantly in international scheduling. AM/PM confusion is one of the most common — writing "7:00" without specifying morning or evening leaves real room for error once a conversion crosses noon in either direction. Assuming a converted time lands on the same calendar date is another: converting a time across a large enough offset can genuinely roll over into the next day or the previous one at the destination, which is easy to miss doing the math by hand and easy to catch with a tool that shows the date explicitly. Finally, it's worth double-checking a time zone converter's underlying data is using the actual date of the meeting, not just today's date — since, as covered above, the offset between two time zones isn't always constant across the year.