Why Conflicts Happen
Learn the root causes of music disputes — and how to prevent them
This is an interactive ResolutU tutorial
Launch it in the app to follow along step-by-step
Root Causes, Not Mistakes
Most music conflicts don't happen because someone made an error — they happen because the industry has multiple overlapping systems that don't automatically stay in sync.
Understanding the root causes helps you prevent conflicts at the source, rather than just resolving them after the fact.
Split Sheet Drift
Always confirm split sheets are signed before distribution — an unsigned split sheet has no legal weight.
A split sheet is the foundational document defining who owns what percentage of a song. Split sheet drift occurs when:
- •Early drafts circulate and get registered before a final version is signed
- •One collaborator registers with a PRO using a different split than the contract specifies
- •Percentages don't add up to 100% — leaving unaccounted ownership
- •A collaborator is added after initial registration without updating existing records
Prevention
Lock the split sheet before distribution.
A split sheet that was correct at creation can become a source of conflict years later if one party gets new representation and finds discrepancies in the registration.
Versioned Contracts
Songs go through multiple contract versions — from demo to release to catalog acquisition. Each version may contain different terms:
- •Early producer agreements often use informal language that creates ambiguity later
- •Re-recording provisions, option years, and reversion clauses change rights over time
- •Catalog sales transfer ownership but not always all the metadata that comes with it
Newer contracts don't automatically supersede older ones in all jurisdictions. Which contract governs depends on its terms, timing, and applicable law.
Late Registrations
Retroactive registration creates reconciliation complexity with organisations like the MLC and HFA.
Registration timelines vary significantly by party and territory. Conflicts emerge when:
- •A songwriter registers their composition with a PRO months after release
- •A newly signed artist retroactively claims credits on tracks released under a previous deal
- •A sample is identified post-release, triggering a retroactive clearance requirement
- •A distributor corrects metadata months after initial delivery, creating two competing records
Prevention tip
Register before you distribute.
DSPs typically use the metadata they received at ingestion. Corrections must be actively pushed and may not propagate to historical royalty calculations.
Territorial Differences
Rights and registrations vary significantly by territory. The same song may have:
- •Different owners in different countries (especially after catalog sales or licensing deals)
- •Different collection society records that don't match
- •Different royalty rates and payment timelines per territory
- •Neighboring rights in Europe but not in the US
A resolution in one territory is not automatically binding in another. Multi-territorial conflicts require coordination across multiple collection societies.
Distributor Errors & Edge Cases
Other common conflict sources include distributor metadata errors (wrong ISRC, missing songwriter credits), remix and sample clearance gaps, cover song misclassification, and name collisions in registries. Prevention is faster than resolution — a metadata audit before release catches most of these errors before they propagate across all DSPs.
Related Resources
Conflict Resolution 101
Understand what a music conflict is and how rights disputes arise
Rights Stack Deep Dive
Explore the layers of music rights — master, publishing, mechanical, performance, and more
Conflict Lifecycle
Follow a conflict from detection through resolution — the complete end-to-end pipeline