New request
How it fits together

Seven layers, one hub

The structure follows the UMCC approval and rights management sketch: landing page on rights, a tracker for status and project management, approval, requests, knowledge, ticketing and hospitality, and detail pages per competition and per process.

LAYER 01

Rights knowledge graph

UEFA contracts ingested; every right extracted with quantity, competition, territory, brand, restrictions, deliverables, expiry and approvals. Usage stats per brand and per contract.
LAYER 02

Request and approval hub

Every brand ask starts here. Automatic checks: available, already allocated, territory conflict, brand conflict, approval needed, UEFA lead time. Routed and time-stamped.
LAYER 03

Asset and content repository

DAM meets rights management: who can use each file, where, until when, in which territories, with its approval history. Stored on DingTalk Drive.
LAYER 04

Hospitality and ticket intelligence

Separate module: inventory, packages, guest requests, allocation rules, wait lists, usage reporting.
LAYER 05

LED and broadcast rights planner

Per round and territory feed: brand, language, approved creative, disclaimer, market version, pushed through approval. Coverage check for priority markets.
LAYER 06

Social rights manager

UEFA deliverables, co-posts, creators, owned channels, player and club rights, Chinese platforms. Remaining rights per brand, live.
LAYER 07

Executive command center

CEO, brand and competition views plus the media value tracker: live for the sponsoring team, quarterly for leadership.

A request, end to end

Brand team asks (hub or DingTalk form)→Hub checks it against rights and LED plan→CAA review→Alibaba Sponsoring sign-off→Rights booked, deliverables opened→CAA creative (Asana)→CAA packages for UEFA→UEFA approval→Talent sign-off if tagged→Final file to DingTalk Drive→Delivery tracked, value counted
Every step posts to the closed DingTalk group and lands in the protocol with a timestamp. An end-of-week digest goes to the team.
DingTalk

Main channel for the Alibaba side. The hub posts approvals, requests and digests to a closed group through a robot, and files final assets to DingTalk Drive. Mocked in this prototype.

Access by role

CAA team edits everything; Alibaba Sponsoring signs off; brand teams see their own rights and requests; leadership gets the command center read-only. CAA-internal files stay hidden from Alibaba roles.

Built by CAA

Prototype on Next.js, data in the browser for the demo. Production: contract extraction on the executed agreement, DingTalk APIs, UEFA LED schedules and broadcast data feeds.