본문으로 건너뛰기

Split Sheets and Producer Contracts: Practical Rights Checklist

A producer-safe split sheet guide for writing shares, master revenue, approvals, samples, metadata, and international collaboration risk.

Split Sheets and Producer Contracts: Practical Rights Checklist
split sheetsproducer contractssong splitspublishingcollaboration

Split sheets and producer contracts

Quick answer: Less-critical localization note: platform dashboards, algorithms, export specs, payout/eligibility, feature availability, and content norms vary by country/language and must be verified in the current local dashboard/help center.

Rights workflows should be documented before release, not reconstructed during a dispute.

  • Save license PDFs or screenshots with timestamps.
  • Keep split sheets and contributor approvals in the project folder.
  • Record territory, term, allowed uses, and payment terms for each asset.

This is operational education for producers, not legal advice. For a signed deal, dispute, takedown, or high-value sync, ask a qualified music lawyer in the relevant territory.

Localization note

Legal, tax, privacy, rights, royalty, and contract guidance changes by jurisdiction. Treat this article as an editorial starting point, not legal or accounting advice.

For Korean readers, localize rights administration, platform tools, tax paperwork, payment rails, and creator-market examples instead of reusing US or EU defaults.

빠른 답변

Split sheets and producer contracts: A split sheet should identify contributors, rights layers, percentages, approvals, payment paths, and source materials before the song is released. It is a workflow document, not a substitute for legal review on major deals. This is operational education for producers, not legal advice. For a signed deal, dispute, takedown, or high-value sync, ask a qualified music lawyer in the relevant territory.

What producers should actually document

A split sheet should identify contributors, rights layers, percentages, approvals, payment paths, and source materials before the song is released. It is a workflow document, not a substitute for legal review on major deals.

Treat clearance as chain-of-title work: who owns the recording, who owns the composition, what use was approved, what territory and term apply, and who gets paid.

A credit line, DM, beat-store receipt, or friendly verbal yes can be useful evidence, but it is not the same as a license that names the rights and permitted exploitation.

Composition split

Who wrote the song or beat and what percentage each writer controls.

Producer action Agree to total 100 percent before distribution.

Master split

Who owns or participates in the sound recording revenue.

Producer action Separate it from publishing in the sheet.

Admin rights

Who can register, license, pitch, and approve changes.

Producer action Name the person or company and require notice for major uses.

Risk map before release

AreaCommon failureConservative move
Producer paid a flat feePayment may not settle publishing unless the contract says soState fee, rights transferred, and retained shares separately.
Work-for-hire languageCan transfer authorship or ownership in some jurisdictions but not automatically everywhereUse lawyer review for buyouts and moral-rights wording.
Unsigned collaboratorPRO conflicts and royalty freezesCollect legal names, IPI/CAE, PRO, email, and signature.
Template copied from another countryLocal rights and moral rights may not waive the same wayAdd territory-specific review for material releases.

Jurisdiction notes for international releases

Use this as a routing map, not legal advice. A beat uploaded from one country can generate claims in another because platforms, PROs, publishers, labels, and neighboring-right societies each operate on their own rules.

TerritoryOperational caution
USSeparate master, composition, mechanical, performance, sync, and DMCA processes. SoundExchange applies to non-interactive digital performance royalties for recordings.
EU/EEAMoral rights and collective-management rules can be stricter than a US-only workflow. Platform takedowns and neighboring rights can involve local societies.
UKPRS, MCPS, and PPL often sit in different parts of the rights stack. Do not assume a US PRO registration covers UK exploitation cleanly.
BrazilECAD and local publishing administration can affect public performance and neighboring-right collections. Portuguese contract language may matter.
RussiaLocal collection and enforcement conditions can change quickly. Keep contracts, source files, and payment evidence in case platforms request proof.
ChinaPlatform clearance, lyric use, and local distribution rules may require local partner review before release or sync use.
Japan/KoreaJASRAC, NexTone, KOMCA, and local neighboring-right workflows can be precise about splits, covers, and sync. Metadata accuracy matters.
Turkey/IndonesiaLocal collecting societies and platform policies may diverge from US templates. Confirm language, term, and territory in writing.
Spanish multi-regionSpain, Mexico, Colombia, Argentina, Chile, and other Spanish-speaking markets are not one legal region. Use country-specific review for campaigns.
Arabic multi-regionMENA markets vary by country, platform, and local partner. Treat Arabic-language exploitation as multi-territory unless a contract says otherwise.

Clearance and enforcement workflow

  1. 1. Separate writer, publisher, and master columns
     Do not let one percentage pretend to cover every royalty stream.
  2. 2. Record identifiers
     Collect legal name, artist name, PRO, IPI/CAE, publisher, email, and tax/payment contact.
  3. 3. Define approvals
     Say who can approve sync, samples, remixes, takedowns, Content ID, and admin registrations.
  4. 4. Attach evidence
     Save beat license, session notes, payment proof, and final export hashes with the split sheet.
  5. 5. Update metadata before upload
     Distributor, PRO, SoundExchange or neighboring-right registrations should match the signed document.

Red flags that should stop the upload

Red flagWhy it mattersWhat to do
No source file or license textYou cannot prove what rights came with the asset.Pause release until the vendor, collaborator, or rights owner confirms terms in writing.
Worldwide sync or broadcast promised in a casual messageSync and broadcast often need explicit rights language.Ask for a formal license or exclude the use from the pitch.
Multiple writers but no split sheetPublishing money may be misdirected or frozen.Get dated approvals before distribution.
A platform claim arrives before release dayFingerprinting can reveal hidden samples or duplicate loops.Resolve the claim before pitching editors, ads, or sync buyers.

This is operational education for producers, not legal advice. For a signed deal, dispute, takedown, or high-value sync, ask a qualified music lawyer in the relevant territory.

Use Plugg Supply as a source-control step for music assets: keep license notes, source links, stems, and export metadata together before release.

무료 다운로드 둘러보기

Learning path

Related answer hubs

Music Production for Beginners Music production for beginners: a simple roadmap from first DAW to finished beat. A beginner music producer should pick one DAW, learn basic MIDI and drum programming, use a small set of free plugins and samples, finish a short beat, export it, and repeat the process weekly. Finishing tracks is mor...

Related catalog

More tutorials from the catalog

More tutorials from the Plugg Supply feed, ranked by catalog popularity.

Browse Tutorials

자주 묻는 질문

What belongs on a split sheet?
Legal names, artist names, roles, writer percentages, publisher data, PRO/IPI numbers, master terms if included, signatures, and date.
Should sample information be included?
Yes. Note cleared samples, royalty-free assets, and any pending clearance.
Can one person register for everyone?
Only if the agreement authorizes it and metadata is accurate.
What if collaborators disagree later?
The dated signed sheet, session records, and payment evidence become the starting point for resolution.