Clean releases in. Fewer rejections out.
Vandall is the workspace where labels and artists assemble a release. By the time it reaches your ingestion queue, metadata is validated, splits are signed, and every change has an audit trail. We hand off. We do not replace you.

Fewer rejections start upstream
Release-readiness scoring
Every project shows a readiness score. Missing ISRC, blank credits, and art under spec get flagged before the package leaves the label.
Structured metadata at the source
ISRC, ISWC, IPI, contributor roles, and credits captured in typed fields, not a Sheets tab the assistant edits the night before delivery.
Signed splits attached to every track
Split sheets e-signed in the project and exported as PDF or CSV. Publisher and admin downstream get a paper trail, not a screenshot.
Audit trail per upload
Who replaced the master, when, and from which device. If a DSP flags a takedown, you can show the chain of custody in seconds.
Read-only access for QC
Invite a distributor QC contact as read-only on a release. They review the package without editing it and without holding a seat on the label plan.
Bulk catalog import
Onboard a back-catalog from CSV on the Business plan. Existing ISRCs, credits, and contributors map into structured projects.
One link QC can answer on
Hand a share link to your QC team. See who opened it, how far they listened, and which version they reviewed, without chasing email replies.
Partner, not competitor
Vandall does not deliver to DSPs. The release leaves our platform clean and reaches your pipeline. Your relationship with the label stays yours.
Before delivery
See the gaps before your QC team does.
Open any project and the readiness panel shows what is missing: ISRC, ISWC, contributor IPIs, art at spec, lyrics, language code. The label fixes it inside Vandall before the package ever hits your ingestion queue.
- Field-level checks for ISRC, ISWC, IPI, and language code.
- Cover art validated against 3000x3000 spec.
- Contributor roles and credits required before the project ships.

Metadata
Codes captured at the session, not the night before delivery.
ISRC and ISWC live in typed fields next to the master. Contributor IPIs are tied to the artist record, not retyped per release. When the package reaches you, the fields are filled in by the people who know the answer.
- Typed ISRC, ISWC, and language fields with format validation.
- Contributor IPIs persist across every project the artist appears on.
- Credits captured per role: performer, writer, producer, mixer, mastering.

What lands in your ingest
Metadata in spec
- ISRC and ISWC captured in typed fields with format validation.
- Contributor IPIs tied to artist records, not retyped per release.
- Cover art validated against 3000x3000 spec before hand-off.
- Language code, primary genre, and explicit flag set on every track.
Paperwork attached
- Split sheets e-signed with full audit trail per signature.
- Producer, writer, and master splits on the same agreement flow.
- Signed PDF and CSV exports ready for the publishing admin.
- Master ownership and label rights captured before delivery.
Hand-off you can trust
- Release-readiness score visible to label and QC alike.
- Read-only project access for distributor QC contacts.
- The link is version-specific, so a comment on it is a comment on that version.
- Vandall stops at hand-off. It does not deliver to DSPs, so your client relationships stay yours.
Splits
Signed paperwork attached to the audio.
Splits live with the project, not in a separate DocuSign folder. Every contributor signs from their phone, the PDF attaches to the release, and the CSV exports straight to whichever publishing admin the label uses. When a sync deal arrives, no one is hunting for who agreed to what.
- Auto-rebalance keeps every sheet at exactly 100%.
- Signers confirm with a click. No Vandall account needed.
- Audit trail captures IPI, IP, device, and timestamp per signature.

Catalog
Bulk import the back catalog without retyping.
On the Business plan, labels import an existing catalog from CSV. ISRCs, contributors, and credits map into structured projects. The historical work that used to live in a Sheets tab arrives in your pipeline with the same shape as everything new.
- CSV import on the Business plan covers existing ISRCs and contributors.
- Each row becomes a project with masters, splits, and metadata in place.
- Onboarding a label catalog stops being a six-week project.

Hand-off
A read-only seat at the table for your QC.
Invite your QC contact as read-only on a release. They open the share link, hear the master, see the metadata and the signed splits, and confirm what they need, without editing the project, without holding a seat on the label plan, and without you ever needing to chase a status email.
- Read-only role for distributor QC on a per-project basis.
- QC comments land on the package itself, so questions are answered in place.
- Vandall does not deliver to DSPs. The package goes to your pipeline.

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
Do you replace our distributor?
No. Vandall is the collaboration and metadata layer the label or artist uses before delivery. The release leaves Vandall and reaches your existing pipeline. We do not deliver to DSPs and we do not own the artist relationship. Your business does not change.
How do labels send a release package to us?
A label invites a distributor contact as a read-only collaborator on the project, or shares a project link. Your QC team sees the master, the metadata, the signed splits, and the readiness score in one place. Nothing is emailed as an attachment.
What metadata is validated before hand-off?
ISRC and ISWC format, contributor IPIs, cover art at 3000x3000, language code, primary genre, explicit flag, and per-role credits. The release-readiness panel flags every gap inside the project so the label fixes it before the package ever hits your queue.
Can we onboard an existing back catalog?
Yes. CSV import is available on the Business plan. Existing ISRCs, contributors, credits, and splits map into structured projects so historical and new work share the same shape in your pipeline.
Do you generate pre-save links or schedule DSP delivery?
No. Pre-save and DSP delivery sit with you. Vandall focuses on the upstream problem of clean metadata, signed splits, and audit trail, so the work that reaches your delivery tool is not the work breaking it.
How is the audit trail captured?
Every upload, metadata change, and signature is timestamped against the user, IP, and device. If a DSP flags a takedown or a contributor disputes a split six months later, the chain of custody is in the project, not in a Slack thread.
Guides on delivery and metadata
- GuideMastering a music release for deliveryThe pre-delivery checklist labels miss most often: metadata, art spec, credits, and the order they should arrive in.
- GuideISRC codes explainedWhat an ISRC is, who issues it, and where rejections come from when the format is off by a single character.
- Use caseMigrate a catalog from SheetsHow a label moves an existing back catalog into structured projects without retyping every ISRC.
- Use caseFile sharing on share linksA comment thread per link, useful when you need to show which version QC signed off.
- NicheFor record labelsThe same project a distributor receives starts here: catalog, roster, structured metadata, and signed splits in one place.
- NicheFor publishersWhere the publishing admin picks up the signed PDF and CSV after the project is delivered to the distributor.
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










