Every podcast host eventually lives the nightmare: the perfect guest, locked in, and then - silence at record time. Nine times out of ten it wasn't a flake. It was a time zone mix-up. Someone confirmed "3 PM" without saying whose 3 PM, daylight saving shifted the gap by an hour, or "Tuesday" turned into "Wednesday" across the date line.

Booking international guests is a solved problem if you have a system.

Why time zone no-shows happen

Three failure modes account for almost every missed recording:

Ambiguous time.

"Let's do 3 PM" with no zone attached. The host thinks their zone; the guest thinks theirs.

Daylight saving drift.

The gap between two cities isn't fixed - it shifts by an hour during the weeks when one region has changed clocks and the other hasn't. A time that was right last month is wrong this week.

Date confusion.

A late-evening slot in one zone is the next day in another. "Thursday 9 PM" your time can be "Friday morning" for a guest in Asia or Australia.

The 5-step booking system

1. Always state the time zone - and the guest's local equivalent

Never send a bare time. Write it as: "Tuesday, June 16, at 10:00 AM your time (Sydney) - that's Monday, June 15, 5:00 PM my time (Pacific)." Spelling out both local times and both dates removes every ambiguity.

2. Find a slot that's humane for both of you

Use a converter's side-by-side view to hunt for the overlap window where both of you are in reasonable working hours. If no comfortable overlap exists, agree explicitly on who takes the awkward hour - and thank them for it.

3. Send a calendar invite, not just a message

A proper calendar invite (Google Calendar, Outlook, etc.) stores the event in UTC under the hood and displays it in each person's own local time automatically. A plain text message in chat does not do this.

4. Double-check around daylight saving transitions

If your recording falls near a clock change, re-verify. 2026 transition dates: US & Canada - March 8 and November 1; UK & EU - March 29 and October 25; Australia (eastern states) - April 5 and October 4.

5. Send a reminder with both local times

24 hours out, send a short reminder that again states both local times and dates. This catches anyone who saved the wrong time originally.

Common civilized overlaps

When two people are far apart, someone may be recording early or late. Look for these workable windows:

  • - US West Coast ↔ Western Europe: early morning Pacific / late afternoon Europe.
  • - US East Coast ↔ Australia/NZ: evening US / morning next-day in Australia.
  • - Europe ↔ Asia: morning Europe / afternoon-evening Asia.

A copy-paste outreach line

"I'd love to have you on. I'm in [your city/zone] and I know you're in [their city/zone]. Would [day, date] work? I can do anything between [X-Y your time], which is [converted range] your time - whatever's least disruptive for you. I'll send a calendar invite so the time shows correctly on your end."

That single paragraph signals you respect their schedule and quietly eliminates the ambiguity that causes no-shows.

Quick checklist

  • ✅ State the time in both zones, with both dates.
  • ✅ Find a slot inside a humane overlap window.
  • ✅ Send a real calendar invite, not just a chat message.
  • ✅ Re-verify if near a 2026 DST transition.
  • ✅ Send a 24-hour reminder restating both local times.