# Common Works Registration (CWR) Workbench

> Create Common Works Registration 2.1 files, check and read existing .V21 files, and understand society ACK responses in one free browser workbench.

*Published by [TrackForge](https://trackforge.studio) · Last updated 2026-09-30*

- **Workbench:** https://trackforge.studio/cwr-tool/workbench
- **Supported standard:** Common Works Registration 2.1 Revision 8
- **Supported public file type:** .V21

---

The TrackForge Common Works Registration (CWR) Workbench helps publishers and rights administrators create a CWR 2.1 file, check or read an existing .V21 file, and understand a society acknowledgement response (ACK).

## Choose a task

### Create a registration file

Build a Common Works Registration 2.1 file from a form or CSV, then download it for review and submission.

**Before you begin:** You will need your sender identity, works, writers, publishers and rights shares.

[Open Create](/cwr-tool/workbench?tab=generate)

### Check an existing file

Choose a CWR 2.1 source file, check it for structural, field, share and destination-rule problems, then open supported files in the editor to amend them.

**Before you begin:** You will need the source registration file you plan to submit or re-submit; society responses belong in Society response.

[Open Check](/cwr-tool/workbench?tab=validate)

### Read an existing file

Turn a registration file into a readable view of its works, writers, publishers and rights shares.

**Before you begin:** You will need the registration file you want to understand.

[Open Read](/cwr-tool/workbench?tab=inspect)

### Understand a society response

Upload a society acknowledgement response (ACK) to see what was accepted, rejected or needs attention.

**Before you begin:** You will need the acknowledgement file returned by the society.

[Open Society response](/cwr-tool/workbench?tab=parse-ack)

## Available Workbench features

- Create Common Works Registration 2.1 .V21 files from a form or CSV.
- Check existing .V21 files for structural, field, share and available destination-profile problems.
- Read works, writers, publishers and rights shares from an existing .V21 file.
- Understand society acknowledgement responses (ACKs) by accepted, rejected and attention-needed outcome.
- Open supported .V21 files in the editor, correct identified issues and download a regenerated file without changing the original upload.
- Use plain-language issue explanations with technical evidence kept available under Technical details.
- Use all four public tasks without creating an account.
- Convert a completed LyricFind spreadsheet into LyricFind’s lyric-1.2 lyrics file or its preferred ownership-1.4 file with ownership and lyrics together, with a review list of rows to fix and values to confirm; uploads are converted and then discarded, never stored.

## Destination submission requirements

These recipient policies sit outside the CWR file-format checks and must be confirmed before submission.

### CAPASSO Africa

If a work includes a sub-publisher or publishing administrator, CAPASSO accepts that party only when it is directly affiliated with, or linked to, CAPASSO. Confirm the relationship before submission. TrackForge can validate the CWR publisher chain but cannot verify that external relationship from the file alone.

## Roadmap

The roadmap uses only three states and does not promise a date without an owned delivery commitment.

### Available now

Implemented in the public Workbench and backed by a dated release entry.

- **Create, check, read and understand responses** — Four outcome-led public tasks cover CWR 2.1 generation, .V21 checking and reading, and society acknowledgement-response review.
- **Correct supported .V21 files in the Workbench** — Check a file, open supported content as a pre-filled draft, correct identified issues and regenerate without changing the original upload. Lossy imports stop with preservation blockers.
- **Society-led CWR generation choices** — Choose familiar destinations including The MLC, PRS for Music / MCPS via ICE, CMRRA, CAPASSO Africa, AllTrack Worldwide, AllTrack US-only, SACEM, SIAE and SGAE. TrackForge states whether it applies recipient-specific checks or the common CISAC Base CWR 2.1 rules.
- **LyricFind lyrics files** — Turn a completed LyricFind spreadsheet into the lyric-1.2 lyrics file or LyricFind’s preferred ownership-1.4 file with ownership and lyrics together, with a review list of rows to fix and values to confirm. Uploads are converted and then discarded, never stored.

### In development

Actively being implemented, without an unowned delivery date.

Nothing is publicly committed to active development right now.

### Exploring

A direction under consideration, not a delivery promise.

- **Additional recipient-specific checking** — Further destination rules will move forward as current technical guidance and recipient evidence are verified. Direct GEMA generation also depends on CWR 2.2 support because GEMA currently requires that version.
- **Public integration access** — A governed way to integrate Workbench capabilities with other systems is being considered. No public API, webhook contract or delivery date is promised.

## Common Workbench questions

**What is a CWR file?**

Common Works Registration (CWR) is the CISAC file format publishers use to tell collecting societies who wrote and publishes a musical work, how rights are shared, and what should be registered.

**What can I do in the CWR Workbench?**

The Workbench has four tasks: create a CWR 2.1 .V21 file, check an existing .V21 file, read a file in plain language, and understand a society acknowledgement response (ACK).

**Which CWR version and destination profiles does the Workbench support?**

The public Workbench creates Common Works Registration 2.1 Revision 8 .V21 files. Society choices include The MLC, CMRRA, AllTrack Worldwide, AllTrack US-only, CAPASSO Africa, PRS for Music / MCPS via ICE, SACEM, SIAE and SGAE; the interface states whether recipient-specific rules or CISAC Base checks are being applied. Direct GEMA generation is unavailable because GEMA currently requires CWR 2.2.

**What does receiver 000 mean?**

Receiver 000 means multiple or unspecified recipients. It remains a valid CWR receiver code, but CISAC Base checks alone do not assess a known recipient’s own profile or prove that one file is ready for every society.

**Does passing validation guarantee society acceptance?**

No. A passing result means the named CWR structure and selected destination-profile checks found no blocking issue. A society can apply additional policy or data checks, and only its acknowledgement response confirms the outcome of a submission.

## Scope and limitations

- The Workbench does not submit files to a collecting society or promise that a recipient will accept them.
- Public generation and checking support Common Works Registration 2.1 Revision 8 and .V21 files; CWR 2.2 is not available.
- CWR 2.1 generation is available for CISAC Base, The MLC, CMRRA, AllTrack Worldwide, AllTrack US-only, CAPASSO Africa, PRS for Music / MCPS via ICE, SACEM, SIAE and SGAE. A separate PRS-specific checking profile remains available for uploaded files.
- The MLC, SACEM, SIAE and SGAE choices currently use CISAC Base CWR 2.1 checks; TrackForge does not yet assess every requirement specific to those organisations.
- GEMA currently requires CWR 2.2 for direct CWR submissions, so the CWR 2.1 generator cannot create a direct-GEMA-ready file.
- Receiver 000 means multiple or unspecified recipients. Under CISAC Base it does not claim that any named society’s destination-specific requirements were assessed.
- Additional society profiles and public integration access remain exploratory until implementation and evidence exist.
- The LyricFind lyrics file is not sent to LyricFind: you add your LyricFind login and upload it yourself.

## Help and updates

- [Help and plain-language issue explanations](https://trackforge.studio/cwr-tool/help)
- [Dated Workbench updates](https://trackforge.studio/cwr-tool/updates)
- [Roadmap](https://trackforge.studio/cwr-tool/updates#roadmap)

---

Source: [https://trackforge.studio/cwr-tool](https://trackforge.studio/cwr-tool)
