Reach students before they drift away
By the time a bad grade appears, the student has usually been struggling for a month. Their coursework activity knew weeks before the gradebook did — and that is the window where you can still do something about it.
In a class of ninety, the student who is quietly lost looks identical to the student who is quietly fine. You find out in week nine, when the only honest advice left is to consider withdrawing.
The signal arrives before the grade does
Activity, module progress and quiz history combine into a per-student picture, and the ones drifting get lifted to the top instead of hiding in row 47 of a table of ninety.
And the shape of the drop matters. A student whose activity falls off a cliff in week four is a different conversation from one who never started, and the roster tells them apart.
Three questions it can answer on a Monday morning
βWho has gone quiet?β
An inactive list plus a class timeline, so you can tell a slow week for everyone apart from one person disappearing. The first needs no action. The second needs an email today.
βIs it them, or is it me?β
Per-question quiz analytics and tool mastery show whether one student missed something or whether two thirds of the room did, which changes what you teach on Tuesday.
βWhat do I open with?β
One student's usage, engagement, module progress, quiz history and badges in a single view. You walk into the conversation already knowing where it went wrong.
Where the signal comes from
β οΈ The fair objection
"This sounds like surveillance, and my students would hate it."
Then it is worth being exact about what is collected. Coursework activity: which tools were run, which modules opened, which quiz items attempted. Not keystrokes, not webcams, not browsing outside the platform, and no proctoring anywhere in the product. Students see their own progress in the same detail you do. The entire purpose is a five-minute conversation in week four, and the privacy position is documented in full for anyone who asks for it.