ChatGPT Prompts for Podcast: Show Notes & Interview Prep

ChatGPT prompts for podcast work when you lock episode topic, guest, runtime, and publish channel before you ask for notes. This guide gives copy-paste kits for show notes and guest interview prep for solo hosts, co-hosts, and producers. You leave with ROLE / TASK / FORMAT scaffolds for GPT-5.5 Instant and GPT-5.6 Sol, plus an EPISODE_FACT sheet that keeps summaries, timestamps, and question banks tied to facts you supply.

You still edit the transcript, confirm quotes, and run the interview yourself. PromptMake /text can scaffold a rough ask at https://promptmake.net/text before you paste into ChatGPT. This page covers show notes and interview prep for audio episodes, not YouTube video scripts with hooks, B-roll cues, or end-screen CTAs.

Who ChatGPT prompts for podcast help

You publish a weekly or monthly show and need clean show notes after each recording, plus a guest brief and question bank before you hit record. The patterns fit interview podcasts, narrative shows with research guests, B2B thought-leadership series, and producer teams that hand notes to a host who never saw the raw outline. You already know the episode angle. You need the model to draft titles, summaries, chapter timestamps, SEO-friendly notes, and interview questions that stay inside what the guest agreed to cover.

Skip this page if you want spoken video scripts for YouTube, Shorts, Reels, or TikTok with hooks, B-roll cues, and platform CTAs. That work lives in the ChatGPT prompts for video scripts guide. Skip it if you want job-seeker mock interviews for hiring loops. That library is separate. Skip it if you want the model to invent guest bios, episode stats, or quotes from a recording you never pasted.

Treat ChatGPT as a notes and prep desk. You supply EPISODE_FACT, a transcript or research packet, and the artifact type. The model proposes show notes, chapter lists, titles, and interview question banks tied to those facts. You reject any draft that adds guest claims, company metrics, or episode numbers you did not supply.

Lock EPISODE_FACT before you prompt

Name the episode constraints in the first block of every podcast thread. Listeners punish vague titles and show notes that promise topics the audio never covered. A polished summary from "write show notes for my podcast" fails the moment you publish with wrong guest titles or timestamps that skip half the talk. Put the constraints in ROLE and repeat the hard ones in a REMINDER line so a long transcript paste does not bury them.

Allowed artifacts: episode title options, short and long show notes, chapter timestamp lists, pull-quote candidates from a pasted transcript, guest research briefs, interview question banks, cold-open / cold-close lines for the host, and newsletter teaser blurbs that match the notes. Banned artifacts: invented guest bios, fake download counts, medical or financial claims you did not paste, and spoken video scripts with B-roll or mute captions for YouTube.

Keep an EPISODE_FACT sheet outside the chat: show name, episode number or working title, runtime target, audience, guest name and approved bio bullets, topics in scope, topics out of scope, tone, brand words to use, words to ban, and publish channels (RSS, Spotify, Apple, YouTube audio). Update it when the guest or angle shifts. Feed it into every prompt. The model should never be your only source of guest truth.

Redact unpublished launch dates, private guest emails, and off-the-record remarks before paste. Consumer ChatGPT is a drafting desk, not a secure production vault. Use your approved workspace tools when legal or compliance requires a locked chat. Never paste raw audio; paste a transcript you own or a research brief the guest approved.

Core ChatGPT prompts for show notes and interview prep

Strong ChatGPT prompts for podcast give four inputs before any tone request: episode facts, source material, the artifact type, and the claim boundary. Episode facts are show name, guest, runtime, audience, and channel. Source material is a transcript excerpt, research brief, or outline you own. The artifact names show notes pack, chapter timestamps, title bank, guest brief, or interview question set. The claim boundary forbids stats, quotes, and guest claims you did not paste.

Paste those four blocks near the top. Put format rules next. Put banned outputs at the end so they survive a long paste. GPT-5.5 Instant, GPT-5.6 Sol, Claude Sonnet 5, and Gemini 3.5 Flash all follow labeled blocks well. Vague "make podcast notes" prompts produce generic blurbs because the model has no guest, no runtime, and no transcript.

Run one artifact type per thread. Mixing a full show-notes pack and a forty-question interview bank in the same chat blurs length rules and claim fences. Close the chat after you finish one pass. Open a new thread for interview prep so post-record notes language does not leak into pre-record questions.

Role, task, format skeleton

Copy this skeleton and fill the brackets with your material:

ROLE: You are a podcast production assistant for [interview show | solo show | narrative series]. You work from EPISODE_FACT and SOURCE only. You write show notes and interview prep a host or producer can publish or use on air. You never invent guest bios, quotes, stats, or episode claims.

