Short answer
Good time zone etiquette for remote freelancers means writing every time with its zone, publishing the hours you overlap with each client, defaulting to async updates, putting meetings inside the overlap and rotating any that fall outside it, and ending each day with a handoff the client can act on while you sleep.
Astrolinks gives each person a daily report written from their own private log. No screenshots. Get it free →
When you freelance for clients in other countries, the time difference shapes everything: when you can talk, how fast a question gets an answer, and whether your client feels looked after or left waiting. Most problems aren't about the hours themselves. They come from small habits: a time written without a zone, a meeting that always lands at someone's midnight, an end-of-day message that says "done for today" and nothing else.
These nine rules are what good remote freelancers tend to do. None of them needs special software, and most take a minute a day.
1. Know your overlap hours with each client
Overlap hours are the part of the day when you and a client are both working. Write them down for each client, because they are the hours that matter most.
Say you work 9 AM to 5 PM in Lisbon. A client in New York working 9 to 5 Eastern overlaps with you from 2 PM to 5 PM your time, about three hours for most of the year. A client in San Francisco overlaps with you for no hours at all, unless one of you stretches. A client in Singapore shares an hour of your morning at most, at the very end of their day.
For each client, decide:
- When you are reachable live. Usually the overlap, or part of it.
- When you do focused work. Usually outside the overlap, when nobody expects a quick answer.
- How you handle the gap. If there is no overlap, async updates carry the work, and you agree on one way to reach each other for real emergencies.
Put the overlap in your email signature or your Slack profile: "Online 14:00 to 17:00 for New York (9 AM to noon Eastern)". Clients plan around what they can see.
2. How should you write times across time zones?
Every time you write should carry its zone. "Let's talk at 3" is a guess. "3:00 PM Eastern Time" is a plan.
A few habits make times unambiguous:
- Name the zone, not just an offset. "Pacific Time" or "Lisbon time" is clearer to most clients than "UTC-8". If you use an offset, remember it changes for places with daylight saving.
- Give both clocks when it helps. "Thursday at 9:00 AM Eastern (14:00 for me in Lisbon)" lets both sides check the maths.
- Use the client's zone first. It is their calendar that matters most to them.
- Write dates in full. 4 March 2027, not 03/04/27, which reads as 3 April in much of the world and March 4 in the US.
- Watch midnight. "Friday at 11 PM" for you can be Saturday for a client to the east. Say whose Friday.
Daylight saving time makes this harder twice a year. In the US it begins on the second Sunday in March and ends on the first Sunday in November. In the EU, summer time runs from the last Sunday in March to the last Sunday in October. Between those dates, the gap between a US client and a European one shifts by an hour, and recurring meetings move with it. Check your calendar in March and again in late October.
3. Is async-first better for freelancers across time zones?
For most freelance work, yes. Async-first means the default way to work together is in writing: a message, a document, a recorded walkthrough, a ticket. Calls are for things that genuinely need a conversation.
Async-first helps across time zones because work doesn't stall while one side sleeps. A clear written question at the end of your day can be answered at the start of your client's, and the answer is waiting when you wake up.
To make it work:
- Write complete messages. Context, the question, the options, your recommendation, and the deadline for a decision, in one message. "Got a sec?" costs a whole day across time zones.
- Decide what can't wait. Agree with each client what counts as urgent and how to flag it, so a real emergency doesn't sit in a channel overnight.
- Keep decisions where they can be found. A decision made on a call should end up in writing in the shared channel or document.
Our guide to async check-ins for remote teams goes deeper on the daily rhythm.

