Making music rights
legible, connected
and actionable.

A composition, a recording and a video can refer to the same music without being the same asset. Their identifiers, contributors, territories and rights need to stay distinct. My work was to make those relationships understandable at the point of decision.

Catalog operations

Establish the identity of an asset and the ownership information attached to it.

Matching and claiming

Compare evidence before linking a work or acting on a use of it.

Finance

Follow earnings from a statement through adjustments and payment.

Work arrived from several applications: a proposed match, an ownership conflict, a statement or a license renewal. A person needed to know what required attention without repeatedly checking each part of the suite.

Find the work

A common home and search provide entry points into assets, creators, usage and licenses.

Separate the signals

Activity describes what happened. Approvals request a decision. Tasks preserve the follow-up.

Keep the context

App labels and linked records identify what an action affects before someone takes it.

A title alone is a weak way to recognize a recording. Similar names, versions and contributor credits make the surrounding metadata essential. I kept identifiers and source information close to the asset, including during editing and batch work.

Recognize

Read the title, artist, company and ISRC together; search by the information already known.

Maintain

Edit metadata without losing the link to the collection and its source record.

Organize

Use folders and selection for repeated catalog work instead of opening every asset in isolation.

An asset can have a problem in one right while its other shares remain balanced. In the example, synchronization totals 120%, while mechanical and performance each total 100%. A single warning on the asset would hide that distinction.

Locate

Show the total for each right and identify the one that needs investigation.

Explain

Keep the publisher claims and percentages next to the total rather than reducing the conflict to a status.

Trace

Connect the recording, composition, contributors and change history within the same asset view.

Matching asks whether a recording and a composition belong together. A compact queue helps people process volume, but it cannot carry all the evidence. I paired that queue with an aligned comparison of the two records.

Compare like with like

Titles, artists, writers and identifiers line up across the recording and composition.

Keep uncertainty honest

Confirm, reject and review later are distinct outcomes. Unpaired recordings remain visible as unfinished work.

Support throughput

Move between individual reviews and selected items without changing the meaning of the decision.

A matching asset is only part of a copyright review. The video, channel, traffic, confidence and exact music segments all contribute context. I brought them together before the claim decision, rather than asking people to act on an isolated score.

Prioritize

Use the review queue and usage context to choose what needs attention.

Inspect

See the matched work alongside the video and select the detected time ranges.

Decide deliberately

Keep claiming separate from saving a review for later, and distinguish pending, potential and inactive work.

A license connects a customer to particular uses of music. The code alone is not enough to explain what is allowed, where it applies or whether it is still active. I organized the workspace around those relationships.

Understand the permission

Read the reference, allowance, expiry and status together.

Follow the relationship

Move between licenses, customers, channels and licensed videos within the same application.

Prepare for renewal

Make the dates and current state legible before a permission expires.

A headline earnings figure needs a path back to its sources. Gross, net, adjustments and previous claims do not answer the same question. I gave people ways to examine the period, the asset and the underlying statement before interpreting a total.

Start with the overview

Compare gross and net across the selected period.

Find the contribution

Inspect asset earnings and the client, territory or platform context behind them.

Follow the report

Keep statement status and detailed reports accessible from the same financial workspace.

Reporting revenue does not mean a payout has happened. I separated upcoming, historical and pending payments, with the supporting documents close by, so the status of the money was explicit.

Distinguish

Show what is expected, what has been paid and what is still pending.

Verify

Keep the relevant statement, reference and payment details available for inspection.

Retrieve

Search and filter the financial documents without rebuilding context elsewhere.

An organization brings together people with different responsibilities. Membership, roles and groups shape what those people can do. I made that structure explicit instead of leaving access to be inferred from a job title.

Recognize the person

Keep member identity, role and status in a readable list.

Define the responsibility

Manage roles and group membership with visible, deliberate controls.

Bring someone in

Make an invitation a clear action with a named recipient and an assigned role.

Catalog and royalty data can arrive through different providers and transfer methods. I treated setup as a short sequence: choose the source, configure the connection and review what is about to be established.

Choose

Identify the provider and the type of information being connected.

Configure

Expose the relevant location, credentials and synchronization frequency.

Review

Put the configuration in one place before confirming the connection.

The suite’s behavior also depended on settings: duplicate handling, match confidence, claim policy, reminders and account security. I grouped these controls by purpose so maintaining the platform would not require knowing its internal structure.

Application behavior

Keep ingestion, matching, claiming and licensing controls with the application they affect.

Account needs

Separate billing, notification delivery and security from day-to-day asset work.

Support

Provide a route to help and the information needed to resolve an issue.

I joined as the first designer and grew the design function to a team of eleven. Alongside the product, I developed Ictinus and helped connect design and front-end engineering through CODA. The same need ran through all three: preserve context as work moves between specialists.

The design outcome

A connected workspace spanning catalog, matching, claiming, licensing, reporting and organizational control.

The tradeoff

Specialist detail needs room. Shared patterns should make that detail easier to navigate without flattening the differences.

What I would evaluate

Whether people can identify the right asset, explain a decision and move between review and financial work without losing their place.