The Podcast Delivery and Revision Workflow I Use for Weekly Client Shows

SHOW_EP47_MV2 is open in a browser tab, the episode runs forty eight minutes, and there is exactly one client comment sitting at 00:18:12 saying the guest sounds thin from here until the ad read. That single note is my whole job for tomorrow morning, and I know precisely where to start, because a podcast delivery and revision workflow that works is supposed to produce exactly this, right, one clear instruction pinned to an exact moment in a specific version.

My video editing agency used to do it the other way, a shared folder link in an email, a follow up two days later asking whether anyone had watched it, and finally a reply saying something around the eighteen minute mark, maybe a bit before, can you fix the audio thing. So you scrub around guessing what they heard, you export again, the client says no not that bit, and a forty minute podcast episode quietly eats three days of your week.

So this is the sequence I run now for weekly client shows, from project setup to the final handover, with the places where it usually breaks called out honestly. If the multicam edit itself is where you are stuck, my notes on the video podcast editing workflow cover that half of the job, right, and this post picks up the moment the export is done.

The link is the client's whole experience

The host never sees your timeline, only the page your link opens, so that page deserves the same care as the cut itself.

What clients expect when you deliver podcast edits

Podcast clients are usually not video people, and that matters more than editors like to admit. The host is a founder or a coach, they open your link on a phone between two meetings, and if your email says download this 6 GB file and reply with notes, they open it four days later and your Friday release slips to Monday.

What they expect, basically, is to click once and watch the way they watch anything else, right, without installing something or creating another login. In PlayPause the client opens one browser link and playback runs off a streaming copy while your original file sits untouched, so they see a normal video player instead of a download bar. The catch here is that most editors only notice how much this matters after a couple of episodes slip.

The second expectation is that their note gets heard the first time. A host who says the intro drags does not want to say it twice, and if round two comes back with the intro still dragging, trust me on any level, that relationship gets colder very very fast. I wrote about that fracture point in round three of feedback, because what usually ends a podcast retainer is the host feeling like they keep repeating themselves, right, far more than any single editing choice.

Setting up one project per client show

Before any delivery happens there has to be structure, and I mean really boring structure. Each client show gets one project, each episode gets its own card inside it, and the versions stack on that card, so MV1, MV2 and MV3 live together instead of in folders named final, final2 and final_USE_THIS.

1Create one project per client show

2Add a card per episode with the episode number in its name

3Stack every new export on that card as MV2, MV3 and so on

4Set a custom status so the whole team sees where it stands

Naming is where I would spend your first hour, because SHOW_EP47_MV2 tells me the show, the episode and the version at a glance, and that is basically version control borrowed from software and applied to a folder of MP4s, which kills mistakes like sending the host the cut from before the sponsor fix.

Roles are simpler than people expect, so your assistant editor gets Editor, your producer gets Manager, and the client needs no role at all because they only ever see the share link. Pricing is flat per workspace rather than per person, and if you are a solo freelancer juggling six shows, the freelance editors setup is where I would start.

Sending episodes for approval with a single link

The send itself looks the same every week in my agency. The export goes up as MV1 on the episode card, the status flips to In Review, and I generate a password-protected share link for that one episode, which goes to the host and the producer and nobody else. I never send a folder, because a folder invites the client to wander into last month's episode.

The password matters more for podcasts than for most video work, because episodes often carry an unreleased guest or a sponsor read that is not public yet. Password-protected links are on every plan, and so is instant revoking, so if a link ends up somewhere it should not, you kill it in one click.

Link expiry is the part editors forget until it bites them. Creator links run 30 days and the files expire with them, Agency links run 90 days and Enterprise links never expire, and when a host comes back weeks later to pull a clip for a reel, 30 days runs out fast, so I put podcast clients on Agency at the very least.

50

members on Agency

250 GB

storage on Agency

90 days

link life on Agency

The quiet advantage is who-watched analytics, which tells you who opened the link, when, and from which city. I am not using that to police anyone, to be very honest, I use it so I stop nudging a host who already watched the cut twice on Sunday and simply has not replied yet, because the nudge is what makes you look needy, right, and the data removes the guesswork.

Collecting timestamped podcast feedback that points to exact moments

This is the part that actually saves you the days. Every comment a client leaves lands on an exact frame, so 00:18:12 works like an address, you click it and you are standing on the problem. They can leave a range comment when an issue spans a whole segment, for instance an ad read that needs re-recording, and they can draw on the frame when the note is visual, which in video podcasts is usually a misspelled lower third.

Clients comment without making an account, right, and that is the biggest reason this sticks with busy hosts, because a login is a step that gets deferred and a deferred step in a weekly show is a missed release. If guests also need to sign off on their segments, the no-login review links for podcast guests page walks through that case.

Threaded replies and @mentions keep disagreements in one place as well. When the producer says cut the tangent at 31:00 and the host says keep it, that resolves under the comment instead of in a WhatsApp group I am not in, and in my agency notes arriving over WhatsApp reliably double the round, because somebody has to retype them and something always gets lost.

Old way

Notes in email, WhatsApp and a shared doc, all pointing at rough timings

With PlayPause

Every note sits on its exact frame inside the version it belongs to

On Agency and up there is AI transcription with a clickable transcript, and for podcasts it is the feature I would not give back. The host scrolls to the line they half remember, clicks it, and the player jumps there, and you get an SRT export from the same transcript, which I walked through in making an SRT file for YouTube.

