Label digital asset organisation checklist for UK labels

Label manager reviewing music asset checklist

TL;DR:

Creating a comprehensive release manifest and registering all identifiers before delivery ensures proper royalty collection and distributor acceptance. Accurate metadata, consistent file naming, and embedding identifiers in master files prevent rejected submissions and unmatched royalties. Using standardized templates and strict data discipline simplifies tracking, speeds up payouts, and maintains catalogue integrity.

Create a release manifest, assign ISRCs and a UPC, register ISWCs and IPI numbers, embed core identifiers in your master files, and store everything with strict naming and backups — that is the one-line action plan. Do it before delivery, and distributors accept your files; collection societies at PRS for Music, PPL and MCPS can match and pay you. Skip any step, and the UK Music Metadata Agreement places the liability squarely on the party that created the data — your label.

Here is the 10-point label digital asset organisation checklist to copy into your workflow:

Assign ISRCs to every recording and a UPC/EAN to the release.
Register each composition at PRS for Music and obtain the ISWC.
Confirm IPI/CAE numbers for every writer and publisher.
Embed ISRC, artist name, track title and publisher in BWF/XMP metadata.
Name every file using the standard formula before delivery.
Check artwork is minimum 3000×3000px RGB JPG or PNG.
Validate audio specs: WAV or FLAC, minimum 16-bit/44.1kHz.
Complete and validate the DDEX-inspired release manifest (CSV).
Register performers at PPL before the release date.
Run a final manifest check for blank ISWC/IPI fields before submitting.

Musicvideomarketplace supports the visual asset side of this workflow, producing export-ready music videos and short social clips that slot directly into the visuals folder of your release structure.

What does a phase-by-phase release checklist look like?
What metadata fields must you capture, and how does a DDEX-inspired manifest look?
How should you name, structure and back up your files?
Who registers what at PRS for Music, PPL, MCPS and BPI?
How do you validate a delivery and recover from a rejection?
Where can you find copy-and-paste templates for release admin?
Key takeaways
Why metadata discipline is now a business decision, not an admin task
Get your video assets release-ready with Musicvideomarketplace
Useful sources to bookmark

What does a phase-by-phase release checklist look like?

Metadata errors at release are the hardest to fix — they cause royalty misattribution, chart ineligibility and distribution takedowns. The table below maps each phase to its tasks, owner and typical UK timeline phases without specific numeric weeks or days.

Labels should establish ISRC management and royalty-tracking processes before their first release to preserve catalogue continuity. Unmatched revenue from the first 90 days is recoverable, but it requires manual intervention with the collection society — time no manager wants to spend.

What metadata fields must you capture, and how does a DDEX-inspired manifest look?

The UK Metadata Agreement defines two levels of required data: recording-level and work-level. Miss either, and your delivery is incomplete.

Recording-level fields: release title, track title, recording artist (exact spelling matching PRS/PPL entries), ISRC, UPC/EAN, track duration, file format, file name, language, explicit content flag.

Work-level fields: work title, ISWC, composers and lyricists with IPI/CAE numbers, publisher name, publisher IPI/ISNI, writer splits and co-writer percentage shares.

The sample manifest below shows how these fields map across a single CSV row, so distributors and collection societies can match rights without manual chasing.

Column	Example value
release_title	Midnight Circuit EP
track_title	Neon Drift
recording_artist	Asha Vega
isrc	GBxxxxxxx
upc_ean	5060xxxxxxxxx
file_format	WAV
file_name	MidnightCircuit_NeonDrift_Master_v1_20260301.wav
iswc	T-xxxxxxxxx-x
composer_name	Asha Vega
composer_ipi	00xxxxxxxxx
writer_split_pct	100
publisher_name	Circuit Music Ltd
publisher_ipi	00xxxxxxxxx
explicit	No

Using a standardised manifest inspired by DDEX lets you export a single CSV that matches distributor and collection-society fields, cutting rework and improving payment matches.

