The Digital Nomad's Timezone Math: How to Keep Your Team Overlap When You Move Every Month

Most nomad-city guides rank places by cost of living, wifi speed, and visa rules — all real constraints, but none of them tell you what actually breaks first when you're doing this while holding down a job with a fixed-location team. What breaks is overlap. A route optimized for weather and rent can quietly cost you eight hours of team overlap between two stops that are only a few time zones apart.

One route, tracked stop by stop

Take a worker whose team is anchored to New York (EST, working 9am–6pm) moving through six popular nomad stops over a year. Here's how much working-hours overlap survives at each one:

The pattern is not "Latin America good, Southeast Asia bad" as a vague rule of thumb — it's that the offset gap crosses roughly 9–10 hours somewhere between Buenos Aires and Bali on this particular route, and that's the point where the working day simply stops touching at all, not where it gradually gets a little worse. One especially notable case: Medellín, Colombia sits at the exact same offset as EST for most of the year (both fixed at UTC-5, since Colombia doesn't observe DST) — a nomad based there keeps essentially full overlap with a New York team without any schedule adjustment at all, right up until the US shifts to EDT for the summer, at which point Medellín is a clean, predictable 1-hour offset instead of zero.

What to actually do during a zero-overlap stretch

A stop like Bali or Chiang Mai doesn't have to mean going dark on your team — it means changing which tools carry the weight. Three things make a zero-overlap stretch workable rather than stressful: agreeing in advance with your manager on which one or two meetings a week are worth the fringe-hour cost (using the best available compromise window, not whatever's convenient), shifting anything that doesn't strictly need a live conversation to a recorded update or written doc, and being explicit about your new hours rather than letting people discover the gap when a message goes unanswered for twelve hours. Teams that handle this well tend to treat it as a temporary async mode with a clear start and end date, not a permanent renegotiation of how the whole team works — that distinction is usually what determines whether the arrangement gets extended or quietly resented.

If your team does need one live touchpoint a week during a low-overlap stretch, use the actual best available slot rather than the first one that comes up in a scheduling thread — see the fair rotation formula for how to work out which candidate time costs the least across everyone involved, not just you.

Planning a route around overlap, not against it

If keeping US-team overlap matters more than following the classic nomad circuit, the practical rule is: stay within roughly 6 hours of your team's offset for as long as your job requires live collaboration, and treat anything past 9–10 hours as an async-only stretch rather than trying to force live meetings into a 6am or 11pm slot indefinitely. That doesn't mean skipping Southeast Asia or Oceania — it means sequencing it for a period when your role can genuinely run async, or pairing it with an explicit conversation with your manager about which meetings you'll miss and how they'll be covered, rather than discovering it live at 6am with a client on the call.

Before committing to a stop, check the actual overlap rather than guessing from the offset number alone — a 9-hour gap and a 9.5-hour gap can produce very different usable windows depending on exactly where your team's working hours start and end. Drag your own hours against any city on the SyncHours planner, or see the full breakdown of which offset gaps preserve real US-hours overlap in which time zones let digital nomads keep US business hours.