60 items

Podcast Episode Production

A field-tested per-episode production workflow for podcasters—from first outline to final analytics. Use it to ship consistently, catch problems before listeners do, and build a process your whole team can follow. For more background and examples, see the guidance below; for built-in tools and options, use the quick tools guide.

Author

Checklistify Editorial Team

Last Updated

Checklist Items

0 done•60 left•6 of 7 sections collapsed

Confirm the episode topic, angle, and single core audience takeaway

Write one sentence that completes this prompt: 'After this episode, my listener will be able to ___.' If you cannot finish that sentence clearly, the topic is still too vague. A clear takeaway anchors every downstream decision—what questions to ask, which tangents to cut, and how to write the title. Keep this sentence in your outline header so you can check against it during editing when deciding what stays and what goes.

Confirm and document the episode format: solo, interview, co-host, roundtable, or narrative

Each format carries different prep and editing demands. Solo and narrative episodes require the most scripting time—often 2–4 hours of preparation per 30 minutes of finished audio—but give you full editorial control and predictable pacing. Interview formats depend on strong question design and a guest brief; roundtables need a facilitation plan to prevent crosstalk and ensure all voices are heard. Document the confirmed format alongside the episode number so a producer, editor, or VA can pick up the project without asking.

Confirm and lock the episode number and working title

Use a consistent numbering scheme from episode one and never change it—podcast apps and RSS feeds use episode numbers for sorting and download attribution. The working title can evolve before publish, but the number must be locked immediately. If you produce episodes in batches, use zero-padded numbers (EP042, EP043) to prevent alphabetical sorting errors in your project folder, DAW, and hosting platform dashboard.

Schedule the recording date and add it to your calendar with two reminders

Block your recording session at least one week before the intended publish date to preserve buffer for editing, review, and unexpected delays. Set a 24-hour-before reminder to run gear checks and a 1-hour-before reminder to clear your recording space and silence notifications. If you release on a weekly cadence, work backward from your publish day and protect recording slots with the same firmness you would protect a client meeting—treat them as non-negotiable production appointments.

If guest episode: send the invitation at least 7 days out with date, time, topic brief, and recording platform link

Include the precise recording start time in the guest's timezone (link to a timezone converter if uncertain), a one-paragraph topic brief so they can prepare specific examples rather than relying on generic answers, the exact platform you will use (Riverside.fm, Zencastr, Zoom), the expected total session length including warm-up, and one sentence describing your audience. Send a calendar invite alongside the email—an email alone is frequently forgotten. Guests who receive a clear brief arrive with better stories and require significantly less on-mic coaching.

If guest episode: collect bio, headshot, website URL, and preferred social handles before record day

Request a short bio of 2–4 sentences the guest uses in introductions, a high-resolution headshot (minimum 800×800px, JPEG or PNG), their website URL, and their active social handles for tagging in post-publish promotions. A simple intake form via Google Forms or Typeform sent in the invitation email is the most reliable collection method. Missing assets on publish day are the single most common reason post-publication social promotion is delayed by 24–48 hours.

Research the topic or guest thoroughly before writing your outline

For guest episodes: search for their previous podcast appearances to find questions that have already been asked exhaustively, then build your questions around the gaps. Skim their most recent writing, product launch, or public talk for current context your audience has not heard elsewhere. For topic episodes: read the current top five search results and identify what they all miss or oversimplify—that omission is your angle. Budget 45–90 minutes of focused research for a 30-minute episode. Shallow research produces interchangeable episodes; thorough research produces ones people share.

Write the episode outline or script with a timing estimate for each segment

Interview shows need at minimum: an opening hook of 30–60 seconds, five to eight prepared questions in a logical arc from context-setting through insight to application, two to three follow-up prompts per question, and a structured closing segment. Solo and narrative formats benefit from a detailed script or tight bullet outline to prevent rambling, which compounds in editing time. Estimate your recording duration before you start: the average speaker covers 130–150 words per minute, so a 30-minute episode needs roughly 4,000–4,500 words of outlined or scripted material. Mark which segments are must-include versus flexible so in-the-moment decisions are clear.

Compile all resources, tools, books, and links you plan to mention on air

Create a dedicated resources section in your episode document with the full URL, a short description, and whether you have an affiliate or referral relationship with that product. If you plan to mention a promo code, confirm it is active before recording day so you state the correct code on air. Broken or incorrect show-notes links are among the most-cited listener complaints in podcast reviews and erode the trust that keeps subscribers returning. Verify every URL is live before the episode publishes.

Confirm sponsor reads, ad copy, placements, and required disclaimer language for this episode

Obtain the sponsor's approved ad copy before record day. Read the copy aloud once in advance to check for awkward phrasing—it is far easier to request a copy edit than to re-record mid-session. Note the agreed placement (pre-roll, mid-roll at a specific timestamp, or post-roll) and the agreed read length, typically 30 or 60 seconds. If no sponsor exists for this episode, mark this item not applicable rather than leaving it unchecked; an unchecked item looks like an unresolved task.

