Know What May Be Used. Know Who Approved It.

Partial and Managed

Rights are not a note at the end of production.

Keep agreements, deal terms, releases, licenses, credits, territories, dates, restrictions, approvals, and delivery obligations connected to the event, source file, product, property, or campaign they govern.

Book it. Build it. Sell it. Run it. Capture it. Share it.

Current Contracts, Rights, Licensing and Clearance application surface
Current IMC Machine application surface. Individual functions carry their own maturity, provider, access, and approval requirements. Open the full size application screen.

The Problem It Solves

The event record should not disappear between systems.

Contracts, Rights, Licensing and Clearance

A song is cleared for the room but not the stream. A photograph is licensed for the website but not a paid advertisement. A performer release is signed, yet nobody can find the version that covers the final edit. The creative work moves quickly. The permission record falls behind it.

Complete Workflow

Move from source to approved outcome.

Contracts, Rights, Licensing and Clearance

  1. Identify the people, work, source media, property, performance, intended uses, territories, terms, and responsible reviewer.
  2. Record the relevant deal memo, contract, rider, license, release, credit, restriction, and expiration.
  3. Attach rights information to the actual asset, event, campaign, episode, property, or delivery package.
  4. Flag missing permission, conflicting terms, required credit, limited use, and human review.
  5. Route the record to the owner, producer, attorney, licensor, client, or other named authority.
  6. Preserve the approved terms, permitted delivery, proof, renewal date, and audit history.

What The User Gets

Useful work, visible responsibility, and a record worth keeping.

User outcomes

  1. Permissions visible before a file enters publication or distribution.
  2. Credits, territories, durations, and use limits attached to the work they control.
  3. Better handoffs among creator, producer, client, attorney, distributor, and archive.
  4. A durable rights history for future reuse, renewal, licensing, or withdrawal.

Examples and samples

  1. A theater records performance rights, union terms, music cues, performer releases, archival limits, and approved promotional excerpts.
  2. A film or music release connects masters, contributors, splits, artwork, samples, licenses, metadata, credits, and delivery status.
  3. A festival tracks artist agreements, sponsor use, vendor terms, photo releases, broadcast permission, and settlement obligations.
  4. A property campaign records listing authority, photographer rights, floor plan use, Matterport delivery, disclosures, and approval.

Visual Workflow

Contracts, Rights, Licensing, and Clearance from source to approved outcome.

Follow the practical movement of the work. The machine organizes, drafts, compares, and prepares. The responsible person keeps authority over approval and release.

Contracts, Rights, Licensing, and Clearance workflow for people, work, intended uses, agreements, releases, conflicts, human approval, and permission records
Contracts, Rights, Licensing, and Clearance. The workflow records intended uses, agreements, riders, licenses, releases, credits, limits, open questions, authorized decisions, and the resulting permission record. Open the full size workflow. Open this workflow in Figma.

Evidence And Boundaries

Show what is current. Name what still requires people, providers, or a managed scope.

  1. Current and public surfaces support contract drafting workflows, riders, deal memos, release and license records, rights schemas, asset level rights, approval gates, and property rights records.
  2. Human legal review remains required. The product is not represented as universal contract lifecycle management, automatic rights clearance, or a substitute for counsel.
  3. Electronic signature, external rights databases, collection societies, union systems, and distributor acceptance depend on configured providers and verified integrations.

Connected product areas

Read. Compare. Decide.

The website should do the explaining.

Review the actual application surface, the complete workflow, the practical outcomes, and the maturity boundary. Then open the application, browse the catalog, or request a written scope.

Book it. Build it. Sell it. Run it. Capture it. Share it.