There’s a particular kind of tired that only remote workers know. It doesn’t come from working too hard. It comes from working at the wrong times: a 7 a.m. call with one continent, a 9 p.m. “quick sync” with another, and a phone that never quite stops buzzing in between.
You’re not imagining it. A 2025 Microsoft report on the “infinite workday” found that meetings after 8 p.m. were up 16% year over year, that nearly a third of meetings now span multiple time zones, and that the average worker receives around 50 messages outside core business hours every day.
Time zones aren’t the problem. The problem is that most teams run a distributed workday on rules written for an office, where everyone arrives at nine, leaves at six, and can tap a colleague on the shoulder. Those rules don’t survive a six-hour time difference. Here are the ones that do.
Rule 1: Default to Async, Meet on Purpose
The biggest shift is changing the default. In an office, the default is a conversation and writing is the exception. Across time zones, flip it: writing is the default, and a live call is something you choose deliberately.
GitLab, which has operated as a fully remote company for years, sums up async work in its public handbook: do as much as you can with what you have, document everything, hand ownership to the next person, and move on to something else. The point isn’t to never talk. It’s that no one should have to be awake at midnight for work to move forward.
A useful test before booking a call: does this need real-time back-and-forth? Nuanced decisions, sensitive feedback and anything where tone matters — yes. Status updates, approvals and “just checking in” — almost never.
What actually replaces the meeting
- A written update with the context, the decision you need, and a deadline.
- A short screen recording, when showing beats telling. Loom’s free Starter plan gives you 25 videos of up to 5 minutes each; paid plans start at $18 per user per month billed monthly, with a discount for annual billing.
- A shared document where comments replace a round of calls.
Rule 2: Agree on an Overlap Window — and Protect Everything Outside It
Most distributed teams have a few hours when everyone’s working day overlaps. Name those hours, put them in writing, and treat them as the only time live meetings can happen.
Two to three hours is usually enough. If your team is spread so widely that the overlap shrinks to one hour or disappears, that’s a signal to lean even harder on async — not to keep asking the same people to stay up late.
Share the inconvenience
When there’s no comfortable slot, rotate the awkward one. If the same person always takes the 10 p.m. call, you haven’t solved the time zone problem. You’ve made it one person’s problem.
A free tool like World Time Buddy lays several time zones side by side, so you can see the overlap at a glance instead of doing mental arithmetic every time.
Rule 3: Write Messages That Don’t Need a Reply to Move Forward
Across time zones, every unclear message costs a full day. You ask a question at 5 p.m. your time. They answer while you sleep. You reply with a follow-up. They see it tomorrow. A two-minute conversation becomes a 48-hour one.
The fix is to write messages that are complete on arrival:
- Lead with what you need. “Decision needed by Thursday” beats three paragraphs of background.
- Include the context they’d otherwise ask for — links, numbers, the options you’ve already considered.
- Say what happens if they don’t reply. “If I don’t hear back by Wednesday, I’ll go with option B.” This one line removes most of the waiting.
Rule 4: Stop Sending Your Night Into Their Day
Just because you’re awake doesn’t mean your message has to arrive now. Slack, Gmail and Outlook all let you schedule a message to land at the start of the recipient’s working day. It’s a small habit, but it changes the culture: it tells people that seeing your name at 11 p.m. doesn’t mean they’re expected to answer.
The same rule protects you. Turn off notifications outside your working hours, and set those hours in your calendar and chat status, so colleagues can see when you’re off without you having to explain it every time.
Worth a Look
- Working hours in your calendar. Google Calendar and Outlook both let you set them, so people see when you’re unavailable before they send an invite.
- Scheduling links. Tools like Calendly or Cal.com show others only the slots that fall inside your overlap window.
- A team hours map. A simple shared table with each person’s time zone and working hours. Low-tech, and it prevents most scheduling mistakes.
FAQ
How many hours of overlap does a remote team need?
For most teams, two to three hours is enough, as long as meetings stay inside that window and everything else moves async. With little or no overlap, rely on written updates and short recordings, and save live calls for decisions that genuinely need them.
Is it unprofessional to reply the next day?
Not on a distributed team — it’s the expected rhythm. What matters is that people know when they’ll hear from you. One clear line in your profile or email signature, such as “I’m based in Lisbon and usually reply within one working day,” sets that expectation once.
How do I say no to a meeting outside my hours?
Offer an alternative instead of a flat no: “That’s 10 p.m. for me — could I send a written update instead, or would Tuesday at 3 p.m. your time work?” Most late-night requests aren’t demands. Usually, the other person simply doesn’t know your time zone.
Working across time zones isn’t about being available to everyone, all the time. It’s about building a way of working where you don’t have to be. Write clearly, meet on purpose, protect the hours outside the overlap — and let the work move while you sleep.
The world changed. So did the rules.
Keep reading: how to actually switch off after working from home · the best AI meeting note-takers for remote professionals
