The dashboard nobody looks at
Your platform has a progress report. You opened it once, saw a long list of percentages, and closed it. You suspect a lot of students stop somewhere in module three, where the course moves from ideas to the first real piece of work. You do not know who, or when they stopped.
Months later, a student emails asking for a refund, well outside your window. They say the course 'did not work for them'. When you look, they stopped at lesson 3.2, the same lesson you have a feeling about. Nobody noticed at the time, including you.
Progress data exists but does nothing
Course platforms record which lessons each student completes. What they rarely do is turn that into action. The report is a list, not an alert. Automated emails, where they exist, are based on time since purchase, not on what the student has actually done. So a student who stopped at the hardest lesson gets the same 'how is it going?' email as one who is flying.
- Progress is visible only if you go looking.
- Nudges are sent by date, not by where the student stopped.
- The lessons where students stall are not identified.
- Students who stall tend not to ask for help.
What quiet stalling costs
Students who never finish rarely get the result they bought the course for, so they do not leave testimonials, do not buy your next product and do not recommend you. Some ask for refunds. Your course looks less effective than it is, because the people who would benefit most stopped at the hard bit. You also lose the feedback about which lesson needs improving.
Progress tracking that acts
- Lesson completions are read from your course platform through its API or webhooks, every day.
- Each student's last activity and furthest lesson are recorded, so the service knows who has stopped and where.
- You set what counts as stalled, such as no progress for ten days, and it can differ by module.
- For each lesson where students commonly stop, you write a short nudge: an encouragement, a shortcut, a link to a worked example or an invitation to the next live call.
- Stalled students receive the nudge for the lesson they stopped at, sent from your email tool as a normal email from you.
- Students who stay stalled after a nudge appear on a short list for a personal message from you or your team.
- A simple report shows which lessons produce the most stalls, so you know where the course itself needs work.
| Stopped at | Nudge (example) | If no response |
|---|---|---|
| Module 1, lesson 3 | A short 'most people skip this, here is the five-minute version' | Personal message |
| Module 3, first project | Link to a worked example and the next live call | Invite to a pod check-in |
| Final module | Reminder of the certificate and what finishing unlocks | Personal message |
Students who finish
Students who hit the hard lesson get help at the moment they need it, in your voice. You see who is stuck without trawling a dashboard, and your personal messages go to the people who most need them. Over a few cohorts, the stall report tells you which lessons to rewrite, which is more useful than any survey.
Refund requests from students who stopped months ago become less common, because you knew they had stopped and reached out while it still mattered.
Is this happening in your course?
- You do not know who has stopped progressing.
- Your automated emails are sent by date, not progress.
- Students ask for refunds after stopping partway.
- You suspect a particular lesson loses people but cannot prove it.
- Your platform's progress report is rarely opened.