How to Manage Client Meetings Across Multiple Time Zones

Client calls do not pause because you moved to a different time zone. This guide covers how to actually schedule and run client meetings while working from abroad: the tools that do the math for you, how to decide who takes the bad time slot, and the one mistake that quietly wrecks meeting times twice a year. None of it requires waking up at 4am on a regular basis.

Map the real overlap before you promise a time

Before you agree to a standing weekly call, work out how much genuine business-hours overlap actually exists between you and your client. This changes the entire conversation about what’s realistic.

Bali to New York

Roughly a 12 to 13-hour gap, depending on the time of year. There is no shared 9-to-5 window at all, only early morning for one side against late evening for the other.

A gap this size makes neighborhood choice more about daily comfort than about closing the clock. Canggu, Ubud, and Seminyak each handle that differently.

Medellin to New York

As little as zero to one hour apart, since Colombia doesn’t shift its clocks. This is about the best overlap a remote worker can get with a US East Coast client.

That near-zero gap is one reason Medellín keeps coming up for nomads serving US clients. The neighborhood you pick there still shapes cost and safety.

Chiang Mai to London

A 6 to 7-hour gap, which still leaves a workable late-morning-to-afternoon window on both ends.

A 6 to 7-hour gap still means shifting your morning earlier for European calls. Chiang Mai’s coworking scene makes that shift easier to hold to.

Lisbon to New York

Around 5 hours, close enough that a mid-morning call on one side lands in early afternoon on the other.

A 5-hour gap is about as workable as a transatlantic schedule gets. It’s part of why Lisbon stays popular with nomads on US client hours

Write the actual gap down before you commit to a cadence. A 13-hour gap means someone is always working outside normal hours, and it’s worth deciding upfront whether that’s sustainable weekly or better saved for a monthly check-in.

Let a tool do the time zone math

Manually converting time zones in your head is where mistakes happen, especially once daylight saving shifts are involved. A handful of tools remove the guesswork entirely.

  • World Time Buddy: free, browser-based, and built specifically for this. Stack your city and your client’s city side by side and it highlights standard working hours in each zone, so you can see the overlap window at a glance instead of doing the math yourself.
  • Calendly: the free plan covers one meeting type, enough for a single recurring client call. The Standard plan runs $10 per user per month and adds multiple event types plus automatic time zone detection, so a client booking a slot always sees it in their own local time, not yours.
  • Google Calendar’s time zone display: turning on the secondary time zone setting shows your client’s local time next to your own on every calendar view, which catches obvious scheduling mistakes before you send the invite.

Whichever tool you pick, put it between you and the client rather than trusting either side to convert manually. A meeting invite that shows the correct local time on both ends removes almost every version of the “wrong time” mix-up.

A close, warm-toned illustration of a laptop screen showing an abstract color-coded timeline of stacked hour columns

Decide who bends, and rotate the tough slot

Someone in a client relationship is usually going to take the less convenient time. The question is whether that’s always you.

  • Default to the client’s working hours for the first few meetings while the relationship is new. It signals reliability, and it’s the safer default when you don’t yet know how flexible they are.
  • Ask directly once trust is established. Most clients will offer a slightly earlier or later slot if you simply explain the gap and propose a specific alternative, rather than just stating you’re unavailable.
  • Rotate the inconvenient time for any recurring call with a wide gap, alternating which side takes the early morning or late evening slot every few weeks. This matters most on a Bali-to-US-East-Coast style gap, where there’s no time that’s comfortable for both sides.
  • Batch client calls into a single block on the days you do them, rather than scattering awkward-hour meetings across the week. One difficult morning is easier to absorb than three.

None of this needs to be a formal negotiation. A short note along the lines of “I’m 12 hours ahead this month, does an 8am your time work instead of 5pm?” usually settles it in one message.

A split composition, one half in warm coral sunrise light with a coffee cup, the other half in deep teal night

Push what doesn’t need to be live to async

Not every client update needs a synchronous call, and cutting the ones that don’t is the fastest way to reduce how often the time zone gap actually bites.

  • Loom records a screen-and-voice walkthrough in place of a status call. The free plan allows 25 videos of up to 5 minutes each, which covers most weekly update needs without a paid plan.
  • Otter.ai transcribes and timestamps live calls automatically, so a client in a different time zone who couldn’t join gets a searchable record instead of a “sorry I missed it” email.
  • A shared doc with a running log (Notion, Google Docs) works for simple status updates that don’t need a face. Post it on a schedule the client can count on, and reserve the live call for decisions that actually need real-time back-and-forth.

The goal isn’t zero meetings, it’s making sure every meeting that does happen across a painful time gap is one that genuinely needed to be live.

The mistake that quietly breaks meeting times: mismatched DST

Thailand, Indonesia, and most of Southeast Asia don’t observe daylight saving time at all. The US and Europe do, and they don’t even switch on the same dates as each other. That means a meeting time that lines up perfectly in January can drift by an hour in March or November, with nothing on a plain calendar invite flagging that it happened.

This is exactly the failure mode a time-zone-aware scheduling tool is built to catch, since it recalculates the local time on both ends automatically instead of relying on a fixed offset someone typed in months earlier. If you’re scheduling manually through email rather than a tool, put the meeting time in UTC in the invite itself as a backup reference, and double check the gap in the two weeks around US and EU clock changes each year.

A textural close-up of an analog clock face or wall calendar page, soft directional light suggesting either dawn or dusk

Search flights on FlyBibe for your next base

The time zone gap is easier to manage when you pick your base with it in mind, whether that means chasing overlap with a specific client region or accepting the gap in exchange for a lower cost of living. Wherever the math points you next, search flights on FlyBibe and get moving.