A release is not a single moment. It is a long sequence of small, easily forgotten tasks: contracts, artwork, credits, submissions, promo assets, pitches, accounting preparation. When those tasks live in different tools, things slip, and the slips are discovered by the distributor, the artist or the press, never by the label first. A release workflow is how you discover them yourself.
A release is a sequence, not a moment
Most release problems are timing problems. Artwork that arrives after the pitch deadline. Splits confirmed after registration. A pre-save link created the day before release. None of these are hard tasks; they are tasks that were not started early enough because nobody could see them coming. Laying the whole sequence out, with lead times, turns surprise into schedule.
Build a release template
Write down every task that happens between ‘we are releasing this’ and ‘first statement received’. Group them into phases, give each a lead time relative to release day, and assign a default owner role. That is your template. Every new release is a copy of it with dates filled in.
A first version usually looks like the list below. Most labels add and remove tasks after two or three releases, which is the point: the template is where the label's process lives.
- Twelve weeks out: contract signed, splits confirmed, release date agreed, catalog number assigned.
- Ten weeks out: masters delivered and checked, artwork brief sent.
- Eight weeks out: artwork approved, metadata and credits complete, label copy reviewed.
- Six weeks out: delivered to distributor, pre-save set up, pitch materials ready.
- Four weeks out: editorial pitches submitted, press and playlist outreach started.
- Release week: links checked on all platforms, announcement scheduled, artist assets shared.
- After release: performance reviewed, first statement reconciled, retrospective held.
Assign owners and deadlines
Every task needs one owner and one date. ‘The team’ does not deliver artwork; a named person does. Dates should be calculated from the release date so that moving the release moves every deadline with it, rather than requiring someone to re-plan by hand and miss one.
Collect assets early and in one place
Chasing assets is the most common reason releases slip. The fix is a visible list, per release, of what is required, what has arrived and who is responsible for the rest. When the artist can see the same list, the chasing largely stops, because ‘what do you still need from me?’ answers itself.
Keep the assets with the release, not in a shared drive folder that mirrors the release loosely. When the master is updated, the release should show the new file and the date it changed.
Make status visible
A release board that shows every active project, its phase, and anything overdue removes the most expensive meeting in a label: the weekly ‘where are we’ round. Everyone can see what is done, what is blocked and what is late, and the meeting becomes about decisions instead of updates.
Automate the nudges
Once tasks have owners and dates, reminders can be automatic. A task due in three days with no progress pings its owner. An asset still missing two weeks before delivery pings the artist and the project lead. Nobody has to remember to chase, so chasing happens consistently and politely instead of in a panic.
Review after release
Hold a short retrospective after every release: what slipped, why, and which template task or lead time should change. Improve the template rather than blaming individuals. After a handful of cycles the template encodes everything the label has learned, and new team members inherit it on day one.