Scheduling Meetings Across Time Zones Without the Headache

By the UtilityForge Editorial Team · Published October 22, 2026 · 6 min read

Remote and international teams all hit the same wall. Someone proposes "9 a.m. on Tuesday", and half the team has to ask, "Whose 9 a.m.?" A little structure goes a long way toward making cross-time-zone meetings less painful and more fair.

Start with the overlap

Before suggesting a time, work out when people are all within reasonable working hours. Say your team is in India (UTC+5:30), the UK (UTC+0 or +1) and the US East Coast (UTC-5 or -4). India's late afternoon is the UK's late morning and the US early morning. That's a narrow window, and it's the only one that works without someone sacrificing sleep.

When the overlap is small, that's useful information. It tells you to keep live meetings for what truly needs them and handle the rest in writing.

Always say the time zone

This sounds obvious, and yet it's the most common mistake. "3 p.m." means nothing on its own. Better: "3:00 p.m. IST (9:30 a.m. UK, 4:30 a.m. New York)". Calendar invites handle the conversion for you, but chat messages and emails don't. If you're communicating in text, include at least your own zone and, ideally, a UTC reference.

Use the zone name or abbreviation carefully, too. "CST" can mean Central Standard Time (US), China Standard Time or Cuba Standard Time. Using a city, like "Chicago time", or an offset from UTC removes the ambiguity.

Daylight saving is the silent troublemaker

The clocks change on different dates in different countries, and many places don't change at all. India doesn't use daylight saving. The US usually changes in March and November; the UK and most of Europe change in late March and late October (and not on the same dates as the US). For a few weeks each year, the gap between two cities can shift by an hour, and a recurring meeting that worked perfectly in February can suddenly land at a bad time.

When you set up a recurring series, check the times again around those transition weeks, and tell people in advance when the shift is coming.

Be fair about who takes the inconvenient slot

If there's no perfect time, don't let one group always have the early morning or late night. Rotate it. Alternate the slot between two options, or share the pain evenly across the quarter. People notice when it's always them, and it builds resentment faster than almost anything else in a distributed team.

Consider alternatives to the live meeting

Recorded updates. A short video with notes lets people catch up in their own time.
Written decisions. A shared document with comments often works better than a call.
Handover notes. If you work in "follow the sun" shifts, a clear log at the end of each day stops work from stalling.
Shorter, fewer calls. Hold live meetings for decisions and discussions, not for status reports.

Working hours aren't universal

A nine-to-six window is a common assumption, but not everyone shares it. Lunch is at different times in different cultures; some countries have a long midday break, and the working week itself differs (some places work Sunday to Thursday). Public holidays also vary, so before you book anything important, check that it's not a holiday for someone on the invite.

A simple routine that works

Pick the date you want.
List every participant's location.
Look at the whole 24-hour grid and find the hours where everyone is inside working time.
Choose the one that's least bad for the people who have to stretch.
Send the invite with the time written in at least two zones.

The meeting time zone planner does step three for you. You choose a date and up to four zones, and it highlights the hours that fall inside everyone's working window, using your browser's own time-zone data so that daylight-saving changes on that specific date are respected.

Good scheduling is mostly consideration. Make the time clear, share the inconvenience fairly, and remember that everyone on the call is somebody's morning, somebody's evening, or somebody's lunch.