Working across time zones: overlap hours, async handovers and meeting etiquette

TUREFF• •0

On a team spread across continents, someone is always starting their day while someone else is finishing theirs. Done well, that means work moves around the clock. Done badly, it means messages that wait a day for an answer, meetings at midnight for the same few people, and a team that is tired all the time. These are the habits that make a distributed team work.

Know the overlap

Start by working out when everyone is awake and working.

Put the team's working hours side by side in a shared document or a world clock tool.
Find the overlap window: the hours when most people are online at once. It may be only one or two hours, or none.
Use that window for what genuinely needs live conversation, and do everything else asynchronously.

If there is no overlap at all, the team needs to be fully asynchronous, and that has to be designed in rather than hoped for.

Write handovers, not just messages

The most useful habit on a cross-time-zone team is a written handover at the end of the day.

What you finished.
What is in progress and where it lives.
What you are blocked on, and who can unblock it.
Any decision you need, with the options and your recommendation, so it can be made without you.

The person starting their day should be able to carry on without waiting for you to wake up. A question that takes one message to answer instead of three saves a full day.

Make messages complete

Include links, screenshots and context in the first message.
Say clearly what you need and by when, and whether it is urgent.
If something truly is urgent, agree a separate way to reach people for it, so ordinary chat does not have to be watched at night.

Meeting etiquette

Always state times with a time zone, or better, send a calendar invite, which shows it in each person's local time.
Rotate inconvenient slots. If a meeting has to be early for one region and late for another, take turns rather than always asking the same people to stay up.
Keep live meetings for discussion, not for reading out updates that could be written.
Share an agenda in advance so people can contribute in writing if they cannot attend.
Record meetings or write notes, including decisions and who is doing what, and post them where everyone can find them.
Keep cameras optional for people joining at the edges of their day.

Calendars and tools

Set your working hours and time zone in your calendar so others see when you are available.
Watch for daylight saving time. Countries change their clocks on different dates, and some do not change at all, so a meeting that was at a sensible hour can shift by an hour for part of the year. Check recurring meetings around March, April, October and November.
Use dates that cannot be misread. 03/04 means different days in different countries; write 3 April or 2026-04-03.
Show local times for deadlines too. "End of day Friday" is a different moment in Seoul and in San Francisco.

Protect your sleep

Sleep is what goes first on a global team, and a tired team makes more mistakes.

Decide the latest and earliest times you will take calls, and put them in your calendar.
If you take a late call, start later the next day; do not just add hours to both ends.
Turn off notifications outside your working hours. If something is genuinely urgent, the agreed urgent channel will reach you.
Try to keep the same sleep and wake times through the week, including weekends, rather than swinging between them.

For managers

Measure people by what they deliver, not by how quickly they reply or how often they are online. Notice who is always joining at bad hours and fix it. And write down how the team works, the core hours, the urgent channel, the handover format, so new starters do not have to guess. Which time zones does your team span, and what has made it work? Share your tips or problems in the comments.