Scheduling a meeting when your team spans New York, London, Singapore, and Sydney is one of the most common — and most frustrating — challenges of modern remote work. With a 15-hour gap between the Sydney vs New York time difference alone, finding a time that works for everyone requires strategy. This guide gives you a practical, tested framework for scheduling meetings across time zones without burning out your team.
Step 1: Map Your Team's Time Zones
Before picking a meeting time, create a clear map of each participant's time zone with their current UTC offset. Do not assume — ask directly or check their calendar settings. Remember that "Pacific Time" could mean PST (UTC−8) or PDT (UTC−7) depending on whether daylight saving time is active.
Our time difference calculator makes this easy: compare any two cities to see the exact hour gap, current times, and overlap windows. For US-only teams, the California vs New York time difference is the most common gap to bridge.
Step 2: Find the Overlap Window
The golden rule: identify reasonable working hours (8 AM – 8 PM) for each participant and find where they intersect. Here is a real example for a 4-city team:
| City | Working Hours | In UTC |
|---|---|---|
| New York (EST, UTC−5) | 8 AM – 8 PM | 13:00 – 01:00 |
| London (GMT, UTC+0) | 8 AM – 8 PM | 08:00 – 20:00 |
| Singapore (SGT, UTC+8) | 8 AM – 8 PM | 00:00 – 12:00 |
| Sydney (AEST, UTC+10) | 8 AM – 8 PM | 22:00 – 10:00 |
The only 4-way overlap is roughly 08:00–10:00 UTC, which translates to 3–5 AM in New York, 8–10 AM in London, 4–6 PM in Singapore, and 6–8 PM in Sydney. New York gets the worst deal here — which brings us to Step 3.
Step 3: Rotate the Pain
If one region consistently takes inconvenient hours, rotate the meeting time monthly so the burden is shared fairly. One month, New York wakes up early; the next, Singapore stays late. This builds team trust and signals that you respect everyone's time equally. Use our 11 AM SGT to PST or 2 PM EST to MST pages to quickly check what specific times translate to.
Step 4: Use Calendar Tools That Auto-Convert
Never, ever rely on phrases like "let's meet at 3 PM my time" in a Slack message. Instead:
- Google Calendar — sends invites that auto-convert to each recipient's local time
- Calendly — shows available slots in the visitor's own time zone
- Outlook — has a built-in time zone comparison view in the scheduling assistant
- Our converter — bookmark the EDT to CST converter or PDT to EDT converter pages for quick verification
Step 5: Default to Async When Possible
The most enlightened remote teams recognize that not every discussion needs to happen live. For updates, status reports, and non-urgent decisions, use asynchronous communication:
- Loom — record a 5-minute video update instead of scheduling a 30-minute meeting
- Notion or Confluence — write decisions and context so anyone can read on their schedule
- Slack threads — ask questions that people can answer when they start their day
Reserve synchronous meetings for brainstorming, relationship-building, and complex decisions that benefit from real-time dialogue.
Step 6: Verify with a Converter Before Sending
Before clicking "Send" on that calendar invite, double-check the time using our time zone converter. Common conversions to verify:
- EDT to CST converter — US East to Central coordination
- EDT to MST converter — EST to Mountain Time (Arizona)
- CEST to CST conversion — Europe to US Central
- EST to JST conversion — US East Coast to Japan
- PST to AEST converter — US to Australia
Each page includes live clocks showing the current time in both zones, so you can verify at a glance whether your meeting falls during reasonable hours for both sides.
Bonus: Use Time Zone Abbreviations Correctly
One of the most common scheduling errors is using the wrong abbreviation. EST and EDT are different — confusing them shifts your meeting by an hour. When in doubt, use the generic abbreviation (ET, CT, PT, MT) which automatically implies the correct seasonal offset. Our time zone blog has more articles on these nuances.