01
Identify the source recordings and their roles
List the files supplied and explain which recording belongs to which part of the episode. Distinguish the original interview, any replacement lines and additional material such as an introduction. Preserve a stable reference to each source rather than relying on a filename like final audio. In this fictional project, a later recording might replace only one answer, not the whole interview. Making that relationship explicit helps the editor understand what to use. Confirm that the material may be shared for the agreed work through the appropriate project process.
02
Attach notes to identifiable moments
Use timestamps or another clear reference when commenting on a particular moment, and state which file the reference concerns. Separate an agreed edit from a suggestion and from a question for the producer. An example note might identify an answer that needs clarification without asking the editor to infer what the speaker intended. Keep the episode outline nearby so local changes can be considered in context. The aim is to make the editorial request understandable while preserving the distinction between what was recorded and what the team proposes to do with it.
03
Specify the next deliverable and review step
Describe what the editor should return at this stage and who will review it. That might be a first assembly with unresolved questions marked, rather than a finished release. Identify any required project settings through the agreed production brief instead of expecting the editor to guess them. In the interview example, a producer may need to resolve one section before final polishing. Record that dependency and keep subsequent notes tied to the delivered version. A clear handover gives the next person a useful starting point without pretending that every editorial decision has already been settled.