4. Respect the client's evening, and protect your own
Sending a message at someone's 11 PM isn't rude in itself. Expecting a reply is. Most tools let you schedule a message to land at the start of the recipient's day, which is kinder and also more likely to be read.
When you do send outside their hours, say so: "No rush, this is for your morning." And avoid calls, phone messages and urgent tags outside their working day unless something is really broken.
The same goes the other way. If a client keeps messaging at your 2 AM, set expectations politely: "I'm offline after 18:00 Lisbon time, and I'll pick this up first thing, which is 4 AM yours." Clients usually respect boundaries they know about.
5. How do you schedule meetings fairly across time zones?
Put recurring meetings inside the overlap whenever there is one. When there isn't, spread the cost.
- One-off calls: the person asking usually adapts. If you need the call, offer times that work for the client.
- Recurring calls with no overlap: rotate between a time that suits them and one that suits you, so nobody is always on at 6 AM or 10 PM.
- Offer slots, not "whenever". Two or three options, each written in the client's zone and yours.
- Send calendar invites, not just a time in a message. Calendar apps convert the time for each person, which catches errors.
- Keep it short and recorded. If someone has to attend at an awkward hour, respect that with a tight agenda, and share notes for anyone who couldn't join.
6. End each day with a handoff
Across time zones, your end-of-day message is how a client knows what happened while they weren't watching. It is also what lets them unblock you before you wake up.
A good handoff covers:
- Done: what you finished today, with links.
- In progress: what's half done and where it lives.
- Blocked: anything you are waiting on, and exactly what you need, from whom.
- Next: what you will do tomorrow.
- Back online: when you will be reachable again, with your time zone.
Times in the handoff should be on the client's clock, because that is the clock they read it on. If you worked from 18:02 to 00:53 their time, say so; it tells them when the work happened in their day. Our guide on how night-shift VAs keep US clients updated has examples for big time differences.
7. Make your availability easy to see
Clients shouldn't have to work out when you are around. Share it once and keep it current.
- A line in your signature or profile with your hours in your zone and theirs
- A shared calendar showing when you are online, if the client uses one
- A quick heads-up before travel days, public holidays or a move to a new time zone
That last one matters for digital nomads. If you move from Europe to Asia, every overlap changes. Tell each client a week ahead what your new reachable hours will be, in their zone.
8. Plan around holidays and weekends in both countries
Public holidays differ by country, and so do weekends in some regions. A deadline on a holiday in your client's country may not get a review, and an invoice due on a bank holiday may arrive late. At the start of the year, note the client's main public holidays next to yours, and plan deliveries around both.
9. Agree how fast replies should be
"Quick question" means different things to different people. Agree a simple rule with each client, such as: messages answered within one working day, urgent issues by a call or a named channel, and nothing expected outside working hours. Then keep to it. Predictable beats instant.
How Astrolinks helps with time zones
Astrolinks is our app, a desktop app for Mac and Windows that keeps a private log of your workday on your own computer and sorts the time by client. Give each client their time zone, and their end-of-day report gives its times, shift and date on their clock, like "Worked 2h 14m, from 18:02 to 00:53 Pacific Time". Where their clock differs from yours, it shows theirs too, so you don't do the maths at the end of a long day.
A workday starts four hours before your shift, so a late session stays one day, even across midnight. Press ⌃⌥N (Ctrl+Alt+N on Windows) in any app and start a line with "blocked" or "tomorrow", and it lands under Blockers or Tomorrow in the report, which covers most of a handoff. If the Wi-Fi drops as you press Send, the report waits on your computer and goes once you are back online, for up to a day. It never takes screenshots and never records keystrokes.
The languages and time zones page has the details, and Astrolinks for digital nomads covers working for clients in several zones while you move.
A quick time zone etiquette checklist
- Your overlap hours with each client are written down and visible.
- Every time you write has a zone, and dates are written in full.
- Messages outside a client's hours are scheduled or marked "no rush".
- Recurring meetings sit in the overlap or rotate.
- Every working day ends with a handoff on the client's clock.
- Clients hear about travel, holidays and time zone moves in advance.
For more on keeping clients informed without constant check-ins, read remote team updates without micromanaging.
Sources
- NIST: daylight saving time
- European Commission: summertime