#10

Confirm your recording environment is quiet and acoustically treated

Hard surfaces—bare walls, tile floors, glass windows—cause flutter echo and comb filtering that is very difficult to remove in post-production. Quick low-cost treatment options: record in a walk-in closet filled with clothing, drape a thick blanket behind your mic and over nearby reflective surfaces, or use a portable reflection filter on your mic stand. Record 15 seconds of silence in the room and listen through headphones—you should hear almost nothing. If a single sharp hand clap produces a noticeable 'ring' that sustains, the room needs more absorption. Even modest acoustic improvement at the source saves 20–30 minutes of noise cleanup in editing.

#11

Check microphone connection, input selection in your DAW, and set input gain correctly

Target peak input levels between -12 dBFS and -6 dBFS while speaking at your normal conversational volume—never allow the meter to reach 0 dBFS, which causes clipping that cannot be recovered in post. If using an audio interface, adjust the gain knob so your loudest natural speech peaks around -6 dBFS, not your average volume. The wrong input device—built-in laptop mic instead of your external microphone—is the most common session-start error; always confirm the selected input in your DAW's audio preferences, not just in your operating system's sound settings, which can override your DAW silently after a restart.

#12

Verify headphone monitoring is active and set to a comfortable, non-fatiguing volume

Monitoring through headphones while recording lets you catch problems in real time: a buzzing cable, a guest who forgot to unmute, or a notification sound cutting into the session—rather than discovering the issue two hours later in editing. Use closed-back headphones if recording in the same physical space as a co-host to prevent bleed. Set monitoring volume low enough to stay focused on the conversation; monitoring too loud can cause you to unconsciously pull back from the microphone, which reduces your recorded level and adds a distant quality to your voice.

#13

Open your DAW or recording software and confirm the correct input device, sample rate, and bit depth

The industry standard for podcast audio is 44.1 kHz sample rate at 24-bit depth; 24-bit preserves more headroom during editing even if the final export is 16-bit. If you record at 48 kHz—common when using a video-oriented interface—confirm your DAW matches; mismatched sample rates cause chipmunk-speed or slow-motion playback that is easy to miss on first listen. Save a DAW template session with all settings locked in by default so you never configure these from scratch before a recording session.

#14

Record a 30-second test clip and critically listen before starting the full session

This single step prevents the majority of ruined recordings. Listen for: wrong input device selected (distant, thin sound), gain set too low (barely visible waveform), gain set too high (distorted peaks), background hum from HVAC or computer fans, and mic placed farther than 8 inches from mouth (which causes thin, reverberant audio). Listen to the test clip through headphones, not room speakers. If anything sounds wrong, diagnose and fix before pressing record on any real content. A 3-minute setup check prevents a 3-hour re-recording session.

#15

Test your remote recording platform with a 60-second sample call and confirm local recording quality

Platforms such as Riverside.fm and Zencastr record each participant's audio locally on their own device before syncing the files after the call—this eliminates the audio degradation inherent in streaming connections. Confirm that local recording is explicitly enabled in your platform settings, not just the fallback stream recording. After a brief test call, download and listen to the local audio file before the real session begins. Warn guests not to refresh their browser tab during recording; on some platforms, a page refresh terminates the local recording process silently while the stream continues, giving you only the compressed backup.

#16

Send your guest a clear tech-check reminder with five specific instructions 24 hours before recording

Include these instructions in plain, non-technical language: (1) Use wired earbuds or closed-back headphones—not wireless AirPods in ambient mode, which add latency and compression artifacts. (2) Position the microphone 4–6 inches from your mouth, slightly off-axis to reduce plosive sounds on words starting with 'p' and 'b.' (3) Record in the quietest room available—a parked car in a garage works surprisingly well. (4) Close all unused applications before the call, especially video streaming, cloud sync clients, and multiple browser tabs. (5) Use a wired ethernet connection if possible. Guests who receive specific, actionable instructions deliver consistently better audio than those who receive a generic reminder.

#17

Create and name the episode project folder and DAW session files before pressing record

Use a consistent naming format: ShowName_EP042_GuestLastName_YYYYMMDD. Create subfolders labeled Raw, Edited, Final, and Assets before you start recording. A clear structure means any team member can open the project and locate files without asking. Save the DAW session file inside the project folder immediately after creating it—never rely on autosave default paths, which scatter files unpredictably across your drive and can be impossible to locate after a system update or DAW reinstall.

#18

Record 10–15 seconds of room tone or ambient silence at the start of each session

Room tone is the natural ambient sound of your environment—HVAC hum, distant traffic, slight air movement—captured with no one speaking or moving. You use it in editing to fill the gaps between cuts so that transitions between removed sections do not create jarring contrast between active ambient sound and complete digital silence. Ask every participant to be fully still and silent, then record. Label this clip clearly in your timeline (for example, 'ROOM TONE EP042'). If you forget at the start, capture room tone at the very end of the session before anyone disconnects.

