Watu Quiz (and Watu Pro) keeps a thorough record of every taking and every answer. watupro_taken_exams stores score, pass status, time taken, user, and quiz ID. watupro_taken_answers stores the per-question correctness data. The native admin gives per-quiz takings lists and aggregate counts but stops short of cross-quiz dashboards with item-level analytics.

SleekView Charts reads both tables and renders a configurable dashboard. A Number card counts total takings this month. A Pie card splits passed and failed across the catalogue. A Bar card ranks quizzes by takings volume. A Line card plots daily activity so course designers see when learners are most active. Per-question difficulty audits live in a second dashboard built from watupro_taken_answers.

Charts refresh live from the Watu tables, so inline regrades, certificate issuance changes, and new takings all flow into the next render. The default Watu admin keeps working; SleekView Charts only adds the cross-quiz and item-level surfaces the operational layer needs.

Watu has been around long enough that its storage is robust: every taking and every answer persisted, with categories and certificates handled in Pro. What it never grew was a dashboard layer. Instructors review per-quiz drill-downs; designers iterate questions on gut feel; L&D admins find issuance failures only after a student reports them.

The signals are already in watupro_taken_exams and watupro_taken_answers. SleekView Charts reads them and builds Pie, Bar, Line, and Number cards that finally answer the operational questions Watu deployments hit at scale, without changing how the plugin renders quizzes or issues certificates.