Three teammates in New York, one in Berlin, one in Singapore. Somebody opens with "sometime Tuesday?" and forty messages later the team has spent more effort locating an hour than the hour was worth. Then two people miss it anyway.
If your cohort spans more than about six hours, stop trying to schedule your way out. Run the overlap math once, protect a single recurring window, and move the real work onto handoffs—because in a spread-out team the handoff, not the meeting, is what decides how fast you finish. The general case for working this way is covered separately. What follows is specific to distance: the arithmetic, and what it quietly does to a team that never runs it.
The arithmetic nobody runs
Pick the window everyone genuinely accepts for team work—say 8am to 9pm local. That's 13 hours. Your usable overlap is that window minus your widest offset gap.
- 6 hours apart (New York and Berlin): 7 hours of overlap. You barely notice the problem exists.
- 9 hours apart (San Francisco and London): 4 hours.
- 11 hours apart (Chicago and Singapore): 2 hours.
- 13+ hours apart: zero. Every live meeting now costs somebody their sleep or their evening, and the only question is whose.
Two things about that table surprise people. First, hours are not what you actually lose—slots are. A 7-hour overlap gives you about a dozen half-hour start positions for a 90-minute meeting. A 2-hour overlap gives you two, and at two, one person's standing work commitment or a kid's bedtime deletes the window entirely.
Second, overlap is set by your two extreme members, not by how many you have. A fifth teammate in London on a New York–Singapore team costs nothing; they sit inside a gap that already exists. A fifth in Auckland ends the shared window outright. So "we added one person" is never the right frame—ask whether they land inside your spread or outside it.
Run the numbers in week one, publish one recurring slot, and stop negotiating. The team time-zone overlap planner does that subtraction on a half-hour grid and names who pays for each slot. Everyone gives real availability in their own local time—not "I'm pretty flexible," which is what people say in week one and revoke in week five.
Rotation of pain is a decision you'll make silently
Here's what happens without anyone choosing it: the majority zone proposes a time convenient for the majority zone, the one person outside it says "that works," and now they take a 6am call every week for ten weeks. Nobody decided that—it fell out of a default. But it is a decision the team made, and the person on the wrong end knows exactly how many times it has happened.
Rotate it. If the antisocial slot has to exist, it moves—this week early for Singapore, next week late for New York. If your spread makes rotation impossible, pay in a different currency: that person is exempt from the live window entirely, gets a written brief within the hour, and owns a decision the meeting isn't allowed to make without them.
And be honest about the second cost. Someone on a 6am call is worse at that call. They contribute less and push back less—not because of who they are but because of what time it is where they are. Then the team reads that flatness as disengagement. You didn't just distribute inconvenience unevenly; you degraded one person's contribution and held it against them.
The handoff is the unit of work
When you're nine hours apart, a day is a relay, not a shared room. That changes the price of a sloppy end-of-day note from mild friction to a full cycle.
The specific killer is "any questions, let me know." It reads as polite. What it does is hand your teammate a decision they can't make and a person they can't reach. They start their day blocked, ask, and your answer arrives as they're logging off. One round trip is one day. Three and the deliverable is late—and nobody was slow, and nobody can point to the hour it was lost in.
So write the handoff as though the reader cannot reach you, because they can't:
- What I finished, with the actual link to the actual file. Not "pushed some updates."
- What's next and who owns it, named, so nobody wakes up and has to ask.
- The decisions I already made, with the assumption stated out loud: "I used FY26 revenue as the denominator. If that's wrong, change it and tell me—don't wait for me."
- Open questions, each paired with a default. "If the source extract won't load, use last week's and flag it in the notes." This is the whole skill.
That last rule deserves stating on its own: never send a question across a time zone without also saying what you'll do if nobody answers. It turns a blocking request into a notification your teammate can override in thirty seconds, instead of a day you both lose.
"Due Friday" is five different moments
Friday 23:59 in Singapore is Friday 11:59 in New York. One teammate's Friday ends while the other still has twelve hours of it left. Both read the same message, both are right, and one is going to be genuinely shocked.
Pin one canonical zone—whichever the submission portal enforces, since that's the only one that can actually fail you—and write every deadline with the offset spelled out: Fri 6 Nov, 18:00 ET (23:00 GMT / Sat 07:00 SGT). Include the day. Half the confusion in distributed teams isn't about the hour at all; it's that the date rolled over for some people and not others.
Then set internal deadlines in handoff cycles rather than hours. If integration surfaces a problem at 9pm ET Thursday and the only person who can fix it is asleep until 9pm ET Friday, you've burned your last window and the fix will not happen. Co-located teams buy slack in hours; you buy it in cycles, and two is the minimum that survives one surprise. There's more on protecting that integration buffer if it keeps eating your weekends.
One meeting that's genuinely synchronous
When your shared window is 90 minutes a week, the scarcest thing on the team is not anyone's effort. It's the overlap minute. Spending twenty of them on "so how's everyone doing" has a real price, and you'll pay it on Thursday night.
The meeting that must be live is the one where people disagree about judgment—not facts, not status, not who's behind. Those need tone, interruption, and the ability to change your mind mid-sentence. Dry runs are the other genuine one. Everything else is written work wearing a calendar invite.
So arrive with the disagreement already written down. In a compressed window, live time should resolve a conflict, not discover one—and the norms for writing it up are worth agreeing on early.
When someone becomes structurally invisible
Watch for this one, because it never announces itself. Three people are online, a question comes up, they settle it. Not malicious—just easier than waiting. Repeat that eleven times over a term and the person outside the window has been absent from every decision the team made.
What follows is worse. They stop being asked. They stop pushing back on things they'd have pushed back on. And at the end of term, three teammates independently write "less engaged"—which reads as a claim about a person and is actually a description of a calendar. Your defense, on that end of it, is the handoff record: written, timestamped, and much harder to argue with than a memory of who talked in meetings. There's a fuller treatment of those evaluations.
Two structural fixes beat good intentions. No decision is final until it survives one cycle in writing—if it was made live, post it with an objection deadline spanning the absent person's next working day. And give the teammate in the hardest zone ownership of something on the critical path, not something peripheral. Being unavoidable beats being remembered.
If you're still choosing a program
Time-zone spread is a property of the format, knowable before you enroll rather than discoverable in week three. Online programs recruit nationally and sometimes globally, so a twelve-hour spread inside one team is a normal outcome. Evening part-time cohorts are almost entirely local, and this barely arises. Executive formats sit in between, with residencies supplying real synchronous time a few times a year.
None of those is the right answer. But if you'll be the one member in a distant zone, weigh it at admission—while it's still a choice—rather than absorbing it silently as a 6am call every Tuesday for two years.