#19

Run a spoken level check with every participant before beginning episode content

Ask each person to speak for 20–30 seconds at their normal recording volume—not a test 'check check,' which people deliver at an artificially measured level that does not represent their conversational voice. Ask them to describe their morning or tell a brief story. Watch your meters while they speak and target -12 to -6 dBFS peak for each track. On remote recording platforms, confirm that each participant's waveform is visibly active in the session dashboard—a completely flat waveform means their audio is not being captured at all.

#20

Record the full episode and maintain a consistent microphone distance of 4–8 inches throughout

Proximity effect on cardioid microphones increases bass frequency significantly as distance decreases, so leaning forward during animated or excited sections creates tonal inconsistency that is difficult to correct in post. If you need to cough or sneeze, mute your channel or turn sharply away from the mic. Periodically glance at your recording meter to confirm it is still active—DAW freezes and accidental channel mutes are the primary cause of partial recording losses that go unnoticed until the editing session.

#21

Use a verbal marker or a single sharp hand clap when restarting a section

Say 'take two' clearly before restarting, or give a single sharp hand clap that creates a distinct visible spike in the waveform—easy to locate in the timeline during editing. This is considerably faster than scrubbing blindly through audio searching for where a restart occurred. Write a short note in your session log with the approximate timestamp (for example, 'retake at ~14:20—stumbled on the intro to question three') to further accelerate the editing pass.

#22

Continue recording through small stumbles and corrections; do not stop the session for minor errors

Stopping and restarting recording for every small mistake creates dozens of short audio files rather than a continuous session, which dramatically increases import time, sync complexity, and total editing duration. A natural stumble followed by a self-correction takes fewer than 10 seconds to remove in post. The exception: if you completely lose your train of thought for more than 30 seconds or head in entirely the wrong direction, pause briefly, say 'resuming from [topic]' clearly, and continue—this gives your editor a clean anchor point in the timeline.

#23

Record all sponsor reads as a separate, dedicated take after the main episode content is captured

Recording sponsor reads after the main content is safely captured removes performance pressure and typically produces a more relaxed, natural delivery. Record two versions when possible: one straight read matching the approved script and one with a personal ad-lib endorsement. Store both in a clearly labeled clip (for example, EP042_Sponsor_Acme_Takes) so the options are easy to compare in editing and so you can swap in a revised read if the sponsor sends updated copy after your first edit is done.

#24

Record a fresh standalone outro or call-to-action segment specific to this episode

Produce a new outro for each episode rather than reusing a dated recording—references to 'last week's episode' or specific guest details become confusing when episodes are replayed months later. Record the outro after the main session when your voice is warmed up. Keep it under 60 seconds; listener completion rate data consistently shows drop-off accelerating when outros exceed 90 seconds. Include one primary call to action (subscribe, review, join the community) and at most one secondary link—more than two actions dilutes follow-through on all of them.

#25

Back up all raw audio files to a second location immediately after the session ends

Apply the 3-2-1 rule: three copies, stored on two different types of media, with one stored off-site or in the cloud. Copy raw files to an external hard drive and a cloud service such as Backblaze, Google Drive, or Dropbox before editing, renaming, or closing the session. A 60-minute session at typical raw file sizes uploads in 5–10 minutes on a reliable connection. Raw audio is almost always unrecoverable if lost; a re-recording requires rescheduling the guest, risks a worse outcome, and doubles your production time for that episode.

#26

Take rough timestamp notes during recording of strong moments, tangents to cut, and sections to redo

Use a notepad, open text document, or voice memo to jot approximate timestamps and brief notes: '12:30 – great launch story, consider for audiogram,' '18:00 – off-topic tangent, cut in edit,' '24:15 – retake, second version is better.' These notes become the first draft of your editing map and reduce editing time by 30–40% for complex or long-form episodes. The marginal time spent making notes during recording is recovered several times over during the edit.

#27

Import all raw audio tracks into your editing software and organize them in the timeline

Create a separate track for each speaker and label each by name. Apply consistent color coding—for example, host always in green, guest always in blue—so you can navigate the timeline quickly without reading every label. If you recorded on Riverside or Zencastr, download both the local recording files and the backup stream recording, then use the local files as your primary tracks; they will be noticeably higher quality than the compressed stream. Save the session immediately after import before making any edits.

#28

Align and sync all multi-track recordings to a common reference point

Use the hand-clap spike you captured or identify a loud common sound—the first sharp word of a question, a shared laugh—and align all tracks to it by zooming in to the waveform level. Adobe Audition includes an automatic multi-track sync feature; most other DAWs require manual alignment by dragging clips. After aligning, group all tracks so they move together during subsequent edits. Misaligned tracks produce a subtle doubling or echo effect that listeners perceive as an audio quality problem even when they cannot specifically name what they are hearing.

#29

Apply noise reduction or background noise removal as the first processing step on all tracks

