Release Day Checklist

This guide is for DIY artists, managers, and small release teams responsible for a distributed recording on its first public day. It provides a practical system for checking what listeners can see and hear, recording defects, routing problems, communicating accurately, and handing unresolved work to a named owner.

The operating model is global, but it is an Open Music Business editorial framework—not a platform rule or industry standard. The named platform examples were checked on July 30, 2026. Timing, tools, access, analytics, correction routes, and legal requirements can vary by service, distributor, territory, account, and later product changes.

This article covers final preflight through the first-day or next-business-day handoff. It does not replace long-range release planning, rights and royalty registration, sustained marketing, or provider-specific correction guidance.

Open Music Business provides educational information, not individualized legal, financial, tax, contract, privacy, royalty, or rights advice. Check current provider instructions and seek a qualified, jurisdiction-aware professional before making destructive catalog changes, changing identifiers, or submitting infringement claims when the consequences may be material.

Short answer: use the five-step loop

1. Verify: Test the public listener experience, not merely the distributor dashboard.
2. Record: Capture the expected result, actual result, scope, evidence, owner, and next review time.
3. Route: Send the issue to the distributor, platform, link vendor, or qualified professional that can act on it.
4. Communicate: Promote verified destinations and correct only affected links or messages.
5. Monitor: Recheck incidents and capture comparable analytics baselines without treating day one as a final verdict.

Remember: Verify → Record → Route → Communicate → Monitor. This is an editorial operating model informed by general incident-response practice, not a procedure imposed by music platforms. Google’s incident-response workbook supports the underlying use of clear roles, records, communications, and handoffs.

Fast release-day checklist

• [ ] Confirm the intended release time, time zone, territories, and participating services.
• [ ] Compare public titles, artist names, audio, artwork, credits, explicit tag, date, and track order with the approved release record.
• [ ] Check that each track appears on the intended artist page.
• [ ] Play the beginning, middle, and ending of every track.
• [ ] Open every priority smart-link button on the devices and in the territories that matter to the campaign.
• [ ] Assign an owner to every defect.
• [ ] Save the observed URL, timestamp, territory, device, screenshot or playback note, and provider case number.
• [ ] Separate observed facts from suspected causes.
• [ ] Pause or correct only affected links or placements when verified alternatives remain available.
• [ ] Set a next action and next review time for every open incident.
• [ ] Record analytics definitions, time zone, territory, and observation window before comparing results.
• [ ] End the shift with a written handoff for every unresolved item.

Command-center table

Copy one row for each check or incident.

| Item | Expected | Observed | Scope | Severity | Owner | Status | Evidence | Provider case | Next action | Next review | |---|---|---|---|---|---|---|---|---|---|---| | Service, track, profile, or link | Approved state | Public result | Service, territory, device | Stop and escalate / Contain and route / Observe and recheck | Named person | Not checked / Verified / Open / Resolved | URL and evidence filename | Number or not yet filed | Specific action | Date, time, time zone |

A useful evidence filename convention is date_time-timezone_service_territory_device_observation. The convention is an organizational suggestion, not a platform requirement.

Severity-routing matrix

| Category | Use it when | Immediate action | |---|---|---| | Stop and escalate | The wrong recording is live; an upload may be unauthorized; identifiers are ambiguous; a rights dispute exists; or someone proposes a takedown, deletion, or re-upload with material consequences. | Preserve evidence. Do not make a destructive change or legal submission until the current provider route and, where appropriate, qualified human guidance are clear. | | Contain and route | A meaningful listener path is defective, but verified alternatives remain—for example, a wrong artist page, broken campaign button, bad artwork, or important metadata error. | Pause or correct only the affected destination or placement, keep verified options available, open the appropriate provider case, and schedule a review. | | Observe and recheck | The public release is correct but analytics are incomplete, a lower-priority destination is still being checked, or a playback problem cannot be reproduced after basic troubleshooting. | Record the baseline and recheck time instead of repeatedly changing the release. |

These categories organize attention; they do not establish universal legal or platform thresholds.

Essential terms

