Music studio ops

Music Studio Ops

A production-ready operations skill for small to mid-size audio production and music studios. Covers the full project lifecycle across five production categories — from client intake through final delivery — with frameworks for client communication, talent coordination, vendor management, file delivery, and proposals.

Built to international standards. Region-aware communication guidance included. Use this as a starting point and adjust to your studio's specific workflow, market, and production style.

Author: Abdelrahman Hammad
License: MIT — free to use, adapt, and share with attribution.

---

How to Use This Skill

1. Identify the production category first — each has its own workflow, timeline, and deliverable set
2. Use the relevant domain for the task at hand (communication, delivery, proposals, etc.)
3. Call a template by using the trigger phrases listed in the Templates section
4. Adapt the region-aware tone guidelines to your client's location

---

Production Categories

Always identify the category before advising on any project task. Each category has distinct client expectations, timelines, revision norms, and deliverables.

---

Category 1 — Commercial Music Production

Profile: Jingles, brand anthems, advertising music, campaign tracks, sync placements for ads.
Client type: Marketing teams, brand managers, advertising agencies, creative directors. Feedback is often non-technical and subjective.
Timeline: Fast — 1 to 3 weeks typical. High revision culture.
Key inputs at intake: Campaign brief, reference tracks, brand guidelines, required duration cuts, broadcast specs, delivery deadline.
Deliverables: Multiple duration cuts (15s, 30s, 60s), stems, broadcast-ready stereo master (WAV 48kHz/24bit), MP3 versions for digital use.
Common friction: Vague briefs, last-minute cut changes, version scope creep, approval delays from multiple non-technical stakeholders.
Revision protocol: 2 rounds included as standard. Additional rounds = change order.

---

Category 2 — Documentary Music Production

Profile: Original score, atmospheric beds, thematic motifs, sync-to-picture for documentary films and series.
Client type: Production houses, broadcasters, directors, streaming platforms. More collaborative and technically aware than advertising clients.
Timeline: Medium to long — 4 to 12 weeks depending on runtime and delivery platform. Director-led feedback.
Key inputs at intake: Cut of the film or episode (locked or working), spotting notes or scheduled spotting session, mood and reference direction, broadcast network or platform, delivery specs.
Deliverables: Scored video export, stereo mix per cue, stems per cue, cue sheet (title, timecode in/out, duration, composer, usage type), M&E split if required by broadcaster.
Common friction: Picture lock delays pushing the scoring timeline, cue revision requests after delivery, missing or vague spotting notes upfront.
Revision protocol: Tied to picture lock. Scoring begins only after lock is confirmed in writing. Post-lock revisions = change order.

---

Category 3 — Feature Film & Independent Movie Scores

Profile: Original score composition and full production for narrative feature films and independent movies. Ranges from intimate low-budget indie productions to larger studio features.

Client type:

• Independent films: Direct collaboration with the director. Relationship is close, feedback is personal and vision-driven. Director is typically both decision maker and day-to-day contact.
• Feature films (larger productions): Usually working through a production company or music supervisor. Less direct director access. More formal approval chain with multiple stakeholders.

Composer model: In-house composer or freelancer hired per project. Studio manages the full pipeline — composition through final delivery — regardless of composer arrangement.

Timeline: Medium to long — 6 to 20 weeks depending on film runtime, picture lock status, and delivery format. Entirely tied to the film's post-production schedule.

Key inputs at intake:

• Picture lock status — confirmed locked or expected lock date
• Spotting session scheduled or spotting notes available?
• Temp music references the director has been cutting to
• Emotional and tonal direction per act or scene
• Estimated runtime and number of cues
• Delivery specs — stereo, 5.1, Dolby Atmos?
• Festival submission or theatrical release deadline
• Budget range (directly affects orchestration scope and composer time)

Standard deliverables:

• Stereo mix per cue (WAV 48kHz/24bit)
• Stems per cue (strings, brass, percussion, synth, etc.)
• Full score mix end-to-end
• Cue sheet (title, timecode in, timecode out, duration, composer, usage type)
• Video export with score locked to picture

Dolby Atmos deliverables (when requested):

• Atmos immersive mix (.atmos + ADM BWF)
• Binaural render for headphone/streaming delivery
• 7.1.4 bed mix
• Always confirm exact Atmos specs with the receiving facility or platform before beginning the mix — Netflix, Apple TV+, and cinema venues each have different format and loudness requirements

Common friction:

• Picture not locked when scoring begins — leads to wasted work if the cut changes
• Temp music attachment — director expects the final score to closely resemble the temp tracks; address this expectation explicitly during the spotting session
• Orchestration scope not defined upfront (live players vs. sample libraries vs. hybrid)
• Festival deadline pressure compressing the scoring and mixing timeline
• Atmos delivery requirements surfacing late in the project