In Premiere, the Premiere Pro panel shows those comments inside Premiere and jumps the playhead when you click one, and for editors working in DaVinci Resolve or Final Cut the loop is export, upload, review, then work through the timestamped list, which is fine for podcast notes that are mostly cuts and audio fixes.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

Keeping podcast editing revision rounds from stretching into week two

Two rounds is what I write into the contract, because a weekly show that takes three rounds is always one episode behind. Round one is notes on MV1, round two is a confirmation pass on MV2, and anything raised after that is a new request rather than a continuation.

Here is a normal week for one show, for instance. The host records on Thursday, files reach me Friday, MV1 goes out Monday afternoon, notes come in by Tuesday evening, MV2 goes out Wednesday, the confirmation pass comes back Thursday morning with the status flipped to Approved, and the episode releases Friday, right, with a spare half day for the week a guest's audio arrives late. Every step has a fixed day, so if Tuesday passes with no notes, I check who opened the link before I chase anyone, does that make sense, right.

Structure helps with scope creep too, because in podcast editing it shows up as four small asks spread over six days, each one awkward to refuse on its own. When every note is timestamped inside a version the count is visible, so you can say we are at eleven notes on MV2 and the last three are new direction, and the contract wording I use is in my piece on writing a revision policy.

Side-by-side version compare, on Agency and up, ends the argument about whether something was fixed, because MV2 sits next to MV3 and the answer is on screen. Playbooks, also Agency and up, hold the per-client rules that never change, like this host wants the cold open under twenty seconds, so a new editor inherits the standard instead of learning it through three rounds of correction. The turnaround math for weekly shows is in keeping podcast review under 48 hours.

• Two rounds written into the contract
• Every note timestamped inside a version
• New direction logged as a new request
• Version compare used before arguing about a fix

Letting clients upload raw recordings to you

Delivery runs in both directions, and the incoming side is usually messier. A host records on Thursday, ends up with three camera files and a separate track for every mic, and then spends Friday fighting a file transfer site while your edit window shrinks.

Guest version upload, on Agency and up, lets somebody send you a file without an account and collects their name and email as they do it, so you know which take came from whom, which is exactly what you need for the remote guest who recorded their own side locally. Upload size is unlimited on Agency and Enterprise and capped at 10 GB per file on Creator, which with long multicam recordings is usually the first limit you hit.

Bulk upload of 100 plus files is on every plan, which saves the afternoon when a backlog of episodes arrives together. If podcasts are your main business, the podcast review platform page shows how the recording and review sides connect.

Handing over the final files

Approval and delivery are two separate moments, and treating them as one step is how editors end up chasing invoices. Once the status flips to Approved, the handover follows the same small routine every week, right, starting with both sides knowing exactly what the client gets.

For a typical video podcast client my handover package is the approved video master, a separate audio file because their podcast feed wants audio, the SRT for YouTube, and any short clips that were in scope, all carrying the same SHOW_EP47 prefix so they sort together. That list goes into the onboarding doc on day one, so nobody asks on a Friday where the audio version went.

The Google Drive integration on Agency and up lets viewers save files straight to their own Drive, so the client holds the master in their own storage, and the backup side protects me too, because at the end of the day I do not want to be the single point of failure for somebody's archive. The wider version is in delivering final video files, and the wording I send is in my video delivery email template.

“

Approval is a status on the card, and handover is the routine that follows it every single week.

I'm pretty sure the biggest shift comes from treating delivery as a defined process with a start and an end, closer to project management than to firing off files, and you see what I mean here, once it is defined it repeats, and a repeating process is what lets you take on show number seven without hiring.

Frequently asked questions

Do my podcast clients need an account to leave feedback?

No, and this is the part I would never compromise on. Your client opens the share link in any browser, watches straight away, and leaves timestamped comments without signing up for anything, on every plan. You can put a password on the link for unreleased episodes and revoke it instantly if it travels somewhere it should not, and the fewer steps between the host and their notes, the faster your round closes.

Which plan should a podcast editor with five shows pick?

For five weekly shows I would pick Agency, and the reason is the feature set more than the limits. You get AI transcription with SRT export, guest version upload so hosts can send raw recordings without an account, side-by-side compare, Playbooks and the Google Drive handover, plus 90 day links and no upload cap per file. Creator works fine while you are at one or two shows and your recordings stay under 10 GB a file.

How do I stop a client from adding notes after approval?

I handle it with structure rather than emotion. Two rounds go in the contract, every note is timestamped inside a specific version, and anything arriving after the Approved status gets logged as a new request with its own scope. Because the whole history sits on the episode card, the conversation becomes a factual one about which version a note belongs to, right, rather than a debate about what somebody remembers asking for.

What happens to my episodes if I downgrade my plan?

Downgrading never deletes your content, so your projects, versions and comments stay exactly where they are. What changes is which plan features you have from then on, so if you drop from Agency to Creator, tools like AI transcription and guest version upload are no longer part of your plan. For archive-heavy podcast work I would check link life before downgrading, because Creator links run 30 days.

If you cut podcasts for other people and you are tired of losing days to delivery, start the 7-day free trial on any plan, set up one project for your busiest show, and send the next episode as one password-protected link instead of a folder. You will know inside one weekly cycle whether it fits.

So yeah. That's my way of saying it.