Tutor LMS Certificate hangs off the course completion event. When a learner finishes a course, Tutor sets the tutor_enrolled post to completed and the certificate add-on writes a postmeta entry recording which template was issued and when. The data is correct. The list of issued certificates is in WP Admin. Issuance volume per month, template mix, top courses by certificates issued and the issuance trend over time are not default visuals on either screen.

A learning programme that runs at scale cares about that picture. A drop in monthly issuance against a flat enrolment trend is the first sign that something downstream of completion is broken: the certificate template changed, the trigger lost a course assignment, or the gradebook scoring shifted enough that learners who used to pass no longer cross the threshold. Without a visual, the drop takes a quarter to surface, usually in the form of a learner complaint.

SleekView Charts reads tutor_enrolled, the certificate postmeta and the tutor_gradebooks rows directly. A Number card counts certificates issued this month. A Pie splits the issuance across templates. A Bar ranks courses by certificate count. An Area trends issuance per day against the catalogue release calendar. The whole picture lives on one screen, in WP Admin, next to the data it comes from, with no separate analytics pipeline.

A Tutor LMS site that runs at any reasonable scale quickly accumulates more configured certificate templates than the team can track in their head. Most issuance comes from two or three templates, the rest sit unused, and the small downstream changes (a renamed template, a moved course assignment, a new scoring threshold) silently change the issuance shape without producing any alert. The data is in WordPress already.

tutor_enrolled has the completion row, the certificate postmeta has the template, tutor_gradebooks has the underlying score. Putting those on a Number, Pie, Bar and Area card collapses what used to be a quarterly content audit into a thirty-second monthly glance. The team sees template usage at a glance, broken trigger configurations surface as a flat trend on the area card, and the conversation with the programme sponsor moves from "we think things are fine" to a live dashboard URL.