Revision protocol:

• Scoring begins only after picture lock is confirmed in writing
• Pre-lock cue drafts are exploratory — not counted as billable revision rounds
• Post-lock: 2 revision rounds per cue included as standard. Additional rounds = change order
• If picture changes after scoring has begun: assess cue impact, issue a change order for all affected cues

Composer coordination:

• Run an internal spotting session before briefing the composer
• Provide written notes, temp tracks, and reference films — not just a verbal brief
• Set internal delivery deadline 5 to 7 days ahead of client deadline for QC buffer
• For freelance composers: confirm rights, credits, and royalty arrangements in writing before work begins

---

Category 4 — Mixing & Mastering Only

Profile: Client brings finished recordings. Studio scope is purely technical — no composition or arrangement.
Client type: Independent artists, record labels, other studios. Generally technically aware.
Timeline: Short — 2 to 7 days per project. Tightly defined scope.
Key inputs at intake: Stems format (WAV/AIFF, sample rate, bit depth), track count, reference track for target sound, delivery platform (streaming, broadcast, vinyl, cinema), desired loudness target in LUFS, revision expectations.
Deliverables: Mixed and/or mastered file at platform-specific loudness, stems if requested, DDP image or WAV depending on format.
Common friction: Stems delivered in wrong format or sample rate, missing loudness reference, client expecting arrangement or composition changes within a mixing brief.
Revision protocol: 1 round of revisions included as standard. Define clearly upfront what counts as a revision versus a new mix direction — this boundary prevents disputes.

---

Category 5 — Sonic Branding

Profile: Brand audio identity — sonic logo, on-hold music, UI sounds, retail and venue atmosphere, brand anthem, audio style guide.
Client type: Enterprise brands, agencies, startups, institutions. Multi-stakeholder approval chains are common. Decision maker and day-to-day contact are rarely the same person.
Timeline: Long — 6 to 16 weeks. A discovery phase is required before any production begins.
Key inputs at intake: Brand guidelines and visual identity, brand values and personality descriptors, existing audio assets if any, competitor audio references, intended use cases (broadcast, digital, physical space, UI), full stakeholder and approval map.
Deliverables: Sonic logo (5–10s), brand anthem (60–90s), on-hold music, UI sound set, audio style guide document, all stems and source files.
Common friction: Stakeholder misalignment on creative direction, subjective feedback without defined criteria, scope expanding after production has begun.
Revision protocol: Phased approval gates — each phase requires written sign-off before the next begins. Changes to an already-approved phase = change order.

---

Domain 1 — Project Lifecycle Management

Standard 3-Phase Pipeline

Phase 1: Pre-Production

• Client brief received and reviewed
• Category identified
• Intake checklist completed (use category-specific template)
• SOW drafted and signed
• Timeline confirmed with milestones
• Internal team briefed
• Reference materials and assets collected

Phase 2: Production

• Creative and technical work in progress
• Internal review completed before any client-facing presentation
• Client presentation and structured feedback collection
• Revision rounds executed per category protocol
• Final approval obtained in writing

Phase 3: Post & Delivery

• Delivery checklist completed (use category-specific template)
• All files named and organized per naming convention
• Final handoff to client with delivery confirmation
• Project closure summary sent
• Internal archive completed

Project Status Definitions

Status	Meaning
Intake	Brief received, not yet started
Pre-Production	SOW active, gathering inputs and assets
In Production	Active creative or technical work underway
Client Review	Delivered to client, awaiting feedback
Revision	Incorporating approved change requests
Pending Approval	Final version submitted, awaiting sign-off
Delivered	All files handed off and confirmed received
Closed	Invoice settled, files archived

---

Domain 2 — Client Communication

Universal Communication Principles

Regardless of region, these apply to all client interactions:

• Always confirm receipt of briefs, feedback, and approvals — never leave a client wondering if you got their message
• Put approvals, scope changes, and revision requests in writing — verbal agreements cause disputes
• Lead with what you can do before addressing what falls outside scope
• Set clear response time expectations at project kickoff and honor them

---

Region-Aware Tone Guide

Use this to calibrate your communication style based on the client's cultural context. When in doubt, default to formal — it is always easier to relax tone once a relationship is established than to recover from being perceived as too casual.

---

North America (US & Canada)

• Tone: Direct, friendly, and efficient. Get to the point quickly.
• Feedback culture: Clients expect honest, straightforward status updates. They appreciate transparency about problems.
• Formality: Low to medium. First names from the first email are common.
• Revision culture: Moderate. Contracts and scope boundaries are generally respected.
• Tips: Be specific about timelines and deliverables. Ambiguity reads as unprofessional.

Western Europe (UK, Germany, France, Netherlands)

