A cue can be right for the film and still remain stuck for days. The problem is not always composition. It is often a question nobody settled at kickoff: who actually signs off the score?
On many films, the director carries the creative point of view. The producer protects the film, schedule and commitments. Editorial knows the cut in detail. A network, agency, client, music supervisor or distributor may also have approval rights. All of them can offer useful information. They should not all send separate briefs to the composer.
I want an approval chain before the first mockup. It should identify who contributes, who consolidates and who decides.
Separate consultation from sign-off
The final decision-maker does not need to be the only listener. They are the person who resolves the conflict when two valid notes point in different directions.
Editorial may protect pace. The director may protect ambiguity. A producer may worry that the cue feels too dark for the intended audience. Those concerns can coexist, but the composer cannot turn three unresolved positions into one reliable revision.
I ask for one primary contact. That person gathers the notes, relates them to the film’s intention and sends one consolidated direction. Depending on the production, this may be the director, producer, music editor or another post lead. The job title matters less than actual authority.
External approvals must also be visible. If a client or network can reopen the direction, an internal yes is a milestone, not final sign-off.
Define what each review is approving
A direction sketch, synced mockup, orchestration pass and final master are different objects. They should not face the same test.
Early reviews should settle dramatic function, palette and how assertive the score should be. A simple mockup can answer those questions without pretending to be a finished recording.
The next stage can approve cue architecture: in and out points, growth, silence, hit points and relationship to picture. Writing detail, production and orchestration follow. Final mixes, deliverables and stems come after those choices. They cannot solve an unresolved brief.
This sequence prevents a common category error. Someone may reject a direction because the temporary mockup sounds small, even though the review was meant to assess the theme. Conversely, polished production can make an unclear dramatic idea feel approved.
Give notes against the same cut
An actionable note identifies the moment, intended effect and perceived gap. “At 01:12:08, the tension drops before the door opens” gives me a problem to solve. “Make it more cinematic” could mean register, motion, density, scale or simply level.
Everyone should review against the same picture export with visible burn-in timecode. The filename, frame rate and cut date need to be unambiguous. Otherwise a music note may actually be a response to an editorial change.
I also separate preference from correction. “I prefer version two” is a choice. “The dialogue becomes harder to understand” describes a mix consequence. Both may matter, but they lead to different work.
Consolidate before the composer receives the notes
A comment list is not a decision. If the director asks for less score while the producer asks for more energy, forwarding both sentences transfers the production’s unresolved choice to the composer.
I prefer one note document or one message per review round. Conflicting requests should be discussed first. If a disagreement remains open, name it and identify who will choose after the next test.
Consolidation also establishes priority. Some notes protect story clarity or legal deliverables. Others are optional preferences. Without a hierarchy, a minor adjustment can destabilize an approved scene.
I would not decide by anonymous vote. Film music is not a contest where the least objectionable option automatically wins. Sign-off needs to remain connected to the film’s point of view.
Reduce versions by testing one hypothesis
Five alternatives can look like progress while postponing the decision. As the version count grows, the room often compares surface details instead of explaining what the scene needs.
I would rather build one revision around a clear hypothesis: keep the restraint of version three, but move the lift until after the reveal. The result is readable. Even if it fails, the production learns something specific.
Every version needs a stable name. I do not silently replace an approved link with a new file under the same filename. I state what changed and what deliberately stayed the same. Version control feels bureaucratic only until three stakeholders comment on three different exports called final.
Put feedback deadlines into the post schedule
Score approval belongs in the post-production calendar. I work back from the dub: final masters and stems, production sign-off, cue lock, first mockups, spotting and picture turnover.
Each round needs a delivery date and a feedback date. If the production must consult a network, agency, financier or client, that time must be included. A week of waiting cannot quietly become a one-day writing deadline at the end.
Silence also needs a rule. I do not assume no response means approval unless the production has explicitly adopted that process. Important stages are safer with a recorded yes.
Know what can reopen an approved cue
An approved cue may need to change when picture changes, dialogue is replaced or the dub exposes a conflict. That is not failed approval. It is a new constraint.
Repeatedly reopening the musical direction because of late preference is different. I separate three categories: a correction to the approved version, a conform to new picture, or a change of brief.
That distinction affects schedule, scope and trust. A short picture change can require structural rewriting. A level correction may require no recomposition at all. Naming the category prevents every request from being treated as either trivial or catastrophic.
Protect the handoff to the dub
Before delivery, I confirm full mixes, stems, required alternates, file format and timeline start. I also ask who can still request a change on the dub stage.
Stems give the re-recording mixer useful flexibility around dialogue and effects. They should not make the mixer the accidental new music director. Deliverables cannot reconstruct an intention the production never approved.
A lightweight approval log is often enough. For each cue, record picture version, music version, status, decision-maker, consolidated notes and approval date. That record gives post a shared memory when the cut or team changes.
A short chain creates better decisions
The goal is not less conversation. It is usable conversation. A strong idea may come from editorial, sound, production or a client. The composer still needs one direction rather than a meeting transcript dropped into an inbox.
Before scoring begins, I want five answers: who contributes, who consolidates, who signs off, what each stage approves and when feedback is due.
When those roles are clear, notes become more precise. Unnecessary revisions can fall. The schedule has room to breathe. The score can be judged by what it does for the film, not by how well it survives an invisible approval maze.