In Audacity or Adobe Audition, sample a 0.5–1 second section of room tone—a gap between words with no speech—then apply noise reduction conservatively, starting at 6–10 dB of reduction rather than the maximum setting. Over-processing creates a metallic, garbled quality sometimes called the 'underwater effect,' which is more distracting to listeners than the original light noise. iZotope RX (Elements version costs approximately $99) is the industry standard for difficult noise problems such as intermittent traffic, fan hum, or electrical interference. For mild consistent hiss, Audacity's built-in noise reduction is usually sufficient.

#30

Edit out extended pauses, false starts, off-topic tangents, and distracting filler word clusters

Target a natural speech pace: silences longer than 1.5 seconds in mid-sentence are usually cuttable, but pauses before a key point or after an emotional statement carry narrative weight and should be preserved. Remove false starts and repeated sentence openings. Reduce filler words like 'um' and 'uh' but do not eliminate every single one—complete removal makes speech sound robotic and unnatural. Descript's filler-word removal tool can accelerate this pass at scale, but always do a listening pass afterward to restore any pauses that carry meaning.

#31

Balance the volume of all speakers to a consistent average loudness across the full episode

Target an average dialogue level of -16 to -18 LUFS (Loudness Units Full Scale) for each speaker track before applying mix-bus processing. Use a loudness meter plugin—Youlean Loudness Meter has a free version—rather than relying on visual waveform height alone, which does not accurately represent perceived loudness. A guest who is consistently 6 dB louder than the host causes listener fatigue and generates comments about audio quality issues, even from listeners who have no technical audio vocabulary.

#32

Add intro music or jingle at the episode start and set its duration to 5–15 seconds

Standard intro music length is 5–15 seconds before the host begins speaking; anything longer risks a skip-forward on mobile, where the 30-second skip button is prominently displayed. If you prefer a longer music bed, duck it under the speaking voice to -20 to -25 dB so it becomes background ambience rather than a competing signal. Use consistent intro music across every episode—repeated exposure trains listener pattern recognition and signals to returning subscribers that content is beginning. License music through services such as Artlist, Musicbed, or Epidemic Sound to avoid platform content-ID claims.

#33

Insert pre-approved sponsor reads at the planned pre-roll, mid-roll, or post-roll timestamps

Place the sponsor read clip at the timestamp noted in your production outline, then add a brief musical sting of about 0.5 seconds or a short pause before and after to signal the transition. Pre-roll ads have the highest completion rate but can feel abrupt immediately after the intro; mid-roll ads placed at a natural topic transition perform best for listener retention and sponsor satisfaction. Confirm the final read length in your timeline matches the agreed duration—many sponsors audit episode files for compliance and a significantly shorter or longer read can affect the relationship.

#34

Add outro music and position your final call to action so it is fully audible before the music fades in

Fade outro music in under the last 10–15 seconds of your spoken CTA rather than after it ends—music fading in underneath speech signals to the listener that the episode is closing while keeping the CTA audible. A common error is setting outro music too loud relative to the voice, which competes with the CTA and measurably reduces follow-through on subscription and review requests. End with 0.5–1 second of complete silence after the music fades rather than a hard cut; it lands less abruptly across all playback environments and headphone types.

#35

Apply EQ, compression, and limiting to the final mix and verify loudness against platform targets

A standard voice processing chain: high-pass filter at 80–100 Hz to remove low-end rumble, a 2–3 dB boost at 2–4 kHz for presence and intelligibility, compression at 3:1 to 4:1 ratio with a moderate attack of around 10 ms to control peaks without stripping natural dynamics, and a true-peak limiter with a ceiling of -1 dBTP. Target -16 LUFS integrated for stereo delivery and -19 LUFS for mono—these are the loudness normalization reference points for Spotify and Apple Podcasts. Your DAW's standard VU meter does not measure LUFS; a dedicated loudness meter plugin is required for this step.

#36

Export the final episode as an MP3 with the correct bitrate and fully populated ID3 metadata

Standard delivery for speech-only episodes is MP3 at 128 kbps mono, which runs approximately 60 MB per hour of audio. Use 192 kbps stereo only if your episode includes significant music content; the larger file meaningfully slows download time on mobile data connections. Before exporting, populate your DAW's metadata fields: show name, episode number, episode title, artist, and album art as a minimum 1400×1400px JPEG. Most major podcast hosting platforms reject uploads without embedded artwork, causing silent publish failures that are easy to miss. Export to your Final subfolder using the standardized episode naming convention.

#37

Listen to the complete exported MP3 file from start to finish before uploading to your host

Listen on at least two different playback systems: quality headphones or speakers, and a phone speaker or basic earbuds. Edit-point clicks, sudden volume jumps, incorrect fades, and missing sections are often inaudible on studio monitors but immediately obvious on earbuds and phone speakers. This pass also catches sponsor reads that exported at the wrong level, episode intros that failed to render, and metadata that did not embed. Skipping this step is the single most common cause of re-uploads after publish, which creates duplicate episode entries on some directories and resets listener play counts.