TASK: Turn EPISODE_FACT and SOURCE into a [show notes pack | chapter timestamps | title bank | guest research brief | interview question bank] for [episode topic]. Keep every claim tied to SOURCE. Mark gaps with [NEED SOURCE]. If I ask for YouTube video scripts with B-roll or mute captions, refuse and offer a podcast show-notes or interview-prep artifact instead.

FORMAT: Use the section headers listed under OUTPUT_SHAPE. Timestamps in [mm:ss] when SOURCE includes time marks. Cap each show-notes section at [N] words unless I raise the limit.

EPISODE_FACT: [show name, episode working title, runtime, audience, guest, topics in/out of scope, tone, banned words, publish channels]

SOURCE: [transcript excerpt, research brief, guest-approved bio, outline]

OUTPUT_SHAPE: [list required sections]

RULES: No fake download stats. No medical or financial advice beyond SOURCE. No invented guest quotes. If a claim needs a detail I did not supply, write [NEED SOURCE].

REMINDER: Podcast show notes and interview prep only. Never invent proof. Never write video B-roll scripts.

That reminder line stops the model from padding with "as the guest explained" lines you never recorded. Models love tidy narrative. Your rule forces a gap marker you can fill from the transcript or guest form.

Paste-ready kits for show notes

Show notes pack pattern adds: "From EPISODE_FACT and SOURCE, write show notes. Sections: Episode title (3 options, max 12 words each) | One-sentence hook | Summary (120–180 words) | Key takeaways (5 bullets) | Guest bio (only from SOURCE) | Resources mentioned (only if named in SOURCE) | CTA for listeners (subscribe / review / next episode). Mark any missing fact [NEED SOURCE]. No invented quotes. Output with those headers only." You paste into your host notes field and trim to house length.

Chapter timestamps pattern: "TASK: From TRANSCRIPT with time marks, list chapters. For each: [mm:ss] | Chapter title (max 6 words) | One-line topic. Cap chapters at [8–12] for a [runtime] episode. Merge short asides. Flag any stretch longer than 8 minutes without a chapter break. Do not invent topics absent from TRANSCRIPT." Producers drop this into Spotify or Apple chapter fields.

Pull-quote and SEO blurb pattern: "TASK: From TRANSCRIPT and EPISODE_FACT, propose 5 pull quotes under 25 words each with [mm:ss] if available. Then write a 90-word SEO description that names the guest and topic from SOURCE only. Ban clickbait the episode cannot deliver. Flag any quote that needs verification as [NEED CHECK]." Hosts use quotes for social clips; you still listen and confirm wording.

Title bank pattern: "TASK: From EPISODE_FACT and SOURCE, write 10 episode title options. Types: Guest + topic | Outcome for listener | Question title | Series-consistent style matching [past titles]. Max 60 characters. No fake numbers. Output as a numbered list only." Pick one title after you lock the cut.

Paste-ready kits for interview prep

Guest research brief pattern:

TASK: From EPISODE_FACT and GUEST_PACKET (approved bio, links, past episodes you named), write a one-page host brief. Sections: Guest snapshot (SOURCE only) | Why this episode for our audience | Three story angles tied to SOURCE | Topics to avoid (from EPISODE_FACT out-of-scope list) | Open questions marked [NEED SOURCE]. Do not invent career history or company metrics.

Interview question bank pattern: "TASK: From EPISODE_FACT and GUEST_PACKET, write 18 questions. Groups: Warm-up (3) | Core topic (8) | Specific stories (4) | Listener value / how-to (2) | Soft close (1). Label each question with intent. Cap each question at 25 words. Ban questions that demand medical, legal, or financial advice beyond SCOPE. Mark any question that needs a fact not in GUEST_PACKET as [NEED SOURCE]." Hosts cut to 10–12 for a standard interview runtime.

Follow-up and callback pattern: "TASK: From QUESTION_BANK and EPISODE_FACT, add 1 follow-up probe under each of the 8 core questions. Probes stay under 15 words. No new claims. Flag probes that assume a guest answer you did not hear yet." Use this after you lock the main bank so you stay ready when the guest goes short.

Pre-interview email pattern: "TASK: From EPISODE_FACT and QUESTION_BANK, draft a guest prep email. Sections: Thanks | Episode angle in one sentence | Topics we will cover | Topics we will skip | Logistics (length, format) | Ask guest to correct any bio error. Tone from EPISODE_FACT. No invented schedule facts. Mark missing logistics [NEED SOURCE]." Send only after you fill logistics yourself.

Step-by-step podcast prompt workflow

