It's 14:02. The room is quiet, your levels are good, the guest is not there.
At 14:06 you start refreshing your inbox. By 14:11 you're writing a message, deleting it, writing a shorter one. Somewhere around 14:17 you decide they've bailed on you, close the laptop, and then they join at 14:22 with a cheerful "sorry, back-to-back!" and no idea that you spent twenty minutes rehearsing how annoyed to sound.
This article is the protocol I wish someone had handed me for those twenty minutes. It's written for the host sitting in the recording room with the clock running. Booking advice, no-show prevention, contracts, all of that comes later in the piece, because none of it helps you at 14:06.
Most late guests are not no-shows
Start here, because it changes every decision that follows.
Most guests who aren't there at the top of the hour turn up. They're on another call that ran over. They're in the parking lot. They clicked the calendar invite instead of the studio link and are sitting in an empty Google Meet wondering where you are.
The mistake isn't waiting. The mistake is treating minute 6 like minute 30: composing the wounded-professional email, mentally cancelling, letting your energy drain out so that when they do arrive you sound like someone doing them a favor. Guests hear that. Alex Blumberg's On Interviewing makes the point from the other direction: the more certain you are in your behavior, the more relaxed your guest is. A host who has spent twenty minutes stewing is not projecting certainty. It costs you the first ten minutes of tape.
So: assume late until proven absent, and give "proven" a specific number.
The protocol, minute by minute
Minutes 0 to 4. Do nothing, and hit record.
No message yet. Four minutes late is not late in most people's calendars, and a "just checking, are we still on?" at minute 2 reads as anxious.
Do start the recording, though. Two reasons. You will never again have the conversation where someone says something great in the first ninety seconds and you realize the transport was stopped. And the small talk when they finally join, the apology, the story about the meeting that ran long, is often better cold-open material than anything in your outline. You can always delete the file.
Minute 5. One message, on the channel they actually read.
Short and unbothered:
"Hey [name] — I'm in the studio and set up whenever you are. Here's the link again: [link]. No rush."
That message does three jobs. It re-delivers the link, which in my experience is the fix for a lot of late guests: they aren't avoiding you, they just can't find it. It sets no emotional tone you'll have to walk back. And it gives them a socially cheap way to arrive late without an apology tour.
Channel matters more than wording here. Email is the wrong pick. Someone who is late is late because they're in something else, and nobody in a meeting checks email. Send it wherever you last had a real back-and-forth with them: WhatsApp, SMS, LinkedIn DM, the Slack Connect channel their PR person set up.
Minute 10. Second message. Open the reschedule door without walking through it.
"No problem at all if today's gone sideways — happy to grab another slot. If you can still make the next 20 minutes, I'm here and we can do a tight version."
The second half of that sentence is the part that saves episodes. You've just told them a shortened recording is a real option, which is the thing a flustered latecomer most needs to hear. Plenty of guests who would have quietly cancelled will take a 25-minute version instead.
Minute 15. Decide.
This is the line I'd draw for a normal guest. If there has been no reply of any kind on any channel by minute 15, stop waiting for the episode to happen and start doing something useful with the room.
Two exceptions, and they're worth honoring: a guest in another timezone who has crossed a date boundary, and a genuinely senior person whose assistant does the scheduling. For those, wait 25 and route the second message through the assistant.
Minute 20 onward. It's a no-show. Behave accordingly.
Send one line closing the loop, then stop thinking about it:
"Looks like today didn't work out — no drama. Send me two windows that suit you next week and I'll take one."
Note what that doesn't do. It doesn't ask for an explanation, it doesn't perform disappointment, and it doesn't offer to re-book on the spot with a link, which puts the work back on you. Two windows, from them.
The 38-minute episode
Here's the situation nobody writes about. They joined at 14:22. You have the room until 15:00. You planned a 60-minute conversation and you have 38 minutes.
Your instinct will be to cram. Resist it. A 60-minute outline delivered in 38 minutes produces an episode where every answer gets cut off one beat before it gets good.
Cut segments instead. NPR's show editor's interview checklist makes the point that you want the right number of questions for the length of the segment, not the maximum number. Applied here: take your run-of-show, delete two whole topics, and keep the follow-up depth on what's left. Three topics explored properly beats five topics sampled.
Then tell the guest the new shape, out loud, in one sentence. "We've got about 35 minutes, so I'm going to skip the origin-story section and go straight to the [X] thing." Guests relax when they know the frame. They also stop trying to fit their whole life story into the first answer.
One more thing, and it's the part people skip: decide before you start whether this is still a publishable episode or a pre-interview you're going to redo. Both are fine. What ruins the tape is deciding at minute 30.
Where an AI producer helps
Re-planning an episode in the ninety seconds while your guest connects their headphones is genuinely hard, and it's the part of this that software can actually take off your hands.
Liyam keeps your on-screen script visible while you record, with the run-of-show organized by topic, which is what makes "delete two topics and keep the depth" a decision you can make in a few seconds rather than a scramble through your notes. Pacing prompts are optional cues that keep you on structure without scripting you, which matters most on a compressed clock. Live questions generate real-time follow-ups from what's actually being said, so when you've cut your topic list in half you can go deeper on what's left instead of reaching for the next prepared question.
And if the late start is because the guest never had a prep call, the prep call agent can sit in on one and draft the outline, segments and questions from the conversation, or you can drop your research in as files, links and notes and get a ready-to-record structure back.
None of that stops a guest being late. It shortens the distance between "they're here, twenty minutes down" and "we're recording something good."
Making it happen less often
Prevention is worth exactly one section, at the end, because it's the least useful thing to read while you're waiting.
- Put the studio link in the calendar invite itself, in the location field, not only in an email. Wrong link and wrong platform cause more late joins than anything else I've run into, and this costs nothing to fix.
- Confirm 24 hours out, and again 30 minutes out. The 30-minute one is the one that works. One line, with the link. Those two messages are the tail end of a longer sequence — see what to send a podcast guest before recording.
- Write the timezone the way normal people read it: "Tuesday 2:00pm New York time (7:00pm London)". Never just "2pm ET".
- Do a pre-interview. Transom's art of the pre-interview is about story, but it has a useful side effect: a guest who has already spoken to you once treats the recording as an appointment with a person, not a slot in a calendar.
- Build a two-episode buffer. Not glamorous. It converts a no-show from a crisis into an inconvenience, and it's the only structural fix on this list.
FAQ
How long should I wait for a podcast guest before cancelling?
Fifteen minutes for a standard guest. Twenty-five if they're in another timezone or their scheduling runs through an assistant. Message at minute 5 and again at minute 10 before you make that call, and send those messages somewhere other than email.
Should I keep recording while I wait?
Yes. Start the transport at the scheduled time and leave it running. Storage is cheap, and the unguarded two minutes right after a late guest joins are frequently the best cold open you'll get all week.
What do I say to a guest who is twenty minutes late and doesn't apologize?
Nothing about the lateness, on tape. Say "we've got about 35 minutes, so I'm going straight to [topic]" and get moving. If it's a pattern with someone you want to keep booking, raise it afterwards in writing, once, without heat.
Is it worth having a no-show policy?
For a hobby show, no. For a show where you're paying for a studio or an editor, one line in the booking confirmation does the job: what happens if they can't make it, and how much notice you need. Cancellation fees are overkill and they cost you guests.
Bottom line
Wait fifteen minutes. Message at 5 and at 10, on a channel they actually read, and keep both messages free of any tone you'd have to walk back later. Record from the top of the hour regardless. When they arrive, cut topics rather than depth, and say the new shape out loud.
A late guest almost never costs you the episode. Handling the wait badly costs you the first ten minutes of the one you get.
If you'd rather have the run-of-show, the pacing and the live follow-ups handled while you're doing that re-planning in your head, that's what Liyam AI is built for. There's a free trial, so you can point it at your next recording and find out whether it holds up on a bad day.