#38

Write a specific, benefit-driven episode title that reflects the core takeaway and performs in search

A strong title formula: [Specific Outcome] + [Method or Context]. For example, 'How to Negotiate a Higher Salary Without Losing the Offer' outperforms 'Salary Negotiation Tips' at every stage of discovery. Avoid vague qualifiers—'amazing,' 'powerful,' 'mind-blowing'—which give a prospective listener no information about what they will gain. Keep titles under 60 characters so they display without truncation in podcast app browse and search views. Include the guest's full name if they have an established audience—their name can surface the episode to their followers through platform search.

#39

Write a complete episode description and show notes with timestamps and all resources

The first 3–5 sentences of your description appear in podcast app preview cards and must deliver standalone value—write them so a reader who has never heard your show understands exactly what this episode delivers. Include a 2–3 sentence topic summary, three to five timestamped chapter highlights, a guest bio paragraph if applicable, and every resource, book, product, and tool mentioned in the episode. Aim for 500–1,000 words in your show notes; longer notes improve podcast SEO and serve as a reference document for returning listeners. Never copy the transcript verbatim into the description field—it reads as spam to both listeners and search engines.

#40

Create or commission a full transcript or accurate chapter-level summary

Full transcripts serve two distinct groups: listeners with hearing impairments who cannot access your content otherwise, and search engines that cannot index audio content. AI transcription tools such as Descript (integrated with a DAW-based workflow), Otter.ai (approximately $10 per month), and Rev (human transcription at approximately $1.50 per minute) generate draft transcripts in minutes. Always review AI-generated transcripts for proper nouns, technical terms, book and product names, and sponsor brand names—these are where automated transcription makes the most frequent errors. A rough transcript requiring 20 minutes of correction is faster than writing one from scratch and meaningfully expands episode discoverability.

#41

Compile, verify, and format all resource links mentioned in the episode with UTM tracking

For every resource, book, tool, or guest URL: confirm the link is current and loads correctly, verify whether you have an affiliate or referral relationship and apply the appropriate link format, and add UTM parameters if you want to track traffic from show notes back to your analytics (example: ?utm_source=podcast&utm_medium=shownotes&utm_campaign=EP042). Broken links are among the most frequent listener complaints about show notes. A link management tool such as Pretty Links or Bitly creates readable, trackable short URLs you can update without modifying published show notes if a destination URL changes.

#42

Create episode artwork and promotional audiogram clips sized correctly for each distribution channel

Square episode artwork at 3000×3000px JPEG is required for Apple Podcasts and Spotify browse display. For audiogram clips, produce a 60-second version in 9:16 ratio (1080×1920px) for Instagram Reels and TikTok, a 30-second version in 1:1 ratio (1080×1080px) for Instagram feed and Twitter/X, and a 90-second version in 16:9 for YouTube Shorts or LinkedIn video. Tools including Headliner, Descript, and Canva simplify audiogram creation. Select a clip that functions as a standalone teaser—it should raise an interesting question or deliver a single compelling insight without requiring full episode context.

#43

Write the email newsletter copy for this episode with a subject line that references a specific tension or takeaway

Subject lines that name a specific tension or outcome outperform generic episode announcement lines by 15–30% in open rate across most audience sizes. Compare: 'Why I stopped batching my podcast and what actually changed' versus 'New episode out now.' The email body should be a personal note of 100–200 words sharing one specific insight from the episode—not a copy of your show notes or a transcript excerpt. Include the episode title, a prominent listen link, and a secondary link to the show notes. An email that reads like a message from a real person consistently outperforms one that reads like a press release.

#44

Draft social media posts for publication day and schedule a day-3 follow-up post at the same time

Write platform-native posts rather than identical copy pasted across channels. For LinkedIn: a 150–300 word narrative post with a text hook and the episode link added in the first comment, since LinkedIn's algorithm deprioritizes posts containing external links in the body. For Instagram: the first line of the caption as a bold question or statement, with the resource link in your bio. For Twitter/X: a short thread leading with one key takeaway followed by three to five supporting points, with the episode link in a reply below the thread. Draft and schedule the day-3 follow-up at the same time you prepare launch-day content—scheduling it later is how follow-up posts get consistently skipped.

#45

Upload the final exported audio file to your podcast hosting platform

Confirm the file size is within your host's per-episode limit before uploading—most platforms cap files at 500 MB to 1 GB, and a 128 kbps mono MP3 runs approximately 60 MB per hour. Verify the upload completed fully before leaving the screen; partial uploads occasionally pass without an error message and produce episodes that cut off mid-way through for listeners. After upload, use your host's built-in episode preview player to confirm the file streams correctly before entering any metadata.

#46

Enter all episode metadata: finalized title, full description, season number, and episode number

