How to Build a One-Song Release Brief
A practical way to turn one song's verified facts, audience, assets, timing, and campaign decisions into a brief a small release team can use.
The short answer
Build the brief around one song's confirmed identity, listener promise, campaign objective, audience, assets, owners, dates, budget boundaries, and measurement plan. Keep facts separate from hypotheses, and give every task one owner and one decision date. A useful brief does not predict streams or playlist placement. It makes the release easier to deliver, explain, test, and review after launch.
Three things to know
- 01
Start with verified song, artist, rights, metadata, and delivery facts before writing promotional language.
- 02
Choose one campaign action to prioritize, then make the audience, assets, owners, and dates serve it.
- 03
Write down what the team will learn and what it will change, without treating platform results as guaranteed outcomes.
What should the brief verify before work begins?
Use this short gate before the team turns the brief into public campaign activity.
- 01
Release identity
Confirm artist, title, version, release date, duration, genre fields, explicit status, and any assigned identifier against the delivery source.
- 02
Rights and approvals
Confirm the team has permission for the recording, artwork, names, clips, credits, and quoted language it plans to use.
- 03
Primary action
Name one audience action for the campaign phase and state how the team will observe it without promising a particular result.
- 04
Owners and dates
Assign every deliverable an owner, approver, dependency, and date, including the release-day and post-release review responsibilities.
- 05
Evidence boundary
List the source for each material fact and mark audience, creative, attribution, and outcome statements as hypotheses when unverified.
What belongs in a one-song release brief?
A one-song brief should answer what is being released, why it matters to the intended listener, what the campaign is asking that listener to do, and who will do the work. Include the confirmed title, artist, version, release date, rights status, metadata, approved description, audience hypothesis, assets, channels, owners, deadlines, budget limits, and review points. Keep it short enough to use in a working meeting.
How should an artist separate facts from campaign hypotheses?
Create two labeled blocks. The fact block contains information the team can verify in the catalog, agreement, distributor account, platform profile, or approved asset folder. The hypothesis block contains the audience, message, channel, and behavior the team wants to test. This distinction prevents a mood description from becoming an unsupported audience claim and gives the team a clean way to revise assumptions after observing real campaign signals.
How can one song have a clear listener promise?
Describe the listening experience in plain language without claiming that every listener will react the same way. Name the sound, setting, or emotional use the team is presenting, then connect it to a specific audience context. For an electronic track, that might be late-night focus, a reflective commute, or a discovery playlist context. The promise guides copy and creative; it is not a performance guarantee.
How should the brief choose one campaign objective?
Choose one primary action for the campaign phase, such as driving an owned landing-page visit, inviting a save, building awareness for a release, or collecting qualified press interest. Secondary observations can still be recorded, but they should not compete for equal attention. Write the objective as an observable action and define the reporting window, so the team knows what it is reviewing and when.
How should a small team turn the brief into a schedule?
Work backward from the public release date. Put delivery and metadata checks first, then approvals, platform submissions, asset production, audience-facing content, outreach, release-day ownership, and the post-release review. Assign one owner per task and one person who can approve it. Mark dependencies explicitly: a pitch cannot use final details until the release information is confirmed, and a post-release read needs a defined date and data source.
How should the team review a one-song campaign after launch?
Review the brief against what actually happened. Record which assets shipped, which messages were used, which channels produced observable actions, what work was late, and what the available platform or first-party data can and cannot show. Do not turn correlation into attribution. End with a small number of decisions: continue an angle, change the creative, adjust the next date, or document the lesson for another release.
How can Babbage's Awake illustrate the brief without becoming a case study?
The repository catalog identifies Awake as a Babbage track with a 218-second duration, electronic genre, chillsynth subgenre, a non-explicit classification, and an ISRC. A brief could use those verified fields in its fact block, then label any listener or content angle as a hypothesis for testing. That example demonstrates the method; it does not report campaign results or claim that the track fits every audience.
How this guide uses evidence
Practical notes
- Babbage's Awake example is a first-party catalog example: the repository lists its duration, genre, subgenre, explicit classification, and ISRC.
- The brief structure is a constructed operating example. It does not report Awake campaign performance or imply a guaranteed audience response.
- Spotify pitch timing and eligibility belong in the delivery checklist, while playlist decisions remain outside an artist or label team's control.
Source notes
- Velveteen Records catalog, lib/catalog.json, Babbage artist and Awake track records, accessed August 12, 2026.
- Spotify for Artists Support, Pitching music to playlist editors: https://support.spotify.com/us/artists/article/pitching-music-to-playlist-editors/
- Repository source log, artifacts/content-batch/2026-07-18-goal/batch-006.md, Spotify pitch timing and eligibility notes, accessed August 12, 2026.
Frequently asked questions
- Is a one-song release brief the same as a press release?
- No. A press release is outward-facing copy, while a campaign brief coordinates facts, decisions, owners, assets, timing, and measurement for the team.
- How long should a one-song release brief be?
- Keep it as short as the team can use reliably, usually one working document with a fact block, decision block, schedule, and review plan.
- Should the brief include an unreleased song's ISRC?
- Include the identifier when it has been assigned and verified, but do not invent one. Leave the field marked pending until the responsible delivery source confirms it.
- Can a release brief promise playlist placement or streams?
- No. The brief can document an eligible pitch, outreach task, or promotion test, but platform and audience decisions remain outside the team's control.
- What should change after the first release review?
- Change the next decision that the evidence supports, such as the message, asset, audience segment, timing, owner, or reporting question. Keep unsupported explanations labeled as hypotheses.