WORK EXPERIENCE Β· PODCAST PRODUCTION

From Idea to Episode

A five-day, hands-on guide to making a real interview podcast β€” planning, recording, editing, mixing & mastering, and publishing. By the end of the week you'll have produced a finished episode.

0 of 0 steps ticked off

Save your work:
β˜…

Welcome β€” start here

The mission this week: interview 2–3 family members about their lives and turn it into one finished, published-quality podcast episode. You'll do every job a producer does, and you'll use the same gear and software used on Devpolicy Talks.

πŸ—ΊοΈHow the week works

Each day runs roughly 9:00am to 3:00pm with a lunch break and two short breaks. Every day follows the same rhythm:

  • Before questions (5–10 min, ~9:00) β€” think before you dive in.
  • Learn β€” short videos and reading, explained in plain English.
  • Do β€” the real hands-on work, with a tick-box checklist.
  • After questions (~2:45) β€” reflect on what you learned.

Everything you type and tick is saved automatically in this browser. You can close the page and come back β€” your work will still be here. (It saves only on this computer, so use the same one each day.)

Your work saves on the device you're using. If you swap between a phone and the Mac, use Export my answers to download a copy you can keep or email to yourself.

🎚️Your toolkit β€” the gear & software

The recording chain (how sound gets recorded)

Your voice travels through a chain of equipment. Each link has a job:

  • ATR2100x microphone β€” turns your voice into an electrical signal. It's a dynamic mic, so it ignores most room noise. Speak close, about a fist's width away.
  • Zoom H5 recorder β€” a portable recorder that captures the interview straight to an SD card. Perfect for sitting down with family. The mics plug into its two XLR inputs (XLR is the standard balanced microphone connector) and each person gets their own track.
  • Cloudlifter β€” the ATR2100x has a quiet output, so the Cloudlifter gives it a clean +25 dB (decibel) boost. Less hiss, more signal. It runs on 48V phantom power (a 48-volt feed sent up the cable to power gear that needs it).
  • Focusrite Scarlett β€” your audio interface at the Mac. It does double duty: it's how you record any voiceover (your intro, outro and any narration), and it's how you listen while editing and mixing β€” your headphones plug into it for clean, accurate sound. It bridges the analogue mic world and the digital computer, and supplies 48V phantom power.
  • Mac Mini (M4 Pro) β€” where the editing, mixing and publishing happen.
  • ATR-M70x headphones β€” closed-back headphones so the sound doesn't leak back into the mic. Wear these whenever you record or edit.
  • TC Electronic loudness meter β€” a dedicated hardware meter at the desk that reads the true loudness (in LUFS β€” Loudness Units, the standard measure of how loud audio actually sounds) of your mix. You'll use it on Day 4 to master the episode to the right level; it isn't used while recording.

You'll use two recording setups this week:

🎀 Field (the interview): Mic β†’ H5 β†’ SD card

πŸ–₯️ Desk (voiceover + editing): Mic β†’ Cloudlifter β†’ Scarlett β†’ Mac

From Day 3 onwards you're at the desk, with the Scarlett as your audio interface β€” headphones plugged into it for editing and mixing, and the mic on it whenever you record voiceover.

The software (what each program is for)
  • Zoom / Descript Rooms β€” for recording a remote guest down the line.
  • Descript β€” edits audio by editing text. You'll cut out mistakes and waffle here first, in the rough stage. Easiest place to start.
  • Adobe Audition β€” the professional audio workstation. This is where you repair, EQ (equalise, i.e. adjust the tone), compress, mix and master the episode to a polished finish.
  • iZotope RX β€” specialist repair tools (noise removal, de-clicking, de-essing) that run inside Adobe Audition.
  • iZotope 12 β€” iZotope's mastering software, used right at the end to set the episode's final loudness with its built-in limiter.

🐞Tattle β€” your production HQ

