Music Spotting Session Checklist for Film, TV, and Game Composers

Overview

A spotting session is a focused conversation about where music should appear, what each cue needs to accomplish, and how the score should interact with dialogue, sound design, editing, gameplay, or the wider story. It may happen in a screening room, over a video call, or inside a shared production workflow. The format varies, but the goal is consistent: replace broad reactions such as “this scene needs more energy” with decisions a composer can act on.

For a film or television project, the team may review the cut from beginning to end and mark entrances, exits, transitions, musical rests, and moments that require a particular dramatic function. A streaming project may follow a similar process while allowing for changing episode cuts or delivery stages. A game spotting session often focuses less on a fixed timeline and more on states, triggers, exploration layers, transitions, intensity levels, and the conditions under which music changes.

Preparation matters because spotting time is limited. Before the meeting, watch or play through the material, note questions, confirm which version you are reviewing, and create a system for recording decisions. Afterward, your notes should be clear enough to guide cue planning, mockups, collaboration, revisions, and eventual delivery. For related documentation, see Cue Sheet Basics for Composers.

What to track

1. The approved picture, build, or reference

Record the file name, version, date, frame rate if supplied, and timecode convention. For games, record the build number or design document version. Never assume that two files with similar names contain the same edit. If the reference changes during or after the meeting, mark which decisions need to be checked again.

2. Cue boundaries and purpose

For each proposed cue, note the start point, end point, scene or level reference, and dramatic purpose. Useful purpose statements are specific: “introduce the character’s private theme,” “hold tension without revealing the threat,” “create momentum during the escape,” or “leave space for the final line.” If a cue is intended to bridge two scenes, document what it connects and whether the transition should feel continuous or deliberately interrupted.

3. Creative direction

Capture references to tone, instrumentation, texture, tempo, density, harmony, performance style, and emotional point of view. Also record what the team does not want. “No prominent melody under dialogue” is more actionable than a general request for subtlety. If references are mentioned, write down the exact track, scene, or quality being referenced and distinguish the desired function from the surface sound.

4. Dialogue, effects, and space

Mark scenes where music must remain sparse, where sound effects carry important information, and where dialogue needs clear priority. Ask whether music should stop before a line, thin out under a reveal, or continue through an edit. These decisions affect arrangement, orchestration, mixing, and the amount of room left for later sound work.

5. Timing flexibility

For linear media, identify fixed hit points, flexible transitions, editorially sensitive cuts, and moments that may move. A composer can plan differently for a cue that must land on a precise action than for one that simply supports a scene’s overall arc. For games, track whether a musical event is looped, layered, stinger-based, transition-based, or triggered by player action. Note the expected behavior when a player pauses, fails, repeats, skips, or changes state.

6. Ownership, questions, and next actions

Every unresolved item should have an owner and a follow-up point. Separate confirmed decisions from suggestions and open questions. A simple spotting worksheet can use these columns:

• Reference and timecode or gameplay state
• Cue name and estimated duration
• Story or gameplay function
• Musical direction and exclusions
• Dialogue or sound-design considerations
• Decision status: confirmed, provisional, or open
• Owner, deadline, and next review

Keep a separate list for business and delivery questions, including file formats, stems, naming conventions, revisions, approvals, and who will supply updated picture or gameplay references. These details belong in the workflow even when they are not creative decisions.

Cadence and checkpoints

Use the spotting process as a series of checkpoints rather than a single meeting. A practical cadence looks like this:

1. Before spotting: Confirm the reference, watch or play through it once without stopping, then review it again while marking likely cue areas. Prepare concise questions about story intent, timing, sound priorities, and approvals.
2. During spotting: Log decisions in real time. Read back important timecodes and summarize ambiguous requests before moving on. If the team disagrees, record the alternatives instead of silently choosing one.
3. Within one working day: Send a clean recap with the cue list, open questions, changed assumptions, and next actions. A written recap gives collaborators a shared reference and makes later revisions easier to trace.
4. At the first mockup review: Compare the result with the spotting intention, not only with isolated musical taste. Ask whether the cue enters and exits correctly, supports the scene, leaves room for other elements, and behaves as expected in context.
5. At each major picture or build change: Recheck timecodes, cue boundaries, triggers, transitions, and the emotional logic of the sequence. Do not carry old notes forward without labeling them as verified.
6. Before final delivery: Confirm that the approved cue list matches the delivered assets, including alternate versions, stems, loops, transitions, and naming conventions where applicable.

Film and television workflows usually emphasize timecode, picture revisions, and editorial changes. Games require an additional checkpoint for implementation behavior: a cue can work musically in isolation but fail when a player enters a state earlier, stays longer, or moves between states unexpectedly. The same worksheet can serve both formats if it includes a clear field for the project’s timing model.

How to interpret changes

Not every change requires a new musical idea. First classify the change. A timing change may require editing, re-orchestration, or a new transition. A story change may alter the cue’s purpose and require a deeper rewrite. A sound-priority change may call for thinner instrumentation or a different register. An implementation change in a game may require new layers, triggers, fallback behavior, or loop lengths.

Compare the revised material with three questions:

• Is the original dramatic function still valid?
• Are the original entry, exit, and hit points still relevant?
• Has another production element taken priority?

If the answer to the first question is no, revise the cue brief before revising the notes. If the answer to the second is no, update the timing plan and identify any downstream edits. If the answer to the third is yes, document the new priority so the composer, editor, sound team, and developer are working from the same assumption.

A useful change log includes the date, reference version, affected cue, old decision, new decision, reason for the change, and resulting action. This prevents repeated debates and helps identify patterns, such as frequent late picture changes or recurring uncertainty about game-state transitions. Treat those patterns as workflow signals rather than personal failures; they may indicate that the team needs earlier references, clearer approval points, or more flexible cue designs.

When to revisit

Revisit this checklist before every new spotting session and after any meaningful change to the reference. A monthly or quarterly workflow review is also useful for composers managing several projects: inspect unresolved questions, compare planned and actual revision cycles, and update your worksheet to reflect the tools and delivery conventions you currently use.

Update your process when your DAW, video-playback system, notation software, sample libraries, collaboration platform, or game-audio implementation tools change. Confirm that timecode displays, export settings, frame-rate handling, video references, and file naming remain reliable. Tool behavior can change after an update, so test a small workflow before relying on it for a full project.

Before your next meeting, take these practical steps:

1. Download or request the latest approved reference and label it clearly.
2. Play through the material once without stopping and once while taking notes.
3. Build a cue list with boundaries, purpose, sound priorities, and open questions.
4. Separate confirmed decisions from preferences that still need approval.
5. Prepare a short list of timing, creative, technical, and delivery questions.
6. After spotting, send a recap and schedule the next checkpoint around the first meaningful review.

For broader workflow support, the film, TV, and game scoring portfolio guide can help you present finished work, while the collaboration agreement checklist can help clarify responsibilities once the scoring plan becomes a shared project. A well-maintained spotting document will not eliminate change, but it will make change visible, discussable, and easier to turn into music.