A second editor needs more than audio files. They need to know which version is current, which decisions are approved and what kind of work comes next. A short handoff note can prevent several rounds of unnecessary changes.
Describe the current state
Name the project version and the latest review export. List the important remaining tasks, such as balancing one guest, checking an edit near the ending or preparing the final delivery file. Separate approved structure from open questions.
Include a small source map when file names are not obvious. Explain restarted recordings, replacement answers and known missing sections. Use timestamps where possible, since a clear location is more useful than a paragraph about the problem.
Tell the editor whether they may change the episode structure or should focus only on technical cleanup. Without that boundary, two good editors can make different changes to the same material.
Verify the package before sending
Open the copied project from the handoff folder. Check for missing-file warnings and confirm that referenced assets are included or available through an agreed path. Never place a secret key or personal password in a handoff readme.
Ask the recipient to confirm that the project opens and that the listed tasks are understood. Keep your original copy until that confirmation arrives.
When the handoff returns, save the new work under a distinct version rather than silently replacing the only copy. Compare the review notes with the actual changes. The aim is a clear chain of decisions, not a rigid editing style that prevents the next person from improving the episode.