Turn taste into a brief
A revision round works best when the first brief names the job of the music, not just a genre. Include duration, edit points, narrative function, energy curve, reference traits to borrow or avoid, vocal or lyric constraints, intended platforms and required delivery files. ‘Make it more cinematic’ is a reaction; ‘reduce the drum density under the voice-over from 0:12 to 0:28’ is an actionable change.
Separate creative preferences from facts the producer needs to preserve. A campaign's brand pronunciation, a timed picture lock or a required legal tag should not be buried in a mood-board comment. Keep one source of truth for the brief, with date and version, so a later listener can tell whether a change answers the original request or introduces a new direction.
Use a change log, not a comment pile
For each requested change, record the timecode or section, request, reason, priority, requester, response and status. Group overlapping feedback before sending it to the maker; two stakeholders asking for opposite emotional directions need a decision, not two invisible revisions. Label examples as ‘reference only’ unless the client has supplied material cleared for copying or incorporation.
The change log is a creative coordination tool, not a contract or legal advice. It gives the group a way to see scope movement. If the client asks for a new cut length, an alternate campaign message and different instrumentation after approving the direction, name those as new decisions rather than implying they were defects in the prior version.
Define an acceptance listen
Before delivery, agree on an acceptance checklist: correct duration and edit points, intelligible dialogue space where required, approved credits, agreed file formats, complete filenames and audible conformance to the brief. Use a controlled listening setup where practical and identify whether feedback is about the mix, arrangement, performance or the underlying brief. A single ‘sounds wrong’ message cannot be efficiently revised.
If editable delivery is required, say what that means: consolidated stems, aligned start point, sample rate and bit depth, tempo map, MIDI, session file or just a stereo master. The EBU's BWF documentation shows why an audio file can carry useful metadata, but it does not guarantee that every recipient can open every session or embedded field. Deliver a plain manifest too.
Close the round with a handoff
Send the approved mix and any agreed editable materials with a version number. Preserve the brief, change log, final acceptance note and a checksum or file list. This is not bureaucratic excess; it prevents a later social cut or localisation request from starting with an unidentified attachment. It also makes it easier to state what was delivered without overstating rights or authorship.
For a small project, this can be one shared page and one tidy delivery folder. The goal is not paperwork for its own sake. It is to give the client a reliable way to hear and approve the decision they asked for.
Continue in Rights & release, or A stock-music licence excludes work you do not own.
Evidence & further reading
Go to the source.
Primary references checked 19 September 2026. Practical exercises are editorial guidance, not reported product tests.
- BWF - A format for audio data files in broadcasting ↗
Primary specification explains BWF as an audio-file format with metadata support.
European Broadcasting Union · Source date 2011-05-20 · Accessed 2026-09-19 - EBU Tech 3364 Audio Definition Model ↗
Primary standard distinguishes audio-description metadata from the audio-carrying format.
European Broadcasting Union · January 2014 (document cover) · Accessed 2026-09-19