Composer-to-Tech Handoff: Specs and Checklists for TV Scoring Projects

Composer-to-Tech Handoff: Fix the friction that wastes days in post

Hook: You finished a cue at 2 a.m., exported dozens of audio files, and uploaded them — then post asks for everything again in a different format. If that sounds familiar, this guide gives you a single, battle-tested technical handoff template and checklist (sample-filled with Hans Zimmer–style production demands) so composers and post teams align on stems, deliverables, metadata, and timecode the first time.

Why a rigorous handoff matters in 2026

Streaming platforms and broadcasters continue to tighten and diversify delivery specs. In late 2025 and into 2026, the industry accelerated adoption of object-based mixes (Dolby Atmos), widespread use of 32-bit float stems for archival and dynamic processing, and automated metadata ingestion in post workflows. That means a sloppy handoff now creates more rework than ever — teams must provide clear, machine- and human-readable specs to be accepted by modern content pipelines.

What this article gives you

• A copy-pasteable technical handoff document template (filled with a Hans Zimmer–style sample)
• Concrete deliverable specs and file-naming standards
• Stem and mix recommendations for stereo, 5.1, and Atmos projects
• Metadata and timecode best practices for sync and automation
• Preflight and QA checklists you can print or attach to deliveries

Top-level rules to agree on before composing

1. Agree sample rate and bit depth up front. For TV: 48 kHz / 24-bit is the baseline. For hybrid scoring sessions, deliver archived 96 kHz / 24-bit or 48 kHz / 32-bit float stems if requested.
2. Decide loudness strategy early. Deliver: (A) pre-loudness stems/mix (no processing for platform loudness) and (B) final loudness-compliant masters. Specify target LUFS for each platform.
3. Define stem granularity. Are stems by instrument family, by bus, or both? Large hybrid scores (Hans Zimmer style) often require 40–120 stems per episode.
4. Lock timecode format. Agree SMPTE frame rate (23.976/24/25/29.97/30) and embed/attach ISRC/episode identifiers.
5. Use a single naming convention and manifest file. Provide a CSV or JSON manifest that lists every file and its metadata.

Delivery specs — current best practices (2026)

Below are practical, platform-agnostic deliverables. Always confirm with your producer/platform for overrides.

Core audio deliverables (per episode)

• Stereo premix: WAV, 48 kHz / 24-bit, interleaved stereo (2ch), normalized per platform loudness spec. Include both pre-loudness (as produced) and final -14 LUFS/-1 dBTP (example for streaming) unless a different target is specified.
• 5.1 surround premix: WAV, 48 kHz / 24-bit, interleaved 6ch or 6 mono files following BWF channel ordering. Provide downmix metadata.
• Dolby Atmos ADM BWF: Object-based ADM file for Atmos versions. If not producing Atmos, clearly state that and provide stems ready for Atmos renderer.
• Music-only stems: Each stem WAV, 48 kHz / 24-bit (or 32-bit float archive), 100–120% of track length to include handles. Stems grouped by family: Strings, Brass, Woodwinds, Choir, Percussion, Bass, Synths, FX, Hybrid Beds.
• M&E (Music & Effects) track: Where required, provide an M&E mix (music + effects, no dialogue), 48 kHz / 24-bit.
• DAW session(s): Save and deliver the DAW session only on request. Include plugin list, versions, and frozen stems if plugins are proprietary.
• Project archive: Full sample/patch lists, orchestral cue sheets, and a zip with exported audio and manifest files.

File formats and bit-depth strategy

• Primary delivery: Broadcast-safe WAV (RIFF/BWF), 48 kHz / 24-bit integer.
• Archival/dynamic stems: 32-bit float WAV or 24-bit at 96 kHz if audio contains ultra-high frequency artifacts used for sound design. State purpose in manifest.
• Metadata containers: Include BWF chunk metadata plus a machine-readable manifest (CSV or JSON) with cue name, start TC, duration, file path, stem type, and loudness metadata.

File naming conventions — use one consistent pattern

Below is a robust pattern that survives automation and manual search. Replace tokens with show-specific values.

Canonical pattern

SHOW_EP##_SXXEYY_CUE_##_STEM_##_DESCRIPTION_v##.wav

• SHOW: short show code (4–8 chars)
• EP##: episode number with leading zeros
• SXXEYY: optional season/episode token
• CUE_##: cue number or timecode range
• STEM_##: stem number with family code
• DESCRIPTION: human-readable family (STR, BRASS, SYNTH, PERC)
• v##: version counter

Example (Hans Zimmer–style filled)

Imagine a Zimmer-like hybrid action cue with orchestra, choir, synth beds, and processed percussion.

