Remote work

Working across time zones

Distributed teams rarely fail because of distance. They fail because of unclear overlap, unfair meeting times and messages that wait a whole day for an answer. A few habits fix most of it.

1. Map your real overlap

Start by listing everyone's normal working hours in their own local time, then convert them to one reference zone. The window where everyone is working is your overlap. Between neighbouring regions — say London and Lisbon — that might be the whole day. Between Toronto and Bengaluru it may be an hour or two, or none at all. Live.City's world clock wall and city comparison show the exact difference instantly.

2. Protect the overlap for things that need it

Synchronous time is your scarcest resource. Use it for decisions, debates and relationship-building — not for status updates that could be written. Many teams set a rule that recurring meetings may only be scheduled inside the overlap window.

3. Rotate the pain

If there's no comfortable overlap, someone will take calls early or late. Rotate who that is, week by week or meeting by meeting, so the burden doesn't always fall on the same region. Recording meetings and sharing written notes lets people skip the worst slots without losing context.

4. Write for the reader who's asleep

Asynchronous messages should be complete enough to act on without a follow-up. Include the context, the decision or question, the deadline in the reader's time zone (or in UTC), and what happens if they don't reply. One well-written message saves a 24-hour round trip.

5. Watch the daylight-saving trap

Many countries don't use daylight-saving time, and those that do switch on different dates. For a few weeks each spring and autumn, the gap between, for example, New York and London shifts by an hour. Schedule recurring meetings in a calendar that handles time zones automatically, and double-check anything booked across those weeks.

6. Use UTC for anything technical

Logs, deployments, incident timelines and deadlines are far less error-prone in UTC. Reserve local times for human conversations.

7. Respect local calendars

Weekends differ — in some countries the working week runs Sunday to Thursday or Monday to Saturday — and public holidays vary widely. Keep a shared calendar of team holidays so no one schedules a launch on someone else's national holiday.

8. Mind energy, not just hours

A 9 pm call is technically possible but rarely someone's best thinking. Check local time before you ping a colleague, and use scheduled-send so messages arrive at the start of their day.

A sample team charter

• Core overlap: two hours, published in everyone's local time.
• Recurring meetings only in the overlap; rotating slot otherwise.
• Async-first: decisions written up within 24 hours.
• Deadlines stated in UTC.
• Response expectation: within one working day in the recipient's time zone.

Hiring internationally or planning a move closer to your team? See how cities compare on time zone and lifestyle with our data-first method.