The 8-Week Release Timeline

An eight-week release plan gives you enough room to finish the recording, confirm its identity, deliver it to services, check how it appears, and prepare listeners for launch. It is a planning framework—not a universal platform or industry deadline. Distributor processing, DSP review, territory, metadata, and your rights setup can all change the amount of time you need. The safest approach is to choose a release date, work backward, and build in contingency rather than treating every date below as mandatory.

The central deadline is delivery. Spotify says independent artists generally use a distributor or label distributor to deliver music to Spotify, while distributors may also handle delivery to other streaming services and pay royalties earned from streams. The exact relationship, fees, commissions, and services vary by provider. See Getting music on Spotify and the Spotify for Artists Provider Directory for the platform’s current guidance.

First, understand the route

A release travels through several connected stages:

1. You complete and approve the recording.
2. You preserve the recording’s identity and assign or confirm its ISRC.
3. You prepare the work, recording, songwriter, performer, contributor, and identifier metadata.
4. You upload the release to your distributor with a future date.
5. The distributor delivers it to DSPs and stores.
6. Services process, review, and display the release.
7. You verify the delivered listing before launch.
8. You pitch and promote the release within the opportunities actually available to you.

The order matters. A last-minute creative change can affect the recording identity, metadata, identifier, delivery package, and every downstream check. An early upload, meanwhile, does not guarantee that every service will make the release live at exactly the same moment. DistroKid specifically warns that service processing times and curated-service acceptance can be outside its direct control, which is why it recommends advance delivery and a custom future release date when synchronized availability matters. Read How Long Does It Take for My Music to Be Available in Streaming Services? for distributor-specific guidance.

Week 8: choose the date and lock the plan

Start with a release date that leaves room for the work still unfinished. Write down the intended title, version, principal artist name, track list, release type, target services, territory assumptions, and the person responsible for approvals. If the release includes several tracks, treat every track as a separate recording identity even when the tracks belong to one release package.

At this stage, decide what “ready” means. The audio should be in its intended final state, the artwork and release text should be approved for submission, and the rights and contributor information you plan to provide should be gathered. The evidence supports a careful metadata process, but it does not establish one universal artwork specification, promotional calendar, or distributor checklist. Use your distributor’s current requirements for those items.

A useful decision rule is simple: if changing something would require a new upload, new identifier, or new metadata review, do not call the release locked yet. An eight-week runway is illustrative. Spotify’s guidance establishes a seven-day minimum for particular Spotify workflows, and DistroKid recommends about four weeks for synchronized availability; neither source creates a universal eight-week rule. See Pitching music to Spotify playlist editors and Uploading.

Week 7: finish the recording and preserve its identity

Use this week to complete the final recording decisions. Confirm the approved master, its version title, principal artist, duration, recording type, and intended year of first publication. Keep the final audio file and the reference information together in a project record that will remain available to your team.

This is also the right point to distinguish a musical work from a sound recording. The work is the underlying composition; the sound recording is the particular recorded performance; the track is the service-facing presentation that may connect those pieces. The distinction matters because a changed recording is not merely a spelling correction. A new performance, materially different version, or other change may need its own treatment under the relevant delivery and identifier rules.

The International ISRC Handbook says an ISRC should be assigned when the creative processes are complete and the release decision has been made. It also explains that the code is bound to a recording through reference details such as title, version, artist, duration, type, and first-publication year. Consult the International Standard Recording Code (ISRC) Handbook – 4th Edition. Assigning an ISRC is distinct from copyright registration and does not itself establish ownership.

Do not assign an identifier to a recording that is still changing simply to make the calendar look complete. Instead, finish the creative process, make the release decision, then record the identifier alongside the exact reference metadata. If you later replace the audio, stop and ask your distributor or rights administrator whether the identifier and submission need to change.

Week 6: assemble the metadata package

Create one authoritative metadata sheet before you upload. At minimum, check the recording title, version title where relevant, principal artist, duration, recording type, and first-publication year against the final audio and the identifier record. Then add the information needed to represent the musical work and its contributors: songwriters, performers, producers, featured artists, and other contributors required by your delivery workflow.

