There's a particular kind of silence that follows a badly timed message. A client in Amsterdam asks a question at 09:00 their time, assumes you've seen it, and by the time you open your laptop in Chiang Mai the thread has gone cold. Nothing dramatic happened. Nobody was rude. But trust took a small dent, and those dents add up.
Time zones are rarely the real problem. Most friction comes from unclear expectations: when you'll reply, when you're genuinely reachable, and what counts as urgent. Sort those three out and the twelve-hour gap stops being something you apologise for.
Assuming Your Working Day Is Theirs
New nomads often picture a shared rhythm that doesn't exist. A designer in Lisbon working with a client in Toronto has perhaps two usable overlap hours in the day. If you don't name them, the client invents their own — usually the ones that suit them.
Decide on a daily overlap window and state it in both time zones. Something like: "I'm reachable live between 15:00 and 17:00 GMT, which is 10:00–12:00 in Toronto." Put it in your email signature, your proposal and the shared calendar. If live time is scarce, protect it for decisions and keep everything else written.
Mistaking Fast Replies for Good Communication
Two opposite errors cause the same damage. The first is going quiet for twenty hours on a question that needed a yes or no. The second is replying at 03:00 and then being unreachable for the rest of the client's day. Both teach the client that your availability is a lottery.
Adopt a two-tier policy and say it out loud:
- Acknowledge within one business day of the client's time zone, even if the answer is only "I'll have this to you by Thursday, 14:00 your time."
- Deliver within a stated window for anything bigger than a quick answer, and tell them early if it slips.
Acknowledgement is cheap. Silence is expensive.
Leaving Times and Dates Open to Interpretation
"I'll send it Monday," "by end of day," "this afternoon" — each of these means something different on each side of the world. A Monday deadline in Sydney lands on Sunday for a client in London.
Write deadlines the boring way: day, date, time, zone. "Tuesday 9 March, 16:00 GMT (17:00 CET, 22:00 ICT)." Lead with the client's zone if you want it to land well. Avoid "EOD" and "COB" entirely; they only work when everyone shares an office and a clock. If a deadline matters, confirm it back in one sentence so there's nothing to argue about later.
Getting Caught Out by Clock Changes
Daylight saving trips up experienced freelancers, not just beginners. Europe and North America shift on different dates, some regions don't shift at all, and for a week or two your long-standing call sits an hour out.
Before each seasonal change, check every recurring meeting and reconfirm it in writing. Use a calendar that stores the time zone rather than your memory of it, and put the zone in the invite title. Ask the client to confirm too — a two-line message prevents an empty meeting room.
Boundary Errors That Turn Into Resentment
Answering at 03:00 because the phone buzzed feels helpful for a fortnight. Then it becomes expected, then it becomes resented — by you. The reverse is worse: disappearing for a hiking day with no warning and leaving a client to guess when you'll surface.
Set quiet hours, write them down, and use scheduled sends so your reply arrives at a civilised hour without you being awake for it. One line at the start of an engagement does most of the work:
I work 09:00–17:00 ICT and check messages twice a day. I'll acknowledge anything within one business day of your time zone; anything truly urgent should come by phone. I'm offline on Sundays.
Put a version of that in the contract or welcome email. If the wording carries legal weight for you, have it checked properly.
Writing Async Messages That Cost the Client Time
Async work fails when the message makes the reader do the work. A five-paragraph update with the actual question buried in the middle, a bare "thoughts?", the same request sent by email, Slack and a project tool — all of it slows the client down.
Use a shape they can answer in one pass:
- Context: two lines, no backstory.
- The decision or deliverable: what you need from them, or what you're handing over.
- Options: if there's a choice, name two or three with a recommendation.
- Deadline: in their time zone, not yours.
Keep it to one channel. Batch updates into a short weekly note rather than a drip of half-thoughts.
Falling Into Hybrid Team Habits That Don't Travel
In hybrid teams, decisions get made in the room before the call, and the remote person hears about them a day later. If you're the only one away from headquarters, the stand-up time will default to the majority's convenience, and that will often be your evening.
Ask for written recaps and an agenda sent before the call, so you can contribute rather than catch up. Rotate meeting times where you can, so the same person isn't always the one logging on at 22:00. If a decision happened without you, ask what changed and who owns it — politely, once, in writing.
Build the Rhythm Once, Then Stop Explaining It
None of this takes long to arrange, and it removes the low-grade anxiety that follows new nomads around: the feeling that you're always either too slow or too available.
- Publish an overlap window in the client's time zone.
- Write every deadline with a day, date, time and zone.
- Acknowledge within one business day, even without the answer.
- Set quiet hours and use scheduled sends.
- Recheck recurring calls before each clock change.
- Keep decisions in one written thread.
Do that in the first week of a new client relationship and the gap stops being a source of friction. Work moves on while one side sleeps. That is the arrangement you signed up for.
Photo: AlphaTradeZone / Pexels
