Inspiration
What it does
How we built it
Challenges we ran into
Accomplishments that we're proud of
What we learned
What's next for WhosNext Event Command Center
Inspiration
Event organizers rarely lack information. They lack a clear answer to a more urgent question: What should I handle next? Schedules, player records, volunteers, sponsor commitments, scoring, and live operational issues often live in separate tools. The organizer is left to mentally combine them while the event clock keeps moving.
WhosNext Event Command Center was built to reduce that cognitive load. It gives an organizer a concise administrative brief, a transparent readiness score, and one prioritized next action across the next six events.
What it does
WhosNext turns event operations into a decision-oriented command center rather than another crowded dashboard.
- Summarizes the next six events and identifies what needs attention now, soon, or later.
- Calculates an explainable readiness score from unfinished, weighted work instead of presenting an unexplained AI number.
- Orders actions by consequence and deadline, not simply by when a task was entered.
- Provides a 30-day rolling calendar that combines events with plain operational tasks.
- Supports golf, bowling, pickleball, basketball, volleyball, and running events.
- Shows event-specific views for players, sponsors, volunteers, check-in, live play, scoring, awards, and wrap-up.
- Surfaces live issues such as pace-of-play risks and recommends a specific response.
- Keeps exception tools, such as missing-score recovery, out of the normal workflow until needed.
The result is a calmer organizer experience: one score, one next step, and enough supporting detail to act confidently.
How we built it
We started with the organizer's real workflow rather than a generic dashboard template. The product has two levels:
- A portfolio view that compares the next six events and establishes cross-event priorities.
- A focused event command center that explains readiness, shows the event journey, and exposes the next operational decisions.
Codex was used as the implementation partner to turn the workflow into a working application, iterate on the interaction design, build the calendar and event views, and test the experience in the browser. GPT-5.6 was used to help transform raw operational state into concise administrative summaries, prioritized recommendations, and plain-language explanations of why an action matters.
The interface keeps the human in control. Recommendations are paired with owners, deadlines, downstream impact, and visible score calculations so an organizer can verify the reasoning before acting.
Challenges we ran into
The hardest design problem was deciding what not to show. Event software can easily become a wall of tables and status indicators. We had to preserve operational depth while making the first screen understandable in seconds.
A second challenge was making readiness trustworthy. A score is useful only when the organizer can see why it changed, so WhosNext shows the starting score, the weight of open work, and the current result.
We also needed one product to support very different event types without making every workflow feel generic. The portfolio layer stays consistent while each event exposes the operational details that matter for that format.
Accomplishments that we're proud of
- A working multi-event command center that is immediately understandable.
- Transparent readiness scoring.
- Prioritization based on operational consequence and deadline.
- A rolling calendar that connects events and tasks without becoming a project-management maze.
- Event-specific tools that remain available without distracting from the next decision.
What we learned
The best event assistant does not try to replace the organizer. It reduces uncertainty, explains tradeoffs, and helps the organizer focus. A short, defensible recommendation can be more valuable than a large amount of analytics.
What's next
Next, WhosNext can connect to live registration, volunteer, sponsor, messaging, GPS, and scoring systems; persist organization-specific workflows; support role-based team views; and learn from completed events to recommend earlier interventions in the next event cycle.
Built With
- 5.6
- adhd
- codex
- hopesanddreams
- medium
- sol
Log in or sign up for Devpost to join the conversation.