How to propose meeting times across time zones
Cross-timezone scheduling fails when each person mentally converts differently. The fix is boring and effective: pick a reference timezone, list times in that zone (or dual-label each option), and only offer hours that fall inside both people’s working days.
You do not need a booking link to do this well. You need overlap-aware options and wording that makes the conversion obvious.
Steps
- 1
Establish both working hours
Note your local working window and theirs if you know it (or ask). A slot that is 4pm for you may be 8am or 1am for them — cut those before you propose.
- 2
Pick a reference timezone for the message
Common approaches: list everything in their timezone (easier for them), or list in yours and add a dual label. State the choice in the first sentence.
- 3
Convert the candidate windows once
Use a time-zone converter or meeting overlap helper so you are not doing arithmetic in your head. Double-check dates around DST transitions.
- 4
Offer two to four overlapping options
Fewer, better options beat a dozen marginal ones. Prefer mid-overlap hours over edge cases that only work if someone stretches.
- 5
Ask them to confirm the zone when they reply
Invite a reply like “Thu 10am Pacific works.” Restating the zone in the confirmation catches mismatches before the invite goes out.
Skip the manual steps — get your cross-timezone availability from Google Calendar
Sign in once, generate free times, and paste them into the message you already started.
Free · Read-only calendar access
Example cross-timezone proposals
Example only — sample times, not live calendar data. Copy and adapt.
Could we meet next week? Offering times in your timezone (UK / GMT): Tue: 3–4:30pm GMT (10–11:30am Eastern on my side) Wed: 4–5pm GMT (11am–12pm Eastern) 45 minutes is plenty — reply with a preference and I will send the invite.
Here are a few overlaps that work for both PT and ET: • Mon 1:00–2:00pm PT / 4:00–5:00pm ET • Wed 9:00–10:00am PT / 12:00–1:00pm ET Either work for a quick sync?
Frequently asked questions
Should I list both timezones for every option?
Dual labels reduce mistakes when people are new to each other’s zones. Once you have a rhythm, a single reference zone plus “I’ll send the invite in …” can be enough.
What about daylight saving changes?
Convert using the actual meeting dates, not “today’s” offset. Abbreviations like PST/PDT can flip; naming the city or region helps.
Is a world clock or converter enough?
Converters help for one-off math. For recurring cross-zone meetings, finding true overlap windows first saves rounds of email.
When is a booking link better across zones?
When many people need to self-serve against your hours and you maintain timezone rules in a scheduler. For a single thread, clear proposed times are usually faster.
Ready for your real calendar?
Pull live cross-timezone availability from Google Calendar and copy it in about ten seconds.
Free · Read-only calendar access