Event Tickets stores every attendee as a post linked to an event, with order references when paid tickets flow through WooCommerce. The default admin scopes attendee lists per event, which works for one event at a time but makes it hard to read the operational picture across a multi-event day.

Charts reads the attendee CPT and aggregates it into number, pie, bar, and area cards. Total checked-in versus pending, ticket-type distribution, attendees per event, and registrations over time become four cards on the same screen. Each card uses the same attendee meta the FooEvents Check-Ins app and the badge generators use, so the numbers match what staff see on the door.

The dashboard is built for the rituals organizers run on event day: a quick check on check-in pace per event, a ticket-type breakdown for the catering count, and a registrations-over-time card for the marketing close-out. None of it requires a second reporting plugin or a CSV export to a spreadsheet.

Ticketing is a tempo problem: a registration push opens, attendees arrive, the day rolls, refunds happen, the next event opens. Event Tickets captures every piece of that data correctly in attendee posts and order records, but the default admin renders it one event at a time. The cost is procedural, not technical: organizers re-derive their catering and staffing numbers from the attendee list each morning, the door team has no visibility into check-in pace until staff phone in a status, and finance reconciles refunds in a separate tool.

Charts brings the same data into four cards on one screen. Total attendees, check-in status, per-event counts, and a weekly registration trend live in the admin where the events live, and the cards read the same status meta the scanner app writes. The data is the same; the dashboard finally exists.