These prompts turn your raw podcast recordings into polished show notes that drive engagement and discoverability. Each prompt produces a finished draft you can publish immediately, no additional editing required.
These prompts pair well with Jasper AI for YouTubers-specific tone control, or Copy.ai for fast iteration.
Interview Episode Show Notes
You are a podcast content manager writing show notes for an interview episode.
Episode title: {episode_title} Guest name: {guest_name} Guest expertise: {guest_background} Episode length: {duration_minutes} minutes Main topics covered: {three_to_four_key_topics} Best quotes from guest: {two_memorable_quotes} Links mentioned: {relevant_links_or_resources} Target audience: {listener_demographic} Tone: {conversational / professional / casual}
Write 400 to 500 word show notes that open with a compelling hook about why this guest matters to the audience. Include a bulleted topic breakdown, highlight the best quotes in pull-quote format, and close with clear next steps for listeners. Add timestamps for major topic shifts.
When to use it: Right after recording an interview when you need show notes published within 24 hours for maximum algorithm impact.
Pro tip: Always lead with the guest’s biggest credibility marker in the opening line—it hooks browsers scanning multiple podcast options.
You are writing show notes for a podcast interview with an industry controversy angle.
Episode title: {episode_title} Guest name: {guest_name} Controversial topic: {specific_controversy} Guest’s stance: {their_position} Episode length: {duration_minutes} Key counterarguments discussed: {opposing_viewpoints_covered} Supporting evidence mentioned: {data_or_examples} Audience warning level: {mild / moderate / heated_discussion} Platform restrictions: {youtube_friendly / uncensored}
Write 350 to 450 word show notes that frame the controversy clearly without taking sides. Open with stakes—why this matters now. Use neutral language that respects both perspectives. Include content warnings if needed. End with discussion prompts for comments.
When to use it: When your guest takes a strong position on a divisive industry topic and you need to attract engagement without alienating subscribers.
Pro tip: Use phrases like “explores the debate around” instead of “argues for”—it keeps you neutral while promising valuable content.
You are creating show notes for a technical expert interview that needs to appeal to beginners.
Episode title: {episode_title} Expert name: {expert_name} Technical topic: {complex_subject} Beginner-friendly analogies used: {two_to_three_analogies} Practical takeaways: {actionable_advice_given} Resources for learning more: {books_courses_tools} Episode length: {duration_minutes} Complexity level covered: {beginner_to_intermediate / intermediate_to_advanced} Most valuable tip: {standout_practical_advice}
Write 300 to 400 word show notes that translate technical jargon into accessible language. Open by acknowledging this topic intimidates people, then promise it will make sense. Break down complex concepts using the analogies from the episode. Close with a confidence-building next step.
When to use it: After interviewing a technical expert when your audience includes beginners who might skip the episode based on the title alone.
Pro tip: Include a “no prerequisites needed” statement early—it prevents intimidated listeners from clicking away immediately.
You are writing show notes for a rapid-fire expert interview with multiple mini-topics.
Episode title: {episode_title} Expert name: {expert_name} Number of topics covered: {topic_count} Time per topic: {average_minutes_each} Topics with timestamps: {topic_list_with_times} Best one-liner advice: {memorable_quick_tips} Expert’s main credential: {authority_builder} Follow-up resource: {where_to_learn_more} Energy level: {high_energy / rapid_pace / intensive}
Write 250 to 350 word show notes structured as a preview guide. Open with the variety promise—“We cover X topics in Y minutes.” List each topic with its timestamp as scannable bullets. Include the best quick tips as teasers. Frame this as a masterclass condensed.
When to use it: When you record a fast-paced expert session covering multiple topics and need show notes that help listeners navigate to their interests.
Pro tip: Lead with the timestamp list—power listeners will bookmark specific sections and return multiple times, boosting your engagement metrics.
You are creating show notes for an interview where the guest shares a personal failure story with business lessons.
Episode title: {episode_title} Guest name: {guest_name} Failure described: {what_went_wrong} Financial impact: {money_lost_or_scale} Lessons learned: {key_insights_gained} What they’d do differently: {specific_changes} Current success: {how_they_recovered} Timeline: {how_long_recovery_took} Audience takeaway: {preventable_mistakes} Emotional tone: {vulnerable / matter_of_fact / inspiring}
Write 400 to 500 word show notes that balance vulnerability with value. Open with the stakes of the failure to create drama. Focus on lessons rather than dwelling on mistakes. Close with hope—how the failure led to their current success. Make it clear this isn’t just entertainment but education.
When to use it: After recording a raw, honest conversation about failure when you need to frame it as valuable learning content, not just drama.
Pro tip: Include the recovery timeline in your opening—it gives listeners hope and makes the failure feel surmountable rather than catastrophic.
Solo Episode Show Notes
You are writing show notes for a solo podcast episode teaching a specific skill.
Episode title: {episode_title} Skill being taught: {specific_skill} Your qualification to teach it: {credibility_statement} Step-by-step process covered: {main_steps_taught} Common mistakes addressed: {pitfalls_warned_against} Tools or resources needed: {requirements} Time to implement: {realistic_timeframe} Difficulty level: {beginner / intermediate / advanced} Success metric: {how_to_measure_progress}
Write 350 to 450 word show notes that position this as a mini-course. Open with the skill’s value and your credibility. Outline the learning path clearly. Include implementation guidance and realistic expectations. Close with a specific first step listeners can take today.
When to use it: After recording a tutorial episode when you need to convince browsers this delivers real skill-building value, not just theory.
Pro tip: Include your failure count when learning this skill—“I made these mistakes so you don’t have to” builds trust and relatability.
You are creating show notes for a solo episode responding to audience questions.
Episode title: {episode_title} Number of questions answered: {question_count} Question themes: {common_topic_threads} Most surprising question: {unexpected_one} Your biggest mindset shift answer: {paradigm_changing_response} Practical tools mentioned: {resources_shared} Personal stories shared: {vulnerability_moments} Episode length: {duration_minutes} Audience interaction level: {high / moderate / mixed}
Write 300 to 400 word show notes formatted as a Q&A preview. Open by thanking the community for questions. Highlight the most surprising or valuable question as a hook. Group similar themes together. Include timestamps for different question batches. Close by encouraging more questions.
When to use it: After recording a Q&A episode when you need to make the content feel organized and valuable rather than random.
Pro tip: Feature the weirdest question first—it creates curiosity and makes listeners wonder what other unusual topics you cover.
You are writing show notes for a solo episode sharing controversial industry opinions.
Episode title: {episode_title} Main controversial stance: {your_unpopular_opinion} Industry standard you’re challenging: {common_practice_criticized} Your supporting evidence: {data_experience_examples} Likely pushback: {expected_disagreements} Stakes for listeners: {why_this_matters} Personal experience basis: {your_credibility} Nuance acknowledgment: {where_others_might_be_right} Call to action: {what_you_want_listeners_to_do}
Write 400 to 500 word show notes that create curiosity without being clickbait. Open with the stakes—why this opinion matters. Preview your evidence without spoiling the argument. Acknowledge you might be wrong but explain why you’re speaking up anyway. End with a respectful invitation to disagree.
When to use it: After recording an opinion episode when you need to attract engagement while maintaining credibility and avoiding flame wars.
Pro tip: Include a sentence acknowledging smart people disagree with you—it disarms defensive listeners and makes them more likely to consider your points.
You are creating show notes for a solo episode breaking down a current industry event.
Episode title: {episode_title} Event being analyzed: {specific_news_or_incident} Timeline of what happened: {chronological_facts} Key players involved: {companies_people_stakeholders} Your unique angle: {perspective_others_missed} Implications for listeners: {how_this_affects_them} Historical context: {similar_past_situations} Predictions made: {what_you_think_happens_next} Credibility basis: {why_your_analysis_matters}
Write 350 to 450 word show notes that position you as a trusted industry analyst. Open with the event’s significance. Explain your unique insight angle quickly. Promise both facts and interpretation. Include timeline context. Close with actionable implications for your audience.
When to use it: Within 48 hours of a major industry event when you need to add valuable commentary to breaking news.
Pro tip: Record and publish within 24 hours—industry event episodes lose relevance fast, but early thoughtful analysis builds authority.
You are writing show notes for a solo episode where you admit you were wrong about something significant.
Episode title: {episode_title} What you were wrong about: {specific_previous_position} When you first stated it: {timeframe_reference} Evidence that changed your mind: {new_information} Impact of being wrong: {consequences_for_you_or_others} New position: {updated_stance} Lessons about changing minds: {meta_insights} Apologies owed: {who_you_need_to_acknowledge} Going forward: {how_this_changes_your_approach}
Write 300 to 400 word show notes that model intellectual humility. Open by owning the mistake directly. Explain what changed your mind without defensiveness. Focus on lessons about evolving opinions. Close with renewed credibility—being wrong and admitting it makes future opinions more trustworthy.
When to use it: When you need to publicly update a significant position you’ve taken and want to model good intellectual behavior for your audience.
Pro tip: Reference the specific episode or content where you were wrong—transparency about past positions builds more trust than vague admissions.
Roundtable Discussion Show Notes
You are creating show notes for a roundtable podcast with multiple expert guests debating a topic.
Episode title: {episode_title} Debate topic: {central_question_or_issue} Participants: {names_and_brief_credentials} Number of guests: {participant_count} Main positions represented: {different_viewpoints} Most heated exchange: {conflict_moment} Surprising agreement: {unexpected_consensus} Unresolved questions: {what_remains_debated} Episode length: {duration_minutes}
Write 400 to 500 word show notes that capture the debate energy. Open with the stakes of the topic and credibility of participants. Map out the main positions clearly. Highlight the most dramatic exchange without spoiling outcomes. Close with questions listeners should consider.
When to use it: After recording a multi-guest debate when you need to convey the intellectual fireworks while helping listeners follow the different positions.
Pro tip: Name the participants’ positions in shorthand early—“the skeptic,” “the optimist,” “the pragmatist”—so listeners can track who’s talking.
You are writing show notes for a roundtable where experts solve a real business problem together.
Episode title: {episode_title} Problem presented: {specific_business_challenge} Problem owner: {whose_real_situation} Expert participants: {names_and_specialties} Different approaches suggested: {variety_of_solutions} Consensus solution: {agreed_upon_approach} Implementation timeline: {realistic_timeframe} Resources needed: {tools_budget_people} Success metrics: {how_to_measure_results} Follow-up planned: {checking_back_commitment}
Write 350 to 450 word show notes that frame this as a real-time case study. Open with the problem’s relatability to your audience. Introduce experts by their relevant specialty. Preview the solution without spoiling the reasoning process. Close with how listeners can apply similar thinking to their situations.
When to use it: After recording a collaborative problem-solving session when you need to show the practical value of multiple expert perspectives.
Pro tip: Mention if you’ll follow up on implementation results—it creates a compelling reason for listeners to subscribe for updates.
You are creating show notes for a roundtable retrospective on industry predictions made a year ago.
Episode title: {episode_title} Original predictions episode: {reference_to_past_content} Participants then vs now: {who_returned} Predictions being reviewed: {specific_forecasts_made} Accuracy scoreboard: {who_got_what_right} Biggest miss: {most_wrong_prediction} Unexpected development: {what_nobody_saw_coming} New predictions: {forecasts_for_next_year} Lessons about forecasting: {meta_insights} Stakes for listeners: {why_predictions_matter}
Write 300 to 400 word show notes that balance accountability with entertainment. Open with the courage of making public predictions. Score the hits and misses fairly. Focus on what wrong predictions teach us. Close with new predictions and a commitment to review them again.
When to use it: Exactly one year after making industry predictions when you want to build credibility through transparent accountability.
Pro tip: Celebrate the participants who got things wrong most dramatically—it encourages future bold predictions and makes better content.
You are writing show notes for an emergency roundtable responding to breaking industry news.
Episode title: {episode_title} Breaking news event: {what_just_happened} Recording timeline: {hours_after_news_broke} Expert participants: {who_you_assembled_quickly} Initial reactions: {first_takes_from_each_guest} Information gaps: {what_we_still_don’t_know} Immediate implications: {short_term_effects} Longer-term questions: {bigger_picture_concerns} Action items for listeners: {what_people_should_do_now} Follow-up commitment: {when_you’ll_revisit_this}
Write 250 to 350 word show notes that capture urgency while acknowledging uncertainty. Open with the news significance and your rapid response. Preview different expert takes. Acknowledge this is preliminary analysis. Close with concrete next steps for listeners and promise of updates.
When to use it: Within hours of major breaking news when you need to provide immediate expert analysis while being transparent about evolving information.
Pro tip: Record these episodes in under 4 hours of news breaking—being first with thoughtful analysis matters more than perfect information.
You are creating show notes for a roundtable where participants share their biggest professional failures.
Episode title: {episode_title} Participants: {names_and_current_success_levels