The UK Industry Agreement on Music Streaming Metadata recommends complete work and recording registrations near release, accurate recording and contributor metadata, identifiers where available, and accurate display of credits. It is a UK industry agreement and recommendation, not universally binding law or a global platform specification. Its principles are still useful as a quality-control checklist, but you should not present them as a worldwide legal requirement. Read the United Kingdom Industry Agreement on Music Streaming Metadata.

Have at least two people review names, roles, spellings, featured-artist formatting, version labels, and identifiers if your project allows it. Compare the metadata sheet with the audio file, your contributor records, and the distributor form. Do not guess at a credit because a field is required. Resolve uncertainty with the appropriate contributor, rights administrator, or distributor process before submission.

A practical “single source of truth” is a folder or document containing the approved master, the release metadata, the ISRC information, contributor details, and the final submission values. The point is not to create paperwork for its own sake. It is to prevent small inconsistencies from being copied into multiple systems.

Week 5: submit to the distributor

Upload the release with the chosen future date. Select the correct release and track information, enter the identifiers, and review every field before final submission. Confirm which stores and DSPs the distributor will deliver to, how territories are handled, and whether any service-specific options affect timing. These details vary by distributor and are not established by the evidence packet as universal rules.

DistroKid recommends uploading about four weeks in advance when synchronized availability across services matters. It also explains that future release-date controls can be used to plan availability and that pre-orders apply only to certain participating stores rather than streaming services. These are DistroKid-specific statements, so use them as an example of why your own provider’s instructions matter. See Uploading.

Save the distributor’s confirmation, release ID, submitted date, and exact metadata snapshot. If the distributor reports an error, correct it promptly and recheck whether the correction changes delivery timing. Do not assume that a successful upload means the release is already available everywhere. It means the delivery process has started.

Week 4: confirm delivery and begin the verification loop

By this point, the release should be in the distributor’s processing and delivery pipeline. Check the dashboard for rejected fields, missing identifiers, processing notices, or service-specific exceptions. If your distributor provides delivery statuses, record them. If it provides estimated processing ranges, treat those as estimates rather than promises.

DistroKid’s guidance gives examples of variable service timing, including stated ranges of two to five days for Spotify and one to seven days for Apple Music/iTunes, while noting that some Apple reviews may add one to two weeks. These figures are distributor-specific and time-sensitive; they should not be converted into a universal timetable. The broader planning lesson is to preserve contingency time and contact the distributor when the status does not match its current guidance. The relevant source is How Long Does It Take for My Music to Be Available in Streaming Services?.

Once a service listing appears, verify the title, artist page, track order, version, duration, credits, and identifier where visible. Look for accidental duplicate artist pages, incorrect contributor roles, or a release attached to the wrong recording. If something is wrong, document the exact problem and use the distributor’s correction process. Keep checking because one service may display the release before another.

Week 3: prepare the Spotify pitch and listener path

If Spotify editorial pitching is part of your plan, use Spotify for Artists to pitch an upcoming unreleased song. Spotify recommends pitching at least seven days before release. That timing also supports follower Release Radar inclusion when the other eligibility conditions are satisfied. Read Pitching music to Spotify playlist editors for the current workflow.

The pitch is an opportunity to provide context, not a placement order. Spotify states that editorial placement is not guaranteed. Do not promise a playlist feature to collaborators or listeners, and do not build the entire campaign around an outcome no platform has promised.

Release Radar has additional limits. Spotify says first-week eligibility requires delivery at least seven days before release, but a listener may not receive a track if they have already heard it. The rules can also exclude Various Artists releases, some re-releases and alternative versions, and limit a listener to one song per artist per week. These are Spotify-specific constraints, not general DSP rules. See Getting music on Release Radar.

Use this week to make the listener path clear: decide where people should find the release, what link or destination you will share, and which collaborators need approved information. Those campaign choices are optional tactics, not requirements established by the packet. The evidence supports timing and eligibility checks; it does not prescribe a particular social platform, advertising budget, content schedule, or number of posts.