• HPW_EP03_S01E03_CUE_045_STEM_01_STRINGS_v02.wav
• HPW_EP03_S01E03_CUE_045_STEM_02_BRASS_v02.wav
• HPW_EP03_S01E03_CUE_045_STEM_10_SYNTHBEDS_v02.32f.wav (archive copy in 32-bit float)
• HPW_EP03_S01E03_CUE_045_MIX_STEREO_v04.wav

Metadata manifest — machine-friendly and human-readable

Deliver a CSV/JSON manifest alongside audio files. Include the following fields at minimum:

• file_name
• show_code
• episode
• cue_number
• description
• stem_type (MIX/STEM/M&E/ATMOS)
• channels (1,2,6,object)
• sample_rate
• bit_depth
• start_TC (SMPTE)
• duration
• loudness_preLUFS
• loudness_POSTLUFS (if final)
• notes

Sample CSV row (filled)

file_name,show_code,episode,cue_number,stem_type,channels,sample_rate,bit_depth,start_TC,duration,loudness_preLUFS,loudness_postLUFS,notes
HPW_EP03_S01E03_CUE_045_STEM_01_STRINGS_v02.wav,HPW,03,045,STEM,2,48000,24,00:44:12:02,00:01:12,-18.5,,Live strings group mic'd and close

Timecode & sync best practices

Timecode errors are the most frequent cause of rework. Standardize these points up front:

• Frame rate: Use the episode's frame rate and embed frame-rate metadata in BWF fields. If the show is 23.976 FPS, deliver files and TC in 23.976.
• Start TC: Provide a start TC for every stem that corresponds to the picture timeline. Always include full SMPTE (HH:MM:SS:FF).
• Handles: Provide at least 1–2 seconds of handles for small cues; 10–30 seconds for complex stems destined for editing.
• Burn-in checks: If requested, supply a reference stereo with burn-in timecode to validate alignment.

Stems granularity strategy — practical patterns

Below are approaches used on large scoring projects. Choose one and stick with it.

By-family (recommended)

• Strings (divisi and full)
• Brass
• Woodwinds
• Choir
• Percussion (pit vs. processed)
• Bass / Low End
• Synth beds / Sound design
• Rhythm (drums, groove elements)

By-use (optional, more granular)

• Beds (sustains and pads)
• Hits & risers
• Underscore cues
• Spots (short cues, hit effects)

Quality and loudness QA checklist (printable)

1. All files play without corruption in two DAWs.
2. Sample rate & bit-depth match manifest and show spec.
3. No digital clipping anywhere (check both pre- and post-export).
4. Channels are correctly ordered and labeled.
5. Verify phase coherence for stereo pairs and multi-mic groups.
6. Confirm start TC is embedded and matches picture reference.
7. Check RMS/LUFS: deliver both pre-loudness and final loudness masters, with measurements attached.
8. Embed BWF or add sidecar metadata and manifest file.
9. Include plugin list, frozen stems, or printed automation if session not provided.
10. Checksum verification (MD5 or SHA-256) attached in manifest.

DAW and plugin notes — what to include

Producers increasingly automate ingest of session data. Provide:

• DAW name and version (Pro Tools 2024.12, Logic Pro 10.8, Cubase 13, etc.).
• OS and hardware used for any proprietary processing (for reproducibility).
• Detailed plugin list with versions and types (UAD, Native Instruments, proprietary boutique FX).
• If plugins are proprietary or custom, render frozen stems with processing baked in and also provide dry stems if requested.

Automation-friendly extras (2026 trends)

As of 2025–2026, post workflows ingest more machine-readable metadata and take advantage of AI tools for stem separation and loudness correction. Provide these extras to reduce manual intervention:

• Machine-readable manifest (JSON + CSV) with schema version.
• Stem-level loudness metadata (LUFS RMS) and true-peak values.
• Stem type tags for AI-assisted rebalancing (EX: "dialog-safe", "noiseshield").
• ADM export for Atmos-ready stems and object metadata.

Composer-to-Tech Handoff Template (copy & use)

Use this as the top-level document attached to any delivery. Fill the bracketed fields.

Technical Handoff Document (SAMPLE-FILLED — Hans Zimmer–style)

Project: HPW (Working code)
Episode: 03
Season/Episode: S01E03
Composer: Zimmerian Collective (Lead: A. Composer)
Deliverable date: 2026-01-20
DAW: Pro Tools 2024.12
Frame rate: 23.976
Sample rate (deliver): 48 kHz / 24-bit (primary)
Archive stems: 48 kHz / 32-bit float (secondary)
Loudness targets:
  - Streaming final (Apple/Netflix/Prime): -14 LUFS +/-0.5, True Peak <= -1 dBTP
  - Broadcast (US): -24 LKFS +/-1