• Tone: Professional and precise. Slightly more formal than North America, varies by country.
• UK: Understated, polite, indirect about dissatisfaction — read between the lines.
• Germany: Very direct, detail-oriented, process-focused. Contracts are taken seriously.
• France: Relationship and quality-focused. Creative input is valued and expected.
• Formality: Medium to high on first contact. Warms up over time.
• Tips: Documentation is important in European markets. Always follow up verbal discussions with written summaries.

Middle East (GCC, Levant, North Africa)

• Tone: Formal, relationship-first. Business follows rapport — do not rush to transactional language.
• Formality: High, especially for first contact and government/enterprise clients. Use titles.
• Feedback culture: Indirect. Silence or vague positive responses may indicate unspoken concerns. Ask open questions.
• Approval chains: Often long and multi-layered. The person you speak to daily may not be the decision maker.
• Response time: Flexible around prayer times, Ramadan, and national holidays. Plan timelines accordingly.
• Tips: Always copy a secondary stakeholder on formal updates. Frame scope issues as "ensuring the best outcome" rather than a direct no.

East Asia (Japan, South Korea, China)

• Tone: Highly formal, respectful, and relationship-driven. Hierarchy matters significantly.
• Japan: Indirect communication is the norm. "Difficult" often means no. Consensus (nemawashi) takes time — do not pressure decisions.
• South Korea: Formal but faster-moving than Japan. Responsiveness is valued highly.
• China: Relationship (guanxi) is central. Decisions can move quickly once trust is established.
• Formality: High. Use full titles and surnames until explicitly invited to use first names.
• Tips: Patience is essential. Do not interpret deliberate pace as disinterest. Written follow-ups after meetings are expected and appreciated.

Latin America (Brazil, Mexico, Colombia, Argentina)

• Tone: Warm, personal, and relationship-driven. Building rapport before business is standard.
• Formality: Medium. Friendly but respectful. Personal connection matters as much as the work.
• Feedback culture: Positive and diplomatic on the surface — probe for specific concerns with open questions.
• Timeline culture: More flexible. Build buffer into deadlines and confirm closer to delivery.
• Tips: WhatsApp is a widely accepted professional communication channel in many Latin American markets. Match the client's preferred channel.

---

Scope Creep Response Framework

When a client requests something outside the agreed SOW:

1. Acknowledge the request warmly and without defensiveness
2. Reference the original SOW scope clearly but without making the client feel blamed
3. Offer to accommodate via a change order
4. Give a brief, honest indication of timeline and cost impact
5. Never refuse outright — frame it as: "This falls outside our current agreement and we'd love to make it happen — let me put together a quick amendment."

Revision Request Handler

When client revision notes arrive:

1. Confirm receipt immediately
2. Categorize each note: Creative (subjective direction change) / Technical (objective correction) / Out of scope (new request)
3. Respond with clarity: what you will action, what needs clarification, what triggers a change order
4. Confirm turnaround time in writing before beginning work

---

Domain 3 — Talent & Session Coordination

Session Brief Standard

Every brief sent to a composer, voice talent, session musician, or sound designer must include:

• Project name and production category
• Their specific role and what is expected from them
• Reference material — audio files, mood boards, reference tracks, temp music
• Technical specs — format, sample rate, BPM if applicable, key if applicable
• Session date/time or remote delivery deadline
• Number of revision rounds they are entitled to
• NDA reminder if the project is confidential

Composer Brief (Film Score Specific)

In addition to the session brief standard, include:

• Director's written notes on tone, emotion, and intent per act
• Temp music tracks the director has been using
• Reference films for sonic direction
• Cue list with timecodes, scene descriptions, and emotional targets
• Picture lock confirmation status
• Rights, credits, and royalty terms — confirmed in writing before work begins

Session Notes (Post-Session Record)

Document immediately after every session:

• Date, project name, attendees
• What was recorded or produced
• What was approved in session
• What requires follow-up and by whom
• Next step and deadline

---

Domain 4 — Vendor & Freelancer Ops

Contractor Onboarding Checklist

• Scope of work defined and agreed in writing
• Rate confirmed and payment milestones set
• Deadline confirmed
• NDA signed if project is confidential
• Reference materials and assets delivered to contractor
• Delivery format and specs confirmed
• Revision round limit agreed upfront
• Rights and credits terms confirmed (especially for composers)

Quality Review Protocol

Never submit contractor output directly to the client. Always:

1. Review against the original brief point by point
2. Check all technical specs — format, sample rate, loudness, file naming
3. Obtain internal sign-off from a senior creative or ops lead
4. Only then present to client

---

Domain 5 — Delivery Pipeline & File Management

File Naming Convention

[ClientName]_[ProjectName]_[Deliverable]_[Version]_[YYYYMMDD]

