Sound Reports and Track Names: Small Habits That Help Post

A report is a guide to the material

After a shoot, editorial may receive dozens or hundreds of audio files. Without understandable identification, someone first has to establish who is speaking, which microphone belongs to each track and whether a problem was present in the original recording. A sound report should simplify that orientation. It does not need to be long; it needs to be specific, consistent and clearly connected to the delivered files.

Agree the format before filming. Some teams expect an export from the recorder, while others maintain their own production log. Project, day, scene and take identification form a useful foundation where that system is used. On a documentary, interview name, location or time block may be more meaningful. The scheme should match how the editor will search for the material.

Let track names explain the content

A label such as “boom,” or a clear speaker identifier, is more useful than an unexplained number. Avoid trying to fit an entire technical history into a short name field. Put detail in a note or accompanying document. On sensitive projects, follow the agreed participant naming convention and avoid embedding unnecessary personal information in metadata that will move between teams.

When a microphone moves to another participant, update the identification or clearly record the change. An outdated name can be worse than no name because it appears authoritative. After a substantial configuration change, check both the track map and signal routing. Distinguish the working mix from isolated microphone tracks so that the purpose of each is clear during editorial and later sound work.

Record observations, not vague judgements

A note saying “bad sound” offers little help. Describe the interference, affected speaker and approximate point in the recording. For example, identify a wireless dropout during a particular line or traffic noise in the final answer. If another microphone or take provides a clean alternative, mention it without promising that it will automatically fit the selected picture.

The director’s preferred performance and the technically cleanest recording may be different takes. Keep those observations separate and do not attribute a creative decision to someone who did not make it. A “preferred” label should have a clear origin. Use one agreed method for time references so that the note can be matched to the right point without additional interpretation or calculation.

Close the day with a check

Before handover, compare the report with the actual files. Look for missing entries, unintended duplicate names and unexplained exceptions. Identify room tone, atmospheres and additional dialogue so their connection to the scene is evident. If the report changes after delivery, provide a clearly identified new version and explain the meaningful correction.

When planning production sound, request an editorial contact and an example of the expected handover. A simple agreement about names and notes can prevent repeated questions during post-production. A report cannot replace a good recording, but it preserves context and helps the next team work with the material confidently. Keep the language factual and concise, and give exceptional events enough detail to be useful without burying ordinary takes under unnecessary commentary.

When several recordists contribute, use consistent abbreviations or include a short key. A label obvious to one person can be ambiguous to the next team. Avoid unnecessary internal nicknames and keep corrections traceable. A useful report should still make sense weeks later, when nobody remembers the exact scene or why an unusual name was chosen.