This is a two-person workflow
This piece assumes you already work with a producer or a screening assistant who reads pitches before you do. If you sort your own inbox solo, the two-question triage in how to triage inbound guest pitches is the faster fit. What follows solves a different problem: getting two people to a decision without a meeting.
Why the greenlight call keeps slipping
A producer forwards five pitches on Tuesday. You are recording, then traveling, then behind on a different guest's onboarding. By the time a slot opens for a call, the producer has forgotten which pitch had the warm intro and which was a mail-merge. The pitch waits on a shared calendar instead of a decision.
A verdict formed out loud in a live conversation lives in that conversation and nowhere else. Move it onto a record both of you can open on your own time, and the meeting stops being the thing standing between a pitch and an answer.
What the producer fills in, what you fill in
The rubric has two owners. The producer fills in what came in: the topic, where the pitch came from, and whether there is a real connection behind it. You fill in one field only, the verdict: yes, no, or hold, with one line on why. Neither of you touches the other's field.
| Field | Who fills it | What it captures |
|---|---|---|
| Topic and fit | Producer | Whether the pitch matches an episode your audience already shows up for |
| Source and connection | Producer | Cold blast, a mutual, or a guest referral, and how strong the thread is |
| Verdict | Host | Yes, no, or hold, decided from the two fields above |
| Reason | Host | One line explaining the verdict, for the record the producer reads next |
The decision log is what keeps the review async
A rubric without a log gets re-argued. Write the verdict once, with the date and the reason, and treat it as closed. The log is where a decision stays decided. If the producer disagrees, they add a note under the existing verdict instead of forwarding the pitch again.
This is the same principle that works for handing podcast editing to a VA: a standing artifact removes the live explanation, once. Here the artifact is the pitch record instead of a checklist, and the two people are you and your producer instead of you and an editor.
A week of async review, start to finish
The workflow runs on whatever cadence pitches actually arrive, not a scheduled sync. Five steps carry it from inbox to booked slot, and none of them require both of you online at the same time.
- The producer screens the inbox and forwards anything on-topic, filling in the topic and connection fields on each pitch as they go.
- You open the queue once a day, or whenever you have ten minutes, and read only the two filled-in fields, not the original pitch email.
- You write the verdict and one line of reason directly on the record. That is the whole decision.
- The producer sees the verdict the next time they open the same view and acts on it: sends the yes, sends the decline, or books the hold for the weekly batch.
- Anything marked hold gets one look every week. Anything untouched after two weeks defaults to decline. Nothing ages out silently.
When the async review is not enough
Two cases still need a real conversation. A pitch the producer flags as a possible yes but you read as a pass, or the reverse, is worth five minutes live before either of you commits language to the guest. A guest above your usual ceiling, a sponsor conflict, or a legal flag also skips the async lane.
Everything else, the routine on-topic pitches and the routine declines, is exactly the kind of decision the rubric was built for. Save the live conversation for the pitch that actually needs two judgments in the room.
Keep the queue where both of you already look
The rubric and the decision log only work as long as both of you open the same place to read them. A shared doc drifts once someone forgets to update it, and a verdict typed into a Slack thread is gone by the time the producer scrolls back to find it.
Pod Green Room keeps the rubric fields, the verdict, and the reason on the guest's record inside the guest pipeline. Pod Green Room's guest tracking is the same view for both of you. The producer sees the decision the moment you write it, no separate message required.
The same discipline carries past the greenlight. Once a guest is booked and recorded, a post-recording editorial debrief keeps the next set of notes on the record instead of in your head, the same way the pitch verdict did before the guest ever got a reply.