Tattle is the web app Dad built for making podcasts (it's what the real Devpolicy Talks production runs on). It's the home base that ties your whole week together β€” you'll plan the episode, get it transcribed, write the script, generate the shownotes, and publish, all from one place. Sign in at tattle.idrys.org β€” ask Dad for your login (it uses a 6-digit code from an authenticator app).

Tattle runs your episode through these stages β€” you'll move it along one step at a time:

planning β†’ scheduled β†’ recorded β†’ transcribed β†’ scripting β†’ review β†’ finalised β†’ published

What Tattle does at each stage (and which day you'll use it)
  • Day 1 β€” Planning: create the episode in Interview Mode, fill in the Planning page, and set up reusable Document Elements (intro, outro, Acknowledgement of Country).
  • Day 2 β€” Recorded: upload your interview audio and move the episode to recorded.
  • Day 3 β€” Transcribed: Tattle auto-transcribes with speaker diarisation (it labels who's talking), then AI (artificial intelligence) suggests corrections you accept or reject. This clean transcript becomes your editing map.
  • Day 4–5 β€” Scripting: drag-and-drop your episode script from template sections, and generate the intro script you'll voice.
  • Day 5 β€” Collateral & publishing: AI-generate shownotes, a summary, grab quotes, social posts and metadata, then sync the finished episode to Simplecast.

Tattle handles the words and admin (transcript, script, shownotes, publishing). Descript and Audition handle the sound (cutting and polishing the audio). Together they cover the whole job.

πŸ“Stay organised β€” one project folder

Before Day 2, make one folder for the whole episode on the Mac. Keep everything inside it with these sub-folders:

  • raw β€” untouched recordings straight off the mic/Zoom
  • descript β€” the rough-cut export
  • audition_session β€” the Audition project + working files
  • exports β€” the final MP3 (the compressed audio file you publish) and any clips

Name files so you'll understand them in a month, e.g. 20260615_grandma_raw_host.wav. Date first (YYYYMMDD) keeps them sorting in order.

1

Concept, format & interview planning

Goal: Understand what makes a good interview episode, then design the one (or two) you'll record this week. Today is all paper, listening and planning β€” no recording yet.

πŸ•˜Today's plan

  • 9:00–9:30Intro chat & goals for the week
  • 9:30–10:30Learn podcast basics (listening + short videos)
  • 10:30–10:45β˜• Morning break
  • 10:45–12:00Choose topic, audience & guest; outline the episode
  • 12:00–13:00πŸ₯ͺ Lunch
  • 13:00–14:15Write the interview guide & episode structure
  • 14:15–14:30β˜• Afternoon break
  • 14:30–15:00Mock questions / test run & reflections

✏️Before you start β€” answer these

βœ…Do β€” design your episode

A great closing question for a life-story interview: "What's one thing you wish younger people understood about your life?"

πŸͺžAfter β€” reflect

2

Recording β€” tech, mic technique & the interview

Goal: Set up the Zoom H5 with the ATR2100x mics, get clean levels, and record the real interview to the SD card. (For a remote guest you'd use Zoom / Descript Rooms instead; the Focusrite is for your desk voiceover later in the week.)

πŸ•˜Today's plan

  • 9:00–9:20Recap & quick run-through of the interview guide
  • 9:20–10:15Learn the recording chain + test recordings
  • 10:15–10:30β˜• Morning break
  • 10:30–12:00Record the main interview
  • 12:00–13:00πŸ₯ͺ Lunch
  • 13:00–14:00Pick-ups / a short second interview
  • 14:00–14:15β˜• Afternoon break
  • 14:15–15:00Transfer, label & organise files; debrief

✏️Before you record

Once you're rolling, before the real questions, ask your guest out loud whether they're happy to be recorded and for the episode to be shared publicly, and capture that "yes" at the very start of the recording.

πŸŽ™οΈSetting up the Zoom H5

Step 1 β€” get the recorder ready (do this before your guest arrives)
  • Power: the H5 has no internal battery β€” put in 2Γ— AA batteries (or run it from USB). Fresh batteries last about 15 hours.
  • SD card: with the recorder off, slide the SD card in (face up) on the right-hand side. Turn on, then format the card in the menu so it's clean and compatible.
  • Recording mode: choose Multi File and set the format to WAV, 48 kHz / 24-bit (WAV is an uncompressed, top-quality audio file; 48 kHz / 24-bit is its quality setting, and it matches what you'll use in Audition).
  • Plug in the mics: connect each ATR2100x with an XLR cable (the standard 3-pin microphone cable) into Input 1 and Input 2 at the bottom, one mic per person, each on its own track. (Ignore the X/Y mic on top, the recorder's built-in stereo mic, for interviews.)
Step 2 β€” no phantom needed, then arm the tracks
  • The ATR2100x is a dynamic mic, so it does not need phantom power. Leave 48V off for both mics: the H5's preamps have plenty of gain for these mics on their own, so you do not need the Cloudlifter here. (The Cloudlifter and 48V phantom come in later, only on the desk setup with the Scarlett on Day 4.)
  • Arm the tracks: press the Track buttons (1 and 2) so they glow red. Only armed tracks record.
Step 3 β€” set your levels (the golden rule)
  • Each input has its own gain dial (under the little protective bar). No buttons needed β€” just turn the dial for that channel.
  • Have each person talk at normal volume. Turn their dial up until the loudest bits peak around βˆ’12 dB (decibels, the unit on the level meter) β€” strong and clear, never slamming into the top (0 dB is distortion you can't fix).
  • Build in a real safety net. The H5's Backup Record only copies the top X/Y mic (the L/R track), not Inputs 1 & 2, so it will not protect your interview mics. Instead, run a phone voice memo alongside as a genuine second recording (and, if you want a hardware backup, arm the X/Y capsule as a room-safety track too). Never trust a single recording of an interview you can't redo.
  • Plug the ATR-M70x headphones into the H5's headphone socket and actually listen while you set levels. Your ears are the best meter.

Mic technique: speak across the mic, not straight into it, about a fist's width away. That tames "popping" Ps and breath noise.

βœ…Do β€” capture the interview

πŸͺžAfter β€” reflect

3

Rough edit in Descript β€” shape the story

Goal: Get a clean, corrected transcript in Tattle to use as your map, then make the rough audio cut in Descript β€” removing the big stumbles, trimming the waffle, and shaping the story before any detailed audio work.

πŸ•˜Today's plan

  • 9:00–9:20Listen to the raw interview start to finish
  • 9:20–10:30Import into Descript, auto-transcribe, get oriented
  • 10:30–10:45β˜• Morning break
  • 10:45–12:00Content edit (cut by editing the text)
  • 12:00–13:00πŸ₯ͺ Lunch
  • 13:00–14:00Fine-tune, remove filler, draft intro/outro script
  • 14:00–14:15β˜• Afternoon break
  • 14:15–15:00Export the edited audio for Audition

✏️Before you edit

🐞First, in Tattle β€” get your transcript

Before touching the audio, let Tattle do the listening for you. Its transcript becomes the map you'll edit from.

Why transcribe in Tattle first?
  • Speaker diarisation labels who said what, so you can see the conversation as a script.
  • AI Correction suggests fixes for misheard words β€” you accept or reject each one, so you stay in control and learn to spot errors.
  • Version history means you can always compare changes and undo. Nothing is ever lost.
  • This corrected transcript powers everything later β€” the script, shownotes, grab quotes and metadata all build on it.

βœ…Then, in Descript β€” make the rough cut

You'll transcribe again here, but for a different job: Descript transcribes so you can edit the audio by editing its text. Tattle's transcript is your reading map and the source for the script and shownotes; Descript's is the handle you grab to cut the sound. Same words, two purposes.

πŸͺžAfter β€” reflect

4

Editing, repair, mixing & mastering in Audition

Goal: Bring the Descript rough cut into Adobe Audition. Clean it up (noise reduction & repair), shape the tone (EQ & compression), then mix and master to a polished, podcast-ready file.

πŸ•˜Today's plan

  • 9:00–9:20Listen to the rough cut critically, as a listener
  • 9:20–10:30Set up the Audition multitrack session, bring in audio
  • 10:30–10:45β˜• Morning break
  • 10:45–12:00Noise reduction, repair & basic editing
  • 12:00–13:00πŸ₯ͺ Lunch
  • 13:00–14:00EQ, compression, levels & basic mastering
  • 14:00–14:15β˜• Afternoon break
  • 14:15–15:00Final bounce & loudness check

✏️Before you mix

πŸ› οΈThe clean-up & polish steps

What each tool actually does
  • Noise Reduction β€” capture a "noise print" from a second of silence (room tone), then tell Audition to subtract that hum/hiss everywhere. Go gently to avoid a "underwater" sound. iZotope RX is the specialist version of this.
  • Healing / spectral repair β€” paint out one-off clicks, mouth noises or a stray bump.
  • Parametric EQ (equalisation, precise control of the tone) β€” roll off low rumble, add a little "presence" so speech is clear, tame any harshness.
  • Compression β€” gently evens out the loud and quiet bits so the voice stays steady.
  • Mastering & loudness β€” the final step. Podcasts are delivered to a target loudness, not just a peak level, so the whole episode sits at a steady volume. Watch the TC Electronic loudness meter and bring the integrated loudness of the finished episode to βˆ’16 LUFS (the house standard for this show), keeping the true peak under about βˆ’1 dBTP so nothing distorts. Master in iZotope 12 and use its limiter (which raises the overall level and stops the loudest peaks from clipping) to bring it up to βˆ’16; then re-check the integrated reading across the whole episode. βˆ’16 LUFS is the standard target for a mono podcast, which is how this show is delivered.

βœ…Do β€” mix & master

πŸ“ Reading the loudness meter: play the whole episode through and watch three numbers. Integrated LUFS is the average across the entire programme β€” that's the one you master to βˆ’16. Momentary / short-term jumps around moment to moment, which is normal. True peak is the single loudest instant; keep it under about βˆ’1 dBTP. Nudge the master gain or limiter until Integrated settles on βˆ’16 LUFS over the full episode.

🎡 Music beds: a short piece of licensed (royalty-free, i.e. cleared to use) music under your intro and outro gives the episode a signature. The standard moves: fade it in and out, duck it (drop its volume) under any voice so the words stay clear, and keep it low and brief. Use the same bed every episode for consistency.

πŸŽ™οΈ Recording voiceover today: for your intro, outro or any narration, record at the desk through Mic β†’ Cloudlifter β†’ Scarlett β†’ Mac straight into Audition β€” the same interface your headphones are plugged into for monitoring.

🐞 Tattle tie-in: move the episode to the scripting stage. Use Tattle to generate an intro script, tweak the wording, then record and mix that voiced intro/outro into the episode here in Audition. Start drag-and-dropping your episode script from the template sections too β€” you'll finish it tomorrow.

πŸͺžAfter β€” reflect

5

Final polish, shownotes & distribution

Goal: Prepare the episode for release β€” a final quality-control listen, export with metadata, write the title and shownotes, and learn how an episode actually reaches podcast apps.

πŸ•˜Today's plan

  • 9:00–9:45Final uninterrupted listen & minor fixes
  • 9:45–10:30Export final audio & check the file
  • 10:30–10:45β˜• Morning break
  • 10:45–12:00Write title, description, shownotes & pull-quotes
  • 12:00–13:00πŸ₯ͺ Lunch
  • 13:00–14:00Learn publishing: host platform, RSS feed, scheduling
  • 14:00–14:15β˜• Afternoon break
  • 14:15–15:00Project retrospective & "teach back"

✏️Before you publish

▢️Learn β€” watch & read

How does a podcast actually reach Spotify & Apple Podcasts?

You don't upload directly to Spotify or Apple. Instead:

  • The episode goes to a hosting platform β€” for this show that's Simplecast. Tattle pushes the audio, title, description and shownotes straight there for you.
  • Simplecast creates an RSS feed (RSS stands for Really Simple Syndication) β€” a constantly-updating list of all your episodes.
  • Apple, Spotify and other apps subscribe to that feed and automatically pull in each new episode.
  • That's why consistent, accurate metadata (title, episode number, description) matters β€” it's what listeners see everywhere.

🐞In Tattle β€” generate the collateral & publish

This is where Tattle does the most work. From your corrected transcript it can write all the bits that go around the audio, then send the finished episode to Simplecast.

Always read AI-generated text before you publish it. Tattle gives you a strong first draft β€” your job is to make it true, clear and in the show's voice.

βœ…Do β€” release-ready

πŸͺžAfter β€” reflect on the whole week

πŸ†You did it

Plan in Tattle β†’ record β†’ transcribe & correct in Tattle β†’ rough cut in Descript β†’ mix & master in Audition β†’ script & generate collateral in Tattle β†’ publish to Simplecast. That's the same pipeline a professional producer uses. You took a family story all the way from an idea to a finished, published podcast.

Saved βœ“