How to track student progress in a language school

Every small language school runs into the same situation. The owner or the coordinator wants to know how students are progressing, but cannot sit in on every class. They ask the teacher, get an upbeat answer, and walk away feeling like that read is only half the picture. The teacher has a rapport with the student, saw it up close, speaks highly of them. But that is not data, it is an impression.

And once the base grows past a few dozen students, that one-on-one conversation simply stops scaling. The coordinator does not have time to pull a report from each teacher every week, and the teacher does not have time to write a detailed note on every student. Student progress becomes a topic that only comes up when someone asks to cancel.

Why tracking progress in a school is different from tracking 1 student

When a private teacher follows a student's progress, they are looking deeply at one name at a time. They remember the topic of the last class, the recurring mistake, the goal for the week. It works because the universe is small.

In a language school, the problem is different. The coordinator needs a top-down view of the whole base, and at the same time needs to be able to drill down to the individual student when something stands out. They want to answer questions like:

• Which students at the school are progressing at the expected pace;
• Which ones have been stuck for weeks and are at risk of canceling;
• Which teacher is managing to keep students engaged in speaking;
• Which student joined three months ago and still has not moved past the same level.

These are management questions, not classroom questions. And no spreadsheet answers them in time.

How most schools try to track this today

The common setup is a mix of a weekly pedagogical meeting, a master spreadsheet on Google Drive, and a message in the teachers' group chat. The meeting pulls in the verbal report, the spreadsheet tries to standardize the records, and the group chat is for aligning on emergencies.

It works up to a point and breaks down in a few predictable places:

• The verbal report is subjective. Two teachers describing the same level of progress use different words, and the coordinator ends up comparing apples to oranges.
• The spreadsheet depends on the teacher stopping their week to fill it in. It is almost never up to date.
• Without objective class data, it is impossible to know whether a student really speaks less than they used to or whether it was just the teacher's impression.
• When the coordinator suspects something, they have to ask the teacher to "go back over the class" and come back with a diagnosis, which eats up hours nobody has.

The result is a school that only finds out a student stopped progressing once they have already announced they are leaving.

What a student-tracking system needs to do in a school

To scale the read on student progress across a school, three things need to work together:

1. Automatic collection of class data. The teacher cannot be the manual collection point. The system has to record, on its own, what happened in each session: how long the student spoke, which vocabulary came up, how frequent the classes are, the full history of when they joined the room.

2. Coordinator access to that data without sitting in on every class. The coordination team has to be able to see the whole base, compare students, and drill down into a specific student whenever they want, without relying on a verbal report.

3. Standardization across teachers. Every teacher needs to be generating the same kind of record, in the same format, so that comparing student performance across classes actually makes sense.

Without those three, any tracking of student progress goes right back to depending on what each teacher remembers about each student on a Friday night.

The cost of not doing this right

In a small online school, most of the revenue comes from existing students renewing. A student who cancels is expensive to replace, and usually cancels after a few weeks of a bad feeling that nobody noticed in time.

Student tracking based on the teacher's impression is, in practice, late discovery. The school only learns that a student felt they were not progressing once they have already decided to leave. And by then there is nothing left to talk about.

Learning metrics collected automatically give you a chance that the verbal report does not. They let you see, across the entire base, which students deserve a preventive conversation this week, and they give the teacher concrete material to open that conversation.

How Noladi solves this for a language school

In Noladi, every class taught in the live class automatically generates a set of data per participant. For each student who attended the class, the system records speaking time, the vocabulary used, class frequency, and the full history of post-class reviews. It does not depend on the teacher filling anything in.

Because the school is a single organization inside Noladi, the owner or coordinator with administrator permission sees the entire base: every student, from every teacher, with the same standardized indicators. They can open the post-class review of any session and check what actually happened, without having to ask the teacher to reconstruct the class from memory.

This changes the school's pedagogical conversation. Instead of a meeting based on impressions, the coordinator shows up with a real snapshot: these students dropped in speaking time over the last two weeks, let's understand what is going on. The teacher responds based on that same data, and the school can act before the cancellation arrives.

Get to know Noladi for your school

If you run a small online language school and want to stop relying only on what teachers report to understand how students are progressing, it is worth getting to know Noladi's school plan at noladi.app/school. Starting at R$ 499 per month, with live class, automatic post-class review, and a consolidated management view of your entire student base.