Guest appearance agreements for podcasters: why a handshake is not enough

A verbal 'sure, use it' feels like enough when everyone is excited to record. It stops feeling like enough when the episode is clipped for TikTok, quoted in a press release, monetized with ads, or the guest decides two months later that they never wanted their face in the thumbnail.

A guest release is the document that turns that verbal yes into permission someone else can read. It should cover the right to record, distribute, edit, transcribe, promote, and use the guest's name, voice, and likeness. Without it, you are building a catalog on handshakes, and handshakes do not hold up well in disputes.

PodStack is not a law firm. This guide is general information, not legal advice for your show, your state, or your country. If you are making real money, dealing with minors, or handling sensitive topics, spend the money on an attorney who drafts these for a living.

Keep the language plain. The guest should be able to read it in one sitting and understand what they are giving away. At minimum, it should say they consent to being recorded, that you can distribute the recording as a podcast and in related clips, that you can edit for length and clarity, and that you can use their name, image, and biographical details to promote the episode.

It should also address who owns what. The guest keeps anything they brought into the conversation: a story, a method, a piece of intellectual property they already owned. You own the finished episode as a collective work. If the guest is contributing music, a script, or a proprietary process, that needs its own line, not a generic release.

Add a representation that the guest has the right to say what they are saying. If they are speaking for a company, they should confirm they are authorized. If they mention other people, they should take responsibility for whether those people want to be mentioned. This does not replace fact-checking, but it puts the guest on notice that the words are theirs.

A simple release works for a standard interview with an adult who is not being paid. Move up to a fuller agreement when money changes hands, when the guest is a minor, when the topic is legally sensitive, or when the guest is an employee discussing their employer.

Paid appearances can trigger disclosure rules. The FTC's endorsement guidance expects clear disclosure when someone is compensated to appear or promote a product. If the guest is also a sponsor, say so in the audio and the show notes. A release does not satisfy the disclosure requirement; it is a separate box to check.

Sensitive topics include medical advice, legal advice, financial advice, and anything where a wrong statement could hurt a real person. In those cases, a release should be paired with on-air disclaimers and careful editing. The release protects some things; it does not make a false or harmful statement safe.

Consent to record should be obtained before you hit the button, not after the interview ends. Send the release with the booking confirmation and ask for it back before the session. If the guest shows up without it signed, you can record, but you should not publish until it comes back.

Use a recorder that gives you clean, separate tracks. Riverside, SquadCast, and Zencastr record each person locally and upload afterward, which is the safest way to protect audio quality. Descript Rooms fits if your editing already lives in Descript. Whichever you use, run a test clip and confirm the files arrive before the real conversation starts.

Tell the guest where the recording will live and how long you keep it. Some recorders process files in the cloud. That is fine, but it is part of the privacy picture the release should acknowledge, especially if you are recording someone outside your own country.

The finished episode is usually yours to publish, keep online, and remove when you choose. The guest does not get a veto over every edit, but you can offer a courtesy review window if it makes them more comfortable. Put any special promises in writing: a takedown request policy, a deadline for approval, or a restriction on where clips can appear.

Your host stores the file and serves the RSS feed, but it does not own the content. Keep the account in your name and your inbox. Buzzsprout, Transistor, and Spotify for Creators all let you export and redirect if you leave, but only if the account is yours. A release stored in a co-host's account is as risky as a handshake.

Send a one-page PDF with the booking email. Do not hide it in a terms-of-service link nobody reads. If you want a digital trail, use any reputable e-signature service. The signature matters less than the fact that the guest saw the document, had a chance to ask questions, and agreed before recording.

Keep the signed release with the episode files for as long as the episode is online, plus a reasonable backup period. Name the file by guest and date. If you switch hosts, move the release folder too. Losing the release is almost as bad as never having one.

For recurring co-hosts, use a broader agreement that covers the whole series, not a per-episode release. Co-ownership, revenue splits, and exit rights should be spelled out there. A release is not a partnership agreement.

A release does not make defamatory statements true, does not clear music the guest played in the background, and does not replace insurance. If the guest reads a hostile email, names a private person, or makes a medical claim, the release does not shield you from the consequences.

It also does not replace good manners. Tell the guest before you clip them into a promo. Let them know when the episode goes live. Send a transcript if you publish one. The legal document protects your back; the relationship protects your show.