Data tooling
Turning scattered usage exports into one answerable dataset
Planning data lived in separate exports per site and season, which made simple questions unanswerable.
Multi-siteexports merged into one view
Self-servea UI, not a notebook
Questions with answers nobody could reach
"When did we last play this?" and "what has this site leaned on too heavily this season?" are planning questions with real answers sitting in the system, spread across separate exports that nobody was going to reconcile by hand every week.
How I built it
A short Python script normalizes and combines the exports, wrapped in a small web interface so the answer is a page you open rather than a script someone has to run.
Outcome
Planning moved off memory and onto data. It's a small tool, but it's the one that made me stop treating spreadsheets as the limit.