How to Run a Final QA Pass Before a Music Release Goes Live
A final release-check workflow for confirming delivery, artist profiles, links, assets, credits, pitches, and launch-week owners before release day.
The short answer
Run a final release QA pass by checking the delivered release, artist profiles, platform links, artwork, credits, rights notes, pitch status, social assets, smartlink destination, ad setup, press materials, and launch-week owners. The goal is to catch preventable problems before fans, curators, journalists, creators, or label partners see the campaign. Any unclear rights or agreement issue should go to qualified counsel before launch.
Three things to know
- 01
A final QA pass should happen before the last week, because some platform and distributor fixes need several business days.
- 02
The checklist should verify both release operations and campaign readiness: delivery, profiles, links, assets, owners, and reporting.
- 03
Small teams should assign a single owner for each fix so release day does not become a chain of unresolved messages.
Final release QA checklist
Use this pass before the public push so the campaign is not built on broken inputs.
- 01
Delivery status
Confirm the distributor status, release date, UPC or release ID, ISRCs, territories, explicit tags, and store availability.
- 02
Profile placement
Check artist names, featured artist credits, profile destinations, upcoming release views, and screenshots for any mismatch.
- 03
Fan links
Test smartlinks, pre-save or listen links, video destinations, merch pages, email forms, and link-in-bio routing on mobile.
- 04
Campaign assets
Review artwork crops, EPK files, captions, pitch copy, visualizers, short clips, ad creative, and press images.
- 05
Owners and fixes
Assign every open issue to one person with a deadline, status note, and launch-impact decision.
What should the final QA pass cover?
The pass should cover the release itself and the campaign around it. Confirm audio, artwork, metadata, explicit tags, credits, splits, delivery status, artist-profile placement, smartlink routing, EPK links, pitch copy, content files, ad links, press contacts, and reporting access. A final QA pass is useful because it turns vague readiness into a visible list of pass, fix, and owner.
When should the team run the checklist?
Run the first QA pass as soon as the release appears in distributor and platform dashboards, then repeat a smaller pass two or three days before launch. Waiting until release morning is too late for many issues. Spotify says new music needs business-day lead time, and editorial or Release Radar windows can require earlier setup than artists expect.
How should artists check platform profile placement?
Open the unreleased or upcoming view where available, confirm the artist name, featured artists, release title, artwork, track order, and profile destination, then document any mismatch with screenshots. If a track appears on the wrong profile, contact the distributor or platform support quickly. The campaign should not send fans toward a link that might later change.
What campaign assets need one last review?
Review every public asset in the way a fan or partner will experience it. Test the smartlink on mobile, open the private listening link, scan EPK downloads, check short-form captions, confirm artwork crops, preview email links, verify ad destination URLs, and make sure the release CTA is consistent. Small mistakes are easier to fix before the announcement spreads.
How should rights and credits be handled in QA?
The final pass should confirm that credits, splits, contributors, featured artists, samples, artwork permissions, and side approvals are resolved enough for release. This guide is not legal advice. If ownership, licensing, recoupment, work-for-hire, or agreement language is unclear, the team should pause the relevant release action and ask qualified music counsel before creating a public problem.
What happens if QA finds a real problem?
Sort problems by launch impact. A typo in an internal note can wait. Wrong artist profile, missing rights approval, broken smartlink, bad artwork crop, unavailable audio, or incorrect release date needs immediate ownership. Decide whether to fix, delay, simplify, or switch the campaign message. The worst answer is to continue as if the issue does not affect the release.
How this QA guide is grounded
Practical notes
- The checklist uses current platform timing notes plus internal campaign-readiness patterns from the generated guide library.
- Rights and agreement items are framed as issue spotting and counsel escalation, not legal advice.
Source notes
- Spotify Support says new music needs 5 business days to get live and late delivery can delay availability: https://support.spotify.com/us/artists/article/music-not-live-on-release-day/
- Spotify Support recommends setting live dates at least 7 days out so an unreleased song can be pitched for playlist consideration: https://support.spotify.com/us/artists/article/metadata-formatting-guidelines/
- Spotify Support explains artist profile protection and approval behavior for releases: https://support.spotify.com/us/artists/article/artist-profile-protection/
Frequently asked questions
- Is final QA different from uploading the release?
- Yes. Uploading sends the release into delivery. QA checks whether the release and campaign are ready for fans and partners.
- What is the most urgent release QA issue?
- Wrong profile placement, broken links, unresolved rights questions, bad dates, unavailable audio, and incorrect credits usually deserve the fastest attention.
- Should artists delay a release because of a QA problem?
- Sometimes. Delay can be smarter than launching with a rights, profile, link, or campaign issue that weakens the release.
- Who should own the final QA pass?
- One release coordinator should own the checklist, but each fix should still have a named artist, manager, label, designer, or distributor owner.
- Does final QA replace legal review?
- No. QA can surface rights or agreement concerns, but qualified music counsel should review unresolved legal questions before release.