Publish a Release and Hand Off to Your Label
From release readiness to the published package: confirm requirements, publish, and send the share link to your label.
In short
- Release readiness percentage tells you what's blocking.
- Published locks the package. Edits after require a new handoff.
- Your share link never expires and needs no account.
- 1
Open the Send tab
Navigate to your project and tap Send. The top of the tab shows release readiness as a percentage — this rolls up metadata, files, credits, and agreements. Anything below 100% means something is blocking a Published status.

Green readiness, Publish as Release enabled. - 2
Work through Release Requirements
Tap Release Requirements. The checklist is split by mode: Draft needs only one uploaded audio file, Published needs complete metadata, credits, and signed agreements. Each missing item links straight to the section to fix.

Each row links back to the tab that owns the missing field. - 3
Publish as Release
Once Published requirements are green, tap "Publish as Release." The project is bundled into a release package — files, metadata, credits, agreement status — and locked. Your label sees the package in their dashboard immediately.

Published = locked snapshot. Further edits happen through your label. - 5
Confirm your label picked it up
The label sees the release land in their dashboard in real time. If they confirm receipt via comment or dashboard notification, the handoff is complete. Any changes from this point go through your label, not direct re-publishes.
Tips
- Send as Draft first if you want feedback; send as Release when paperwork is done.
- Once published, the release is locked. Edits require a new version conversation with your label.
Was this guide helpful?
If something's unclear or missing, send us a note — we'll reply with the right answer or update the guide.