Use one chat thread per episode phase. Dumping show notes for three old episodes and a new guest question bank into one long thread blurs guests and claim rules. The loop below keeps a stable EPISODE_FACT sheet while you swap only this episode's SOURCE block. You spend free ChatGPT or PromptMake runs on structure, then human time on transcript cleanup, a listen-through, and a guest fact check.

Keep EPISODE_FACT in plain text outside the chat: show name, guest, runtime, audience, in-scope topics, out-of-scope topics, tone, and banned words. Update it after each booking. Feed it into every prompt that touches the episode. The model should never store your only copy of guest bio lines or sponsor reads.

Step 1: Fill EPISODE_FACT and gather SOURCE

Write the sheet in plain bullets. Example: "Show: Ops Desk Weekly. Episode working title: Hiring first ops hire. Runtime: 42 min. Audience: founders building ops from zero. Guest: [name], approved title and company from form. In scope: hiring scorecard, first 90 days. Out of scope: salary bands, named client stories. Tone: practical, calm. Ban: 'guaranteed,' fake download numbers. Channels: RSS + YouTube audio." Ugly notes beat polished fiction.

For interview prep, gather GUEST_PACKET: approved bio, public links the guest named, and past episode titles if you rebook someone. For show notes, gather TRANSCRIPT or a cleaned outline with time marks. Never ask the model to invent either.

Step 2: Prep the interview, then record

Run the guest research brief first. Confirm every bio line with the guest form. Run the interview question bank next. Cut questions that wander out of scope. Send the pre-interview email with logistics you filled by hand.

Optional cold-open draft: "TASK: From EPISODE_FACT, write 3 host cold-open options under 40 words that name the guest and the listener outcome. No fake praise. No invented guest achievements." Pick one opener you can say without a script in hand.

Step 3: Draft show notes, chapters, then publish check

After the cut, paste TRANSCRIPT excerpts or a chapter outline into a fresh thread. Run the show notes pack, then chapter timestamps, then title bank. Close the output. Listen to the episode once with notes open. Fix any summary line the audio does not support.

Optional audit: "TASK: Audit SHOW_NOTES against EPISODE_FACT and TRANSCRIPT. For each claim, reply Keep, Soften, or Remove. Soften means the line overreaches SOURCE. List any timestamp that points to the wrong topic. Never add quotes I did not paste."

Optional scaffold: open https://promptmake.net/text, describe "ChatGPT prompts for podcast show notes and interview prep with EPISODE_FACT for an interview episode," generate once, then paste your EPISODE_FACT into the returned structure. Guests get about three runs per day; free accounts get about five. Use a run to shape the prompt, then finish in your chat model.

Save the winning prompt next to the episode folder so the next booking reuses the same wrapper. Publish only notes you verified against the audio.

Mistakes that wreck podcast ChatGPT use

Mistake 1: Asking for "great show notes" with no guest, runtime, or transcript. The model invents topics the episode never covered. Lock EPISODE_FACT and paste SOURCE first.

Mistake 2: Using video-script kits for podcast episodes. Hooks, B-roll cues, and mute captions solve YouTube filming. Podcast notes need summaries, chapters, and guest-safe question banks. Keep the libraries separate.

Mistake 3: Letting the model invent guest bios or quotes. Ban new claims in RULES. Use [NEED SOURCE] for gaps. Confirm pull quotes by ear.

Mistake 4: Mixing pre-record interview prep and post-record show notes in one mega-thread. Split phases. Reuse EPISODE_FACT; change TASK and FORMAT.

Mistake 5: Asking for forty questions with no runtime or out-of-scope list. You get a laundry list the guest cannot answer in forty minutes. Cap groups and mark bans in EPISODE_FACT.

Mistake 6: Publishing chapter timestamps from a rough outline without a listen-through. Wrong timestamps train listeners to skip. Require [mm:ss] from a real transcript or your editor's marks.

Mistake 7: Trusting Instant or Flash as the final judge on regulated guest claims. Fast models fit first drafts. Route health, finance, or legal-adjacent episodes through a careful edit pass and your own compliance check.

Mistake 8: Never reading show notes against the audio. Fluency on screen is not the same as fidelity to the cut. Require a publish check before you hit distribute.

Model notes for podcast prompts (mid-2026)

ChatGPT often defaults to GPT-5.5 Instant for fast chat. Instant fits title banks, first show-notes drafts, and interview question lists when you already locked EPISODE_FACT and SOURCE. Keep prompts short: ROLE, TASK, FORMAT, EPISODE_FACT, SOURCE, RULES. Skip long chain-of-thought slogans.

GPT-5.6 Sol fits harder edit passes: claim audits against TRANSCRIPT, chapter lists that must match time marks, and notes that must not invent guest quotes. Give goal, constraints, and format. Drop "think step by step" padding on reasoning-class models.

