One package. Everything the release needs.
Masters, artwork, metadata, credits, and the signed agreements, bundled from the project, checked for gaps, published as a locked snapshot, and handed over as one link.
Everything the partner opens
Everything in one deliverable
The package pulls the audio masters, artwork, metadata, credits, and signed agreements straight from the project. Nothing gets re-collected by email.
Gaps flagged before publish
The Release Package tab shows a checklist of what goes out. Missing items are flagged with a warning so you fix them before the partner sees them.
A snapshot that stays put
Publishing locks the package. Later edits to the project do not change the published version, so what the distributor received stays what they received.
Hand over one link
Send the share link and the recipient gets read-only access to every asset: masters, artwork, metadata, and signed agreement PDFs.
The whole thing as one ZIP
Partners who want files get the full package as a single download instead of a folder reassembled from attachments.
Republish when things change
Need to change a published package? Republish and send the new link. The old one keeps working for historical reference.
Assemble
The project already holds the package.
A release handover usually means re-collecting what already exists: the master from one folder, artwork from another, splits from a PDF in someone’s inbox. On Vandall the project is the source. Open the Release Package tab and the checklist shows exactly what will go out, section by section.
- Audio masters, artwork, metadata, credits, and signed agreements in one view.
- Each section reads straight from the project — no duplicate uploads.
- Missing items are flagged with a warning before you can call it done.
Check
Every flagged gap links to its fix.
A flagged section links back to the tab that owns it. Metadata missing a code? Fix it on the Metadata tab, where ISRC and contributor fields are structured and validated. An unsigned split? The Agreements tab shows who has not confirmed yet. When every section is green, the package is publishable.
- Structured metadata with validation, so bad ISRCs are caught before handover.
- Signed split sheets attach as locked PDFs on the project.
- Credits and contributors travel with the release, not in a side document.
The handover itself
In the package
- Audio masters at original quality.
- Artwork and release metadata, structured and validated.
- Credits and contributors as recorded on the project.
- Signed agreement PDFs attached to the release.
Before it ships
- A checklist of every section the package will include.
- Missing items flagged with a warning, not discovered by the partner.
- Fixes made on the tab that owns the data, once.
- Publish only when every section is green.
After you publish
- The package is a locked snapshot. Later edits do not touch it.
- Share link with read-only access, or one ZIP download.
- Republish to amend; the old link keeps working for reference.
- The same link serves distribution, PR, and the label.
Publish
Publish it once. It stays published.
Confirm publishing and the package becomes a stable snapshot. The project keeps moving with new versions and new comments, but the published package does not change underneath the partner who received it. If the release genuinely changes, republish and send the new link; the old one keeps working for reference.
- Published packages are immutable snapshots, not live views.
- Republishing creates a new version without breaking the old link.
- Publish when the release is distribution-ready: it is the finish line, not a draft.
Deliver
The partner opens a page, not a folder.
The recipient gets a share link that opens in the browser with read-only access to every asset: masters, artwork, metadata, and signed agreement PDFs, exactly as published. Partners who want local files download the whole package as one ZIP. Either way, nobody reassembles a release from six attachments.
- Read-only access: partners see everything, change nothing.
- One-click ZIP download of the full package.
- Send the same link to distribution, PR, and the label without re-exporting.
Check the roster from anywhere
Vandall Business runs in a browser, so the release calendar and the task board are as available on the way to a meeting as they are at the desk.
Questions people ask first
What exactly goes into a release package?
- Audio masters, artwork, metadata, credits, and the signed agreements on the project. The Release Package tab shows the full checklist before you publish, and flags anything missing.
Can I edit a package after publishing?
- No, and that is the point. A published package is a stable snapshot, so the version your distributor received never changes underneath them. To amend, republish and send the new link; the old one keeps working for historical reference.
What does the recipient need?
- Just the link. It opens in the browser with read-only access to every asset. Partners who want local files can download the full package as one ZIP.
How do the signed splits get in?
- Agreements are signed on the project itself: each contributor confirms from a link, and the sheet locks as a PDF. The package includes those signed PDFs automatically.
When should I publish?
- When the release is distribution-ready. Publishing locks the snapshot, so it is the finish line of the project, not a draft you circulate for comments.
Reading on release delivery
- GuideMastering music release preparationA release-readiness checklist that maps directly to the package view.
- GuideISRC codes explainedThe code every master in the package needs, and how to get it right.
- ToolMusic release checklistA free checklist of what a release needs before it ships.
- Use caseCatalog management use caseThe catalog the packages come from — filters, views, and CSV export.
- Use caseSplit sheets use caseHow the signed agreements in the package get made.
- AudienceFor labelsThe label view: roster, releases, and rights in one place.
- AudienceFor distributorsWhat clean, complete releases look like from the receiving end.
Trusted by creators globally
Creators on every continent use Vandall to share,
collaborate, and close deals, no matter the timezone.
0+
Projects created
50+
Countries