Teacher insights.

"Teacher insights" is an easy phrase to abuse. YESS draws a hard line: this module is about coverage and compliance — whether the curriculum is being delivered on schedule and the records are being kept — to help a head of department support a teacher who is falling behind. It is not a productivity score, not a ranking, and not a way to read a teacher's grades against their colleagues.

It is also worth being straight about which dimension is actually built. The marketing line reads "impact, coverage, engagement." Today, coverage is the real, working, per-teacher dimension — the report at /dashboard/lms-reports reads it live from the tables teachers fill in. Impact (results attributable to a teacher) and engagement (attendance and participation rolled up per teacher) are not yet aggregated at the teacher level — they are on the roadmap at the end of this book, and we say so rather than pretend a chart exists.

There are three insight surfaces in the app: the per-teacher coverage report, a classroom analytics lens at /dashboard/teacher-insights, and a student at-risk view at /dashboard/lms-analytics. The chapters below take each in turn, and are clear about how finished each one is.

The question is not "is this a good teacher?" — it is "is this class on schedule, and who needs help staying there?"

The built heart of this module is the report at /dashboard/lms-reports. It is a leadership screen — gated on the permission that lets a principal, a vice- principal, a head of department, or an owner see every syllabus plan, not something an individual teacher opens on a colleague. Pick an academic year and a term, and it renders a table with one row per teacher.

Beneath the teacher table sits a second view: subject progress by section — completion percentage and overdue topics per subject and section — plus a history of delivered reports. The whole page exports to CSV or PDF for a governors' pack, and its KPI strip totals the teacher count, the average syllabus completion, the subject-section count, and the open alerts.

A completion rate is a number; an alert is a nudge. YESS generates alerts from the same coverage data in three flavours: behind-schedule (a teacher's overdue topics have crossed a threshold), missing-logbook (lessons taught without a logbook entry), and at-risk (a student whose signals say they need intervention). The active-alert count on each teacher row is the front of this; the alerts themselves link back to the teacher and subject they concern.

A leader can trigger alert generation on demand from the report. The scheduled version — regenerating alerts on a daily cron — is opt-in and off by default, so on a stock install a leader runs it from the button rather than waking up to a fresh batch. Turning that cadence on by default is a planned change.

The screen that literally carries the name "teacher insights," /dashboard/teacher-insights, is a different instrument: a classroom analytics lens meant to help a teacher plan re-teaching. It has two tabs — the hardest quiz questions (ordered by accuracy, worst first) and the weakest course topics (ordered by how many students are struggling) — drawn from real analytics views over quiz attempts and topic progress.

Be aware of its maturity: the underlying views are real, but the finer per-question and per-topic breakdowns on this screen are being reconnected to the current analytics schema, so some columns are still settling. Treat this lens as a developing companion to the coverage report rather than a finished dashboard — the roadmap below tracks the reconnection. For a firm number today, the coverage report in chapter one is the surface to trust.

One surface over is the student-facing side of the same intelligence: /dashboard/lms-analytics, which reads student performance and surfaces at-risk students and the interventions logged against them. It answers a different question than the coverage report — "which students are slipping?" rather than "which classes are behind schedule?" — but the two are read together: a behind-schedule class and a cluster of at-risk students in it are the same story from two ends.

Coverage is built; the other two dimensions of the promise are not yet. Here is the honest backlog, so you can plan around it.

Teacher insights is downstream of the logbook, the gradebook, and attendance — it reads what those modules record. Here is what feeds it.