A guest says yes. When does that become consent?
A guest replies sure to your invite, you book Thursday, and before you hit record you tell them the conversation gets published on the show. They say okay. Play that exchange back and it is real, usable consent for most independent podcasts. No signature required.
The gap most hosts trip on is not whether consent exists. It is what that consent actually covers, and how far past the original episode you are allowed to take it. A yes to being recorded is not automatically a yes to everything you might later do with the recording.
What a recorded yes actually covers
A verbal yes covers exactly what you said out loud before the tape started: that you are recording, and where the episode gets published. It does not stretch to a clip licensed onto someone else's show, an ad cut from their voice, or a repost after they have asked you to take it down.
State more up front and the yes covers more. Tell a guest at the top of the call that clips may run on social, that the audio may live in a transcript, that highlights could appear in a newsletter. Named uses said out loud and captured on tape are covered. Uses you never mentioned are not.
Where a signed release form earns its place
A written release adds one thing a spoken yes cannot: a record that exists independent of the recording itself, readable by someone who never heard the call. A handful of situations call for it specifically, and the list is shorter than most hosts assume.
- The guest is a minor. A parent or guardian signs, not the guest, and a verbal yes from a child carries no weight on its own.
- The guest is speaking for an employer. A written release with named scope protects you if the company later disputes what was said or how it can be used.
- You plan to reuse the material past the one episode: a paid ad built from their voice, a syndicated cut on a different feed, audio licensed into someone else's project.
- The topic is sensitive enough that memory of a verbal agreement will not hold up months later: health, an active legal matter, a workplace dispute.
- You want to publish video, photos, or a headshot alongside the audio, which a recorded audio yes does not automatically cover.
- The guest asks for an embargo, a hold on publishing until a specific date, and you want that date in writing rather than in a text thread you will have to dig up later.
What the release form should actually say
A podcast release does not need to read like a network contract. It needs to name the guest, name what they agreed to, and be signed before the episode goes out. Keep it to what you will actually use.
- The guest's legal name and the date they agreed.
- What was recorded: audio, video, or both, and on what date.
- Where it can run: your podcast feed, your own social channels, your own newsletter. Name each platform rather than writing a blanket every platform.
- Whether clips or excerpts are allowed outside the full episode, and for how long the permission holds.
- Any embargo date, stated plainly, with what happens if no date is set.
- How the guest can ask for a correction or, before publish, ask for something cut.
- A signature line and a date line. A typed name in a reply email works for most independent shows; do not confuse that with an authenticated legal signature for higher-stakes uses.
None of this replaces judgment in the room. A release covers reuse and scope. It does not decide whether a specific moment should air at all, which is a call you make live, not on a form.
Embargo: the date most release forms leave blank
An embargo on a podcast means the guest agreed to be recorded, but asked the episode or a specific clip to stay unpublished until a set date: a book launch, a funding announcement, a product release still under wraps.
The problem is not the request. It is that an embargo agreed to on a call, with no date written anywhere, turns into a guessing game the week you are ready to publish. Put the date in the release itself, and put a default next to it: no date given, and the episode publishes on your normal schedule.
Recording before the signed release comes back
Sending a release does not mean waiting on it before you record. Most hosts record on the strength of the verbal yes, send the written release the same day, and treat the reply as confirmation rather than permission to proceed. Publishing before the release is signed is the step to hold, not the recording.
A release that never comes back is its own answer. If a guest goes quiet on the paperwork after an enthusiastic recording, that silence is worth a direct follow-up before you publish, not a reason to assume the verbal yes was enough all along.
What a release form is not for
A release covers permission and reuse. It is the wrong tool for two problems that look similar and are not. A guest asking you to cut a specific moment is a live editorial call, decided in the room or in the edit, not a clause. A guest who is also a client, sponsor, or competitor needs disclosure, not a signature.
Keep the three separate in your head: consent and scope on the release, sensitive content on the edit, commercial ties on the disclosure line. A pre-interview alignment call is where most of this gets settled before the mic is ever on, which is the cheapest place to settle it.
Putting the consent decision on the guest's file
The decision itself is small: verbal yes, or signed release, and if a release, what it covers and any embargo date. What is easy to lose is where that decision lives once the recording is three months old and someone asks whether you are cleared to run a clip.
Pod Green Room keeps the consent type and any embargo date on the guest record itself, next to the rest of the guest tracking. The answer to are we cleared for this is a field you check, not a memory you trust, and Pod Green Room carries it forward into the guest pipeline the next time that guest comes up for a return episode.
The release you meant to send and never did
Most hosts do not lose a release fight over a bad clause. They lose it over a form that lived in a drafts folder, or an embargo date that existed only in a text message nobody can find six weeks later. The document matters less than whether it is where you can find it when you need it.