Music Release Checklist: From Final Master to 30 Days After Release

A music release checklist works when every task carries a time window, an owner, a dependency, a status, and proof that it's actually done — not just a phase name. The checklist below runs from locking the final master through the 30-day post-release review, with a copyable table you can fill in for your own release.

Who this checklist is for

This is for an independent artist or manager who already has a release date and wants a single list to work from instead of piecing one together from a distributor's dashboard, a notes app, and a group chat. If you haven't set a release date, format, and goal yet, do that first — the timing windows below assume you have.

The release checklist

Each row is a real task with a named owner, what it depends on, and what counts as evidence it's actually finished — not just "in progress." Copy the table, fill in names and dates, and track status as the release moves.

Two windows on this list aren't arbitrary. If playlist placement matters to you, Spotify's own guidance is to deliver your music and submit your pitch at least seven days before release day so editors have time to listen — which is why the pitch row sits in the 2–1 week window, not release week itself. Distribution timing varies by platform too: DistroKid's current estimates put Apple Music at one to seven days, Spotify at two to five days, and Facebook/Instagram at one to two weeks after DistroKid's own review, with some Apple releases needing an extra one to two weeks of manual review and cover-song licensing taking up to fourteen business days. That's the reasoning behind uploading with a locked release date in the 2–1 week window rather than the final days before release — it leaves a buffer if something needs a correction or a slower manual pass.

The identifier and rights rows need the same care. The International ISRC Registration Authority describes an ISRC as the unique identifier assigned to a specific sound or music-video recording; confirm the code with the party assigning it rather than assuming every contributor should create one. The U.S. Copyright Office also distinguishes samples, which can implicate both a sound recording and the underlying musical work, from interpolations, which use newly recorded audio but can still implicate the underlying musical work. Rights and licensing depend on the work, territory, agreements, and intended use, so treat this checklist as an operational prompt—not legal, tax, or accounting advice—and get qualified advice where needed.

Download the release checklist as a CSV to fill in your own owners, dates, and evidence.

What "evidence of completion" actually means

A checked box means someone believes a task is done. Evidence of completion means you can point to the thing that proves it — a written split record, a distributor confirmation email, a locked metadata field, or an outreach log entry. That distinction matters most on rows where ambiguity can turn into release-week rework:

• Rights and metadata without a paper trail. A remembered conversation is difficult to audit later. Keep the contributors, agreed shares, identifiers, and any applicable licences in a written record reviewed by the relevant people.
• "Approved" artwork with no locked file. If the approved version isn't the same file that got delivered to the distributor, you find out during quality control — or after release.
• A checklist with no owner column. A task assigned only to "the team" lacks one clearly accountable person. Every row above names an owner.
• Skipping the day 30 review. The budget-versus-actual and retrospective rows are easy to drop once attention moves elsewhere, but they are the point where the team compares the plan with what happened.

How MNGR fits into this checklist

A spreadsheet can hold this table for one release, but it becomes harder to keep current once dates or metadata change and the release is competing with the rest of the operation. In the current MNGR release workspace, you can keep core release and track metadata, timeline dates, cover art, checklist items with due dates and open/done state, and more detailed release-linked tasks with due date, priority, status, and description. The downloadable CSV remains useful for the fuller owner, dependency, and evidence columns; put that context in the linked task description or keep the completed CSV with your release records rather than assuming MNGR stores a separate evidence field on every checklist item.

MNGR contacts can be linked to releases and carry an interaction history, which gives press and partner follow-up a durable record without promising an automatic follow-up reminder. Income and expense entries can also be linked to a release. MNGR does not currently calculate a dedicated release budget-versus-actual view, so keep the approved budget figure in your release records and compare it manually with the release-linked transactions during the day 30 review.

Copy the checklist above, fill in real owners and evidence for your next release, and keep it in one place you'll actually check through day 30.

Sources

1. Spotify for Artists: Pitching music and videos to playlist editors
2. DistroKid: How long does it take for my music to be available in streaming services?
3. International ISRC Registration Authority: ISRC Handbook
4. U.S. Copyright Office: Sampling, Interpolations, Beat Stores and More