A podcast episode is not finished because its host uploaded an audio file. It must tell a coherent story, respect guest and source rights, reach listeners through a valid feed and provide trustworthy metadata, accessible information and appropriate corrections.
This guide follows a fictional education podcast whose Friday episode is invisible to some apps because it reuses an earlier identifier. Along the way, it explains editorial preparation, remote interviewing, audio quality, RSS, transcripts and the latest measurement standards.
The broader Audio Production guide focuses on the sound master. Journalism addresses evidentiary reporting, while Streaming Services considers platform playback. This article owns the recurring podcast show and open-feed relationship with listeners.
Find the part you need
Read from show strategy to listener feedback or jump directly to the relevant technical or editorial decision.
Chapter index
Promise, planning and guests · Chapters 1–5
Recording, editing and rights · Chapters 6–9
Feeds, identity and access · Chapters 10–13
Publication, measurement and trust · Chapters 14–16
1. Publishing an audio file is not the same as releasing an episode
A fictional education podcast, Pathways in Practice, records an excellent interview with a school laboratory technician about helping students learn from experiments. The editor finishes the audio on Wednesday, the team schedules Friday’s release, and the host posts that the episode is live. Some listeners still see only the previous episode because the RSS feed reuses an old identifier. Others receive the recording without the promised transcript or source references.
The gold standard of podcast production is the ability to publish a coherent, properly authorised episode that eligible listeners can actually find, hear, navigate and trust. Podcasts combine editorial work with audio production, independent hosting and distribution through many apps. A good microphone does not repair incorrect feed metadata, and a successful host upload does not prove the catalogue updated. Pathways in Practice and everyone in this example are fictional.
Back to chapters · Next chapter
2. Define the show promise before choosing a format
A podcast may offer news, interviews, fiction, commentary, education or entertainment. The producer should explain who it is intended for and what a listener can expect: an expert conversation, a series of investigations, carefully scripted storytelling or a relaxed discussion. The editorial promise matters more than using a fashionable episode length.
Pathways in Practice promises parents and students understandable stories about learning and school life. That gives its producer a reason to verify technical claims and avoid presenting one guest’s anecdote as a universal school rule. Define how often new episodes are realistically possible, what evidence a story will require and which decisions remain with the editorial lead. A sustainable niche show can offer more genuine value than an ambitious schedule that collapses after three releases.
Back to chapters · Next chapter
3. Build a calendar that allows meaningful preparation
An episode calendar should connect topics, guests, research, recording, editing, reviews, show notes and release dates. Publishing regularly is useful when listeners depend on the cadence, but treating every date as immovable may encourage rushed fact checking or inappropriate publication. Define what can be postponed and who decides when an episode is not ready.
For the fictional school interview, the guest becomes unavailable to verify a complicated safety-related statement. The producer should be able to reschedule rather than publish an unsupported claim for the sake of the calendar. Plan several episodes ahead where possible and maintain a realistic reserve for corrections. A useful schedule records what is genuinely approved, not only what has been placed in a social-content calendar.
Back to chapters · Next chapter
4. Research claims before giving them a public microphone
A podcast interview may sound authentic even when its factual assertions are incorrect. Producers should research the subject, review significant figures and prepare focused questions that reveal useful explanations. For matters involving public policy, science, safety or law, an appropriate expert or primary source may need to verify what is asserted.
The laboratory technician might describe one school’s demonstration routine. The host should not convert that into ‘all schools must do this’ without checking the responsible authority’s current guidance. Separate personal experience from broadly applicable rules in narration and show notes. The Society of Professional Journalists ethics code offers useful principles for factual podcast journalism, but different genres need their own clearly identified approaches.
Back to chapters · Next chapter
5. Explain guest participation and editorial independence
Guests need an intelligible understanding of the show’s purpose, recording arrangement, intended distribution and any applicable release conditions. An employer’s permission or a guest’s willingness to speak does not automatically clear third-party recordings, confidential material or every aspect of later promotional reuse. Producers should define the agreement before recording.
An interviewee may ask to review their quotations for accuracy, while the producer needs to protect editorial judgement. Decide how genuine factual corrections, confidentiality concerns and editing disagreements will be handled. If a guest raises a legitimate concern about a student’s identity in an anecdote, investigate it rather than claim the microphone alone created unlimited consent. Ethical clarity prevents avoidable conflict when the episode is ready to launch.
Back to chapters · Next chapter
6. Make remote recording resilient to ordinary interruptions
Podcast guests may connect from kitchens, offices or classrooms with differing microphones and network connections. A remote call can sound acceptable in real time while its recording contains dropouts or overlapping speakers. Before committing to a lengthy interview, test appropriate audio capture, consent and backup arrangements.
Mark major interruptions and the moment after which a recording was resumed, so edits do not create a false sequence. Give guests practical preparation instructions that do not require expensive equipment, and support participants who lack a quiet space. A technically imperfect but intelligible answer can be valuable; however, an invented reconstruction of words that were never recorded would be unacceptable as a factual quotation.
Back to chapters · Next chapter
7. Edit an episode without changing what the speaker meant
Podcast editing shapes pacing, clarity and listener comprehension. Removing unnecessary noise, repetition and off-topic material can help, but cutting between sentences may create misleading implications. A producer should distinguish ordinary pacing edits from substantive changes to the meaning of an interview or a disputed claim.
For Pathways in Practice, a guest says a particular laboratory exercise worked only with older students under supervision. Removing the qualifying clause would turn a limited teaching example into an inaccurate recommendation. Editorial review should compare important passages with source context. A final listen is essential: waveform alignment and seamless crossfades do not establish that the story still represents the conversation fairly.
Back to chapters · Next chapter
8. Balance the sound for a real listener and a real platform
Listeners may hear a show while walking, commuting or using inexpensive earphones. Dialogue should remain intelligible, guest levels should be reasonably consistent and music should not obscure essential speech. A compelling intro can become a problem when its level is dramatically higher than the conversation.
The ITU-R BS.1770-5 algorithm helps measure loudness and true peak, while EBU R 128 Supplement 2 discusses loudness in streaming. Neither imposes one universal LUFS target on every podcast feed. Apple Podcasts audio requirements identify acceptable MP3 and AAC RSS formats and recommended technical ranges. Follow the actual hosting and distribution specifications, and listen to the encoded output.
Back to chapters · Next chapter
9. Clear music, excerpts and commercial relationships
An intro tune, licensed sound effect, excerpt from another show or archival interview may involve separate rights and conditions. ‘Available online’ does not mean ‘free for commercial podcast use’. A producer needs appropriate agreements, credits and records covering where the episode and promotional clips can appear.
If a sponsor pays for an episode or offers a benefit in exchange for a mention, the relationship should be disclosed in a manner audiences can understand and under applicable law. Keep sponsor review separate from editorial judgement where the show’s promise requires independence. A funding arrangement should not quietly permit the sponsor to rewrite a guest’s evidence or conceal relevant criticism.
Back to chapters · Next chapter
10. Make the RSS feed a dependable public interface
For open podcasts, the RSS feed is an essential delivery and identity mechanism. It tells compatible listening apps about the show, artwork, episodes and media files. A producer can upload valid audio yet fail to publish correctly because the feed contains a missing required element or a media link the app cannot retrieve.
Apple Podcasts RSS feed requirements specify a publicly available RSS 2.0 feed with required metadata, artwork, at least one episode and valid enclosure information. Servers must support the relevant file access behaviour. The precise rules apply to Apple Podcasts ingestion; another distributor may differ. The key is to treat the RSS output as a product requiring validation rather than an invisible setting left entirely to a hosting dashboard.
Back to chapters · Next chapter
11. Keep episode identity stable across every update
A podcast episode needs a persistent identity even when its audio, description or hosting location changes. Duplicate identifiers can cause an app to ignore a new episode; changing an established identifier can make the same episode reappear as a duplicate, disturbing playback progress and audience records.
Apple’s hosting migration guidance stresses that episode GUIDs must remain stable and explains how redirects can preserve subscribers when feeds move. For Pathways in Practice, the Friday episode needs its own distinct GUID, not last week’s copied identifier. A producer should test the feed after publication and preserve the mapping through future hosting changes. Growth should not depend on replacing listener history with broken duplicates.
Back to chapters · Next chapter
12. Write descriptions, chapters and source notes for navigation
A meaningful episode title and description help listeners decide whether a conversation is relevant to them. Show notes should identify sources, clarify important terms, disclose applicable sponsorship and distinguish corrections from promotional language. A long conversation may also benefit from chapters that let someone return to an explanation.
Apple Podcasts’ current chapter guidance explains creator-supplied timestamps and titles through descriptions, RSS or supported file metadata. The service may also generate English-language chapters automatically where creator data is absent. A producer should check that generated labels correctly describe the discussion, especially where a model might confuse similar school terms. Navigation should be a truthful aid, not a list of sensational fragments that distort the conversation.
Back to chapters · Next chapter
13. Provide an accurate transcript that can be trusted
An audio-only show should not assume every interested listener can hear every episode. A verified transcript helps Deaf and hard-of-hearing listeners, people working in noisy environments and those who need to search or revisit details. Automated speech recognition can accelerate the work, but names, technical vocabulary and speaker attribution often need correction.
W3C guidance on transcripts explains what relevant speech and non-speech information should be represented. The Apple Podcasts episode process can generate or accept transcripts through its supported routes. The fictional school interview’s transcript should be checked against the final audio rather than an earlier draft. If the audio is corrected, decide whether the transcript and chapter timing also require an update.
Back to chapters · Next chapter
14. Test discovery and playback after publishing, not just upload
A host may report ‘published’ while some directories have not yet refreshed or a file link fails on a specific app. Different services can take time to ingest changed feeds. A trustworthy launch checklist includes feed validation, a public catalogue check, playback of the delivered audio, artwork and descriptions, and correct access to any associated transcript.
Apple’s availability troubleshooting guidance explains that duplicate GUIDs, enclosure issues, regional restrictions and feed errors can prevent episodes appearing. If a newly released recording is not visible, identify the actual cause instead of repeatedly creating a new episode. Let listeners know the known status and avoid claiming that all apps are updated until appropriate checks support it.
Back to chapters · Next chapter
15. Measure downloads without pretending every download was heard
Podcast advertising metrics require careful interpretation because episodes can be downloaded for later playback, cached or requested by automated systems. A server-side download is not identical to a listener finishing the conversation or understanding an advertised message. Publishers should explain what their measurement actually counts.
The IAB Tech Lab Podcast Measurement Guidelines v2.3, released September 2026, describe current technical methods for podcast downloads, audience and advertising measures based on delivery records. They do not imply that all dashboard totals on different platforms can simply be added together as unique engaged listeners. A show should distinguish server metrics from platform-specific listening analytics and be transparent about methodology when selling sponsorship.
Back to chapters · Next chapter
16. Keep corrections, listener trust and the next episode connected
An episode may later need a corrected fact, an updated link, a rightsholder remedy or a clarification about a guest’s remarks. A producer should have an accountable way to update show notes, release a suitable correction and notify listeners where the substance of a claim was material. Quietly swapping an audio file without documenting an important editorial change can create conflicting versions.
Return to Pathways in Practice. The team fixes the duplicate feed identifier, verifies the episode audio, adds accurate sources and transcript, and explains any change that could affect the meaning. Production notes preserve the guest agreement and a working source master. The gold standard of podcast production is a consistent relationship with listeners: clear stories, dependable distribution, transparent metrics and the willingness to correct what needs correcting.
Worked example: an episode is uploaded but listeners cannot find it
The podcast and its school interview are fictional. Each stage below is a different form of evidence, not a substitute for the others.
| Reported success | What may still be wrong | Verified next step |
|---|---|---|
| Recording completed | Unverified factual claim or guest concern | Editorial and rights approval |
| Audio exported | Dialogue or codec problem | Listen to the actual encoded master |
| Host says published | Duplicate episode GUID or invalid enclosure | Validate current RSS feed and unique identity |
| Show notes uploaded | Transcript and source links do not match audio | Check accessible notes against final version |
| Dashboard shows downloads | No evidence that all downloads were completed listens | Report download method and separate engagement metrics |
The podcast production checklist
- The show promise, audience and publishing cadence are sustainable.
- Guests understand recording, editorial scope and applicable permissions.
- Important claims are checked and edited without distorting meaning.
- Delivered audio meets actual platform and listener needs.
- Music, excerpts and sponsorship relationships are appropriate and disclosed.
- RSS feed, artwork, metadata, enclosures and persistent GUIDs are valid.
- Transcripts, chapters and source notes match the approved final episode.
- Metrics and corrections are presented without overstating listening or reach.
Current primary references and connected eduKate articles
- Apple Podcasts — RSS Feed Requirements
- Apple Podcasts — Audio Technical Requirements
- Apple Podcasts — Hosting Migration and GUID Stability
- Apple Podcasts — Chapters and Episode Navigation
- W3C — Podcast and Audio Transcripts
- IAB Tech Lab — Podcast Measurement Guidelines v2.3 (September 2026)
- eduKate — Audio Production
- eduKate — Journalism
- Gold Standard Sectors and Services Directory
RSS distributor features, monetisation, advertising law, accessibility and privacy duties vary by platform and jurisdiction. IAB’s v2.3 guidelines concern technical podcast audience measurement and are not evidence that a particular episode was actually heard to completion. This article is general podcast-production guidance.