Sugar Calendar's architectural choice to keep events out of the WordPress posts table is the reason a busy site stays fast. The cost is that the post-list affordances WordPress users expect, including aggregate totals and grouped views, have to be built rather than inherited.

Charts reads wp_sc_events directly and joins wp_sc_eventmeta for per-card breakdowns. Total upcoming events, calendar mix, events per recurrence pattern, and weekly programming density become four cards on one screen. The dashboard preserves Sugar Calendar's speed because every query runs against the same indexed columns the plugin uses internally.

For multi-team setups, the calendar field becomes the primary dimension. Internal, Sales, Holidays, and Marketing each show up as a slice on the calendar pie, and each team can save its own filtered dashboard without needing a separate reporting plugin.

Sugar Calendar made the right tradeoff for performance by keeping events out of the WordPress posts table. The downside is that the post-list affordances WordPress users expect, including aggregate totals and grouped breakdowns, do not come for free. A single team using Sugar Calendar for weekly meetings can live with the default list, but as soon as the calendar splits across Internal, Sales, Holidays, and Marketing, the team needs a per-calendar dashboard.

Charts reads wp_sc_events and wp_sc_eventmeta directly and aggregates them into number, pie, bar, and area cards without losing the plugin's speed benefit. Each team saves a dashboard scoped to its own calendar, and the same plugin admin becomes the planning surface for every function instead of a list to be hand-counted.