TL;DR / Summary: A six-episode podcast season dies when recording and editing compete for the same weekends. Fix the publish date of episode one, subtract twelve weeks, and separate research, recording, edit, and buffer weeks so you never upload a raw take the night a show is supposed to go live.
Seasons need a runway, not a vibe
Solo and two-person shows often treat “launch” as a mood. Guests get booked late, intros are written while exporting, and the first episode lands on a random Thursday because someone finally finished editing. Listeners do not care about your mood. They care whether episode two appears when you said it would.
Twelve weeks is a practical length for a short season: enough time for six weekly episodes with room for one guest cancellation and one bad recording day. Shorter plans force you to publish unfinished audio. Longer plans invite endless “research” that never becomes a take.
Write the date you want episode one public. Then count twelve weeks backward and treat that earlier Monday as production day zero—not the day you buy a nicer microphone.
Weeks one and two: season bible, not fancy gear
Before you touch DAW settings, write a one-page season bible: audience promise, episode length target, recurring segments, and what you will not cover. That page stops mid-season topic drift, which is the main reason edits balloon.
- Episode titles drafted — even if they change later, empty slots get filled
- Guest list with backups — every primary guest needs a secondary topic you can record alone
- Release cadence — weekly or biweekly, chosen once and defended
- Hosting and RSS already live — do not discover DNS issues in week eleven
Pin the launch date with a countdown tool. 12 weeks from today makes the first publish date concrete enough to put next to your calendar alerts for guest confirmations.
Weeks three to five: batch the research
Research expands to fill available evenings unless you cap it. Give each episode a fixed research budget: two sources, five bullet talking points, and one anecdote you personally can tell without notes. If a topic needs a book-length deep read, it does not belong in a twenty-minute episode.
Guest prep that respects their time
Send guests three questions and a time box seven days before the call. Record a thirty-second tech check the day before. Bad audio from a guest is rarely fixed in the mix; it is fixed by catching a headset problem early.
By the end of week five you should have outlines for all six episodes and confirmed recording slots for at least the first four. Empty calendars in week six are how seasons slip a month.
Weeks six to eight: record ahead of the edit
Record episodes one through four in this window even if you only plan to publish weekly. Editing always takes longer than the recording. A buffer of finished takes is the difference between a calm Tuesday export and a panicked Thursday night.
Name files with episode number, guest last name, and date. Store raw takes and project files in separate folders. Losing a project file mid-season is more common than people admit, and it usually happens the week you are already late.
A season is a manufacturing line. Recording is upstream; publishing is downstream. Never let them share the same day.
Keep intros and outros as reusable templates. Re-recording a custom cold open for every episode feels creative until you are three hours behind on episode three.
Weeks nine and ten: edit, loudness, show notes
Edit for clarity, not perfection. Remove long pauses and verbal trips; leave personality. Match loudness to a consistent target so episode two does not blow out someone’s earbuds after a quiet episode one.
Write show notes while the conversation is fresh—same day as the edit if possible. Notes written weeks later invent timestamps that do not match. Include one link list and a short plain-language summary for people who listen at 1.5x and still want the gist.
Schedule uploads into your host as drafts with the correct publish timestamps. Draft status is your friend; “I’ll remember to hit publish” is not.
Week eleven: marketing without stealing edit time
Cut two short clips per episode for social, write one email announcement, and update the website episode list. Do this from already-finished audio. Do not reopen the DAW to “just tweak” the music bed while you should be writing captions.
If you have a trailer, finalize it now. Trailers that ship the same morning as episode one rarely get the attention you hoped for because you are busy fighting export errors.
Week twelve: publish and protect the cadence
Episode one goes live on the date you chose twelve weeks ago. Episode two should already be edited or at least recorded. The final week is for watching the feed update, answering early listener mail, and refusing new “quick guest” ideas that would break the remaining schedule.
After launch, keep a simple board: recorded, edited, scheduled, live. Move cards forward every week. The twelve-week runway only works if you keep treating the season as dated work, not as inspiration that arrives whenever the mic feels inspiring.
The season review date worth writing down
Put a review meeting—solo or with your co-host—on the calendar for seven days after the final episode. Decide then whether a second season deserves another twelve-week block. That decision is cleaner when the first season actually shipped on time, with notes you can read, and with raw files you can still find.