Follow a conflict from detection through resolution — the complete end-to-end pipeline
This is an interactive ResolutU tutorial
Launch it in the app to follow along step-by-step
Conflicts are detected when two or more conflicting ownership claims appear in the same rights domain for the same work. For "Midnight Run": the platform's ingestion system detects two ISRC registrations for the same recording — one from Producer A's distributor (60% ownership) and one from Label B (100% ownership).
Before a conflict can be assessed, all the raw data must be normalized into a consistent format.
Example: Midnight Run
Triage Factors
Triage determines the priority and complexity of the conflict.
Each party is asked to submit documentation supporting their claim.
Example: Midnight Run
Key principle: Signed contract > Unsigned correspondence
Evidence quality matters. A signed PDF beats an unsigned draft. A dated registration beats an undated one. A notarized document carries more weight than a plain email.
Most conflicts are resolved through negotiation before reaching formal arbitration.
Example: Midnight Run
Once parties reach agreement (or a determination is made), the resolution is formalized.
After resolution, the conflict record is archived with all submitted evidence, the timeline of events, resolution terms, and pattern data. Archived conflicts are a valuable resource — patterns across resolved cases reveal systemic issues like distributor gaps, PRO registration mismatches, or recurring split sheet problems that can be addressed upstream.
Understand what a music conflict is and how rights disputes arise
Explore the layers of music rights — master, publishing, mechanical, performance, and more
Compare the possible outcomes when a conflict is resolved — from agreed splits to arbitration