Skip to content
Convokast

How to Pitch International Podcasts Across Time Zones

Pitch international podcasts with location-based time zones, local-date confirmation and calendar invitations that survive daylight-saving changes and scheduling handoffs.

Research this article with AI

Follow Convokast on Google

Add Convokast to your Preferred Sources.

How to Pitch International Podcasts Across Time Zones

Pitch international podcasts around editorial fit first, then handle time zones as booking data. Ask for the host's city or named time zone, offer dated windows in both sides' local time and send a calendar invitation that carries the zone. Recheck the local date and clock time after every reschedule. Avoid building the booking around abbreviations or a copied offset.

International outreach also needs local show research. A podcast may publish in your language while serving a different market, business culture or audience problem. The topic must fit before scheduling matters.

Research the market as well as the show

Start with the show's own site, recent episodes and guest instructions. Identify where the host and production team work, the audience they address, the language used on air and whether the show records remotely. Do not infer all of that from a podcast-directory country label.

Listen for local references in recent episodes. A general business topic may need a regional case, regulation, customer behavior or market boundary to be useful. Only include those details when the guest can discuss them accurately. International relevance does not come from adding "global" to a domestic pitch.

Check whether the show publishes interviews and whether the proposed speaker resembles recent guests in role and subject. The guide to finding podcasts to guest on provides a research process that works across markets. Add local fit as a required field rather than treating geography as a list-building filter.

Record the host's stated submission route. A public form, producer address or guest policy should take priority over a guessed personal email. Use the language of the show unless its instructions invite another language.

Keep the first pitch focused on the conversation

A host does not need a block of time-zone arithmetic before deciding whether the topic fits. Lead with the audience problem, proposed premise and guest proof. Mention remote availability in one line if location could otherwise create doubt.

A concise sentence is enough: "The guest is based in Toronto and can record remotely during working hours that overlap with your production team." Save detailed windows for the reply unless the show requests them in the original submission.

The podcast guest pitch guide covers the core message. For an international pitch, add only the details that reduce genuine uncertainty: location, recording language, remote setup and any market-specific reason for the angle.

Avoid apologizing for the time difference. Scheduling is an operating task, not a weakness in the guest. The useful question is whether both sides have a workable overlap.

Ask for a named time zone

When the host expresses interest, ask for their city or location-based time zone and confirm the guest's. Names such as Europe/Paris or America/Toronto give calendar systems a rule set tied to a location. A bare abbreviation can be unclear, and a fixed numeric offset may stop matching local clocks when daylight-saving rules change.

IANA explains that its Time Zone Database represents the history of local time for representative locations and is updated when political bodies change boundaries, UTC offsets or daylight-saving rules. Software vendors distribute those updates to users. That is why the booking record should retain the named zone rather than a manually calculated offset alone.

The iCalendar specification, RFC 5545, defines the TZID parameter used to connect a local date and time to a time-zone definition. It distinguishes that from UTC and from a "floating" local time with no zone attached. A booking team does not need to write calendar code, but it should use calendar software that stores the event with the intended zone.

Ask plainly: "Which city or time zone should we use for the recording?" Confirm the answer in the booking note.

Offer dated windows that each side can verify

Send a small set of workable windows. Every option should include the date, guest-local time, host-local time and named zones. Include the weekday because an interview can fall on different local dates when the parties are far apart.

Use a format like this:

OptionGuest local timeHost local timeStatus
ATuesday, morning, America/TorontoTuesday, afternoon, Europe/ParisAvailable
BWednesday, late morning, America/TorontoWednesday, late afternoon, Europe/ParisAvailable
CThursday, early morning, America/TorontoThursday, evening, Europe/ParisAvailable if confirmed

Replace the descriptive times with exact clock times in the real email. The table here shows the fields without inventing a universal schedule. Generate the conversion for the actual date, then have a second person or calendar view verify it.

RFC 3339, the Internet timestamp standard, explains that a numeric local offset expresses the relationship between local time and UTC. That is useful for representing a specific instant, but a future booking still benefits from the location-based zone because civil-time rules can change. Do not reuse a conversion from a different date.

