How to Work Remotely Across Time Zones Without Losing Your Mind
You thought working remotely meant flexibility. Then you tried to find a weekly meeting time for your team in Bangalore, your manager in Berlin and your client in Vancouver.
Bangalore is UTC+5:30 all year. Berlin is UTC+1, or UTC+2 in summer. Vancouver is UTC-7 all year since British Columbia stopped changing its clocks after March 8, 2026. Put a 9 AM to 6 PM day in each and the three-way overlap is zero, in January and in July. The first two cities share a few hours. The third city shares one hour with Berlin in winter and none in summer.
Seeing that plainly is the useful part. Once you know how many hours exist, you stop trying to hold a daily stand-up that can't fit and start designing the week around what's possible.
Count the Overlap Before You Plan Anything
The method is short:
- List each person's city.
- Write each person's 9 AM to 6 PM as UTC.
- Find where all the windows meet. That's the only time everyone is at work.
Here are common pairs, worked out from the time zone database for a normal January week and a normal July week:
| Pair | January overlap | July overlap |
|---|---|---|
| New York and London | 4 hours (9 AM to 1 PM New York) | 4 hours (same) |
| San Francisco and London | 1 hour (9 to 10 AM San Francisco) | 1 hour (same) |
| Bangalore and Berlin | 4.5 hours (1:30 to 6 PM Bangalore) | 5.5 hours (12:30 to 6 PM Bangalore) |
| Berlin and Vancouver | 1 hour (5 to 6 PM Berlin) | none |
| New York and India | none | none |
The pairs that hold their overlap all year (New York and London, San Francisco and London) are the ones where both sides change their clocks. Where one side doesn't change, as with India, or with Vancouver now, the overlap shifts by an hour twice a year. The weeks in March and October when the US and Europe change on different Sundays can move the New York and London overlap by an hour as well; the DST 2026 page lists the dates.
When There Is No Overlap, Write for It
New York and India have no shared working hours at all. The slot teams use is a compromise: 8:00 to 9:30 AM in New York in winter is 6:30 to 8:00 PM in India. Someone starts early or stays late, and it should be a choice you've made, not a default. If you rotate the discomfort, see how to run a fair meeting rotation.
For everything else, work asynchronously on purpose. A few habits that help:
- Send messages that can be answered without a call. "Can we talk about the API design?" waits for a meeting. "I'd use JWT instead of session tokens because of X. Two questions: Y and Z. If you agree, go ahead; if not, tell me what's wrong" can be answered in one reply at the other side's 9 AM.
- Put the zone in every deadline. "Friday 5 PM IST" can't be misread. "Friday" can.
- Write decisions down. The person who was asleep during the call needs the outcome without asking someone to remember it.
- Record when there's no other option. If the only live slot is at 5 AM for one person, a recording is kinder than a rotation that never ends.
Core Hours: Pick a Small Window and Protect It
Core hours are the few hours when everyone agrees to be reachable, not necessarily in a meeting. Choose them inside your real overlap, towards the middle of it.
For a New York and London team the overlap is 9 AM to 1 PM in New York, so 10 AM to noon is a comfortable core: both sides are well into their day and nobody is near the end of it. For New York and India the compromise slot is about 90 minutes (8:00 to 9:30 AM New York in winter), and a 30-minute core inside it is realistic; everything beyond that is async.
Core hours solve "is anyone around?" and quick decisions. They don't solve deep collaboration, which needs more than a short window and usually a deliberate, longer meeting set well in advance.
Tools That Help
- A calendar that stores named time zones. Create recurring meetings in "Eastern Time" or "India Standard Time", not a fixed offset like UTC-5. A named zone follows daylight saving; a fixed offset doesn't.
- A short team reference. A shared page with each person's city, zone and working hours answers "what time is it for Sarah?" in five seconds.
- The world clock for "is it a reasonable hour there right now?". It builds a clock of up to 30 cities, but the list resets when you reload the page, so keep the team list in your shared reference instead.
- The time zone converter for a specific meeting on a specific date.
- The meeting scheduler when you have a candidate slot: enter it for up to three places and it marks who ends up outside a 9 to 5 day.
Protecting Your Own Hours
When a teammate's morning is your evening, you slide into two shifts: your own day plus the overlap that suits them. Set limits before you need them. Block focus time, mute notifications outside your hours, and state your hours plainly: "I'm online 9 AM to 6 PM IST and I'll reply to anything else the next day" is a complete sentence.
What to Do Next
Do the overlap count for your own team this week: write each person's city, convert 9 to 6 to UTC, and see how many hours are left. Then decide what the team will treat as live time and what it will treat as async. The converter gives you the exact offsets for any date, and the guide to scheduling a meeting across time zones walks through finding a slot step by step.
Related Articles
- How to Schedule a Meeting Across Time Zones (The Complete Guide): the step-by-step method for finding working-hours overlap, with tables for US and India and for US and Europe teams.
- How Digital Nomads Manage Multiple Time Zones (With Real Examples): managing client relationships while your own time zone keeps changing.
- World Clock vs Time Zone Converter: Which Tool Do You Actually Need?: which tool fits which question, and where the meeting scheduler comes in.