Backed by Y CombinatorThree documents and three sheets that gate an episode's Published status on a filled Clip Log, not on how good the recording was.
Free download · No account needed
What you get
Pack of 6 files: 3 documents, 3 spreadsheets
Podcast Production Workflow TemplateEpisode Pipeline
Published is a status the sheet has to earn, not a box anyone can check.
| Episode | Guest | Stage | Clip Log |
|---|---|---|---|
| required | |||
| required | |||
| required |
No row in the Clip Log column, no move to Published. A finished edit is not the same thing as a finished episode.
Podcast and video-show consumption keeps setting records: 130 million Americans listened to or watched a podcast in the last week, per Edison Research's 2026 Infinite Dial survey. Audio and video are now a dual-format medium rather than two separate audiences. What ranks for "podcast production workflow template" is a Kanban board: discover, outreach, scheduled, recorded, published, with clipping folded into a fifth stage called grow. The stages are correct, and the board still lets an episode reach published with an unbriefed guest and no clip plan, because nothing on it actually stops that.
This pack ties both gaps to the pipeline directly instead of leaving them as habits to remember. The Guest Brief goes out with the angle, the questions and what to prepare, and the Guest Register logs the date it actually went out against the scheduled recording date. On this pack's own worked quarter, every guest briefed five or more days out came in clean: no missing material, no scramble. Guests briefed inside two days came in clean once out of three, and the other two cost real edit time recovering from an unprepared guest.
The same discipline runs on the other end. The Clip Log gates the pipeline's own Published status: no episode moves there until it carries a row for every planned channel, a declined row with a reason counting as filled. The ten published episodes this quarter logged 63 clips against a 20-clip baseline of one show-notes post and one social cut each, a 3.15x difference, because the log is a required stage, not a separate project. For repurposing one existing recording instead of running a weekly show, see the content repurposing pack.
Episode PipelineThe Marrow Sessions, weekly B2B interview show. 12 episodes this quarter.
| Ep | Guest | Stage | Clip Log |
|---|---|---|---|
| 21 | N. Dalrymple | Published | Complete, 6 clips |
| 22 | H. Osgood | Published | Complete, 5 clips |
| 23 | K. Marchetti | Edited | Blocked, no rows yet |
| 24 | W. Aduba | Recorded | Not started |
Episode 23 is fully edited and still cannot move to Published. That is the gate working, not a bug in the sheet.
Guest Register12 guests this quarter. Lead time is the brief's send date against the record date.
| Guest | Lead time | Prep submitted | Outcome |
|---|---|---|---|
| D. Achterberg | 7 days | Yes | Clean |
| M. Petrakis | 5 days | Yes | Clean |
| H. Osgood | 1 day | No | Rework, dead air cut |
| K. Marchetti | 2 days | No | Rework, missing bio |
9 of 9 guests briefed 5+ days out came in clean. 1 of 3 briefed inside 2 days did.
Clip LogEpisode 13, 7 rows logged from one recording.
| Clip type | Channel | Status |
|---|---|---|
| Short-form video | Shorts/Reels/TikTok | Live |
| Audiogram | Live | |
| Quote card | Live | |
| Quote card | Live | |
| Newsletter blurb | Sent | |
| Blog write-up | Blog | Live |
10 published episodes this quarter logged 63 clips against a 20-clip baseline, a 3.15x difference.
The angle, the ordered questions with an anchor marked, and what the guest is not the right person to answer, written before the recording like a content brief for a conversation instead of an article.
What actually gets sent to the guest: the questions in advance, what to prepare, and the technical requirements, logged with the date it went out.
Every guest with their brief's lead time against the record date and the recording outcome, so the lead-time policy is provable, not assumed.
Every episode's stage from booked to published, with a locked GUID and a Published column gated on the Clip Log actually being filled.
The fixed structure every episode's notes follow, including the GUID rule that keeps a directory from ever showing one episode twice.
One row per planned clip, required before an episode can move to Published; the standard channel set includes a newsletter blurb, which is raw material for the newsletter program pack once that show has a list to write to.
Cadence, format and the standard clip channels get set once. The guest-brief lead-time policy defaults to five days, the point where this pack's own worked quarter turned clean.
The Guest Brief goes out built from the Episode Brief, and the Guest Register logs the date it was actually sent against the scheduled recording.
Booked, briefed, recorded, edited, clipped, published. Each stage is a real status change on the Episode Pipeline, not an assumption about where things stand.
The Clip Log gets a row per planned channel before the episode can move to Published, so clipping happens on schedule instead of whenever someone remembers.
Yes, the Word and CSV download needs no account or card. Edit with AI installs the pack in River and sets up the pipeline from whatever is already booked for your next recording, guests included.
A board tracks stage names: discover, scheduled, recorded, published. This pack makes two of those stages earn their status. Published will not move without a filled Clip Log, and Briefed is not real until the Guest Register shows a brief actually sent, with the lead time that predicts whether the recording goes clean.
The content repurposing pack maps outputs for one long-form report or recording, commissioned once. This pack runs a recurring show: guest booking, an episode-by-episode pipeline, and a clip log gate built into a schedule that repeats every week, with guests to prep and a cadence to hold.
Log it as declined with the specific reason, rather than leaving the row off. A guest's echoey audio might rule out a stand-alone audiogram; that still clears the Clip Log gate, because the show decided the channel does not apply, instead of simply never getting to it.
Yes. Each panelist gets their own copy with the shared angle and anchor question, plus which of the ordered questions are aimed at them specifically, so nobody arrives having only skimmed a brief written for someone else.
No. The pipeline, the Guest Brief and the Clip Log apply the same way to a recorded video interview show. The Show Notes Format doc's GUID rule comes straight from Apple's own RSS guidance, which governs video enclosures the same way it governs audio ones.
Written by
Co-founder & CEO, River
Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.
Send what's booked for the next recording. River sets up the pipeline and drafts the Guest Brief with your lead-time policy already applied.
Edit with AI