Three recordings called final, final again, and final good can be surprisingly difficult to sort the next day. The strongest performance may sit in a file with an unhelpful name, while a technically clean take contains a wording error. A small labelling system separates the identity of a take from your opinion of it, allowing both to remain useful as the edit develops.
Give each take a stable identity
Choose a short project name, a section identifier, and an increasing take number. For example, a recording named garden-intro-t03 can remain identifiable even if it is later rejected. Keep the names short enough to read in the editor and consistent enough to sort without guessing.
For longer sessions, include a date or session code so take numbers do not collide. Use a filename style supported by the computers involved, avoiding characters that another system may reject. Preserve the recorder’s original files in a separate location if you rename working copies.
Note what actually happened
After a take, write a brief observation while it is fresh: clear delivery, incorrect product name, traffic during final sentence, or good second paragraph. These notes are more useful than a star alone. A technically imperfect take may still contain the most natural explanation, and a favourite may need a small replacement phrase.
For a long recording with several attempts, add time references to the relevant passages. Say a short spoken slate before the performance where appropriate, then leave a pause. Do not talk over the ending of a useful take just to label it; preserve its clean tail for the editor.
Keep selection separate from storage
Use a selection log or editor markers to identify preferred passages rather than repeatedly renaming files to include best. A preference can change when the surrounding edit changes. Keep rejected takes available until the project’s retention decision is made, especially if they contain unique wording or a repairable section.
Hand over the meaning of the labels
Put a brief explanation of the naming system beside the recordings. Include which script or outline was used and any changes made during the session. Another editor should be able to match take identifiers, notes, and files without asking which good version you meant. Before leaving the session, open a few files and confirm that the log points to recordings that actually exist.
The system should be quick enough to use while recording. If entering notes becomes a distraction, simplify them to the details that influence selection. Stable identities and specific observations are sufficient for many small projects, and they remain useful long after your memory of the session has faded.
