WP Meetings models meetings, agendas, and attendance as a custom post type with associated meta and a child taxonomy or table for attendees. The admin lists meetings one by one and exposes the agenda inside each meeting editor. Useful for the operator running today's meeting; a poor fit for the chair or governance lead reviewing the year.

SleekView reads the meeting CPT and the attendance records and turns them into chart cards. Upcoming meetings, status mix, attendance per meeting, and weekly cadence sit on one dashboard. The same cache the SleekView table view uses powers the cards, so chart and grid never disagree.

The dashboard does not change how WP Meetings stores meetings or attendance. The plugin still owns the agenda editor and the per-meeting view. SleekView reads the rows and groups them in the four shapes a governance review actually cares about.

WP Meetings is the right tool for managing today's meeting: agenda, attendance, minutes, all on the same per-meeting screen. It is the wrong tool for the chair who needs to know whether the team is keeping its rhythm. The data is structured, the rows exist, but the admin only ever surfaces one meeting at a time.

A KPI of upcoming meetings is the morning glance, a donut of status is the governance review, a bar of attendance is the format prompt, and a cadence area is the rhythm check. SleekView reads the meeting CPT and the attendance records, surfaces them as the cards above, and leaves the per-meeting editor untouched. The meeting screen stays the operator's tool.

The dashboard becomes the chair's review.