Examples:

• Nike_SummerCampaign_StereoMaster_v3_20260506.wav
• DocFilm_EpisodeOne_CueSheet_v1_20260506.pdf
• BrandCo_SonicLogo_Stems_FINAL_20260506.zip

Version Control Rules

• Never overwrite a file — always increment the version number
• Keep all versions until the project is closed and archived
• Only one file per deliverable ever carries the _FINAL suffix — the approved, delivered version
• Internal archive folder structure: Client → Project → Category → Deliverables / Working Files

Loudness & Format Standards

Platform / Use	Loudness Target	Format
Streaming (Spotify, Apple Music)	-14 LUFS integrated	WAV 44.1kHz / 24bit
Broadcast TV / Radio (EBU R128)	-23 LUFS integrated	WAV 48kHz / 24bit
YouTube	-14 LUFS integrated	WAV 48kHz / 24bit
Cinema (theatrical)	-24 LUFS	WAV 48kHz / 24bit
Podcast / online video	-16 LUFS integrated	WAV 48kHz / 24bit
Vinyl mastering	No LUFS target — dynamic priority	WAV 96kHz / 24bit
Dolby Atmos — streaming	-18 LUFS integrated	ADM BWF + .atmos
Dolby Atmos — cinema	-24 LUFS	ADM BWF + .atmos

Always confirm Atmos delivery specs directly with the receiving facility or platform. Netflix, Apple TV+, Amazon, and cinema venues each specify different format requirements and loudness targets.

---

Domain 6 — Proposals & Sonic Branding Ops

Universal Proposal Structure

Works across all production categories — adjust section depth per project size:

1. Executive Summary — What the client will gain; lead with value not process
2. Understanding of the Brief — Demonstrate you listened and understood their goal
3. Our Approach — Methodology, creative philosophy, why your studio for this project
4. Phased Delivery Plan — Phases with clear deliverables, milestones, and approval gates per phase
5. Deliverables List — Full itemized list of everything included
6. Timeline — Phase-by-phase with realistic milestones
7. Investment — Pricing per phase or project total; payment milestone structure
8. Team — Who is working on the project and their relevant experience
9. Selected Work — Relevant past projects as proof of capability

Sonic Branding Phased Delivery Model

• Phase 1: Discovery + Moodboarding + Creative Direction Approval
• Phase 2: Sonic Logo + Brand Anthem Draft
• Phase 3: Full Suite Production + Final Delivery + Audio Style Guide

Each phase requires written client sign-off before the next phase begins. Changes to an approved phase = change order.

---

Domain 7 — Stakeholder Management

Stakeholder Map (Complete for Every Project)

Role	Who It Is	Responsibility
Decision Maker	Final approval authority	Signs off on creative direction and deliverables
Day-to-day Contact	Your primary point of contact	Receives updates, relays feedback
Creative Reviewer	Gives subjective feedback	Usually the creative lead or director
Technical Receiver	Receives and QCs final files	Engineer, post-production supervisor, or IT

In enterprise and institutional projects, the decision maker and day-to-day contact are rarely the same person. Identify and confirm both at the start of every project — waiting until delivery to find the real decision maker is a common source of delays.

Approval Chain Best Practice

• Map the approval chain at intake, not at delivery
• Build approval time into your project timeline (enterprise clients can take 5–10 business days per approval round)
• Always get approval in writing — email confirmation is sufficient; verbal is not
• If approval is delayed beyond the agreed window, send a polite follow-up and note any timeline impact in writing

---

Templates

Ask for any template using its trigger phrase and this skill will generate it in full, adapted to your project details.

Template	Trigger Phrase
Project Intake Brief (per category)	"intake brief for [category]"
Project Status Update	"write a status update for [project]"
Revision Request Handler	"help me respond to this revision"
Session Brief	"write a session brief for [talent/role]"
Composer Brief (Film Score)	"composer brief for [film name]"
Delivery Checklist (per category)	"delivery checklist for [category]"
Dolby Atmos Delivery Checklist	"Atmos delivery checklist"
Vendor Scope Agreement	"vendor scope for [contractor name]"
Sonic Branding Proposal	"sonic branding proposal for [client name]"
Universal Project Proposal	"project proposal for [client name]"
Project Closure Summary	"project closure for [project name]"

---

Out of Scope

This skill does not cover:

• Music theory, composition technique, or mixing/mastering instruction
• Legal or music licensing frameworks (sync licenses, PRO registration, copyright)
• Accounting, invoicing software, or financial reporting systems
• Agile, Scrum, or software product development workflows
• Studio equipment selection or acoustic treatment

---

This skill is a starting point. Fork it, adapt it to your studio's workflow, market, and production categories, and make it yours.