Practical guide

A producer-to-reviewer handoff that does not lose the episode

Last materially reviewed 2026-09-19

Quick answerHand over one identifiable draft, a clear decision and the evidence needed to approve it.
What to know

Make the draft identifiable

Use the show, working episode title and version of the source media in the handoff. Include the intended publication date and any unresolved editorial questions. Do not send several similarly named files and ask the reviewer to infer which is current. A short, complete record reduces repeated work more effectively than an elaborate task system filled with ambiguous completion labels.

What to know

State what approval means

Ask the reviewer to approve specific things: final audio, title, description, links or scheduled release. Distinguish approval of content from confirmation that the hosting upload completed. A reviewer who listened to a local file has not necessarily checked the file attached to the draft. Keep that final association visible so a correct editorial decision does not result in the wrong media being published.

What to know

Handle revisions without losing history

When a change is requested, retain the original request and identify the revised media or text. Mark superseded versions clearly rather than overwriting every reference without explanation. Avoid republishing or recreating the entire episode merely because a draft needs correction. Follow the supported editing path and check which changes affect the live feed before saving them to a published item.

What to know

Close the loop after release

Record the actual public episode reference and who verified it. If publication is delayed or the result is uncertain, keep the task in that state rather than marking it done to clear the queue. The next person should know whether to review, publish or investigate, not have to repeat the whole process. This handoff can be a small shared record; its usefulness comes from preserving identity and responsibility, not from adopting another software subscription. For a correction, note the exact requested change beside the new version. “Updated” alone does not tell the reviewer whether the sponsor link or the audio introduction was fixed.

Continue when useful

Next: The small-network podcast launch checklist

Launch only after content, ownership, distribution and recovery each have an observable pass.

Open The small-network podcast launch checklist →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Transistor team roles — Merchant documentation · transistor.fm · Merchant-controlled · checked 2026-09-19
  2. Transistor distribution — Merchant documentation · transistor.fm · Merchant-controlled · checked 2026-09-19