Deliverables:
  - MIX_STEREO_HPWEp03_CUE045_v04.wav (48/24) — final loudness -14 LUFS
  - MIX_5.1_HPWEp03_CUE045_v02.wav (48/24)
  - ADM_HPWEp03_CUE045_v01.adm.wav (Atmos object file)
  - STEMS (01-20): STRINGS, BRASS, WOODWIND, CHOIR, PERC, SYNTH, BASS, FX, HYBRID_BED (48/24)
  - ARCHIVE_STEMS (32f): SYNTHBEDS, GRANULAR_FX (48/32f)
Naming convention: SHOW_EP##_SXXEYY_CUE_##_STEM_##_DESC_v##.wav
Timecode alignment: cue start TC 00:44:12:02 (SMPTE 23.976). All stems include handles: +15s pre / +10s post.
Manifest: HPW_EP03_CUES_MANIFEST_v02.csv attached.
Notes:
  - Choir recorded live; mics list attached. Several choir hits heavily processed with spectral FX — frozen stems delivered and dry stems available on request.
  - Synth instrument list + patches included in 'synth-patches.zip'.
  - Plugin list and versions attached; frozen stems provided where third-party licenced synths are used.
QA attached: LUFS report, MD5 checksums.
Contact for issues: post.supervisor@studio.example  (preferred), +1-555-555-5555

Common pitfalls and how to avoid them

• Inconsistent naming: Enforce the naming scheme and validate filenames with a script before uploading.
• Wrong frame-rate: Always embed and print TC and provide a burn-in reference for acceptance testing.
• Missing metadata: Use a manifest generator tool or simple spreadsheet template — human-readable manifests reduce back-and-forth.
• Plugin-only sessions: If a session depends on rare plugins, freeze/bounce processed stems and include dry versions for future rework.

Quick Pro Tools export checklist (practical steps)

1. Set session sample rate and frame rate to show spec.
2. Consolidate stems: Edit > Separate > Export Selected Tracks as Files (include handles).
3. Ensure BWF metadata includes start TC and project title.
4. Scan exported files for true-peak > -1 dBTP and clipping.
5. Generate MD5 checksums and attach manifest.

Advanced strategies — future-proofing your deliveries

In 2026, forward-looking practices reduce rework:

• Deliver Atmos-ready stems: Even if the show doesn't request Atmos yet, provide stems grouped to be easily mapped to objects.
• Use 32-bit float archives: Provides headroom for future processing and AI separation without losing quality.
• Structured metadata: Use JSON schema for manifest so future automation can ingest and validate before human review.
• Keep an automated preflight script: A small preflight script that checks filename patterns, sample rate, bit depth, TC presence and MD5 will save hours.

Final actionable takeaways

• Agree on specs before composition begins: sample rate, loudness, frame rate, and stem granularity.
• Use a single naming pattern and provide a machine-readable manifest (CSV + JSON recommended).
• Deliver both pre-loudness stems and final loudness-compliant mixes unless told otherwise.
• Provide DAW and plugin details. Freeze stems when proprietary plugins are present.
• Adopt Atmos-ready and 32-bit float archival workflows to future-proof high-profile productions.

Call to action

Download the ready-to-use ZIP of this handoff template, CSV manifest example, and printable QA checklist — adapt it as the single source of truth for your next scoring delivery. Want a custom handoff defined to your show's specs? Contact our technical documentation team to generate a one-click handoff pack tailored to your platform and post pipeline.

Related Reading

• Micro-Event Audio Blueprints (2026): Pocket Rigs, Low-Latency Routes, and Clip-First Workflows
• Low-Latency Location Audio (2026): Edge Caching, Sonic Texture, and Compact Streaming Rigs
• Automating Metadata Extraction with Gemini and Claude: A DAM Integration Guide
• Field Guide: Hybrid Edge Workflows for Productivity Tools in 2026
• A CTO’s Guide to Storage Costs: Why Emerging Flash Tech Could Shrink Your Cloud Bill
• How to Run a Product Launch Scanner with ARG-Style Teasers to Grow Email Lists
• How to Measure Your Dog for the Perfect Coat Fit
• Budgeting for Your Tech Stack: How Much Should a Small Business Spend on SaaS?
• How to Host a Low-ABV Herb-Forward Cocktail Night (Syrups, Bitters, and Mocktail Tips)
• Loyalty Programs for Pet Parents: How Unified Memberships Can Save Families Money