A team spread across three continents can feel like a team that never sleeps, and too often one person pays for that coverage with broken sleep and evening meetings. The solution is not heroic availability; it is a small set of agreements about when the team overlaps, what can wait, and how work hands over between time zones. Teams that write those agreements down protect both their output and their people. Teams that leave them unspoken end up rewarding whoever answers fastest at midnight, which is a poor proxy for good work.

Start by mapping every member's working hours in one shared view and finding the window where most people overlap, even if it is only two hours. Protect that window for live discussion, decisions, and anything that genuinely needs back-and-forth conversation. Outside the window, work should proceed asynchronously: tasks move forward through documents, tickets, and recorded updates rather than waiting for a live reply. Rotate the overlap window when the spread is extreme, so the same person does not always take the late or early slot. A fair rotation, written into the team norms, prevents resentment far better than informal goodwill.

A good handoff answers four questions: what was done, what is blocked, what is needed next, and by when. Write it at the end of your day in the shared project tool, not as a chat message that scrolls away overnight. Include links to the relevant document or ticket, name the decision you need, and state the deadline in both your time zone and the recipient's, to avoid date confusion. When you receive a handoff, acknowledge it briefly and flag anything unclear before the sender's next working day, so questions do not sit unanswered for a full cycle. Over time, a consistent handoff format saves more hours than any new tool.

Default to shorter meetings, with an agenda and a written outcome, and ask whether each meeting could be a document instead. Avoid recurring meetings that fall outside someone's working hours on a regular basis; if a meeting must rotate through awkward times, rotate it fairly and record it for anyone who cannot attend. Publish decisions in writing after every meeting, because a decision that lives only in a call excludes anyone who was asleep. Set response-time expectations explicitly, for example that non-urgent messages get a reply within one working day, so nobody feels they must monitor chat at night to prove commitment.

As an individual, publish your working hours in your profile and calendar, and keep a consistent shutdown ritual: close work apps, write tomorrow's first task, and step away from the desk. Use scheduled sending for messages written outside a colleague's working hours, so your late-night productivity does not become their midnight notification. If your role genuinely requires occasional off-hours coverage, agree the pattern in advance, including time off in lieu or adjusted hours the next day. Sustainable time-zone work is a design problem, not a stamina test, and the best distributed teams treat rest as part of the system.

Working across time zones works when overlap is deliberate, handoffs are written, and sleep is treated as non-negotiable. Agree the window, document decisions, and let asynchronous work carry the hours in between. Teams that do that ship steadily without asking anyone to live at their desk. Review the agreements each quarter, because team composition and time zones change, and a window that once worked fairly can quietly become unfair. Small, regular adjustments keep the system fair for everyone.