Eight Guest Booking Mistakes That Cost a Weekly Show an Episode

Sending an Invite Without Confirming the Time Zone

Podcasters run shows with guests from every corner of the country, and often from different continents. Still, it is easy to forget that not everyone speaks in Eastern Time or Pacific Time. If you send a calendar invite with just a time, say, "Wednesday at 4", but don't specify the zone, you're already rolling the dice. The guest may assume their own local time, leading to confusion or missed calls.

Even with digital calendars, errors creep in. Some calendar platforms default to the sender's time zone, while others try to guess based on the recipient's location. If either side travels, settings can shift. Add daylight saving changes, and a 4 PM slot can become an accidental no-show.

The fix is simple: always clarify the time zone in your first invite and double-check that the calendar event specifies the zone correctly. Use UTC offsets or write out the city ("4:00 PM New York / 1:00 PM Los Angeles"). Before show day, reconfirm the time with the guest using both parties' local clocks. This step alone saves a pile of panicked reschedules.

Keep reading: Recording Consent Laws and Guest Releases for US Podcasts

Skipping the Backup Recorder on Both Ends

Every podcaster has a story about an episode that vanished into the void. The recording software crashed, the computer locked up, or an internet drop left a key segment full of gaps. When you only have one recording running, you're gambling with your guest's time and your own.

A backup recorder is not a luxury. It is the safety net that keeps a show on track when the main system fails. The best practice is to have both the host and the guest record locally, each on their own device or app. This way, if the connection breaks or one file gets corrupted, the other can fill in the gaps.

Make it a routine part of your pre-show talk: ask the guest to run a voice memo app on their phone or use a web-based recorder. Give clear instructions and walk them through a test. If you forget, you risk a disaster that only shows up when you hit "stop" and realize the file is missing or unusable.

Booking Back to Back With No Buffer for Tech Checks

Podcasters often try to maximize their time by booking guests back-to-back, especially when running multiple interviews in a day. On paper, it looks efficient, but in practice, it invites all kinds of problems. A guest may have trouble logging in, their microphone might not be recognized, or their internet could lag. Each of these problems can eat up ten or even twenty minutes.

Without a buffer, one tech delay dominoes into the next booking. The host rushes through setup, the guest feels flustered, and the conversation never gets comfortable. Worse, if a guest runs long or needs extra time to wrap up, you end up shortchanging either the current guest or the next one.

The solution is to build at least fifteen to thirty minutes between sessions. Use the buffer for audio checks, solving last-minute tech snafus, and letting everyone settle in. That margin is often the difference between a smooth session and a show that never gets recorded.

Keep reading: What the Mike Daisey Retraction Teaches About Vetting Guests

Letting a Guest Listen on Laptop Speakers

Audio quality is the foundation of a podcast. When a guest listens through laptop speakers, the microphone often picks up the speaker output and feeds it back into the call. This creates echo, feedback, or a hollow sound that can't be fixed in post-production. Even with noise cancellation, bleed-through can ruin a segment.

Many guests, especially those new to podcasting, don't realize this is a problem. They log in, hear fine, and assume all is well. The host may not notice until playback, when editing becomes a nightmare.

At the start of every booking, remind the guest to use headphones or earbuds. If they don't have any, ask them to mute when not speaking. Run a short soundcheck and listen for echo or doubling. Catching it before you hit record protects both the episode and your editing time.

Collecting the Bio and Headshot After the Record

A well-prepped introduction sets the tone for the episode. Yet, many hosts forget to request the guest's bio or headshot until after the interview. By then, the guest has mentally moved on. Their responses become slower, and sometimes the follow-up never arrives.

Without a bio, the host may scramble to write an intro from scratch, pulling details from LinkedIn or old press releases. Mistakes slip in, titles are outdated, and the energy for post-production drops. For the episode page or social media, the lack of a professional headshot lowers the show's polish and branding.

Ask for everything you need, bio, headshot, social links, before the recording day. Send a structured questionnaire or checklist as part of the booking process. This not only saves time but also signals to the guest that your show runs professionally. When these materials are in hand before the call, you can focus on the conversation, not the paperwork.

See how MicPrep handles this for podcasting

Not Verifying Name Pronunciation and Current Title

Getting a guest's name or title wrong is more than a small slip. It can sour the mood, create awkward moments, and start the interview on the wrong foot. Many names are pronounced differently than they look, and job titles change often, especially for guests in fast-moving industries.

If you rely on guesswork or old bios, you risk making a mistake right at the top. The guest may correct you on air, or worse, let you continue in error. This not only affects the guest's trust but also the credibility of your show.

The fix is to double-check pronunciation and titles as part of your pre-interview process. Ask your guest directly for the correct way to say their name and what title they'd like used in the intro. Some hosts record a short name pronunciation audio or ask for a voice note. This tiny step avoids embarrassment and sets a professional tone.

Rolling Tape Before the Release Is Signed

A guest release is your legal safety net. It gives you permission to record, edit, and distribute the conversation. Rolling tape before you have the release signed is risky. If the guest later objects to something said, or if their company asks for changes, you may have no legal standing to use the episode.

Verbal agreements are not enough. Memory fades, and misunderstandings can lead to disputes. Some guests assume an informal chat is off the record until paperwork is signed. In some cases, corporate or institutional guests are not even authorized to participate without formal approval.

Make the release part of your booking flow. Send it early, and require a signed copy before you start the call. Digital signature tools work best, but even a scanned PDF is better than nothing. Confirm receipt and save a copy in your records. This step will spare you from legal headaches and lost content down the line.

Reconfirming Too Late to Refill an Empty Slot

Weekly shows run on tight schedules. If a guest cancels at the last minute, it can mean a missed episode or a scramble for a replacement. Many hosts make the mistake of reconfirming the booking only hours before the record. If the guest bows out, there's no time to bring in a backup.

The better approach is to reconfirm a few days ahead of the session. This gives guests a chance to flag any conflicts early, while you're still able to reach out to alternates. If you wait until the morning of, you're stuck with an empty slot and a scramble.

Use a structured pre-interview process that includes an early reconfirmation and a clear cancellation policy. Some hosts keep a short list of standby guests, but even then, advance warning is key. The goal is to never leave a slot empty because of avoidable scheduling surprises.

A system that ties together scheduling, structured pre-interview forms, and automated reminders can reduce these risks. When guest booking, bio collection, and release management happen in one flow, missed details and last-minute surprises become far less common. This is the kind of workflow a tool like MicPrep is built to support.