• Metadata: Delivered descriptive information such as titles, artist names, credits, roles, release date, track order, artwork, and explicit-content status.
• UPC: The release-level code shown in the distributor record and sometimes requested in correction workflows.
• ISRC: The identifier assigned to an individual recording. The International ISRC Registration Authority explains when an existing recording retains its ISRC and when a materially changed recording may need a new one.
• Smart link: A campaign landing page that offers listeners links to one or more services.
• Artist mapping: The association between a delivered release and the public artist page on which it appears.
• Release mode: Whether availability begins at one worldwide instant or at local times in different territories.
• Account access: The role or permission needed to use a distributor dashboard, artist tool, channel, or provider support feature.

Before the intended release moment

Create one approved release record containing:

• release and track titles;
• primary and featured artist names exactly as delivered;
• approved audio and artwork;
• credits, roles, explicit-content status, release date, release mode, territories, UPC, and track ISRCs;
• distributor release URL or identifier;
• intended artist-page and public destination URLs;
• smart-link URLs;
• account access for the distributor, artist tools, channel, link service, advertising, email, and social accounts;
• current provider support routes; and
• the people responsible for decisions, incident operations, and communications.

One person may hold all three responsibilities, but decisions, investigation, and communications should remain distinguishable in the log.

Do not assume every service will go live at local midnight. Releases can use one worldwide instant or local availability by territory, and participating services may handle timing differently. Confirm the distributor’s settings, time zone, services, and priority territories. Spotify documents release dates and times for delivered music, while the DDEX delivery standard shows that territories and start dates are part of release-deal configuration.

Account access is a preflight dependency. For example, Apple currently says content must have been live on Apple Music for at least five business days before an artist page can be claimed. That makes release-morning claiming unsuitable as a universal first-release plan. See Apple Music for Artists account guidance.

Step 1: Verify the public listener experience

A distributor status or working top-level smart link does not prove that every public destination is available and correct. Compare the approved record with the listener-facing result on priority services and in priority territories.

Check in this order

Availability

• Can a listener find and open the release?
• Is every expected track present and playable?
• Does the public timing match the intended configuration?

Identity

• Is the release attached to the correct primary and featured artist pages?
• Has a same-name artist received the release?
• Has the catalog split across pages?

Audio and version

• Play the beginning, middle, and ending of each track.
• Confirm the recording, mix or master, sequence, explicit version, and duration against the approved record.
• For an apparent Spotify playback fault, first update the app and test another device or web player and another Wi-Fi or data connection. This is Spotify-specific troubleshooting, documented on Spotify’s faulty-audio support page, not a universal platform rule.

Presentation

• Compare the title, artist formatting, artwork, credits, roles, explicit tag, date, and track order with the approved record.
• Check that the release appears in the intended place on each owned artist profile or channel.

Destinations

• Open every important smart-link button rather than testing only the landing page.
• Record the device, territory, destination URL, and whether it opened the intended app or web page.

For Linkfire specifically, routing can vary by location or device, while automated release-day scanning and conversion do not prove every destination match is correct. See Linkfire’s explanations of device and location routing, territory-dependent destinations, and pre-release conversion. Other smart-link products require their own current documentation.

Do not invent a universal waiting period

No approved evidence establishes one propagation delay or wait-before-escalation threshold across all services and distributors. Compare the intended configuration and delivery history with the actual provider’s current guidance. An internal recheck time is a team decision, not a promise about when a provider will repair the problem.

As a dated example, Spotify’s US-English artist documentation said on July 30, 2026 that Spotify needs five business days to make new music live and directs an artist to the distributor when a timely delivered release is missing on release day. This is Spotify-specific and does not override a distributor’s longer lead time. See Spotify’s release-day availability guidance.

Step 2: Record observations before guessing at causes

For every defect, capture:

• expected state and actual observed state;
• timestamp and time zone;
• territory, service, and URL;
• device, app or browser;
• screenshot, screen recording, or playback note;
• affected release, track, UPC, and ISRC where relevant;
• observed impact and scope;
• severity category and owner;
• provider case number;
• next action; and
• next review time.

Write observations separately from hypotheses. “The Spotify button opened an unrelated artist page on an iPhone in the United States at 09:12 CDT” is an observation. “A same-name collision caused the error” is a hypothesis. Amuse and CD Baby document shared or similar artist names as mapping-risk patterns, but those patterns do not prove the cause of a specific incident. See the current wrong-page guidance from Amuse and CD Baby.

