A regular show is a production line. The host records, an editor cuts and mixes, someone writes the show notes, someone else cuts clips for social, and the producer publishes. Each handover is a chance for a step to fall between two people, and with a fixed release day the missing step is usually discovered an hour before the episode goes live. A checklist per episode, started as soon as the topic is agreed, gives every step a name and a date.
Loudness should be the same every week. Apple’s audio requirements ask for a loudness of about −16 LKFS, within 1 dB either way, with true peaks no higher than −1 dBFS. Spotify’s loudness normalisation targets −14 LUFS and turns softer masters up, so most podcasters still master to −16 and let Spotify raise it slightly. Pick one target, measure every master against it, and listeners stop reaching for the volume when your show follows another in their queue.
The RSS feed is the product. Apple Podcasts, Spotify and most other apps read your show from its RSS feed. Apple requires each episode to carry a title, a publication date, an enclosure with the file’s URL, length and type, and a globally unique identifier, the GUID, which never changes. If an episode is re-uploaded or the show moves host, the GUID has to come with it. The server hosting the audio must also support HTTP HEAD and byte-range requests, which matters if you self-host.
Transcripts and chapters are now expected. Apple Podcasts generates a transcript automatically after each episode is published, shown on iOS 17.4 or later. If your host supports the podcast:transcript tag, you can supply your own VTT or SRT file and set the show to display transcripts you provide, which is the only way to be sure guest names and product terms are spelt correctly. Apple reads chapters from timestamps in the episode description, from a podcast:chapters file or from markers embedded in the audio file; the first chapter starts at 00:00:00 and there should be at least three. Since iOS 26.2 Apple also creates chapters automatically for English episodes over ten minutes long, but your own will reflect the structure you planned.
One person owns the episode. In most teams that is the producer: they start the checklist, assign the editor and the person writing show notes, and chase the guest. The host records and approves, but should not also be the one remembering whether the transcript was corrected. Agencies producing a show for a client usually put their own producer in that seat and add the client as the approver, so the client sees one clear request rather than a thread of files.
Someone has to say yes. Once an episode is in the feed, apps can download it to subscribers’ devices, and removing it later does not undo those downloads. That is why the template ends production with a sign-off from the host or producer, and for agencies the client, before anything is uploaded. If the answer is no, the checklist stops there.