How to Fact-Check a DSP Pitch Before Submitting
Use a release fact sheet, official platform rules, and an evidence check before submitting a DSP pitch.
The short answer
Fact-check a DSP pitch by comparing every sentence with the final recording, approved metadata, current platform instructions, and a source you can name. Separate observable song facts from campaign plans, label interpretation, and hopes about placement. Confirm the route, account role, release state, timing, and required fields on the platform's current official page, then save the submitted version so the team can distinguish what it sent from what it merely expected.
Three things to know
- 01
A pitch packet should have one source of truth for the song title, artists, credits, release date, identifiers, version, and campaign facts.
- 02
Platform eligibility, access, timing, fields, and submission routes are platform-specific and can change, so verify them from current official instructions.
- 03
A fact-checked pitch improves accuracy and handoffs; it cannot promise editorial review, playlist placement, streams, or audience growth.
What belongs in the final pitch check?
Run this short review immediately before submitting on each platform.
- 01
Release identity
Title, artists, version, identifiers, release date, language, explicit status, and approved credits match the delivered release.
- 02
Platform route
Current official instructions confirm the account role, release state, timing, fields, and submission owner for this platform.
- 03
Evidence labels
Recording facts, campaign facts, interpretations, and unsupported hopes are separated before the copy reaches the form.
- 04
Access and links
The responsible team member can access the account and every required link, identifier, asset, and approval is available.
- 05
Submission record
The final text, timestamp, route, confirmation, and reporting location will be saved for the release file.
What is a DSP pitch fact-check supposed to catch?
A fact-check catches mismatches before they become a platform submission. Compare the pitch with the final master, approved credits, release metadata, artist roles, delivery status, and the campaign plan. It should also catch claims that sound plausible but have no evidence, such as an unconfirmed co-sign, a promised placement, a cultural label borrowed from someone else, or a release date that has moved. The goal is an accurate record, not a more persuasive exaggeration.
What release facts should be locked first?
Lock the exact track and release title, primary and featured artist roles, version, language, explicit status, writers and producers, label or distributor, release date, territories, identifiers, and final audio link. Keep a dated copy of the approved metadata. If a collaborator, distributor, or label still needs to approve a fact, mark it as pending rather than quietly choosing the version that sounds strongest in a pitch.
How should a team verify the platform route?
Open the platform's current first-party instructions and record the route, required account role, eligible release state, deadline, allowed fields, and confirmation or reporting signal. Do not assume a Spotify workflow applies to Apple Music, Amazon Music, Deezer, or another service. If a distributor or label controls the route, ask that partner to confirm the current process and keep the request in writing. A screenshot or old checklist is a lead for research, not proof of a live rule.
How can you separate facts from campaign interpretation?
Use four labels in the working document: recording fact, documented campaign fact, team interpretation, and unsupported claim. A recording fact might be that the final version uses a live drum kit. A documented campaign fact might be a confirmed video date or booked show. An interpretation might be that the song suits a late-night listening context. An unsupported claim would be that editors or a large audience already want it. Only the first two should be stated as facts.
What should a small team do when collaborators disagree?
Pause the submission and identify the disputed field. The release owner can ask for the approved metadata, lyric or credit confirmation, final master, or written campaign approval that resolves it. Do not solve disagreement by changing an artist role, genre, location, language, or cultural description to make the pitch fit a desired lane. If the dispute affects eligibility or rights, ask the distributor, label, or qualified adviser before submitting.
What should the team save after submitting?
Save the submitted text, date and time, account or team owner, release identifier, platform route, confirmation screen or email, and any next reporting location. Note which fields were adapted for that platform. This record prevents a later team member from treating a draft as the final submission, repeating a rejected assumption, or claiming that a pitch produced an outcome the available reporting does not show.
What does a fact-checked pitch packet look like in practice?
Constructed example: a team preparing a fictional single called Glass Harbour lists the final title, primary artist, release date, UPC, ISRC, version, and confirmed campaign dates in a source sheet. It labels ‘recorded with live drums’ as a recording fact, ‘short film premieres on 14 September’ as a confirmed campaign fact, and ‘fits editorial night-drive playlists’ as an interpretation. The team removes ‘will be a breakout’ because it has no source, then adapts the remaining facts to each live platform form.
Frequently asked questions
- Can one DSP pitch be copied to every platform?
- Reuse verified release facts, but do not copy the workflow blindly. Each platform may have different access, eligibility, timing, fields, and submission routes, so adapt the packet to current official instructions.
- Should an artist mention a hoped-for playlist in a pitch?
- Describe the song and documented campaign context instead of presenting a hoped-for playlist as an expected result. A pitch requests consideration and does not guarantee editorial placement.
- What if the release metadata changes after the pitch is drafted?
- Pause, update the source sheet, check platform eligibility and delivery status again, and save a new dated draft. Do not submit a stale title, date, credit, version, or identifier.
- Does a distributor have to approve every DSP pitch?
- Not always. The current platform route and account setup determine who can submit. If a distributor or label controls the route, confirm its process rather than assuming artist access or authority.
- Is a fact-checked pitch more likely to get playlist placement?
- Accuracy makes the submission easier to review and keeps the campaign record reliable, but it does not predict or guarantee review, placement, streams, or audience growth.