One file per artist holds the profiles, the proof, the approved release versions and every correction. Four steps take a release that landed on the wrong page from scattered emails to a checked fix.
Identity, proof, approvals, and corrections belong to the same record.
01
Confirm identity
Record the artist's streaming profiles and the proof behind each one. Someone other than the person who added the proof reviews it.
02
Approve exact versions
The artist approves a specific release version and its destination profiles. A later version needs its own approval.
03
Track each fix
Open a correction case with one request per platform. Record each reply, and close only after the change is checked, not just requested.
04
Carry the proof
Every action leaves a dated entry. Export a printable or structured case packet for the next handoff.
Step by step
What happens at each step
01 / Confirm identity
List the pages that are really the artist's
Add each streaming profile, one service at a time. Use the artist profile URL, not a song or album link, and add the platform artist ID if you have it. A reviewer examines the sources that connect the artist to that page. Confirmation belongs to that profile; other platforms keep their own review status.
02 / Approve exact versions
Say yes to one exact version
A release version is the recordings, metadata, and artist destinations packaged for distribution. The artist approves one exact version and the profiles it belongs on. Changes create a new version for approval, and a later profile correction leaves the destinations approved in an earlier version as they were recorded.
03 / Track each fix
Follow each platform request to a checked result
A case is one correction. Describe the problem, link the affected release, and select the proof that supports it. Each platform gets its own request, which moves from Draft to Ready, Sent, Waiting for reply and Checked. A request reads Checked once someone has compared the platform's change with reviewed proof.
04 / Carry the proof
Hand over the whole history
Every action is logged with who did it and when. Export a case packet as printable HTML or structured JSON, with the selected proof, the approved version, the platform requests and the history. The export is logged too, so the next person can see what was handed over.
Who's involved
Four roles share one file
Up to four people share one file. Each can do only what the artist allows.
01 / Artist
Owns the file
The artist owns the file and decides who can help.
02 / Representative
Acts with permission
A manager or label person acting with the artist's permission.
03 / Suede operator
Files and records
A Suede team member who files the correction with the platform and records the reply.
04 / Independent reviewer
Checks the proof
A second person who reviews the proof and closes the case when Suede has a stake.
The real-world handoff
Where the record meets your distributor and the platforms
Your existing distributor stays in place
Approving a version records the decision in the artist's file. Delivery keeps running through the distributor you already use.
Each platform runs its own correction process
A person submits each request through the platform's supported correction process, then records the submission and the reply in the case.
A fix counts when it is checked
Exported means a packet was prepared. Sent means a request was recorded as sent. Checked means someone compared the platform's change with reviewed proof.
Legal questions stay with your agreements
Payments, licensing, and legal assignments stay with external providers and agreements. The record holds the claims, the proof and who reviewed each one.
Keep reading
Related pages
Correction cases across platforms
Correction cases with per-platform requests and replies.
Open the fictional artist file. Play the correction story as the artist, representative, operator, and reviewer each take their step, then export the case history.