How Digital Nomads Manage Multiple Time Zones (With Real Examples)
The first week in Bali is great. The weather, the cost of living, a co-working space with decent Wi-Fi. Then your client in Toronto asks for a "quick call at 9 AM" and you work out that 9 AM Toronto is 9 PM in Bali in summer and 10 PM in winter. You've already made dinner plans.
Time zone math is manageable when you stay in one place. When you move every month or two, your clock relationship with every client changes with you, and the change isn't obvious until it causes a problem. Here's how to plan for it.
Pick a Base by Where Your Clients Are
If your clients are fixed, the cheapest way to cut scheduling pain is to choose where to live with their working hours in mind. This table shows how many hours of a 9 AM to 6 PM day you'd share with each client city from five popular bases, in January and July (one number means it's the same in both):
| Base | New York | Los Angeles | London | Mumbai |
|---|---|---|---|---|
| Lisbon | 4 | 1 | 9 | 3.5 / 4.5 |
| Medellín | 9 / 8 | 6 / 7 | 4 / 3 | 0 |
| Mexico City | 8 / 7 | 7 / 8 | 3 / 2 | 0 |
| Bangkok | 0 | 0 | 2 / 3 | 7.5 |
| Bali | 0 | 0 | 1 / 2 | 6.5 |
Calculated from the time zone database. A few things stand out:
- Americas bases suit American clients, Asian bases don't. From Bangkok or Bali you share no working hours with New York or Los Angeles, and live calls happen early in your morning or late at night.
- Lisbon is the middle ground. Full overlap with London, four hours with New York and one with Los Angeles.
- Bangkok and Bali are good for India and short for Europe. Mumbai shares more than six hours with both; London shares one to three.
- The numbers shift by an hour in March and November. Mexico City and Medellín don't change their clocks (Mexico stopped in 2022), while New York, Los Angeles and London do, so the overlap moves for them twice a year.
None of this means you can't work from Bali for a New York client. It means you've chosen to do it with async work and one or two awkward calls a week, and it's better to know that before you book the flight.
Tell Clients Your Hours in Their Time Zone
Your time zone is the variable. Your client's isn't. Don't make them convert.
Instead of "I'm in Bali, so I'm UTC+8", write "I'm available 8 AM to 12 PM your time, Monday to Thursday." Say it once at the start of the work and again when it changes.
For a standing call, fix the slot in the client's time zone and let your own clock move. A weekly 10 AM call with a London client is 10:00 in Lisbon all year, 5:00 PM in Bangkok and 6:00 PM in Bali in winter, and an hour earlier in both in summer, when London is on BST and Bangkok and Bali don't move. Agree the slot in London time and the client never has to think about it.
What Changes When You Move
Moving from Bangkok to Lisbon changes your gap to everything. Bangkok is 7 hours ahead of Lisbon in winter and 6 in summer. A client call that was 5 PM in Bangkok is 10 AM in Lisbon in January, and the Bangalore team call that was at 8 PM Bangkok time (6:30 PM in India) becomes 1 PM in Lisbon. Your whole week gets rearranged.
A short routine keeps the first week calm:
Before you go:
- Write down your recurring meetings in the new time zone. Look for any that land between midnight and 6 AM.
- Tell clients a week ahead, and give your new availability in their time.
When you land:
- Set your calendar's home time zone, then open the next important call and check what time it shows.
- If a regular meeting is now at an unreasonable hour, ask to move it before it happens, not after.
The calendar part deserves care. A call you set for 10 AM London time is stored as one moment, and your calendar shows it in whatever zone it is set to, so it will correctly read 5 PM in Bangkok. What goes wrong is new events: type "9 AM" after you've landed and it's 9 AM in your new city, unless you choose the zone. Common time zone scheduling mistakes covers that and the other traps.
Tools That Help
- The time zone converter for "the client says Tuesday 11 AM EST, what is that for me?". Set the date and it applies the rules in force on that day.
- The world clock to see the current time in a few client cities. It doesn't remember your cities between visits, so keep your list of clients and their zones in a note you can paste back in.
- The meeting scheduler to test a proposed time against up to three locations and see who's outside a 9 to 5 day.
- A calendar that stores named time zones. Choose "London" or "Eastern Time" for recurring events rather than a fixed offset like UTC+0, which doesn't follow daylight saving.
Work So Fewer Things Need a Live Call
The aim isn't perfect alignment. It's to need less live time. Write updates that can be acted on without a reply, record the calls you can't avoid, and put decisions in writing. When a move is coming, use the month before it to deliver ahead of schedule and clear pending issues, so you arrive in the new time zone with nothing waiting on you.
What to Do Next
Make a list of your three most important client cities. Use the table above, or the converter with a date set, to see how many working hours you share from where you are now and from where you're thinking of going. Then write your availability in each client's time zone and send it today. For a longer look at working with a spread-out team, see how to work remotely across time zones.
Related Articles
- How to Work Remotely Across Time Zones Without Losing Your Mind: counting overlap hours, core hours and async habits for distributed teams.
- How to Schedule a Meeting Across Time Zones (The Complete Guide): overlap tables for US and India, US and Europe, and US West Coast combinations.
- World Clock vs Time Zone Converter: Which Tool Do You Actually Need?: which tool fits awareness, scheduling and planning.