Claude Sonnet 5 handles long transcript pastes plus messy producer outlines you want turned into clean show notes. Claude Opus 5 fits careful audits when a wrong guest claim would force a takedown or a correction episode. Gemini 3.5 Flash fits volume work: many title variants, batch question banks across a season calendar, and short blurbs for newsletter and RSS from one notes pack. Gemini 3.1 Pro fits hard reasoning over a thick research packet when you need conflict flags against EPISODE_FACT.

Hedge on exact menu names in each vendor UI. They shift. Re-check the model picker when you open a new thread. Prompting split that holds: Instant and Flash get RTF plus a short sample of your house notes format when you need matching headers. GPT-5.6 Sol, Opus 5, and Gemini 3.1 Pro get goal plus constraints plus format, with an explicit refuse-to-invent rule and a [NEED SOURCE] token. All need your EPISODE_FACT in the message. None replace a listen-through or a guest bio check.

Build podcast prompts with PromptMake /text

Write the rough ask in plain words: interview vs solo, show notes vs question bank, runtime, and guest if known. Open https://promptmake.net/text and generate a structured prompt once. Expect labeled sections you can fill with EPISODE_FACT and SOURCE.

Edit guest bios, timestamps, and episode claims yourself. PromptMake cannot know your transcript. Paste the filled prompt into Instant or Flash for first drafts, or GPT-5.6 Sol / Opus 5 / Gemini 3.1 Pro for claim audits. Keep free-tier runs for scaffolding, not five synonym retries of the same weak "make it engaging" ask.

Workflow that sticks: EPISODE_FACT, gather GUEST_PACKET or TRANSCRIPT, PromptMake scaffold, fill facts, fast model draft, human listen-through, reasoning model audit, you publish. Store one template per artifact type so you do not rewrite ROLE and RULES from scratch each episode.

FAQ

What are the best ChatGPT prompts for podcast in 2026?

The best ChatGPT prompts for podcast lead with ROLE and claim fences, paste EPISODE_FACT and SOURCE, then demand FORMAT for a show notes pack, chapter timestamps, title bank, guest brief, or interview question set. Add a second audit prompt that marks Keep, Soften, or Remove against your transcript or guest packet. Match GPT-5.5 Instant or Gemini 3.5 Flash for first drafts and GPT-5.6 Sol, Claude Opus 5, or Gemini 3.1 Pro for claim audits before you publish.

How do I write podcast show notes with ChatGPT?

Paste EPISODE_FACT plus a transcript excerpt or cleaned outline. Ask for title options, a short summary, key takeaways, guest bio from SOURCE only, resources mentioned, and a listener CTA. Require [NEED SOURCE] for gaps. Listen once with the notes open and fix any line the audio does not support before you paste into your host.

How should ChatGPT prep interview questions for a podcast guest?

Feed an approved guest packet and an out-of-scope list. Demand grouped questions with warm-up, core topic, story, listener value, and soft close. Cap question length and ban topics the guest declined. Add follow-up probes in a second pass. Cut the bank to fit your runtime before you send the prep email.

Are ChatGPT prompts for podcast the same as video script prompts?

Podcast prompts build show notes, chapters, and guest interview prep for audio episodes. Video script prompts build spoken lines, B-roll cues, and platform CTAs for YouTube and Shorts. Use this guide when you publish RSS or podcast apps. Use the video scripts guide when you film talking-head or vertical video. Keep both libraries in separate folders so you grab the right scaffold under deadline.

Can ChatGPT create chapter timestamps from a transcript?

Yes, when you paste a transcript with time marks and set a chapter cap for your runtime. Ask for [mm:ss], a short chapter title, and a one-line topic. Merge short asides and flag long stretches without a break. Always spot-check timestamps against the final cut before you upload to Spotify or Apple Podcasts.

Should I use GPT-5.5 Instant or GPT-5.6 Sol for podcast prompts?

Use Instant for title banks, first show-notes drafts, and interview question lists when EPISODE_FACT and SOURCE are already in the message. Use GPT-5.6 Sol when you need a careful claim audit, chapter lists tied to time marks, or notes that must not invent guest quotes. Run the same facts through both only when you measure quality for a recurring season workflow.

Can PromptMake help with ChatGPT prompts for podcast for free?

Yes. PromptMake /text turns a rough podcast idea into a labeled prompt you can aim at ChatGPT, Claude, or Gemini. Guests get about three generations per day; registered free users get about five. Fill in your own EPISODE_FACT and SOURCE, then paste into Instant for drafts or GPT-5.6 Sol for audits before you publish show notes.