Use your finalized SEO title—not the working title—and your complete show notes text in the description field. Several hosting platforms surface episode descriptions in their own internal search, so treat this text as discoverable content. Set the explicit content flag correctly: mislabeling clean content as explicit restricts it from family-filtered search on Apple Podcasts; mislabeling explicit content as clean can trigger platform compliance reviews. Verify the season and episode numbers match your established scheme before saving.

#47

Add chapter markers and timestamps if your hosting platform supports them

Chapter markers—supported by Apple Podcasts, Podbean, Buzzsprout, and others—let listeners jump directly to segments and give the episode a professional, structured feel in apps that display them. The most efficient workflow: embed chapter markers during your editing session in your DAW and export them with the MP3 file. Alternatively, add them manually in your host's episode editor. Write chapter titles that describe what happens in each specific segment rather than generic labels like 'Part 1' or 'Section 2.' Chapters also encourage listener screenshots and clip-sharing, which extends organic reach beyond your existing subscribers.

#48

Upload episode-specific artwork if this episode uses different imagery from your standard show art

Episode-specific artwork is most valuable for guest episodes featuring a recognizable headshot, seasonal specials, or named series within your show. The minimum accepted size is 1400×1400px; the recommended upload size is 3000×3000px. Export as JPEG or PNG in an RGB color profile—CMYK images render incorrectly or fail validation on most podcast platforms. Verify your export settings in Canva or Adobe Express before uploading; both default to RGB but it is worth confirming. Standard show artwork is perfectly appropriate for regular episodes.

#49

Add relevant episode tags and confirm the content rating is accurate

Use 2–3 topic or genre tags that most accurately reflect this episode's content rather than tagging broadly; overly broad tags reduce the precision of recommendations on platforms that use tag data for surfacing content. The Clean or Explicit content rating applies not only to profanity but also to mature themes, graphic descriptions, substance references, and adult subject matter. Once set, the content rating embeds in your RSS feed and travels automatically to every distribution platform—verify it before publishing rather than requesting post-publish corrections.

#50

Schedule the publish date and time within your consistent weekly or biweekly release window

Consistency in release cadence matters more than the specific day or time you choose. Listeners who subscribe develop a listening habit around your cadence; inconsistent releases break that habit before it fully forms. Most hosts report Tuesday through Thursday between 5 and 8 AM in the primary audience's timezone as high-consumption windows, but your own analytics will show you when your specific audience downloads. Schedule releases at least one hour before your intended go-live to allow sufficient platform propagation time.

#51

Copy and store the final episode URL immediately after publishing and send it to collaborators

Copy both the direct episode URL from your hosting platform and the episode landing page URL from your show website if one exists. Store both in your episode production document and central content tracker. Send the URL to your featured guest within one hour of the episode going live—guests who receive the link, a ready-to-use social caption, and promotional assets on publish day share significantly more often within the first 24 hours, when social momentum is highest. The first-day sharing window is difficult to recapture once it closes.

#52

Verify the episode displays correctly on Apple Podcasts and Spotify within 2–3 hours of publish

Apple Podcasts typically propagates new episodes within 1–2 hours of an RSS feed update; Spotify usually within 30 minutes. Confirm that the title, description, artwork, and audio all load correctly—not just that the episode entry appears. If the episode does not appear after 3 hours, validate your RSS feed at a tool such as Castfeedvalidator.com or Podbase.fm to identify formatting errors. Most propagation failures trace to invalid characters—smart quotes, em dashes, or certain emoji—in the episode title or description field rather than any problem with the audio file.

#53

Send your newsletter to subscribers within 2 hours of the episode going live

Send within 2 hours of publish so the email arrives before the social noise of the same day competes for attention. Schedule the send in advance if your primary audience is in a different timezone. Track open rate, click-through on the episode link, and direct play-link clicks separately where your email platform allows link-level analytics—this data shows which email formats and subject line styles drive actual listens versus passive opens. A consistently timed newsletter trains subscribers to expect and look for your email, creating a reliable non-algorithmic distribution channel independent of any platform's algorithm.

#54

Publish all prepared social media posts across active channels

Post the platform-native content you drafted during show notes preparation. Use a scheduler such as Buffer, Later, or Hootsuite to publish across platforms from a single dashboard and aggregate engagement data in one place. Stagger posts by 5–10 minutes across platforms rather than publishing at the identical second—this gives you time to monitor early engagement and respond to initial comments before the post ages out of the active feed. Algorithmic signals in the first 20–30 minutes of a post's life disproportionately affect its total reach on most major platforms.

#55

Send your guest a full promotional package with the episode link and ready-to-use social assets

Package everything in a single shared folder: the episode listen link, show episode artwork, the guest-specific audiogram clip, and two to three pre-written social captions adapted to the guest's typical voice and audience. Guests who receive a frictionless package—where the only required action is pressing post—share more frequently and more quickly than guests who receive only a listen link and must create their own assets. Contact them directly via email or a personal message, not a reply in the recording platform thread, which guests rarely monitor after the session ends.

#56

Submit the episode to relevant online communities, subreddits, or curated newsletters where topic fit is strong

