How to Write a Good Song Brief
A strong song brief uses one central message, two or three accurate scenes, pronunciation help, a recipient-led music direction, and explicit privacy boundaries.
A good song brief identifies the recipient, the occasion, one central message, two or three specific memories, the desired musical direction, and anything the song must avoid. Write facts and scenes in plain language. You do not need to write lyrics or describe private model behavior.
Start with the emotional job
Decide what the listener should understand after one play. “Celebrate how dependable he has been since retirement” gives the song a clearer job than “make it emotional.” Keep one central message for the chorus; supporting details can sit in the verses.
Use actions instead of generic adjectives
“She is generous” could describe anyone. “She leaves soup outside our door whenever someone is ill” supplies an observable scene. Include two or three details that are accurate, safe for the audience, and easy to understand when sung.
Weak: “Maya is amazing and loves adventures.” Stronger: “Maya drove through the rain to collect us after the last train, then made everyone laugh about the ruined map.”
Give pronunciation help
Write unusual names, places, or family words phonetically. Add the stressed syllable when necessary: “Ana, pronounced AH-na.” Avoid initials, abbreviations, dates, or spellings that a vocalist could interpret several ways.
Choose music for the recipient
Name the closest available genre and describe useful qualities such as warm, restrained, energetic, or spacious. Do not request a clone of a living artist or a specific copyrighted recording. The genre guide explains all 14 directions.
State exclusions and audience
Say who will hear the song and identify topics that must remain private. A playful office story may be safe for a partner but wrong for a public wedding. For memorials, health, apologies, or strained relationships, verify facts with someone close to the situation and keep the emotional claims proportionate.
Song brief template
- Recipient and pronunciation: name, relationship, and phonetic help.
- Occasion: what is happening and why it matters now.
- Main message: one sentence the chorus should communicate.
- Evidence: two or three memories, actions, places, or safe phrases.
- Music: genre, voice, energy, and desired emotional scale.
- Boundaries: facts to verify and subjects, names, or jokes to exclude.
How long should the brief be?
There is no magic word count. Use enough detail to make the story recognizable without turning the form into a biography. A focused paragraph or two is usually easier to interpret than a long chronology. Remove any sentence that does not affect the story, sound, or safety of the result.
Final check before generation
- Read every name and fact aloud.
- Confirm that only one main message competes for the chorus.
- Replace broad praise with a concrete action.
- Remove details the recipient would not want shared.
- Use the previews to test the result rather than assuming the input guarantees it.
Review the complete information checklist and how to assess the previews. When the brief is ready, generate 4 personalized previews before payment.
Everything you want to know
How long should a song brief be?
Use enough detail to make the story recognizable without writing a biography. A focused paragraph or two with one message and two or three memories is usually more useful than a long chronology.
Do I need to write lyrics in the brief?
No. Supply accurate source material, pronunciation, mood, genre, audience, and exclusions. Plain facts and scenes are more useful than trying to force finished rhymes.
What makes a song brief personal?
Use actions, places, rituals, and phrases that belong to the recipient. Replace generic adjectives with verifiable scenes and remove anything they would not want the reveal audience to hear.
Why people choose Cantarova
- Because the template separates message, evidence, music, and boundaries
- Because every personalization detail must be observable and audience-safe
- Because the final preview remains the test rather than an input guarantee