The nine stages a guest moves through
A guest is not simply booked or unbooked. They move through nine states, and each one has a different next action attached to it. Idea, vetted, invited, follow-up owed, yes, scheduled, recorded, published, thanked. Naming the stage tells you what to do today without rereading the whole email thread.
| Stage | What it means | What moves it forward |
|---|---|---|
| Idea | A name you wrote down | Vet them against your audience |
| Vetted | Right person, right topic, right time | Find the warm path in |
| Invited | The ask went out | Wait five days |
| Follow-up owed | No reply, and the clock is running | Send the nudge you planned |
| Yes | They agreed, with no date yet | Offer three specific times |
| Scheduled | On both calendars, prep sent | Confirm the day before |
| Recorded | In the can, not yet edited | Hand it to editing |
| Published | Live in the feed | Send the guest their assets |
| Thanked | Loop closed | Set a re-engage date |
The value is not the label, it is the change of state. A guest sitting at invited for eleven days is a different problem from a guest sitting at yes for eleven days. The first needs a nudge, the second needs three dates, and you only see which one you are holding if the stage is written down somewhere other than your memory.
One row per guest, and five columns that do the work
One row per guest, never one row per episode. The person is the unit, because the same human can be an idea in March, a yes in May, and a re-engage in November. Five columns carry almost all of it: who, stage, date, next action, warm path.
- Guest. The person, plus the one link that proves who they are: their site, their profile, or the episode of somebody else's show where you first heard them.
- Stage. Where they are today, in one word from the list above. If you cannot name the stage, that is the problem, not the spreadsheet.
- Date. When they last moved. Someone who has not moved in two weeks is either owed something or gone cold, and the date is what tells you which.
- Next action. One specific thing with a date on it. Send the invite. Nudge. Offer times. Send prep. Never "follow up," which is a wish rather than an action.
- Warm path. Who could introduce you, or how you already know them. Filled in at idea, not recalled at invite, because that column decides whether the ask lands warm or cold.
Everything else is optional. Topic and notes are useful, and neither saves you if the stage and the next action are missing. A plain pipeline you keep current beats a beautiful one you abandon in week three.
The pipeline dies in the follow-up gap
Most invitations are not turned down. They get buried. The message lands on a bad day, gets marked unread, and disappears under everything else. A pipeline with no follow-up column loses those people silently, and the host reads the silence as a no it never actually was.
So the nudge is not pestering, it is the job. One around day five, while the invitation is still recent enough to place, and a second around day twelve, catches most of the people who meant to reply and did not. A third at three weeks is where you leave the door open and stop. Each one should carry something new: a date that opened up, a listener question, an episode that shows what the show actually is.
This gets skipped because it is invisible work with no deadline attached. Nobody notices the nudge you did not send. Pod Green Room tracks when each invite went out and queues follow-ups on a day five, day twelve, day twenty-one cadence, so the guest pipeline keeps moving during the weeks you are underwater with editing.
The calendar math of a feed that stays full
A weekly show needs a booked pipeline four to six weeks deep. Not four to six names on a list, four to six recordings with dates. Anything shallower and one cancellation puts a hole in the feed, because there is no time left to invite someone, hear back, and schedule them.
Work backwards from the release date. A conversation recorded Monday is not in the feed Wednesday. It needs editing, show notes, art, and a buffer, so the recording happens weeks before the episode it becomes. Then add booking lag. From first invite to recorded is rarely under three weeks, because the ask, the silence, the nudge, the yes, and the calendar each take real days.
So the depth you need is a stack, not a number: a few recorded and waiting, a few scheduled, a few invited, and vetted names behind them. When a feed goes quiet, the cause is rarely a bad episode. It is an empty stage four weeks earlier that nobody was watching.
Vet before you invite, not after
The ask is a limited resource. Every invitation spends a little of your credibility and a lot of your week, so the question of whether this person is right for your audience belongs before the email, not after the yes. A famous guest who is wrong for your listeners costs you both.
- Would your listeners recognize the problem this person solves, even if they do not recognize the name?
- Is there one question only they can answer, or are you booking a job title?
- Have they already said this on ten other shows? Someone can be excellent and still be out of new material.
- Do they have a reason to share the episode: a launch, a book, an audience they are building?
- Can you reach them warmly, or is this a cold ask you will spend three weeks on?
Most hosts skip this because vetting is slower than inviting and nobody is watching them do it. Pod Green Room ranks the contacts you already have by audience fit and warmth, then drafts a specific episode concept for each match, so what enters the guest pipeline has already survived a real question about whether your listeners want it.
The two failures that cost the most
Two things break a pipeline that looks healthy on paper. The double-booking, where two guests both believe they have the same Tuesday. And the gone-cold yes, where somebody agreed six weeks ago, no date was ever offered, and the moment passed. Both are tracking failures, not people failures.
- The double-booking. Someone has to be moved, and the person you move learns exactly how organized you are. It happens when the calendar and the pipeline are separate places and only one of them got updated.
- The gone-cold yes. They agreed in April, nobody sent times, and by June the enthusiasm is gone and the follow-up feels awkward. A yes is a stage with an expiry date, and the action after it is always offering specific times.
- The forgotten thank-you. The episode ships, the guest shares it once, and then nothing. A relationship that could have brought referrals ends at published because no last step was written down.
A yes is not a booking, and a booking is not a published episode. Track the stage, the date it changed, and the single action that moves it next. Almost everything expensive happens in the space between two stages.
When the spreadsheet stops keeping up
A spreadsheet is a good first pipeline, and it holds longer than software companies like to admit. It stops holding the day something moves. One guest reschedules, and the recording date, the editing window, the release date, and the social post you promised all move with it.
One reschedule is survivable. The tell is when the same fact has to stay true in three places at once: the guest's row, the episode calendar, and your follow-up list. That is where a sheet starts quietly lying to you. Pod Green Room works as a podcast CRM for exactly that, keeping guests, invites, prep pages, and series lineups tied to the episodes they belong to, so a moved recording carries the rest with it.
None of that matters until the basics exist, and the basics are a stage, a date, and a next action for every name. The step-by-step on who to write to and what to send at each stage is in the guide to booking podcast guests. The actual emails, including the invite, the nudge, and the re-engage note, are in the template library.