The Challenge
When Cadillac F1 enters the grid in 2026, they face a massive operational hurdle: decentralized chaos. Currently, most teams manage VIP hospitality, stakeholder transport, and freight logistics via fragmented spreadsheets and chat apps.
One error in time-zone conversion or a capacity oversight in a Paddock Club suite can cost millions in partner renewals and operational downtime.
The Research Methodology
Ethnographic Analysis
Analyzed 10+ hours of paddock access footage and Team Principal communication flows to map "The Longest Mile" between HQ and Trackside.
Market Benchmarking
Deconstructed public F1 hospitality packages and VIP ticketing structures to model realistic pricing and access logic.
System Architecture
The technical stack was chosen for **reliability and speed.** Built with Next.js and TypeScript, the system utilizes a centralized planning engine that calculates operational impact in real-time.
Dynamic Risk Engine
I developed a logic layer that cross-references race intensity (e.g., Triple Headers) with freight modes. If a user selects "Sea Freight" for a back-to-back race, the system flags a critical lead-time risk immediately.
The Temporal Sync Hub
Managing three time zones (Track, HQ, and UK Production) is a known friction point. The UI solves this by pinning a "Precision Clock" to the navigation that updates as the user toggles through the global race calendar.
Live Financial Modeling
The budget module tracks catering, personnel hotels, and freight CO2 costs. This creates total fiscal visibility, allowing hospitality managers to see the margin impact of every guest added to the roster.
Key Learnings
This project reinforced that in high-stakes environments, **UX is a safety feature.** Information density must be carefully balanced with visual hierarchy so that stressed operators don't overlook critical alerts.
- "System thinking over aesthetic choice."
- "Proactive risk surfacing reduces decision fatigue."