How to Work Across Time Zones Without Always Being Online

It's 6:42 p.m. where you live. A colleague on the other side of the world has just opened their laptop and asked a perfectly reasonable question. You answer, because it'll only take a minute.

Then they need one more detail. Then another person replies in the thread. Eventually you are cooking dinner with a project discussion open beside the chopping board, and no one has explicitly asked you to work late.

Distributed teams can give people access to talent, friendships and opportunities across the world. They can also create a strange pressure: with somebody always working somewhere, the working day starts to look endless.

The answer is not to become difficult to reach. It is to make your work easier to continue without requiring everyone to be present at once.

Asynchronous does not mean “send messages and hope”

Good asynchronous work is more deliberate than chat. It gives somebody else the context, the decision they need and the place they can continue without having to wake you for background information.

GitLab's public handbook is a useful real-world example. Its remote-work practices favour written context, clear ownership and documented decisions, while recognising that some conversations genuinely work better live. That distinction matters. Async is a method for reducing unnecessary waiting, not a religion against speaking to colleagues.

Start with a shared picture of working hours

Before discussing response time, establish when people are actually working. Include local time zone names, regular working hours, recurring days off, and which hours overlap. Avoid assumptions based on the little clock beside somebody's name. Daylight saving changes can move the overlap unexpectedly.

Here's a simple rule: write the recipient's local working window next to any expectation you set. “Respond tomorrow morning” is ambiguous across continents. “Please review by 2 p.m. London time on Thursday” is something a colleague can plan around.

For a distributed team, distinguish three kinds of messages:

• When you next work: Routine updates, questions and review requests.
• By an agreed deadline: A decision or input needed for a planned handover.
• Urgent through the agreed incident route: A genuine outage, risk or emergency that cannot wait.

If everything is urgent, the distinction has stopped working. If the urgent route isn't defined, people will invent their own by messaging whoever seems most awake.

Write a handover someone can actually use

The difference between “Can you look at the launch?” and a good handover is often another five minutes of writing. Those five minutes can save a full day of waiting across time zones.

Document the decision, not every minute of conversation

An eight-page transcript is rarely a useful handover. The person starting their morning wants to know what changed and what they are responsible for.

After a live call, capture four things: the decision, the reason, the owner and the next check-in. Link the supporting context rather than pasting the entire conversation. That gives absent teammates access to the outcome without asking them to reconstruct it from chat history.

When people repeatedly ask the same question, don't blame them for missing a Slack thread. Move the answer somewhere stable and link it. The place where information lives is part of the team's design.

Make overlap hours a small, valuable resource

When your team shares only an hour or two, it can be tempting to fill every overlap with calls. But that leaves no time to execute the decisions those calls produce.

Use overlap for work that becomes expensive when delayed: resolving ambiguity, discussing a sensitive problem, making decisions with competing trade-offs, or building a relationship with a teammate you've barely met.

Use asynchronous messages for things that are already understandable: progress updates, routine reviews, proposed wording, status checks and simple approvals.

If an async thread has become a maze of misunderstood replies, a short call may be kinder to everyone. Agree the question beforehand, invite only those who can resolve it, then write down the result.

Don't make one region pay for everyone else's convenience

A recurring call that's lovely at 9 a.m. in one location might be dinner time or the middle of the night somewhere else. If the meeting really needs multiple regions, rotate the inconvenient slot, provide a written route to participate, or record the outcome in a way absentees can act on.

Never infer that silence means agreement just because somebody was asleep. Give decisions a review window that spans real working hours. When deadlines cannot move, say so clearly and arrange representation beforehand.

Also consider the actual team rather than abstract time zones. A colleague may have a school run, prayer, medical appointment or caring duties. Remote work is meant to create some room for life, not demand that everyone erase it to participate.

Protect the moment your own day ends

At sign-off, leave a handover and close the channel. If you're off duty, you're off duty. A well-designed escalation route is there for actual emergencies, not for ordinary follow-up questions disguised as emergencies.

One useful message is simple: “I'm signing off now. The latest status and decisions are in the project document. I'll review new comments when I'm back tomorrow. For a production incident, please use the on-call channel.”

If the organisation expects evening coverage, that's a staffing and scheduling requirement to agree openly. It shouldn't rest on one conscientious person keeping the browser open just in case.

A small Calphii thought
Being a good remote colleague should not require living in everyone else's time zone.

Where a personal focus space fits

When colleagues work asynchronously, you may have longer stretches to concentrate. Make those stretches count. Keep the decision document open, a note of the next action nearby and your notifications quiet during a realistic block. In Calphii, a task board, notes and Deep Focus can sit together in the same browser workspace; you don't need to build a second organisation system around them.

But remember the order: first agree how the team hands off work, then use your own tools to make the resulting quiet useful. A timer cannot compensate for missing information from yesterday's shift.

A two-week async experiment

Choose one recurring status meeting or repeatedly delayed question. Replace it for two weeks with a short written update containing the goal, current state, decisions needed, owner and deadline. Keep an escalation route for genuine urgency. At the end, ask whether work moved faster, whether fewer people waited around, and whether anyone felt out of the loop.

If it made things worse, revise it. Perhaps you need a weekly live conversation and daily async updates. The measure is whether teammates can do good work during their own working hours, not whether you've eliminated calls for the sake of it.

If your evenings are still full of “one last reply”, read how to end a work-from-home day. If your calendar has no room for execution, try our guide to meeting-heavy remote work.