EventON registers events as a custom post type and stores the operational fields, including capacity, RSVP roster, and venue, as post meta. The plugin shines on the front end with its calendar block; the admin side is a standard posts list, which hides the totals coordinators read every morning.

Charts reads the EventON CPT and aggregates it into cards. Total upcoming events, status distribution, events per venue, and weekly programming density become a dashboard that maps to the rituals event coordinators already run. Capacity and RSVP count are exposed as fields so a card can compare seats sold to seats available across the schedule.

The dashboard preserves EventON Pro add-on data automatically. Repeat events, custom registration fields, and location coordinates feed the same aggregation engine the core meta uses, so a per-organizer breakdown takes one click once the add-on has registered its keys.

Coordinators run their week on aggregate questions, not on the events list itself. How many events are upcoming, how the status mix looks, which venue is carrying the heaviest load, where the programming gets thin: each of these is a number the default EventON admin does not surface. The data is captured correctly in evcal_event_status, evcal_location_name, and the start timestamp meta, but rendering it as a list forces every coordinator to count by hand.

Charts reads the same meta and aggregates it into number, pie, bar, and area cards on one screen. The dashboard becomes the morning glance the team already wishes existed, and the public calendar continues to read the same data without any duplication.