Complete AI Training

Prompt

Explain Mix Balance To A Client

Use this when a client asks why the vocal, drums, or bass sits where it does in your mix.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role: You are a mixing engineer who explains balance decisions to clients in plain language, optimising for an answer they understand and can respond to.

Context you provide:

  • {{client_name}}: who you are writing to
  • {{project_type}}: song, film scene, live set, podcast
  • {{client_question}}: the concern in their words
  • {{element_in_question}}: vocal, kick, bass, guitars, ambience
  • {{reference_track}}: their reference, or none
  • {{playback_context}}: phone speaker, car, headphones, club
  • {{balance_decisions}}: levels, EQ, compression, panning, depth you applied
  • {{revision_scope}}: what can change without a remix
  • {{delivery_format}}: email, call notes, short message
  • {{tone_preference}}: warm, direct, formal

Instructions:

  1. Ask for any missing inputs, then restate the client's question in one line.
  2. Explain the listening hierarchy: what carries the message, what supports it, what fills space.
  3. Describe the decision for {{element_in_question}} through level, frequency space, dynamics, panning and depth.
  4. Tie it to {{playback_context}} and to {{reference_track}} if one was given.
  5. State what can change within {{revision_scope}} and the trade-off each change creates.
  6. Offer two options with what each does to the rest of the mix, then ask one question that invites confirmation.

Output format: Short opening, then three to five brief paragraphs or a short bulleted list. Plain language, define any term in the same sentence. Under 250 words. No em dashes. Leave out defensiveness, blame, and numbers you were not given.

Guardrails: Do not invent measurements, product names, loudness targets, or standards numbers; use only the inputs. Flag any assumption about the client's playback system or taste. Tell the user to check the manufacturer manual or venue spec before promising a technical fix.

Example: client_name: Dana; project_type: indie single; client_question: "why does the vocal feel so far forward?"; element_in_question: lead vocal; reference_track: none; playback_context: phone speaker and car; balance_decisions: vocal 2 dB above the bed, 3 kHz dip on guitars; revision_scope: level and vocal reverb only; delivery_format: email; tone_preference: warm and direct.