Let the calendar invitation carry the booking

Once the host selects a window, send or accept one canonical invitation. It should contain the event title, guest, host, recording link, named time zone, expected format and contact for changes. Avoid separate invitations from the guest, host and booking agency.

If the host owns the production calendar, follow their process. If the guest team sends the event, assign one owner who can update the time and link. Changing a conferencing link in a side email while leaving the event untouched creates two versions of the booking.

Check the invitation in both local calendar views. Confirm the date as well as the clock time. Then reply in writing with a short statement of each side's local date and time. This catches mistakes before anyone relies on the event alone.

The booking note should record the zone names, event owner and last confirmation. Keep a change log when the event moves.

Recheck after daylight-saving changes and reschedules

A booking arranged well in advance may cross a seasonal clock change for one side before the other. The time difference between the locations can therefore change even when neither person's usual working hours have changed.

Reopen the event close to recording and verify both local views. Repeat the check whenever the date moves. Do not edit only the clock field in an email and assume the calendar follows.

If a participant travels, update the booking from their actual recording location. A guest who normally works in one zone may join from another. Ask whether the available window remains correct and whether the recording setup has changed.

Keep the conversion language concrete: "The invitation shows Tuesday at [guest time and zone] and Tuesday at [host time and zone]." Avoid "same time as before" after any date or location change.

Prepare for language and production differences

Time-zone accuracy gets the guest into the room. The interview still needs preparation for the show's language, pace and production expectations.

Confirm whether the conversation will be in the guest's first language, whether the host wants written terms or names in advance and whether interpretation is involved. Send pronunciation guidance for names, companies and technical terms. If the show uses live video, confirm camera expectations and whether the guest's connection is strong enough from the recording location.

Read recent episode descriptions for the show's preferred terminology. A guest can explain a market difference without pretending every audience uses their home-market language. The podcast interview preparation guide can hold these notes beside the angle and supporting examples.

Give the guest the host's local context, but do not script cultural stereotypes. Specific editorial evidence from the show is useful. Assumptions about an entire country are not.

Follow up in the host's working day

Schedule human follow-up for a reasonable hour in the host's zone. The message may be read later regardless, but a sensible send time makes a live reply easier and reduces accidental urgency outside working hours.

Keep the follow-up tied to the existing thread. Restate the proposed premise and ask whether additional information would help. If the host has already shown interest, include the current scheduling options or booking link. If they have not replied, do not fill the follow-up with time-zone detail.

Use one campaign owner to prevent the guest, agency and colleague from sending separate scheduling messages. The same owner should watch for replies that arrive during the guest team's night and respond when the working day begins.

International podcast outreach is manageable when editorial research and scheduling are kept as separate jobs with one shared record. If you want Convokast to research suitable shows, manage host communication and carry the calendar handoff through recording, talk to us about an international booking campaign.

Common questions

How should I write time zones in a podcast booking email?

Use the date, local clock time and a named location-based time zone, then send a calendar invitation that converts for each attendee. Avoid relying only on abbreviations, since they may be unclear or change with daylight-saving rules.

Should I include available times in the first podcast pitch?

Usually the first message should establish audience and topic fit. Share availability after the host expresses interest, unless the show's submission process specifically requests recording windows.

How can I avoid daylight-saving mistakes in an international booking?

Store the event with a named time zone, confirm the local date and time for both sides and recheck after any reschedule or when the recording date approaches. Do not copy an old numeric offset into a new date.

Who should send the calendar invitation for an international podcast interview?

Follow the host's normal process when they own scheduling. If the guest team sends the invitation, one named person should own the event, conferencing link and updates so every attendee receives the same change.

international podcast outreachpodcast schedulingtime zones

Work with us

Want to be the guest, not the reader?

We pitch, book, and prep you for the shows your buyers already listen to.

Book a discovery call

Free 20-minute call. If we are not a fit, we will say so.