New request
How it fits together

Seven layers, one hub

The structure follows the Haier x UCL 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.

A request, end to end

Product line or market asks (hub or Teams form)→Hub checks it against rights and LED plan→CAA review→Haier Europe sign-off→Rights booked, deliverables opened→Agency creative→CAA submits via Relevent→Relevent / UEFA clearance→Talent sign-off if tagged→Final file to SharePoint→Delivery tracked, value counted
Every step posts to the Haier x UCL Teams channel and lands in the protocol with a timestamp. An end-of-week digest goes to the team.
Teams

Haier works in Microsoft 365, so the hub plugs into it rather than adding a new platform: approvals, requests and digests post to a Teams channel and final assets file to SharePoint. Mocked in this prototype.

Access by role

CAA team edits everything; Haier Europe signs off; product-line teams see their own rights and requests; HQD reviews China and global brand; leadership gets the command center read-only. CAA-internal files stay hidden from Haier roles.

Built by CAA

Prototype on Next.js, data in the browser for the demo. Production: extraction on the Appendix 4 rights package, Microsoft Graph for Teams and SharePoint, UEFA LED schedules and broadcast data feeds.