Sensei's data model splits the work. Courses, lessons, and quizzes are custom post types. Progress, attempts, and grades live in wp_sensei_lms_progress. The default Students screen lists enrolments one course at a time, so cross-course charts (completion-rate share, quiz score trends, stalled-cohort counts) require either Pro reports or manual aggregation.

SleekView Charts reads the progress table and the course post type together. A Number card shows total completions this month. A Pie card breaks down progress by status across the catalogue. A Bar card averages quiz score per course. An Area card plots completions over time so seasonal patterns and post-launch slumps become obvious at a glance.

Filters propagate across the dashboard. Pick a course, group, or date range and every card recomputes against the filtered subset. Cards link to the matching SleekView Table so a high stalled count opens the per-learner queue and a low completion bar opens that course's enrolment list.

Sensei's strength is clean course delivery. The progress table is well-structured, the post types are clean, and integrations work. What's missing is the operational dashboard most academies actually want: completions trending up or down, status share moving the right direction, per-course quiz averages ranked at a glance, stalled-cohort counts visible the moment you sign in.

The default Students screen is one course at a time, by design, because most early Sensei sites had one or two courses. Past a handful of courses, the cross-course view is the daily question and the per-course list is the exception. SleekView Charts reads the same progress table the Tables view reads and turns it into configurable cards, with cross-card filters that scope to whatever slice the team needs that day.