Identify communities where your specific episode topic provides genuine value: topically relevant subreddits, LinkedIn groups, Slack communities, or newsletter curators who cover your subject area. Lead your submission with the specific value the episode delivers rather than a generic 'I made a podcast' announcement. If you are new to a community, spend a few minutes engaging with existing threads before posting; communities reward consistent contribution and penalize one-time promotional drops. Aim for two to three high-relevance community submissions rather than broad low-fit distribution.

#57

Publish a follow-up insight or behind-the-scenes post 3–5 days after the episode releases

A day-3 to day-5 follow-up extends the promotional window and reaches audience segments who missed the launch-day post in their social feed. Effective formats: one surprising statistic or quote from the episode that generated strong listener responses, a personal reaction to the guest's most counterintuitive answer, or a brief 'what I cut from this episode and why' note. This type of post generates replies and discussion that often surface listener questions you can address in a future episode. The post requires no new research if you drafted it during original content preparation.

#58

Review episode analytics at the 7-day and 30-day marks and record findings in your episode document

At 7 days, track: total downloads, primary listener geography, and completion rate—specifically what percentage of listeners reach the 50%, 75%, and episode-end marks. A completion rate above 70% indicates strong content delivery; below 50% usually points to a pacing problem, audio quality issue, or a weak opening hook that fails to establish why this episode is worth 30 minutes of a listener's time. At 30 days, compare against your rolling average to identify statistical outliers. Recording this data in your episode document builds a cross-episode dataset you can analyze after every 10–20 episodes to find patterns.

#59

Archive the completed checklist with episode notes and decisions in your central production records

Store the completed checklist—with notes on any problems encountered, decisions made mid-production, and time spent at each stage—alongside the final audio file, show notes, and assets in the episode project folder. Over 20–30 episodes, this archive becomes your most accurate record of what actually works versus what you intended to do. When you bring in a VA, editor, or co-producer, this archive transfers process knowledge faster than any onboarding briefing or written guide.

#60

📖 The episode that shipped twice

Three weeks into her relaunched business podcast, Priya skipped the final listen. She had been editing for two and a half hours and was confident the file was clean. It was not. An edit-point click artifact—two tracks that had been joined incorrectly during sync—sat right in the middle of her guest's most quotable answer: a jarring 3-second pop that interrupted the sentence. The episode published. By the time a listener emailed, it had 340 plays. She re-exported and re-uploaded a corrected file. The problem: her hosting platform treated the re-upload as a new episode entry for 24 hours on several apps, generating duplicate notifications for subscribers and resetting her launch-day momentum. The second version outperformed the first in completion rate by 18 percentage points—but the first-day social traffic was gone.

What went wrong

Final listen skipped after a long edit session
Sync artifact missed during mix review
Re-upload created duplicate directory entries for 24 hours
Guest had already shared the flawed version to 4,000 followers

⏱ What it cost in time

1 hour re-editing, re-exporting, and re-uploading
2 hours managing listener emails and social comments
340 people heard a degraded version that cannot be un-heard
Launch-week social momentum reset—not recoverable

🧮 What an episode actually costs in time, by format

Per 30 minutes of published audio. These are median estimates from independent podcasters producing 50 or more episodes per year. Your actual numbers will vary by workflow maturity.

Format	Pre-prod	Recording	Editing	Assets + Publish	Total
Solo / Monologue	2–3 hrs	45–60 min	1–2 hrs	1–1.5 hrs	~5–7 hrs
Interview (2 people)	1–2 hrs	40–60 min	1.5–2.5 hrs	1–1.5 hrs	~4.5–7 hrs
Co-hosted / Panel	1–1.5 hrs	35–50 min	2–3.5 hrs	1–1.5 hrs	~5–7.5 hrs
⚠️ Narrative / Scripted	4–8 hrs	1–3 hrs	4–10 hrs	1.5–2 hrs	~11–23 hrs

Editing is the most variable phase. Interview episodes with heavy crosstalk, significant restructuring, or complex multi-topic conversations can push editing time well above these estimates. Narrative formats are outliers—many acclaimed narrative shows invest 20–40 hours per 20-minute episode, which is a different discipline entirely from conversational podcasting.

🔧 Choosing your editing environment

The right tool depends on your technical comfort level, team size, and how much of your editing involves complex sound design versus straightforward spoken word cleanup. Here are the four most widely used options:

Descript

Best for solo and small-team workflows where speed matters more than precision audio control. The transcript-based editor lets you cut audio by deleting words from a text document—no waveform manipulation required. Excellent for filler word removal at scale and for teams where the editor is not an audio engineer.

~$24/mo (Creator plan) · Free tier available · Mac + Windows

Adobe Audition

Best for podcasters already in the Adobe Creative Cloud ecosystem or those who need advanced multitrack mixing, spectral repair, and precise noise reduction control. Steeper learning curve than Descript, but significantly more power for complex audio problems and multi-speaker panel shows.

