A productive film or TV spotting session turns broad creative reactions into decisions a composer, director, picture editor, and music editor can act on. This checklist explains what to record, how to translate the conversation into a production-ready cue list, and which details to review as picture, schedule, or creative priorities change.
Overview
A spotting session is the structured conversation in which the creative and post-production team decides where music belongs, what each cue should do, and how the score will support the cut. It is not simply a screening followed by general comments. The useful outcome is a shared set of notes that can guide writing, editing, recording, approvals, and delivery.
The composer may lead the musical discussion, but the final notes should reflect the responsibilities of the wider team. A director can define dramatic intent; a picture editor can explain editorial pressure points; a music editor can translate decisions into timing, versions, and deliverables; and a producer or post supervisor can flag schedule, budget, or approval constraints. On smaller productions, one person may cover several roles, but the questions remain the same.
Keep three records separate but connected:
- Spotting notes: the reasoning and creative discussion behind each decision.
- Cue list: the structured production record for every planned music entry, exit, version, and status.
- Open-decision log: unresolved questions that could affect writing, editing, recording, or delivery.
This separation prevents a common problem: an expressive comment such as “the scene should feel less resolved” gets copied into a spreadsheet without a clear action. The note should instead become something testable, such as “end the cue before the character answers” or “avoid a full cadence until the following scene.”
What to track
1. Confirm the version and timecode standard
Begin by recording the picture version, episode or reel identifier, frame rate, start timecode, and date of the session. Note whether the team is using drop-frame or non-drop-frame timecode where relevant, and make sure every participant is referring to the same export. A cue that appears at 00:12:14:08 in one version may move or disappear after an edit, so version control belongs at the top of every spotting document.
Use consistent terminology for the main timing points:
- Start: the frame or editorial moment where music begins.
- End: the frame where the cue stops, fades, or hands off to another cue.
- Duration: the planned length between start and end.
- Hit point: a visual, dialogue, action, or emotional event the music may emphasize.
- Changeover: a point where the musical idea, texture, tempo, or instrumentation should shift.
2. Describe the dramatic function
Record what the music is doing rather than only what it sounds like. Possible functions include establishing a character perspective, creating tension, connecting two locations, clarifying a time transition, making a reveal feel inevitable, providing momentum, or allowing a scene to breathe. Also record what the music should not do. “Do not sentimentalize the reaction” can be as important as “support the character’s isolation.”
3. Mark edit flexibility
Not every cue has the same degree of timing freedom. Identify whether the start and end are locked, preferred, or flexible. Mark essential hits separately from optional accents. If a scene may still be trimmed, note whether the composer should write a modular ending, an extendable texture, a loopable passage, or alternate material that can survive a picture change.
4. Capture musical direction without over-prescribing
Write down references, palette ideas, instrumentation, register, density, tempo, vocal treatment, and silence requirements. Distinguish a firm creative decision from an exploratory suggestion. “Low strings and processed percussion are approved” is different from “consider a low-string texture.” This distinction helps the composer know what to write now and what to test before the next review.
5. Record schedule and ownership
Every cue should have an owner for the next action and a date or milestone for review. Track the expected first mockup, director review, revision, final mix, stems, alternate versions, and delivery. Confirm whether the date refers to a rough draft, an approved cue, a recording-ready score, or final deliverables. Ambiguous deadlines create avoidable conflicts later.
A practical cue-list template
Use the following fields as a starting point. Add columns only when they support a real production decision.
| Field | What to record | Example entry |
|---|---|---|
| Cue ID and scene | Unique identifier, episode, reel, or scene reference | 1M03 — Kitchen reveal |
| Picture version | Export or cut version used for spotting | Episode 2 v07 |
| Start / end timecode | Exact entry and exit points, including frame notation where used | 01:04:12:10 / 01:06:03:18 |
| Duration | Planned cue length | 01:51:08 |
| Dramatic function | The narrative or emotional job of the cue | Hold uncertainty without revealing the answer |
| Hit points | Events requiring emphasis, transition, or restraint | Door opens; reaction begins |
| Edit flexibility | Locked, preferred, flexible, extendable, or replaceable | Start flexible; reaction hit preferred |
| Instrumentation | Palette, featured instruments, register, or texture | Muted low strings; sparse piano harmonics |
| Dialogue and sound notes | Lines, effects, or mix space that affect the score | Leave room for final line; avoid dense midrange |
| Versions needed | Stems, alternates, clean ending, cutdown, or source music | Full mix, strings stem, 30-second alternate |
| Delivery milestone | Draft, review, approval, recording, or final delivery date | First mockup before picture review |
| Open decisions | Questions that still require approval | Confirm whether cue continues under credits |
| Owner and status | Person responsible and current state | Composer — writing; awaiting edit confirmation |
6. Keep a separate open-decision log
Do not bury unresolved matters in a comments column. Give each question an owner, a consequence, and a decision date. Useful categories include picture changes, rights or source-music questions, instrumentation approvals, music editor requests, recording needs, mix priorities, and delivery formats. If a decision is not required before writing begins, say so; this prevents the team from treating every unknown as an emergency.
For technical preparation, a maintained project template can reduce setup errors. The DAW template maintenance checklist is useful when turning approved spotting notes into a repeatable writing session. If the score will be mocked before recording, also review the orchestral mockup troubleshooting guide before interpreting playback problems as composition problems.
Cadence and checkpoints
A spotting session should be treated as the first checkpoint in a cycle, not the final word on the score. Use a simple cadence that matches the production schedule:
- Before spotting: collect the correct picture, script, temp-track references, schedule, previous notes, and known delivery requirements. Identify scenes that are still editorially unstable.
- During spotting: resolve cue boundaries and dramatic purpose first. Then discuss palette, references, flexibility, versions, and dates. Read back decisions before moving to the next scene.
- Within one working day: circulate the cue list and open-decision log. Ask participants to correct factual errors, not reopen every creative decision without a specific reason.
- Before the first review: check that every cue has a time range, function, owner, and next milestone. Flag cues whose timing depends on an unconfirmed picture change.
- At each picture update: compare the new cut against the spotted version. Recheck starts, ends, hit points, duration, dialogue clearance, and cue relationships before revising music.
- Before final delivery: confirm approved cue names, final timecodes, stems or alternates, credits information, and any music-editor or post-supervisor requirements.
For episodic work, a weekly or episode-based review may be appropriate; for a short film, the checkpoints may occur around each meaningful picture export. The principle is consistent: review when a recurring variable changes, not merely because a calendar reminder appears.
How to interpret changes
When a cue changes, first identify the type of change. A timing change may require a new ending, revised hit points, or a different musical form. A dramatic change may invalidate the original function even if the timecode remains similar. A mix or dialogue change may call for thinner orchestration, different register, or stems that can be balanced independently. A delivery change may affect file naming, versions, or approval order without changing the composition itself.
Use status labels that describe action: spotted, writing, mockup sent, notes received, revision in progress, approved, recording-ready, and delivered. Avoid a vague label such as “in progress” when the team needs to know whether the next step belongs to the composer, editor, director, or producer.
Do not automatically preserve a cue because it was discussed in the original session. If the scene’s function has changed, revisit the musical rationale. Conversely, do not rewrite a cue solely because the timecode moved by a few frames if its dramatic purpose, edit flexibility, and ending still work. The cue list should help the team distinguish meaningful change from harmless movement.
For games or interactive projects, the same discipline applies, but a linear start and end may be replaced by states, transitions, intensity layers, and implementation conditions. A separate workflow may be needed for middleware and adaptive music; the FMOD and Wwise workflow guide provides a useful comparison point when a film-style cue list is no longer sufficient.
When to revisit
Revisit the spotting record whenever a new picture version changes a cue boundary, character motivation, dialogue pattern, scene order, or delivery requirement. Also reopen it when the director’s reference changes, a temp track is removed, a recording plan is revised, or a previously flexible cue becomes locked. A short update note should state what changed, why it changed, and which downstream files or people are affected.
For longer productions, review the template and terminology quarterly or at the start of a new project phase. Check that timecode labels remain clear, status options still match the team’s workflow, and delivery fields reflect the current post-production process. Scheduling and collaboration platforms evolve, so confirm that shared links, review permissions, version naming, and approval records still work as expected rather than assuming an old process remains reliable.
Before the next spotting session, duplicate the last approved template, remove obsolete cues, and preserve the previous version as an archive. Then prepare a short agenda:
- Which scenes are new or materially changed?
- Which cues are still unresolved?
- Which dates or deliverables have moved?
- Which creative decisions need a clear owner?
- Which cues can be written without waiting for another department?
Finish by sending one clean, dated cue list and one open-decision log. That small habit gives composers, directors, and music editors a shared source of truth—and makes the next spotting session faster, more focused, and easier to act on.
For broader context, compare these notes with the music spotting session checklist and the cue sheet basics guide. They can help separate creative spotting decisions from the later documentation needed for credits and reporting.