Release workflows and quality control

The lifecycle

1. Customer creates a release: metadata, audio, artwork, rights, destinations.
2. Automatic validation blocks obvious problems before submission is possible.
3. Customer submits.
4. Your team reviews in Release Queue.
5. Approve, or return with changes. Returned releases go back to the customer with the flagged fields.
6. Delivery to selected stores.
7. Stores publish on their own schedules.

Steps 4 and 6 are yours. Step 7 is never anyone's.

Where your judgment matters

Automatic validation catches structural problems: missing fields, wrong formats, files that failed to process. It cannot tell you the audio on track 3 is the wrong mix, that the artwork has a store logo in the corner, or that the featured artist is not really on the record.

That is what human review is for, and it is why an approved release under your brand is your quality statement.

Handling resubmissions

Each resubmission re-enters the queue. Getting a return right the first time saves two cycles: specify exactly which field, what is wrong, and what it should be.

Changes after delivery

Some fields can be corrected and redelivered; others cannot. Stores apply changes on their own schedule, and a correction is never as clean as getting it right before approval. Treat approval as the last cheap moment.

Setting customer expectations

Publish your own review turnaround and hold to it. The most common enterprise support load is customers asking where their release is, and a stated turnaround removes most of it. Point them at Distribution and dates for the store-side timing you do not control.