The episode pipeline

Every episode you produce moves through the same four stages: intake (raw files, notes, and assets arrive), edit (cleanup, structure, polish, master), review (host listens, requests changes), and publish (upload, notes, clips, scheduling). The stages are obvious. What separates a producer from an editor-for-hire is that each stage has a written standard attached: what “intake complete” means, how many days the edit takes, how long the host gets to review, and what happens when a stage runs late.

Put the turnaround in writing at onboarding, not in a panic later. A standard agreement for a weekly show: raw files delivered by Tuesday noon, first edit back within three business days, host review within 48 hours, one revision round, publish Friday. Notice the standard binds the host too — a review that comes back Thursday night can't produce a Friday publish without a rush conversation, and the document is what makes that conversation calm instead of personal.

Track every episode on one visible board or list: episode, stage, due date, blocker. When a client asks “where are we?” the answer should be a link, not a scramble. Keep names consistent from stage to stage — the episode number and title in the file name, the board, and the upload, identical everywhere — so nobody, including you at midnight before a publish, ever has to guess which cut is final. Version the edit files too (v1, v2 after revisions), and never overwrite a version the host has already heard.

And when the pipeline slips, say so before the deadline, not after. A producer who flags a delay on Wednesday with a revised date keeps the client. One who goes quiet until Friday teaches the client to start looking for a replacement. Reliability, in practice, is mostly this: no surprises.

The guest workflow

The cheapest audio problem to fix is the one that never gets recorded. Most bad guest audio comes from predictable causes — a laptop mic across a room, a fan, a guest who planned to “just talk from the car” — and every one of them is preventable with a workflow that starts days before the recording, not minutes into it.

Run three steps. The brief: when the booking is confirmed, the guest gets a short document — what the show is, who listens, the topics and rough questions, how long it runs, and where it will be published. A briefed guest arrives prepared, and preparation is half of a good conversation. The tech sheet: one page, plain language — wear headphones, use the best mic you have (borrowed beats built-in), sit in a small room with soft surfaces, close windows and silence notifications, plug in rather than running on battery. The tech check: for high-value guests, five minutes on the recording platform a day or two early. You hear their room and setup while there's still time to fix it, and the guest stops being nervous about the technology.

Day of recording, join early, run a 20-second test, and listen before you let the host start. If the audio is bad, fix it now — move the guest closer, switch the mic input in settings, re-seat them away from the window. Ten minutes of setup saves hours of cleanup you may not fully be able to do, and it's the clearest line between producing and just pressing record.

Batching and templates

Start with the math this whole business runs on: a full-post episode takes roughly 2–4 hours of work per finished hour of interview audio — the edit itself, plus notes, clips, upload, and the small tasks around them. A weekly one-hour show is therefore an 8–16 hour monthly commitment. Producers who price from that number stay in business. Producers who price from “it only took an afternoon once” burn out by spring.

Templates are how you hold that time down. Build a project template in your DAW with the full track layout, your cleanup chain as presets, intro and outro in place, and markers for ad slots — starting an episode should mean importing audio into a working session, not rebuilding your setup every time. Keep the same discipline outside the DAW: a show-notes template (Module 4's skeleton), a file-naming convention you never vary, an export preset locked to −16 LUFS, and a publish checklist the episode passes before it leaves your hands.

Batching is the other half. Batch-record shows benefit you too: four episodes recorded in a week can be edited in a rhythm instead of four separate cold starts. Batch your own tasks as well — write all four sets of show notes in one sitting, pull all the clips in another. Context-switching is the invisible tax on freelance production work. The producer who batches quietly gains several hours a week over the one who doesn't, at identical quality — and those recovered hours are the difference between a calendar that's full and a business that's actually profitable.