How to Share Availability Across Time Zones (Without Confusion)

By Rohan · Last updated: March 2026

You offer 2pm. They think you mean their 2pm. You meant your 2pm. Now someone is sitting in a Zoom room alone at the wrong hour, and the meeting has to be rescheduled.

Timezone confusion is the most common cause of scheduling failures in remote and international work. It's not that people don't know time zones exist — it's that they forget to specify, assume the other person will convert, or get the math wrong.

Here's how to share your availability across time zones clearly, so the meeting actually happens on the first try.

---

Rule 1: Always State Your Timezone

This is the single most important rule. Every time you share availability — whether by email, Slack, text, or any other channel — include the timezone.

Good:

Here are some times that work (EST):

Tue (3/25): 9-10am
Wed (3/26): 2-3pm

Bad:

I'm free Tuesday 9-10 or Wednesday 2-3.

The second version is ambiguous. If you're in New York and they're in London, "9-10" could mean 9am EST (2pm GMT) or they might assume you meant 9am their time.

Put the timezone in the header line before the list. Use standard abbreviations: EST, CST, MST, PST for US time zones, or GMT/UTC offsets for international scheduling (UTC+1, UTC+5:30, etc.).

---

Rule 2: Use the Recipient's Timezone When Possible

If you know what timezone the other person is in, convert your times to their timezone. This removes the mental math from their side and makes it dramatically easier to say yes.

Even better — show both:

Here are some times that work:

Tue (3/25): 9-10am PST / 12-1pm EST
Wed (3/26): 2-3pm PST / 5-6pm EST
Thu (3/27): 10-11am PST / 1-2pm EST

This format eliminates all ambiguity. Both parties can see the time in their own timezone without doing any conversion.

---

Rule 3: Be Aware of Daylight Saving Time

Daylight Saving Time is the silent killer of cross-timezone scheduling. The US, UK, EU, and Australia all switch at different dates, which means the offset between two locations can change by an hour (or sometimes two) at unpredictable times.

For example:

• US "springs forward" on the second Sunday of March
• UK "springs forward" on the last Sunday of March
• During the gap between those dates, the US-UK offset is 4 hours instead of the usual 5

If you're scheduling a meeting 2-3 weeks out and it crosses a DST boundary, double-check the offset for the actual date of the meeting, not today's offset.

The easiest way to avoid DST confusion: use a tool that handles timezone conversion automatically, or specify "EST" vs "EDT" explicitly if you're being precise.

---

Rule 4: Don't Make Them Do the Math

Some people include their timezone and expect the other person to convert. This technically works, but it adds friction — and friction kills scheduling.

If you know they're in a different timezone, do the conversion yourself. If you don't know their timezone, state yours clearly and invite them to confirm:

Here are some times that work (PST — I'm in San Francisco):

Tue (3/25): 10-11am
Wed (3/26): 1-2pm
Thu (3/27): 9-10am

Let me know your timezone and I'm happy to convert these, or feel free to suggest times that work on your end!

---

How to Share Cross-Timezone Availability Quickly

Manually converting times across time zones is tedious and error-prone. If you're scheduling with people in different time zones regularly, it helps to automate this.

ShareAvailability generates your availability in any timezone you choose — not just your local one. If you're in New York but scheduling with someone in London, you can generate your free times displayed in GMT. The tool pulls from your Google Calendar, applies the timezone conversion, and outputs a clean text list.

This is especially useful when:

• You're scheduling across 3 or more time zones (e.g., a team call with people in New York, London, and Tokyo)
• You travel frequently and your local timezone changes
• You're scheduling weeks out and DST boundaries are involved
• You're a remote worker whose teammates are scattered across the world

The output includes the timezone label automatically, so you won't forget to include it.

---

International Scheduling: GMT vs UTC vs Named Timezones

When scheduling internationally, you'll encounter different timezone formats:

Named abbreviations (EST, PST, GMT, IST): Most familiar in casual communication. The problem is that some abbreviations are ambiguous — "IST" could mean India Standard Time, Israel Standard Time, or Irish Standard Time.

UTC offsets (UTC+5:30, UTC-8): Unambiguous and universally understood. Best for international scheduling where named abbreviations might be confusing.

City names (New York time, London time, Tokyo time): The most intuitive option when you know the other person's city. "Let's meet at 3pm London time" is clearer than "3pm GMT" (which doesn't account for British Summer Time).

For most professional scheduling, named abbreviations work fine within the same country. For international scheduling, UTC offsets or city names are safer.

---

Templates for Cross-Timezone Scheduling

When You Know Their Timezone

Here are some times that work (shown in both our time zones):

Tue (3/25): 9-10am PST / 5-6pm GMT
Wed (3/26): 11am-12pm PST / 7-8pm GMT
Thu (3/27): 8-9am PST / 4-5pm GMT

Let me know which works best!

When You Don't Know Their Timezone

Here are some times I'm available (EST — I'm based in New York):

Mon (3/24): 10-11am
Tue (3/25): 2-3pm
Wed (3/26): 9-10am

What timezone are you in? Happy to convert these or suggest times that work better for your schedule.

When Scheduling Across 3+ Time Zones

For group scheduling across multiple time zones, it helps to pick one reference timezone and let everyone convert:

Trying to find a time for all three of us. Here are some windows that might work (shown in UTC):

Tue (3/25): 2-3pm UTC (10am EDT / 7am PDT / 10pm JST)
Wed (3/26): 1-2pm UTC (9am EDT / 6am PDT / 9pm JST)
Thu (3/27): 3-4pm UTC (11am EDT / 8am PDT / 11pm JST)

Let me know if any of these work for everyone!

---

Common Timezone Scheduling Mistakes

Forgetting to include the timezone at all. The number one mistake. Even if you think you're in the same timezone, include it. People travel, relocate, and work remotely from unexpected places.

Using ambiguous abbreviations internationally. "CST" means Central Standard Time in the US but China Standard Time in Asia. When scheduling internationally, use UTC offsets or city names.

Not accounting for DST. If you're scheduling more than 2 weeks out, check whether a DST change falls between now and the meeting date.

Assuming the other person will convert. If you know their timezone, do the conversion for them. It takes you 30 seconds and saves them the effort (and risk of getting it wrong).

---

The Bottom Line

Timezone confusion is completely avoidable. State your timezone every time, convert to the recipient's timezone when you can, and show both time zones for maximum clarity.

If you schedule across time zones regularly, ShareAvailability can generate your availability in any timezone and label it automatically — so there's no chance of forgetting the timezone or getting the conversion wrong.