Run the release, don't chase it.
Tasks, dates and owners on one side. Tracks, credits, identifiers and artwork on the other. One workspace, so the plan and the metadata are never two different truths.
The release tells you what is still missing.
Not a checklist someone maintains in a doc. The workspace knows what a complete release looks like, and what has not been done yet is a list rather than a worry.
Project management, for a release
Tasks with owners and dates. Who is doing it, by when, and whether it is done — on the release, not in a project tool that has never heard of a release date.
A task catalog to start from. Pull in the standard set for this kind of release rather than rebuilding the same thirty steps from memory every time.
Progress by category. Assets, metadata, marketing, delivery — each showing how far through it is, so "are we ready" has an answer before the week of.
A timeline everyone works from. The announce, the pre-save, the video, the release date: one plan on the release itself, not four calendars and a group chat.
Metadata management, in the same place
Tracks with everything a DSP will ask for. Version, contributors, ISRC, explicit flag — held against the recording rather than typed into a delivery form and forgotten.
Identifiers you generate, not chase. ISRCs from your own registrant prefix and catalog numbers to your convention, issued when you need them rather than kept in a spreadsheet somebody owns.
Credits that survive the release. Primary and featured artists, contributors and their roles, attached to the recording — because every royalty question in two years is asked about the recording.
Every asset a release needs, with a place to put it. Cover art and tracklist art, press and behind-the-scenes photos, social assets and banners, visualizer, lyric video, live video, teaser, official video, merch design, liner notes, bio and the audio itself.
Territories at the level you actually need. Worldwide, a region, or a specific list of countries.
Why release coordination goes wrong
The plan and the metadata live apart. Tasks in one tool, track details in a spreadsheet, artwork in a drive. The person chasing the plan cannot see whether the thing being chased is actually complete.
The information arrives from six people and none of them own the whole thing. The mixer has the audio, the designer has the artwork, the publisher has the splits. Whoever assembles it is doing data entry from four inboxes.
Nobody finds the missing field until the deadline. A blank ISRC, an unset territory, artwork at the wrong dimensions — cheap in week one, expensive in the last hour.
What was true at release stops being findable a year later. Who produced it, which version this was, what the catalog number was. The release goes out, the folder goes cold, and the credits get reconstructed from memory.
Four things worth getting right
Open the release the day it is greenlit, not the week before. The cost of an empty field is proportional to how late you find it.
Give every task an owner, including yours. Unowned tasks are the ones that turn up undone on the Friday.
Assign the identifiers early. An ISRC costs nothing to generate and everything to change once something has been delivered against it.
Let each person fill in their own part. One coordinator transcribing six people's answers is the bottleneck and the error source at once.
Common questions
Is this a project management tool or a metadata tool?
Both, and deliberately. Tasks, owners, dates and progress sit on the same release as the tracks, credits, identifiers and artwork — so the person chasing the plan can see whether the thing being chased is actually finished.
Do we have to build the task list every time?
No. There is a catalog of standard release tasks to pull from, which you then adjust. Rebuilding the same thirty steps from memory for every release is the thing it removes.
Does this replace my distributor?
No, and it is not trying to. This is where the release gets planned and assembled so that what you hand over is complete and consistent. You keep whichever distributor you use.
Can I let someone see one release without seeing everything?
Yes. People are invited to a release, so a designer, a publicist or an artist's team member can work on what they are involved in without access to the rest of the workspace.
One workspace. The plan and the package in the same place.