Step 3: Classify the impact

Use the routing matrix before changing links, catalog data, or public messages.

A suspected unauthorized upload is not an ordinary metadata defect. Preserve the evidence and use the relevant legal process only if you are the rights owner or an authorized representative. Copyright submissions may be legal processes and may expose claimant information. Review the applicable provider instructions, including Spotify’s unauthorized-upload route and YouTube’s copyright-removal guidance, and seek qualified advice when the consequences are material.

Step 4: Route the problem safely

Delivered catalog data

Spotify currently routes corrections to artist names, titles, artwork, dates, track order, country availability, explicit tags, roles, and credits through the label or distributor. See Spotify’s metadata-correction guidance.

Apple currently routes missing releases and most delivered metadata or asset corrections through the distributor. Wrong-artist-page issues also have an Apple Music for Artists support route. See Apple’s guidance on music distribution and catalog problems.

Artist-page mapping

A wrong-profile or split-catalog problem on Spotify can be reported through Spotify for Artists. Notify the distributor as well when a delivery-side mismatch may affect other services; a Spotify report addresses Spotify only. See Spotify’s mixed-up artist guidance.

Eligible YouTube Official Artist Channels can request the addition of a missing release or removal of an incorrect release through the desktop Releases tab. Partner-level Art Track corrections use a separate access-dependent workflow. See YouTube’s guidance for managing releases and correcting music information.

Provider forms request different information. CD Baby’s dated wrong-profile workflow, for example, asks for the affected UPC, track names, and correct and incorrect artist-page URLs. Treat those as a provider-specific example, not universal fields.

Link defects

When the release is correct on a service but the campaign link reaches the wrong destination, record the territory, device, displayed button, and actual URL. Correct or pause the affected button while keeping verified destinations available.

Takedowns, re-uploads, and identifiers

Do not delete or re-upload by reflex. Provider-specific workflows show that deletion, replacement, and redistribution can affect editability, timing, linking, play-count continuity, reviews, comments, or playlist associations. Review current guidance from the relevant distributor or service before acting, particularly where the commercial consequences may be material. Examples include Spotify’s re-upload guidance, TuneCore’s release-change process, and DistroKid’s post-upload editing guidance.

The same recording retains its existing ISRC; a materially different recording may require a new one, and an assigned ISRC must not be reused for a different recording. Determining whether an edit, remix, restoration, or remaster is materially different may require specialist application of the ISRC guidance.

Do not promise that a wrong-profile or metadata correction will take a few days. Published provider estimates differ by service, distributor, and requested change and may range from days to weeks or, in some cases, months; see dated examples from Amuse, TuneCore, and DistroKid.

Step 5: Communicate and monitor

Use the command-center table as the message source of truth. Every update should distinguish verified observations from unconfirmed causes and should name the next owner and review time.

Message templates

Internal team

At [time and time zone], we expected [state] and observed [state] on [service, territory, and device]. Severity: [category]. Verified alternatives: [links]. Owner: [name]. Provider case: [number or not yet filed]. Next action: [action]. Next review: [time and time zone].

Collaborators and featured artists

The release is verified at [links]. [Affected destination] is being corrected. Please use only the verified links until the next update at [time and time zone].

Media or campaign partners

The release is available at [verified link]. One destination is affected, so please replace or pause [specific link or placement]. We will send another confirmed update at [time and time zone].

Listeners and fans

[Service] is currently affected. You can listen through the verified links here: [links]. We will update this message when the destination is confirmed.

These patterns intentionally avoid assigning an unconfirmed cause or promising a provider repair deadline.

If you publish prerecorded promotional video, provide accurate captions and review generated captions rather than assuming they are correct. Accessibility obligations vary by jurisdiction; this is safe production guidance, not a universal legal conclusion. See the US government’s social-media accessibility guidance.

Use a lawfully maintained email list, honor opt-outs, and check the rules applicable to the sender and recipients. A global guide cannot state one universal email rule because US and UK requirements differ. Consult the US Federal Trade Commission’s CAN-SPAM guidance and the UK Information Commissioner’s electronic-mail guidance, then obtain local advice when needed.

