Hello! Last time, you turned your interview draft into a guide that separates SAY, ESSENTIAL QUESTION, OPTIONAL FOLLOW-UP, and HOST ONLY. That makes the page easier to use while you listen to a guest.
Now the same guide needs to help someone shape the recording into an episode. In this lesson, you will add planned audio and video edit instructions without making the page difficult to read—or leaving an editor to guess which words were spoken, which notes were private reminders, and which changes you actually want.
One script, two different jobs
A recording guide tells you what to say or ask now. An edit note tells someone what to do with recorded material later. Both can sit near the same interview question, but they need visibly different labels.

That distinction is easy to miss. HOST ONLY: Pause before the next question asks you to change your delivery. AUDIO EDIT: Leave a brief pause before the next question asks the editor to preserve or create space in the finished episode. You might use either note, or both, but they are not interchangeable.
Keep the labels from your host guide and add two editor-facing ones:
- AUDIO EDIT — PLAN: A proposed change to the sound, such as music, a transition, or a section you expect to trim.
- VIDEO EDIT — PLAN: A proposed change to the picture, such as a title, a graphic, or a cut to another available shot.
The word PLAN matters. Before recording, you cannot know exactly what the guest will say or where an edit will fall in the recording. A planned cue tells the editor your intention; it is not a claim that a usable clip already exists. If an instruction depends on what happens during the interview, say so: “If the guest gives a clear three-step answer, consider a three-step graphic.”
Make the labels do the work rather than relying only on colour, highlighting, or brackets. Those visual marks may help you scan the page, but a plain-text copy should still be understandable. In particular, never put an editor instruction on a SAY line.
Write cues an editor can act on
Read the short editing-notes section and opening sample of the Podcast Script Writing Guide from the Idaho Law Foundation. The sample shows spoken lines and sound cues occupying separate positions on the page. Our interview guide will use more explicit labels because it also has to distinguish host-only reminders from instructions for two kinds of editing.
Podcast script writing guide - Idaho Law Foundation
Read the Idaho Law Foundation guide for examples of audio cues placed alongside a script, rather than written as dialogue.
On p. 4, find “STEP 9: ADD AUDIO & EDITING NOTES.” Read the editing cues, from its first bullet through the final example. Then turn to “SAMPLE SCRIPT (10–12 MINUTE EPISODE)” on p. 5. Read the opening example, beginning at the music cue and stopping at the host’s first interview question. Notice which text is spoken and which text describes a sound to add or change.
A useful planned edit note answers four practical questions in as few words as possible: Where does it belong? What should change? What material should the editor use? What should the result feel or sound like? If you do not know one of those answers yet, mark it as undecided rather than inventing it.
For example, “Add music” gives little guidance. This is more usable:
AUDIO EDIT — PLAN: Under the opening SAY line, use the approved intro music at a level that keeps speech clear; fade it out before the first interview question. Asset: confirm approved music file before editing.
The location is tied to lines in the guide, not to a guessed recording time. The note specifies what to do and makes the missing asset visible. Similarly, “Add a graphic” can become:
VIDEO EDIT — PLAN: When the guest explains the final process, show a simple graphic of its main stages if their answer makes those stages clear. Confirm the wording against the recording before creating it.
That condition protects the editor from building a graphic around an answer the guest never gave. For other video cues, you might identify an approved title card, a guest-name graphic with spelling to verify, or footage you have permission to use. If the footage is not yet available, do not imply that it is.
Here is how those notes can fit into the host guide from the previous lesson:
OPENING
SAY: Today we’re looking at what happens when a customer questions a bill.
AUDIO EDIT — PLAN: Put approved intro music under the opening; fade it
out before the first interview question.
VIDEO EDIT — PLAN: Show the episode title during the opening.
Confirm the final title text before editing.
BLOCK 1 — THE PROBLEM
ESSENTIAL QUESTION: What made a dispute hard to resolve?
OPTIONAL FOLLOW-UP: Can you give an anonymized example?
HOST ONLY: Do not ask for details that identify a customer.
VIDEO EDIT — PLAN: If a visual explanation would help, consider a
simple process graphic. Check its steps against the recorded answer.
BLOCK 2 — WHAT CHANGED
ESSENTIAL QUESTION: How did you decide what to change first?
HOST ONLY: Listen for a specific decision, not just a list of improvements.
AUDIO EDIT — PLAN: If there is a natural break between the problem
and the solution, consider a brief transition using approved music.
Keep the guest’s explanation intact.
Notice that the editor cues sit beside the relevant block, while the spoken and host-only lines retain their original jobs. An editor can see your intention without mistaking it for dialogue. You can still depart from the question order during recording; the editor will use the finished recording to locate the actual moment.
Replace planned locations with recording references later
A script is a map of what you intended to cover. After recording, an editor also needs to find what actually happened. That is when you can add accurate time references and identify the speaker’s real words.
Read How to Write Podcast Edit Notes from East Coast Studio. Its four locating details—an in point, an out point, spoken words or an event, and the speaker—are especially useful when you want a specific passage removed. The source also notes that a cut which seems sensible on paper may not sound natural; give the editor enough information to find the passage while allowing a small adjustment for a clean-sounding edit.
How to Write Podcast Edit Notes - East Coast Studio
Read East Coast Studio’s guidance to see how a post-recording note identifies a precise edit, rather than merely describing a planned transition.
In “How Much Detail Is Required,” begin where the author introduces the information an editor needs for a cut. Read the locating guidance through the explanation of why naming the speaker helps. Then, in “Format For Edit Notes,” start with the first example’s description of its cut boundary and read the labeled examples through the explanation of what remains in the edit. Focus on how time references and spoken words check each other.
Do not turn your earlier “20–25 minute interview target” into an edit timecode. That was a pacing estimate. A recording timecode refers to a particular media file after it exists. If you record more than one take, identify the take as well; if separate cameras or audio recorders have different clocks, say which file your timecode refers to.
You can add a clearly marked post-recording note beneath the relevant block. The times below are illustrative only, not times to place in your script:
BLOCK 2 — WHAT CHANGED
ESSENTIAL QUESTION: How did you decide what to change first?
AUDIO/VIDEO EDIT — AFTER RECORDING
Source: main interview recording, take 1.
Proposed removal: 00:12:14 to 00:12:31, guest’s brief tangent.
Keep before the cut: guest, “We tested three versions.”
Keep after the cut: guest, “The clearest version was the simplest.”
Check that the joined answer still sounds natural and remains accurate.
This note is different from AUDIO EDIT — PLAN in three ways. It identifies a real source, gives times from that source, and quotes words you have checked against the recording. The “keep before” and “keep after” lines also tell the editor what the finished answer must preserve. If removing the tangent would change the guest’s meaning, the correct decision is not to force the cut.
When you mean to alter only the audio or only the video, do not label it “AUDIO/VIDEO.” Say exactly which track or picture should change. For example, covering a visible pause with an approved graphic is not the same request as deleting the pause from the conversation. Clear labels prevent a small visual decision from becoming an unintended change to what listeners hear.
Hand off decisions, not guesses
Before sharing the guide, scan it once from the editor’s point of view. Can the editor distinguish a SAY line from every private instruction? Is each planned cue attached to a recognizable part of the episode? Does a note that requests an asset identify whether that asset is available and approved? Are any post-recording times tied to a named recording rather than an estimated running time?
You do not need an edit instruction for every question. Add notes where you have a meaningful intention: an opening treatment, an important visual explanation, a transition, or a passage you know needs review. Too many speculative cues make it harder to see the decisions that matter. Where you are uncertain, use language such as “consider,” “if available,” or “review after recording” rather than presenting a possibility as a final order.
A practical handoff is to keep the scan-friendly host guide as the shared base, then update its editor-facing notes after you listen to the recording. Your experience coordinating work across roles is relevant here: the useful handoff is not the one with the most instructions, but the one that makes the intended result, available material, and unresolved decisions clear.
Key takeaways
Delivery reminders, spoken lines, and edit instructions are different things. Keep SAY and HOST ONLY distinct from clearly labeled AUDIO EDIT — PLAN and VIDEO EDIT — PLAN notes. Place each planned cue beside the relevant script block, specify the intended change, and flag conditions or missing assets. After recording, replace guesses with source-specific times, the speaker’s words, and a clear account of what should remain.
This completes the module: you now have a guide you can scan during an interview and annotate for an editor without confusing planned production choices with the conversation itself.