The window between yes and record is where bookings die
A yes is not a booking. It is an intention that has to survive weeks of someone else's calendar. Everything that happens between the yes and the recording either turns that intention into a date on a calendar or leaves it as a nice email nobody acted on.
Most hosts treat this stretch as admin they will get to. It is not admin. It is the part of the job that decides whether the guest shows up prepared, whether the conversation is any good, and whether they answer your email the next time you have an idea.
Three things go wrong in that window, and it is the same three every time.
- The date was never truly locked. You agreed on a Thursday in a thread, nobody put it on a calendar, and by the time Thursday arrives it belongs to someone else.
- The guest arrives not knowing the topic. They said yes to you, not to a subject, and now the first fifteen minutes are you explaining the show while the recording rolls.
- The tech eats the beginning. Wrong browser, no headphones, a permissions dialog nobody warned them about, and a good conversation starts twenty minutes late and slightly annoyed.
None of that requires a producer to fix. It requires a sequence you run the same way for every guest, so the parts that fail quietly stop being the parts you were meaning to get to.
Lock the date the same day they say yes
Send the calendar invite within a few hours of the yes, and put the recording link inside the invite itself. A date that lives only in an email thread is not locked. A date sitting on their calendar with the join link attached is the closest thing to a guarantee you get.
The most common version of this failure is polite and fatal: a confirmation that promises the recording link will follow closer to the date. Something always happens between the promise and the sending. Now the guest has a date with no link, you have a reminder to write another email, and one of you forgets.
Put the join link in the invite body, name the length in the title, and include the time zone. If your recording tool generates a room, generate it now instead of the morning of. The recording confirmation email is written to carry all of it in one message, including the sentence that tells a nervous guest what the session will feel like.
Then say the thing most confirmations leave out: moving the date is fine and takes one reply. A guest who believes rescheduling requires an apology will go quiet instead of asking.
Write the prep doc as one page, not a script
One page, sent with the confirmation, covering what the episode is about, the areas you want to explore, and how the recording works. Question areas rather than a question list. A guest who rehearses answers to exact questions will read them back to you, and that recording is dead on arrival.
- The premise in two sentences. What this episode is about, and why you asked them specifically.
- Three to five question areas. Themes, not wording. Enough for them to think about, not enough to memorize.
- Who listens. A guest speaks differently to founders than to career changers, and they cannot adjust if you never told them.
- The tech check. Headphones, a quiet room, the browser your tool needs, and a wired connection if they have one.
- The length, and whether you tend to run over.
- How editing works. Whether they can restart an answer, whether anything can be cut, and who has final say.
The editing paragraph does more work than the rest of the page combined. A guest who knows a bad sentence can be pulled will speak freely. A guest who suspects the whole thing is going out untouched hedges every answer, and you spend the edit trying to rescue a conversation that never happened.
Collect what you need before you need it
Ask for the bio, the headshot, the pronunciation of their name, and the links they want plugged in the same message as the confirmation. Wanting all of it on release day is what turns a finished episode into a week of chasing attachments.
Pronunciation belongs at the top of that list and almost never makes it. Ask for it in writing, spelled the way it sounds, and use it in the intro. It is the smallest possible signal that you did the work, and the guests whose names get mangled everywhere else notice immediately.
Keep all of it attached to the booking instead of scattered across a thread. Pod Green Room does that with guest tracking and a prep page for each booked guest, so the bio, the headshot, and the date sit in one record rather than in four replies you have to go find.
Remind them a week out and again the day before
Two reminders, no more. A week out gives them room to move things without guilt. The day before is the one that saves the recording, because it puts the link and the time in front of them while tomorrow is still something they can plan around.
Both reminders repeat the link. Not a reference to the earlier email, the link itself. Assume every prior message is buried and write each one as though it is the only thing they will read.
Running this from memory holds up until you have three guests booked in a month. A guest pipeline with follow-up nudges is what Pod Green Room is built to hold, so the week-out note and the day-before note go out on the days you planned them instead of the days you happened to remember.
Tell the truth about promotion
Say exactly what you will send and when, then stop. Ready-to-post captions, a clip, the link on release day. Promising a guest reach you cannot deliver is the fastest way to make a good episode the last one that person records with you.
Most guests are not counting your downloads. They want to know the episode will exist, roughly when, and whether sharing it will take more than a minute. Answer those three and you have set an expectation you can keep.
Then keep it. On release day, hand them the link and a caption they can post as written, which is what the share request is built to do. The rest of the sequence, from the first invite through the thank-you, lives in the template library.
Run the day the way you promised
Be in the room early, run a real tech check before you start recording, and end when you said you would. The recording itself is the easy part when the ten minutes in front of it are done properly.
- Open the room early. A guest who arrives to an empty studio spends the first minute wondering whether they got the time wrong.
- Check audio before the record button, not after. Headphones on, levels visible, one sentence back to them about how they sound.
- Spend a few minutes not recording. Ask about their week. The stiffest part of any conversation is the opening, and you want to spend it off the record.
- Say the shape out loud. How long, where you will start, and that anything can be restarted.
- End on time. Running long is a small theft, and the guests who let it happen without complaining are often the ones who stop replying.
What all of this protects is the second yes. A guest who had a well-run hour tells other people, comes back for a follow-up episode, and answers when you ask for an introduction. The full sequence from first outreach through the recording is laid out in the guide to booking podcast guests.