~$21/mo standalone or included in CC · Mac + Windows

Audacity

Best for beginners and budget-conscious producers working on straightforward speech content. Free, open-source, and capable of handling basic multitrack work, noise reduction, and standard export formats. Not suitable for complex projects, but for a simple weekly interview show it is entirely sufficient.

Free · No subscription · Mac + Windows + Linux

Logic Pro (Mac only)

Best for Mac users who want professional DAW capabilities—including music production for original intros and outros—without an ongoing subscription. Full multitrack workflow, excellent built-in noise reduction, and a loudness metering suite. The one-time purchase model makes it cost-effective over several years of production.

$199.99 one-time · Mac only · No transcript-based editing

📅 The batch recording day blueprint

Recording one episode at a time means setting up gear, warming up your voice, and clearing your recording space 52 separate times a year for a weekly show. Batching three to four episodes in a single day cuts that setup overhead by 75% and reduces per-episode context switching significantly. For many independent podcasters, batch production is the single most impactful operational change they make.

A practical structure: record two solo or scripted episodes back-to-back in the morning when voice and energy tend to peak, then schedule two guest interviews in the afternoon spaced 90 minutes apart to allow for setup, debrief, and a genuine break between conversations. Front-load all technical checks before the first session—configure your gear once, then record four times.

The trade-off: batching works best for evergreen content. News-adjacent or highly topical episodes may feel dated if they sit in a queue for two to three weeks. Many experienced podcasters batch evergreen solo episodes to maintain a standing two-to-three episode buffer, then record topical or guest episodes closer to their air dates. This approach gives you production insurance without sacrificing timeliness on time-sensitive subjects.

🤝 The guest relationship beyond the recording session

Most podcasters treat the guest relationship as beginning at the invitation and ending at the publish notification. The shows that generate consistent referral-based guest pipelines manage the relationship across three distinct moments:

24 hours before

Send the finalized question list—not to over-prepare the guest, but to let them identify the specific stories and examples they want to reference. Guests who have thought about a question for 24 hours arrive with concrete details rather than vague generalizations. This one step tends to produce 30–40% more quotable, shareable moments per episode.

Within 1 hour of publish

Send the asset package with a single sentence of personal appreciation that references something specific the guest said—not a template thank-you. 'That point you made about pricing at the 18-minute mark already has three listener responses' lands differently than 'Thanks for coming on.' Personalized outreach drives a dramatically higher asset-sharing rate than any form message.

30 days after publish

Send the guest their episode's 30-day download figure and a screenshot of a specific positive listener comment or review that mentioned them by name. Most guests never see the downstream impact of a podcast appearance. Showing them the numbers often prompts a second social share and opens the door to future collaborations, referrals to their network, and a genuine long-term relationship rather than a transactional one.

⚠️ What a 2-week release gap actually costs

Podcast apps rank shows partly on release frequency, so a gap of two weeks or more reduces browse visibility on several platforms. More significantly, casual subscribers—listeners who tune in opportunistically during commutes or workouts—build a listening habit around your release cadence. A broken cadence disrupts that habit before it fully forms. Analytics data across independent podcasts consistently shows that shows returning from a hiatus of three or more weeks lose 15–25% of their pre-hiatus average downloads per episode in the first month back—not because listeners unsubscribed, but because passive listeners stopped actively checking. A standing buffer of two to three completed episodes is the most reliable protection against this effect.

💡 Why downloads and completion rate must be read together

A high download count paired with a low completion rate is not a success—it means your marketing is working but your content is not delivering on the promise your title makes. Download counts are a measure of reach and discoverability. Completion rate is a measure of whether listeners found the episode worth finishing. A single download spike from a viral social post or a guest with a large following inflates your headline numbers temporarily; a consistently rising completion rate trend across 10 or 20 episodes is the signal that the show itself is genuinely improving. Track both metrics together and treat your rolling completion rate as the more honest signal of content quality.

Master This Checklist Quickly

Every important button and option for this pre-made checklist, shown in a glance-friendly format.

Start Here

1
Click any item row to mark it complete.
2
Use the note row under each item for quick notes.
3
Use the tool row for undo, redo, reset, and check all.
4
Use Save Progress when you want to continue later.

Checklist Row Tools

UndoRedoResetCheck allCollapse/Expand sectionsShow/Hide detailsInline notes

Top Action Buttons

Open all sharing and export options in one menu.

Email DraftContinue on another devicePrint or Save as PDFPlain Text (.txt)Word (.docx)Excel (.xlsx)

Add & Ask

Open one menu for apps and AI guidance.

NotionTodoist CSVChatGPTClaude

Copy and customize

Create a new editable checklist pre-filled with your chosen content.

Save Progress

Adds this checklist to My Checklists and keeps your progress in this browser.

Most Natural Usage

Track over time

Check items -> Add notes where needed -> Save Progress

Send or export

Open Share -> Choose format -> Continue

Make your own version

Copy and customize -> Open create page -> Edit freely