Every release as a stack of typed deliverables.
A release is not just a date and a tracklist. It is a stack of typed deliverables, each with its own done-criteria. Labelflow's release workflow knows what shape a release is, and tells you, at any moment, exactly how ready it is.
Most labels track releases in three tools that were not built for releases.
A spreadsheet for the schedule, a chat thread for the chasing, a folder for the files, and a calendar reminder that fires whether or not anything is actually late. Each one holds part of the truth and none of them holds it all.
The cost is not the admin. It is that nobody can answer the only question that matters on a Wednesday: is this release going to ship on Friday, and if not, what exactly is holding it.
The spine the rest of Labelflow attaches to.
Four properties, and everything else in the product hangs off them.
Master, artwork, metadata, distribution, communications. Not a checklist of strings on a page, but typed deliverables that know their own done-criteria. Each one has explicit ready-when logic.
The release knows what it is still waiting on. Artist info incomplete? It tells you which fields. Master not yet QC'd? Highlighted. Friday-night fixes become visible long before they become emergencies.
One number aggregates every deliverable's status, and the colour tells you which kind of number it is. The Monday morning status meeting takes thirty seconds.
Every release lives in one place. No spreadsheet drift, no two versions of the metadata in two systems. Every other feature in Labelflow attaches to this one.
The week reads itself.
You open the release, not the spreadsheet. The deliverables are already there, typed, with the ones that are blocked at the top and a readiness number that means something specific.
The chasing fires on state, not on dates. Communications reads the same deliverables, so a premaster reminder goes out because the premaster is genuinely missing, not because a static schedule said Tuesday.
Nothing is re-keyed anywhere else. Deliverables tracking, distribution coordination, analytics and the artist report all read this record rather than a copy of it.
For anyone holding a release calendar in their head.
If you ship one release a quarter you can hold it in your head, and you probably should. From about one release a month, the head stops being a reliable place to keep it, and the cost shows up as a Friday you did not plan for.
Included on both plans. The release workflow is the foundation of Labelflow, so it is in every Label and Studio tier at no add-on cost. Every other feature, core or paid, attaches to it.