Week 2: run the pre-release audit

Perform a full rehearsal of release day. Confirm that the distributor still shows the intended future date. Check the live or preview listings that are available. Compare the final service display with your authoritative metadata sheet. Verify that the ISRC and recording details remain associated with the intended master, and confirm that all available work and contributor information is accurate.

This is the moment to resolve discrepancies, not the morning of release. Recheck the artist name exactly as it should appear, track titles and versions, featured artists, songwriter and performer credits, contributor roles, release order, duration, and any displayed identifiers. The metadata agreement’s recommendation to pass complete and accurate work, recording, contributor, and identifier data near release makes this audit especially important, while its UK jurisdiction means it should be described as guidance rather than universal law. See United Kingdom Industry Agreement on Music Streaming Metadata.

Create a short issue list with three categories: must fix before release, should fix through the normal correction process, and cosmetic or optional. If a problem affects the identity of the recording, the release date, a contributor credit, or an identifier, treat it as a priority and ask the relevant provider how to proceed.

Week 1: confirm the final countdown

Make sure the Spotify pitch, if applicable, was submitted at least seven days before release. Confirm delivery status and keep the distributor’s current instructions nearby. Check that your release is not relying on a pre-order assumption that applies only to participating stores and not to streaming services.

Prepare the final announcement and any approved materials. Keep the language accurate: say that you are releasing on the planned date, not that a platform will place the song on an editorial playlist. Make sure collaborators know the correct title, artist presentation, release date, and destination. If the release has multiple territories or rights arrangements, confirm that your intended availability matches the distributor’s configuration.

Do one last operational check: who will monitor the listings, who will respond to a delivery problem, and where will you record evidence of what appeared? A simple owner and escalation path can prevent a small display error from becoming an untracked issue.

Release day: verify, communicate, and document

Check the major service listings rather than assuming synchronization. Confirm that the release is live where expected, appears under the correct artist identity, and matches the approved metadata. If one service is late, remember that processing and review can vary. Contact the distributor with the release ID, affected service, intended date, and exact status; avoid uploading duplicate versions unless the provider tells you to do so.

Share the release through your chosen channels and direct listeners to the correct destination. Keep a record of the live links and any discrepancies. The purpose of this record is continuity: it helps you distinguish a service display issue from a metadata issue and gives the distributor concrete information if a correction is needed.

Week +1: review the outcome and preserve the record

After launch, check whether the release remains correctly displayed and whether credits and identifiers are visible as expected. Note which services were available on time and whether any required corrections were opened. Preserve the final master, submitted metadata, distributor confirmation, service links, correction correspondence, and the date of each check.

Review the process rather than treating the result as a verdict on the music. Which fields caused confusion? Which delivery status needed more time? Did the chosen release date leave enough contingency? Did the Spotify timing and eligibility limits affect expectations? Use those answers to improve the next calendar.

A compact working checklist

At production lock: approve the final recording, confirm its version and identity, and preserve the reference metadata.

After the creative decision: assign or confirm the ISRC, remembering that ISRC administration is not copyright registration.

Before submission: complete accurate work, recording, songwriter, performer, contributor, and identifier metadata where available.

About four weeks before release: use your distributor’s current delivery guidance; DistroKid recommends this buffer for synchronized availability, but it is not a universal benchmark.

At least seven days before release on Spotify: deliver the music and submit the Spotify for Artists pitch if applicable, while recognizing that Release Radar eligibility has limits and editorial placement is not guaranteed.

Before and after launch: verify service displays, record discrepancies, and use the distributor’s correction process.

The eight-week calendar is therefore best understood as a buffer map. It gives production and metadata room to settle, delivery room to process, and verification room to catch errors. The exact route depends on your distributor, DSPs, territories, and rights setup. Check current provider instructions close to submission because platform guidance and processing conditions can change. Open Music Business is educational content, not individualized legal, financial, tax, contract, or royalty advice.