A project opens with Audio 1, Audio 2 and Audio 2 copy. You may remember what they mean today. Someone else, or you next month, will need more help.
Name the role first
Use clear labels such as host, guest or room sound when they accurately describe the material. Add a source or take detail only where it helps distinguish similar items.
Keep names short enough to read in the available space. A long sentence that disappears beyond the track header is better placed in a project note.
Separate identity from status
A track’s name should not become the only record of whether it has been checked. Use the project’s agreed notes for unresolved issues and review state. A label reading final can become misleading after the next edit.
Colour can help you navigate, but do not make it the sole carrier of meaning. Written names remain useful when colours are hard to distinguish or the project is viewed differently.
Try a cold handover
Close the session, return later and locate one source and one edited section using the labels alone. Rename anything that still requires you to remember the editing history.
Combine the system with clear take cues. Good names do not make editing decisions for you; they make it easier to know which material you are deciding about.