How to Track Student Progress Using an LMS

You publish the course. Students enroll. And then you genuinely have no idea what’s happening inside it.

That’s the default state for most instructors, and it’s fixable. Your LMS is already collecting the data you need. The problem isn’t a lack of information, it’s knowing which numbers actually tell you something useful versus which ones just fill a dashboard.

Key Takeaways

• Completion rate alone is misleading, a student clicking through every lesson while failing quizzes isn’t learning
• Login patterns are your earliest warning sign for students about to drop out
• When 60%+ of students struggle with the same lesson, the content is the problem, not the students
• Automated alerts for inactivity buy you a window to re-engage before someone mentally quits
• Qualitative feedback (even one question per week) explains what the numbers can’t

The Metrics That Actually Matter

WordPress LMS plugins such as FoxLMS, show you everything, and that’s great. Resist the urge to track all of it.

Start with four numbers: completion rate, assessment scores, time on task, and login frequency. Those four tell you almost everything you need to know about whether a student is genuinely learning or just going through the motions.

Completion rate is the most visible metric and the most misread one. A student who races to 100% completion while averaging 58% on quizzes isn’t succeeding, they’re skipping. Completion only means something when you pair it with how they’re actually performing.

Assessment scores reveal understanding. Quiz results, assignment grades, project submissions, these show whether the content is landing. Track both individual scores and class-wide averages. If 40% of students bomb the same quiz, that quiz (or the lesson before it) needs work.

Time on task is the one most instructors ignore. If someone “watches” a 12-minute video in 90 seconds, they didn’t watch it. Most LMS platforms flag unusually short session times, pay attention to those. 

On the other end, a student spending 3 hours on a 20-minute module is probably stuck and won’t ask for help unless you reach out first.

Login frequency is your early warning system. Daily logins dropping to nothing over 5–7 days is almost always a sign someone is about to quit. You have a short window to re-engage them before they mentally check out.

Setting Up Tracking That’s Actually Useful

The default settings on most LMS plugins are too loose. “Completion” often means a student opened the page, not that they engaged with it. 

Define what completion actually means for each content type. For example FoxLMS has very detailed documentation for each feature which helps you easier navigate through how it works. 

Videos: watching at least 80%. For quizzes: submitting answers, not just opening them. For written lessons: a minimum time on page. It takes 20 minutes to configure this properly and it makes all your data more trustworthy.

For longer courses, milestone tracking works better than tracking the whole course as one unit.  When you are stuck in a long course without breaks along the way it almost feels like you never have progress. Breaking your course into modules give students the sense of progress, and you are able to better track where the engagement is the highest and where it drops. 

If you’re still building the course structure itself, thinking about progress checkpoints from the start makes this whole process easier. 

Reading Your Reports Without Drowning in Data

Here’s a scenario: you log into your LMS and see a student who scored 92% on the first three quizzes suddenly dropping to 71% on the fourth. The first instinct is usually “they’re struggling.” But often that drop means they’ve hit content that requires a different skill set, not that they’ve stopped trying.

Context changes everything. Before you intervene, look at what changed at that point in the course. Did you introduce a new format? A harder concept? New software? The pattern tells you where to look, not necessarily what’s wrong.

Class-wide patterns are often more useful than individual ones for improving your course. If 65% of students drop off at lesson 6, lesson 6 has a problem. Could be the content is unclear, the lesson is too long, or it introduces something without enough setup. Individual tracking would never catch this, you need the aggregate view.

Two things worth tracking side by side:

• High completion + low scores → students are rushing, not engaging. Add required knowledge checks before they can advance.
• Low completion + high time on task → content is too hard or confusing. They’re trying, just stuck.

What to automate vs. what to review yourself

Let the system handle the routine stuff: completion rates, login frequency, quiz scores. Set it to generate a weekly summary you can read in five minutes.

Review personally: discussion forum activity, support requests, any student flagged for unusual patterns. These are the ones that need a human response, not an automated email.

Spotting Students Who Are About to Quit

Students don’t fail suddenly. They show signs for weeks before they stop logging in entirely.

The pattern I see most: strong start, 2–3 lessons completed quickly, then nothing. These students usually underestimated the time commitment. They’re not disinterested, they’re overwhelmed by everything else in their life. A short personal email asking if they need help resetting expectations works better than a generic “complete your course” reminder.

“Surface skimmers” are different. They complete everything fast but fail assessments consistently. They’re clicking through without reading or watching. Adding a required quiz before unlocking the next lesson forces engagement,  or at least makes the skipping visible.

Grade decline over 2–3 consecutive assessments is worth a direct message. Not a form email. Something specific: “I noticed your last couple of quiz scores were lower than your usual, are you hitting a wall on this topic or is there something else going on?” That specificity shows you’re actually paying attention, and students respond to it.

Five-day login gap on a weekly-paced course = reach out immediately. The re-engagement window is short. After about 10 days of absence, most students have mentally moved on.

Automated Alerts Worth Setting Up

Most LMS plugins let you configure threshold-based notifications. Here’s what’s actually worth setting:

• No login for 5+ days (for a weekly-paced course) — triggers a personal check-in email
• Two consecutive failed assessments — flags the student for manual review
• Completion of a major milestone — sends an automated congratulations (these improve momentum more than most people expect)
• Course completion — triggers a certificate + a follow-up asking for a review

Keep automated messages short and specific. “You haven’t logged in this week, here’s a direct link back to where you left off” outperforms “Don’t give up on your learning journey!” by a wide margin. People can tell the difference between a system message and something that was actually written for them.

Reporting for Different Audiences

If you run courses for a training center or corporate client, you’re reporting to people who don’t need (or want) individual student details, they need the aggregate picture.

Student-facing dashboards should show progress, not deficiencies. Completion percentage, upcoming deadlines, quiz scores with room to retry. The goal is to motivate, not to make someone feel behind.

For administrators or corporate clients: completion rates by cohort, average scores, drop-off points, and time-to-completion data. Skip individual names unless they’ve specifically asked for that level of detail.

If you’re managing multiple instructors or courses, cross-course data becomes useful — which courses have the best completion rates, which have the most support requests, which ones consistently produce students who come back for more.

Mistakes That Make Your Data Useless

Tracking too many metrics at once is the most common one. If your weekly report takes 30 minutes to read, you’ll stop reading it. Pick your 4–5 most important indicators and ignore the rest until you have a specific reason to look deeper.

Drawing conclusions from single data points. One bad quiz doesn’t mean a student is failing. One week of low logins might mean they had a busy week at work. Look for patterns across at least 2–3 data points before acting on anything.

Ignoring context. A student logging in at 2am every night might be in a different time zone, or working nights, or cramming before a deadline. The data tells you what’s happening. not why. Always verify before assuming.

And on privacy: be clear with students from day one about what you track and why. Most people are fine with it when it’s framed as “this helps me support you better” rather than surveillance. In some regions (EU especially) you have legal obligations around student data, worth a quick check before you start storing anything.

Use the Data to Teach Better, Not Just to Keep Records

The point of all this isn’t a cleaner spreadsheet. It’s catching the student who’s two days away from quietly quitting — and giving them a reason to stay.

Start simple. Completion rate and quiz scores, a weekly summary, one automated alert for inactivity. That’s genuinely enough to run a better course than 90% of what’s out there.

Add layers as you get comfortable with the data. But even the basics, applied consistently, will improve your completion rates, your reviews, and the quality of what you’re building.