Scheduling a meeting that works for colleagues in New York, London, and Singapore simultaneously is one of the most reliably frustrating tasks in modern global business. There is a reason people joke about it. The overlap between normal working hours in those three cities is essentially zero, New York business hours (9 AM–5 PM EST) are the dead of night in Singapore and very early morning in London.
Despite being a daily challenge for millions of people, most international scheduling is still done poorly: using ambiguous time references, missing DST transitions, ignoring the human cost of late-night or early-morning attendance. This guide walks through how to do it right.
Step 1: Map the Actual Overlap
Before proposing any time, you need to know what your actual options are. Start by listing every city where a participant is based and what their standard working hours are. Then use a time zone converter to map those windows against each other.
Common overlap scenarios:
- US East Coast + Western Europe: A good window is 2 PM–5 PM EST, which is 7 PM–10 PM CET. Not ideal for Europe, but workable for monthly calls.
- Western Europe + India: A good window is 1 PM–3 PM CET, which is 5:30 PM–7:30 PM IST. Late afternoon for both parties.
- US East Coast + Southeast Asia: Almost no overlap. 8 AM EST is 8 PM–9 PM in most of Southeast Asia. Choices involve someone attending very early or very late.
- US West Coast + East Asia: 8 AM PST is 12 AM in Tokyo and 1 AM in Sydney, no reasonable overlap exists. One party must accept an abnormal hour.
Use the UrbanGlobalTrends Time Zone Converter to check specific times for any city pair quickly. Do this before you propose anything.
Step 2: Propose Times with Full Clarity
Nothing causes more international scheduling chaos than ambiguous time references. These common mistakes create confusion and missed meetings every day:
- Saying "EST" when you mean "ET": EST (Eastern Standard Time) is UTC−5 and only applies in winter. In summer, the US East Coast uses EDT (Eastern Daylight Time, UTC−4). Saying "EST" year-round is technically wrong and can cause a one-hour error during summer months. The correct abbreviation is ET (Eastern Time) or just specify the offset: UTC−5 or UTC−4.
- Omitting the date: "Let's meet Tuesday at 3 PM London time" assumes everyone knows what Tuesday it is, that you mean the upcoming one, and that "London time" is currently GMT (it might be BST in summer).
- Not specifying the year for recurring meetings: If you set a recurring monthly meeting using "10 AM EST," that invite will show different local times for participants in summer vs. winter as DST kicks in.
The best format for proposing an international meeting time is to list the time explicitly for each participant's city:
"Let's meet Thursday, 14 August, 3:00 PM London (BST, UTC+1) / 10:00 AM New York (EDT, UTC−4) / 11:00 PM Singapore (SGT, UTC+8)"
This removes all ambiguity and lets each person immediately verify they have the right time for their location.
Step 3: Send Calendar Invites, Not Just Messages
A calendar invite sent through Google Calendar, Outlook, or Apple Calendar automatically converts to each recipient's local time zone based on their calendar settings. This is far more reliable than communicating a time in a chat message, because the calendar application handles all the conversion for you.
When creating the invite, set the time in your own local time zone and let the system convert. Double-check by looking at the invite from another time zone if possible, most calendar applications let you preview the event in a different zone. This catches errors before the invite goes out.
Step 4: Account for Daylight Saving Transitions
The two- to three-week period each year when the US has changed its clocks but Europe has not (or vice versa) catches people off guard every time. During these windows, the normal time difference between US and European cities shifts by one hour.
For example, in a typical week, New York (ET) is 5 hours behind London (GMT/BST). But during the gap after the US springs forward in March and before the UK follows two weeks later, New York is only 4 hours behind London. A standing weekly meeting set to 10 AM New York / 3 PM London will suddenly appear as 10 AM New York / 2 PM London during those two weeks, confusing attendees in both cities.
The solution: always verify the time difference for the specific date of your meeting using a live converter that automatically applies DST rules. Do not assume the difference is the same as it was last week.
Step 5: Acknowledge the Inconvenience Directly
When a meeting requires someone to attend at an inconvenient hour, early morning, late evening, or outside their normal working day, acknowledge it directly in your communication. A simple "I know this is late for you in Singapore, thank you for making it work" costs nothing and builds goodwill. Pretending not to notice that someone is joining at 9 PM signals that you do not value their time.
If the same person regularly takes the inconvenient slot, rotate the meeting time so the burden is shared. For a recurring monthly call with no good overlap, alternate between two different times so that the inconvenient hour is shared equally across regions.
Step 6: Keep Meetings Tight and Respect Local Time Constraints
When someone is joining at 7 AM or 9 PM to accommodate the group, they have a hard stop, a commute they need to make, family they need to see, or sleep they need to get. Respect that. Start on time. End on time. Do not schedule "just a quick follow-up" immediately after the main meeting without checking whether the person attending at an awkward hour can stay.
Tight, well-structured meetings with clear agendas are always better than loose ones. But they are especially critical in international contexts where every extra minute represents a real personal cost to someone in a distant time zone.
Checklist: International Meeting Scheduling
- Map the actual overlap between all participants' working hours before proposing a time.
- Use a time zone converter for the specific date, not a memorised offset.
- Propose times with the local time listed for every participant city.
- Send calendar invites rather than relying on chat messages.
- Check whether any DST transitions will affect the meeting date.
- Acknowledge anyone attending at an inconvenient hour.
- Rotate inconvenient slots so no single region always bears the cost.
- Start and end on time, always.
For quick, accurate time zone lookups when scheduling, use the UrbanGlobalTrends Time Zone Converter. Or read more of our guides in the UrbanGlobalTrends Blog.