Pre-delivery validation checklist:

All ISWC and IPI fields populated — no blanks.
Artist name spelling identical across manifest, PRS portal and distributor dashboard.
Artwork file confirmed at minimum 3000×3000px.
ISRC visible in distributor dashboard before submission.

Pro Tip: Embed ISRC, artist name, track title and publisher directly into BWF/XMP chunks so the data travels with the audio file even if the manifest is separated from the asset — a useful fallback when files are shared outside your DAM.

How should you name, structure and back up your files?

A consistent folder structure prevents lost files and version confusion. The template below scales from a single to a full catalogue.

Hands organizing music label files on desk

/2026-MidnightCircuit/
  01-demos/
  02-sessions/
  03-stems/
  04-mixes/
  05-masters/
  06-visuals/
  07-marketing/
  08-admin/

AES delivery recommendations advise clear labelling of session files, delivering stems and mix variants with session documentation, and avoiding illegal characters in filenames. Apply this naming formula to every asset:

[Project]_[AssetType]_[Role]_[v#]_[YYYYMMDD].ext

Example: MidnightCircuit_NeonDrift_Master_v1_20260301.wav

Banned characters: : * ? < > " | / \ emojis — these break distributor ingest systems.

Version control rules: use v1, v2 for iterative changes; reserve Final only for the approved master; use Final_Rev1 for any subsequent change. YYYYMMDD sorts files chronologically without any additional tooling.

Backup follows the 3-2-1 rule: three copies, on two different media, with one stored offsite. Cloud sync (Google Drive, Dropbox, or a dedicated DAM) handles active work; a separate archival drive or cold-storage service holds masters. Set folder permissions so collaborators can read but not overwrite master files.

Pro Tip: Always export stems as full-duration files, including lead-in silence, so they align on the timeline without manual nudging. Deliver both wet and dry variants where the mix engineer has processed individual elements.

Who registers what at PRS for Music, PPL, MCPS and BPI?

Each UK body has a distinct role, and confusing them is a common source of missed royalties.

PRS for Music handles composition rights. Register the work here to obtain an ISWC and link writer IPI numbers. PRS collects performing and mechanical royalties on behalf of writers and publishers.

PPL handles neighbouring rights for performers and record labels. PPL’s repertoire data policy specifies the recording and rights data attributes it expects; missing or invalid data is treated as unenforceable for payment. Register recordings and performer line-ups at PPL before release.

MCPS (administered through PRS for Music) handles mechanical licensing for physical and digital reproductions. If your distributor does not cover mechanical licensing automatically, confirm the arrangement before release.

BPI is the UK ISRC agency. If you are self-managing ISRCs rather than obtaining them through a distributor, contact BPI to set up a registrant code. Costs may arise at this stage depending on your route.

Order of operations: assign ISRCs and UPC first, then register the composition at PRS and secure ISWC/IPI data, then register performers at PPL — all before the distributor submission deadline.

Keep a registry spreadsheet linking every ISRC to its corresponding ISWC, IPI numbers, file name and folder path. Ensure artist name spellings match PRS/PPL entries exactly to avoid unmatched records.

How do you validate a delivery and recover from a rejection?

Run this numbered checklist before hitting submit:

Audio file type is WAV or FLAC, minimum 16-bit/44.1kHz.
File names match the manifest exactly, character for character.
Artwork is minimum 3000×3000px, RGB colour space, JPG or PNG.
ISRC is embedded in BWF where possible and visible in the distributor dashboard.
Writer splits sum to 100% with no rounding errors.
Release date is formatted as YYYY-MM-DD (ISO 8601) in the manifest.

Common rejection causes: missing IPI or ISWC, mismatched artist naming between PRS/PPL and the distributor, undersized artwork, a distributor-assigned ISRC that is not visible to the label, and incorrect date formatting.

If a delivery fails: correct the metadata, re-deliver using the same UPC where possible (changing the UPC creates a new product and loses chart history), contact distributor support with the relevant manifest rows and proof of registration, and note any blackout periods the distributor imposes between takedown and re-delivery.

Pro Tip: Build a manifest validation pass into your pre-submission routine — a simple spreadsheet formula that flags any row where ISWC or IPI is blank will catch the most common rejection cause before the distributor does.

Where can you find copy-and-paste templates for release admin?

Three templates cover most of what a label needs:

DDEX-inspired manifest CSV — use the column names from the manifest table above. Fill ISRC and ISWC first (they are the linking keys), then artist name, track title and writer splits. Store the completed file in 08-admin/ alongside the release approval sign-off.

Release admin spreadsheet — one row per recording, columns for ISRC, ISWC, IPI, UPC, distributor, delivery date and registration status at PRS and PPL. The label manager signs off each row before submission.

Release-day verification sheet — a simple tick-list: distributor receipt confirmed, ISRC visible, artwork size checked, embedded metadata verified. Takes five minutes and prevents the most expensive mistakes.

For a four-track EP, complete the manifest by assigning four ISRCs (one per recording), entering the shared UPC/EAN on every row, then registering each composition at PRS using the exact track titles from the manifest. Any title discrepancy between the manifest and the PRS registration creates an unmatched work.

Key takeaways

A label that registers compositions at PRS for Music, performers at PPL, and embeds ISRCs in master files before delivery will collect royalties correctly and avoid distributor rejections.

Point	Details
Register before you release	Secure ISWC and IPI data at PRS for Music before the distributor submission deadline.
PPL performer registration	Register performers at PPL before release; missing data is treated as unenforceable for payment.
Embed identifiers in masters	Embed ISRC, artist name and publisher in BWF/XMP so data travels with the file.
Validate the manifest first	Check every ISWC and IPI field is populated before submission to avoid the most common rejection cause.
Musicvideomarketplace for video assets	Use Musicvideomarketplace to export platform-ready music videos and social clips that meet the file-spec and naming rules in this checklist.

Why metadata discipline is now a business decision, not an admin task

The labels that treat metadata as a post-release tidying job are the ones chasing unmatched royalties six months later. The UK Industry Agreement on Music Streaming Metadata makes the position clear: the party that creates the data is responsible for its completeness. That is your label, not your distributor, not your DSP.

What changed is the enforcement. Distributors now reject incomplete deliveries automatically. PPL treats missing recording data as unenforceable. The margin for error that existed when metadata was checked manually has gone. A disciplined manifest and a consistent versioning system are not overhead — they are the mechanism by which your catalogue generates income reliably. Fewer re-deliveries, faster royalty matching, and less time spent by managers untangling unmatched revenue: that is the operational upside of getting this right before release day, not after.

Get your video assets release-ready with Musicvideomarketplace

Sorting your audio masters and metadata is half the job. The visual assets — music videos, lyric clips, short social cuts — need to meet the same file-spec and naming standards, and producing them from scratch takes time most labels do not have.

Musicvideomarketplace

Musicvideomarketplace gives you human-made, ready-to-edit full-length music videos you can customise in minutes: upload your audio, add your branding, and export a YouTube-ready video or a set of short social clips that slot directly into the 06-visuals/ folder of your release structure. The export files arrive named and formatted to match the specs in this checklist, so there is no reformatting step between production and delivery. Browse a ready-to-edit video example and see how quickly a compliant visual asset comes together for your next release.

Useful sources to bookmark

UK Industry Agreement on Music Streaming Metadata (GOV.UK) — the primary government-backed agreement defining metadata responsibilities for releasing parties.
PPL Repertoire Data Policy (PDF) — PPL’s definitive list of required recording, rights and performer data; essential for neighbouring-rights compliance.

Keep these links accessible during catalogue audits and any dispute with a distributor or collection society — they are the primary references for what your label is contractually and technically expected to deliver.

Label digital asset organisation checklist for UK labels