Permission secured. Is your release actually ready?

The permission email arrives. The creative team celebrates. Now somebody needs to connect that approval to the file, credits, metadata, and payment process that will actually leave the building.

This handoff is where a licensing decision becomes a release process. A final master can differ from the reviewed mix; a distributor can receive old songwriter information; a royalty deadline can disappear into somebody's inbox. A single release record makes those mismatches easier to spot.

The checklist below is a suggested operational method for a U.S.-focused release involving negotiated permissions. It does not determine the sufficiency of an agreement or replace the requirements of your distributor, collecting societies, or other markets. Assign each task to a named person rather than leaving the checklist collectively owned.

1. Start with the actual permission and its conditions

Collect the final executed agreement and the approvals it requires. Check whether signatures, payments, further permissions, or other conditions must be completed before the relevant rights can be exercised. A favorable quote and a signed license should not occupy the same status in the release tracker.

Write a short scope summary with a reference back to the relevant document. Record the approved work and recording, version, territories, term, media, permitted changes, and restrictions. Keep the summary useful, but do not let it replace the agreement if the wording differs.

Where several sources or licensors are involved, reconcile every row. If one permission excludes a planned use, the fact that another includes it does not fill the gap. Flag unresolved questions for the appropriate adviser and hold the dependent delivery until they are resolved.

2. Match the final audio to the reviewed version

Compare the release master with the approved reference. Look for creative changes affecting the licensed material: added vocals, longer excerpts, different lyric wording, a new sample, or a substantially different edit. Ask whether any changes fall outside the approval or require further review under the agreement.

Keep descriptive filenames, a version log, and a stable reference for the delivered file. A checksum can help a team identify the exact file it sent; it does not establish that the file is legally approved. The useful connection is between the document, the reviewed material, and the final delivery.

Illustrative example: a fictional duo, North Window, cleared a remix using mix v06. Their final master adds a repeated source-vocal phrase in the outro. The release coordinator spots the difference, checks the approval conditions, and obtains any needed confirmation before replacing the reference file. “The song is already cleared” would have missed the specific change.

3. Reconcile credits and ownership metadata separately

Prepare a single approved metadata sheet with the title, version information, artist and remixer roles, writers, publishers, identifiers where available, and the credits required by the agreement. List the source of each field. Do not infer an ownership share from an artist credit or a master-revenue percentage.

For an authorized derivative work, The MLC instructs that registration must reflect the finalized agreement, including agreed writers, publishers, and shares. It also says an unauthorized derivative work should not be registered. Entering information into a royalty system is a downstream step, not a way to obtain the underlying authorization.

Before anyone enters data, resolve inconsistent spellings, outdated publisher details, provisional splits, or disagreements about which title is approved. Ask the relevant organization how its fields work; do not change the underlying agreement merely to make an upload form convenient.

4. Keep recording and composition identifiers straight

An ISRC belongs to the recording; an ISWC identifies the composition. IFPI's guidance addresses when changes such as remixes or edits require a new recording code. Confirm the correct treatment with your distributor or ISRC agency instead of copying the source recording's code into a new remix.

Use consistent identifiers across the systems that need them. SoundExchange explains why accurate ISRC-associated metadata matters for identifying recordings and matching usage. A code helps a system recognize an asset; it does not prove ownership or clear borrowed material.

5. Build a handoff sheet a colleague can inherit

Keep sensitive agreements in appropriately restricted storage and share access only with people who need it. The working sheet can point to the evidence without attaching full contracts to every routine email.

Handoff item	Record	Suggested owner
Permission	Executed documents, scope summary, completed conditions.	Licensing lead
Approved assets	Audio/lyric versions and required final approvals.	Producer or release coordinator
Metadata	Approved title, roles, writers, publishers, shares, credit wording.	Publishing/release administrator
Identifiers	Recording and work codes, plus who assigned or confirmed them.	Distributor liaison
Delivery	Recipient, delivered version, territory settings, confirmation.	Release coordinator
Administration	Reporting periods, payment dates, responsible person.	Accounting lead
Future-use limits	Expiry, approval triggers, excluded uses, transfer restrictions.	Catalog manager

One person may cover several roles on a small release. Write their name anyway. The purpose is to make ownership of the work explicit, not to imitate the staffing of a large label.

6. Put the continuing obligations on the calendar

Schedule statements, payments, renewals, and any notice dates required by the actual agreement. Record where incoming revenue data will come from and who can access it. If a payment calculation depends on a particular revenue definition, carry that instruction into the accounting handoff.

After delivery, check the live title, version, credits, and availability against the approved sheet. Platform display can differ from back-end metadata, so investigate material mismatches with the relevant party rather than assuming one screen reveals every field.

Keep the restrictions with the catalog as it moves. A later sync pitch, second-language adaptation, additional remix, or label transfer can require new decisions. The old permission is evidence of what was agreed for that release, not an automatic answer to the next proposal.

A complete handoff lets a colleague understand what can be released, which file was approved, how contributors should be represented, and what must happen afterward. That is how a one-time clearance becomes a manageable part of a music catalog.

Sources & further reading

• The MLC: registering an authorized derivative work
• IFPI: ISRC assignments, changes, and musical-work identifiers
• SoundExchange: ISRCs and recording metadata

The handoff sheet is an editorial project-management recommendation. Follow the agreement and the applicable requirements of the services and territories involved.