The short version: propose two or three concrete slots in the client's local time, state your own zone in brackets, and pair every slot with the weekday and date. A clear menu turns an open-ended question into a quick yes, so the meeting books in one reply instead of a five-message thread.
Booking across borders rarely fails because the calendars don't overlap. It fails because of language: a vague ask, an ambiguous time, a missing zone. Tighten those three things and most of the back-and-forth simply disappears.
Why does "what works for you?" cause loops?
It feels polite, but it quietly hands the client every hard job at once. They have to guess your working hours, convert between zones, and choose from an unlimited set of options. Faced with that much effort, people defer the reply, answer vaguely ("sometime next week?"), or suggest a slot that lands at 3:00 AM for you. Each of those forces another round.
A short menu does the opposite. Two or three slots is small enough to answer in seconds, large enough to feel flexible. You have already done the time zone maths, so the client only has to say yes. The stakes are higher than a single thread: Asana's Anatomy of Work Index, a survey of more than 13,000 knowledge workers, found that they spend almost two-thirds of their time on "work about work" such as coordinating and chasing updates rather than the skilled job itself, and scheduling is squarely part of that drag.
What does a clean proposal look like?
The whole method fits in five steps. Run through them once and the message almost writes itself.
- Find the overlap first. Identify a couple of windows where both of you are comfortably inside working hours, not just technically awake.
- Lead with the client's local time. They are the one you want to make a decision easy for, so put their clock first.
- State your own zone in brackets. One short aside lets them see the slot is reasonable for you too.
- Anchor to the weekday and date. "Thursday 5 June" is far harder to misread than "Thursday" alone, and it catches date-line slips.
- Offer a fallback to propose. Invite alternatives only if none of your slots fit, so the default path is still a quick yes.
Put together, a strong message reads like this:
"Could we meet next week? Three options, all in your time: Tuesday 3 June, 9:30 AM IST; Wednesday 4 June, 10:00 AM IST; or Thursday 5 June, 4:00 PM IST. (Those are 5:00 AM, 5:30 AM and 11:30 AM BST for me.) Happy to find another slot if none suit."
How should I write the time so it can't be misread?
Time zone notation is where good intentions go wrong. A few habits remove almost all the ambiguity.
- Use a 12-hour clock with AM/PM, or 24-hour, but never mix them. "7" is unreadable; "7:00 PM" is not.
- Name the zone, don't assume it. "10:00 AM your time" is good; "10:00 AM IST (your 5:30 AM BST)" is unmissable.
- Spell out the weekday and date together. The weekday is a built-in safety check: if the date and day don't agree, someone made a conversion error.
- Mind half-hour offsets. India is UTC+5:30 and Nepal UTC+5:45, so the gap is rarely a round number of hours.
| Avoid | Write instead |
|---|---|
| "Let's do 10am." | "Thursday 5 June, 10:00 AM IST (your 5:30 AM BST)." |
| "What works for you?" | "Tue 9:30 AM, Wed 10:00 AM, or Thu 4:00 PM your time?" |
| "Sometime tomorrow." | "Wednesday 4 June, between 2:00 and 4:00 PM EST." |
| "7 your time." | "7:00 PM your time (CET), Friday 6 June." |
Offsets shift when clocks change, and not on the same dates everywhere. A 9:00 AM London call that was eight hours behind New York can briefly become seven during a transition week. Re-check the gap whenever a meeting lands near a clock change rather than trusting a number you memorised last month.
Confirm before you both forget
Agreement is not a booking. The moment the client picks a slot, write it to both calendars and let the invitation carry the time zone for you. A proper calendar event stores the absolute moment, so it renders correctly on each side no matter where either of you travels next.
Send the invite immediately while the reply is fresh, set a sensible reminder, and add a one-line agenda so the event is self-explanatory days later. If you handle scheduling for someone else, the same discipline applies, just multiplied: see our notes on time zone scheduling for executive assistants for handling several principals at once.
Let the tool do the maths
The reason these messages take so long is the conversion in your head, and that is exactly the part worth automating. Atlas lets you pin the client on a world map, see the overlap where you are both awake, and write the meeting to your calendar in one tap, with every offset, half-hour quirk and daylight-saving shift already handled. You spend your effort on the agenda, not the arithmetic.
Frequently asked
How do I schedule a meeting with an international client without endless emails?
Why does "what works for you?" cause scheduling loops?
How should I write a time zone so a client can't misread it?
Whose time zone should the meeting be proposed in?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.