What Happens Between Music Upload and Release Day?
Trace a music release through distributor validation, store delivery, platform ingestion, quality review, artist mapping, verification, updates, and launch monitoring.
The short answer
After upload, a distributor validates the release, sends structured audio and metadata to selected services, and records delivery status. Each platform then ingests, reviews, maps, schedules, and displays the content under its own rules. The artist must verify the intended profile, date, territories, audio, artwork, metadata, identifiers, and links, submit controlled corrections through the proper source, and monitor the release when it becomes live.
Three things to know
- 01
Treat upload, distributor approval, delivery, platform ingestion, mapping, scheduling, live availability, and correction as distinct states.
- 02
Keep an evidence ledger with timestamps, delivery references, screenshots, URLs, territories, owners, and support cases.
- 03
Change release data through the responsible label or distributor and verify the platform result instead of assuming a submitted update is complete.
Which states should a release ledger record?
A single progress label cannot show where a release is actually blocked.
- 1
Submitted
Record final package, uploader, account, date, stores, territories, rights, identifiers, payment, and submission confirmation.
- 2
Validated
Capture automated and human review, tickets, answers, revisions, approval, final package hash, and delivery authorization.
- 3
Delivered
Log each recipient, delivery ID, timestamp, version, resends, acknowledgements, rejects, and distributor support owner.
- 4
Ingested and mapped
Verify artist identity, catalogue entity, date, roles, artwork, tracklist, flags, territories, URI, and preview surfaces.
- 5
Live and observed
Check production audio, pages, credits, links, markets, campaign destinations, defects, cases, corrections, and closure evidence.
What does the distributor validate after upload?
The provider can check account status, audio format, artwork dimensions and content, title formatting, artist roles, credits, language, advisory flags, dates, territories, identifiers, rights declarations, cover or sample information, and store-specific eligibility. A human or automated review may return questions or reject fields. Answer with source evidence and change only what is necessary. Record the original package, submission time, validation result, revisions, approver, and final package so later platform differences can be traced.
How is a release delivered to streaming services?
The distributor packages audio, artwork, metadata, identifiers, availability, territory, and rights instructions into each service's supported delivery process. Spotify says artists work through a distributor and that distributors handle delivery and royalty accounting. A delivered status means the provider sent a package; it does not prove every recipient accepted, mapped, scheduled, or displayed it. Record which stores were selected, which version was sent, the delivery or batch identifier, timestamp, and any later redelivery.
What happens during platform ingestion and review?
A service validates the files and fields, matches identifiers, interprets artist roles and dates, applies policy and quality checks, associates the release with catalogue entities, and schedules availability. Apple says its quality-assurance team reviews music, art, and metadata and can issue tickets. Processing can vary across services and releases. Curated or restricted products may have additional decisions. Do not infer rejection from silence or acceptance from one service. Track each platform state independently.
How does artist-profile mapping happen?
Platforms may use supplied artist identifiers, names, catalogue history, provider mappings, and internal systems to select a profile. Shared or similar names create risk. Supply exact Spotify URIs or other supported artist identifiers for existing profiles and identify new artists correctly. Check primary, featured, remixer, and release-level roles. Spotify says supported distributors can specify artist IDs and that Upcoming can reveal incorrect unreleased deliveries. Mapping is an identity field, not a marketing choice, so never manipulate roles to access features.
What can artists verify before release day?
Use distributor dashboards and platform artist tools to check available details. Spotify Upcoming can show delivered unreleased music, artwork, date, tracklist, URI, and eligibility, although some release types do not appear and visibility can take around 48 hours. Verify the exact profile, audio version if previewable, track order, titles, roles, artwork, identifiers, explicit status, earliest territory date, release timing, and selected markets. Save evidence even when everything is correct.
How do corrections move through the same chain?
Report the defect to the data source that delivered it, normally the label or distributor, with the release, track, field, current value, correct value, platform, territory, evidence, and urgency. The source sends an update or replacement, and the platform processes it. Some changes are editable while others may require redelivery or re-upload. Spotify directs artists to their data source for metadata updates. Keep one case owner and do not close the issue until every affected surface is rechecked.
What should the team monitor on release day?
Open production links in signed-out or clean sessions where practical and check required territories, artist profiles, release and track pages, audio, artwork, credits, advisory labels, date, availability, smartlinks, and campaign destinations. Record first observation time and screenshots. If a defect appears, protect fans from broken paid links, classify scope, notify partners with facts, and open a complete case. A release can appear at different times or have a localized issue, so avoid a global conclusion from one device.
What supports this release-state model?
Practical notes
- Spotify describes distributor delivery, Upcoming visibility, artist mapping, release-detail updates, and post-release movement as separate operations.
- Apple describes a quality-assurance review of music, artwork, and metadata before content appears correctly in its services.
Source notes
- Spotify for Artists: Getting music on Spotify and Unreleased music in Spotify for Artists, accessed July 18, 2026.
- Apple: Apple Music Style Guide 2.4, accessed July 18, 2026.
Frequently asked questions
- What does delivered mean in a distributor dashboard?
- It generally means a package was sent to a service, not that the release is accepted, correctly mapped, scheduled, or live.
- Can an artist edit Spotify release metadata directly?
- Spotify currently directs artists to the label or distributor that supplied the data for release-detail changes.
- Why can one platform show the release before another?
- Services have independent ingestion, validation, review, mapping, scheduling, territory, and update processes, so their observable states can differ.
- Does a release missing from Upcoming mean it was not delivered?
- Not always. Spotify excludes some release types, visibility can lag, and the distributor must confirm the intended delivery and artist profile.
- What evidence helps resolve a delivery problem?
- Keep submission and delivery IDs, timestamps, source files, metadata, identifiers, platform URLs, territories, screenshots, current and expected values, and case history.