Treat first-day analytics as timestamped baselines, not final judgments. Spotify and Apple document different time zones, definitions, privacy thresholds, refresh schedules, and later processing. Record the platform, metric definition, territory, time zone, observation window, and denominator before comparing snapshots. See Spotify’s statistics update guidance and Apple’s documentation for New Release Insights and analytics definitions.

Common release-day traps

• Do not treat Spotify song pitching as a release-day task. Spotify’s documented song-pitching route is for an upcoming, unreleased song; eligibility ends once the song is live, and placement is not guaranteed. See Spotify’s pitching guidance.
• Do not assume Apple Music for Artists provides an editorial-playlist submission button. The reviewed Apple Promote documentation describes promotional assets and links, not an artist-facing editorial submission route. Check current Apple or distributor guidance instead. See Apple’s Promote documentation.
• Do not use TikTok One Creator Marketplace to deliver a recording to TikTok’s music catalog. TikTok describes that product as a route for creator opportunities and brand collaboration. See TikTok One Creator Marketplace guidance.
• Avoid services that guarantee Spotify streams or playlist placement. Spotify says those services violate its conditions and may lead to adjusted counts, withheld royalties, distributor action, playlist removal, or content removal. This warning concerns guarantees and manipulation, not all independent promotion. See Spotify’s artificial-streaming guidance.
• Do not claim that replying to every comment improves algorithmic visibility. Reply when it serves listeners or the community, but treat performance claims as platform- and evidence-dependent.

Worked example: the single is on the wrong Spotify profile

Assumptions

These inputs are invented for illustration, not a reported incident:

• Artist A is releasing Track A.
• The intended release moment is August 14, 2026 at 00:00 America/Chicago.
• Priority territories are the United States and United Kingdom.
• Apple Music and YouTube display the correct release.
• Spotify attaches the single to an unrelated same-name profile.
• The Linkfire Spotify button opens the wrong profile on one tested phone.
• The artist records invented URLs, UPC, screenshots, device details, and timestamps.
• A Spotify-directed advertisement is paused while verified destinations remain available.
• The team chooses an internal review four hours later. Four hours is an invented team decision, not a provider service promise.

Classification

The incident is Contain and route because a meaningful Spotify listener path is defective while verified Apple Music and YouTube alternatives remain available. The checks have not shown an unauthorized upload, rights dispute, identifier conflict, or wrong recording, so the observed facts do not justify the Stop and escalate category. If later evidence revealed one of those conditions, the classification would change.

Applying the loop

Verify: The Spotify destination reaches the unrelated profile on two tests. Apple Music and YouTube match the approved record.

Record: The log captures the expected and actual profile URLs, affected track, UPC, territory, phone, screenshots, timestamps, observed scope, and verified alternatives.

Route: The artist submits Spotify’s wrong-profile report and notifies the distributor because a delivery-side mismatch could affect other services. The same-name pattern remains a hypothesis, not a proven cause.

Communicate: The Spotify-specific advertisement is paused. Messages direct listeners and partners to verified Apple Music and YouTube destinations without promising a repair time.

Monitor: The incident receives an owner, next action, provider case number when available, and the invented four-hour internal review time. The artist does not delete or re-upload the release without current provider guidance.

Solo and staffed-team ownership

For a solo release, one person may make the containment decision, perform the checks, file the cases, and send updates—but each responsibility remains separately recorded.

For a staffed release:

• the release lead approves pausing the affected advertisement and any higher-consequence catalog decision;
• the operations owner verifies destinations, maintains evidence, and files provider cases; and
• the communications owner updates collaborators, campaign partners, media, and listeners from the shared record.

End-of-day handoff

For every unresolved incident, record:

• the verified and affected destinations;
• the latest observation with timestamp and time zone;
• evidence location;
• severity category;
• provider case number and latest reply;
• decisions already made;
• current owner;
• next action;
• next review time; and
• the condition that would require escalation.

Release-day operations are complete when the checks are documented and every unresolved incident has an owner, next action, and review time—not necessarily when every provider has completed every correction.

Choose the next workflow

• Continue the campaign with the Release Week Marketing Playbook.
• For the broader correction workflow, continue to Release Takedowns and Corrections and still confirm the current instructions of the provider involved.
• Address royalty-registration gaps with the Song Registration Checklist.
• Plan the next campaign earlier with The 8-Week Release Timeline.