How to track teacher hours at a language school

Every online language school hits the end of the month with the same question. How many hours did each teacher work this month. The answer should be one click away. In practice, it usually comes from a spreadsheet that each teacher fills in on their own. Teaching hours become an agreement, not a number.

Why teacher hours are so hard to close out

At a small school with three, five, or ten teachers, teacher hours are the single most important piece of the operation. They decide how much each person gets paid, whether the schedule is balanced, whether one teacher is overloaded while another sits idle. And they tend to be the weakest link in the whole control system.

The reason is simple. Without a system of its own, the only way to know how many hours each teacher actually delivered is to ask them. At the end of the month the teacher opens a spreadsheet, remembers (or tries to remember) the classes they taught, and jots down the duration, the student, the date. They send it to the coordinator. The coordinator cross-checks it against the schedule, finds a discrepancy, asks for a correction, and waits for a reply.

The process works with one teacher. It breaks with five. With ten it becomes unworkable.

How most schools handle this today

The most common way to track teacher hours is an improvised stack of tools that were never built for it.

A Google Calendar shared with every teacher, each one adding their own classes. It works for seeing the day. It does not work for adding up hours at the end of the month, because Google Calendar does not export a per-person report with totaled durations.

A Google Sheets spreadsheet where each teacher reports what they taught. It works as long as every teacher is reliable and remembers to fill it in. It does not work when someone forgets an entire week, or logs a 50-minute class as a full hour, or marks a cancelled class as taught. And it does not work when the school wants to audit anything.

A WhatsApp group where a teacher posts "just finished a class with so-and-so." No comment.

Generic HR software (time clocks and the like) that records when the teacher clocks in and out but has no idea whether the class actually happened, whether the student showed up, whether it was a real lesson or a cancellation. It counts logged hours, not hours of class actually taught.

Each of these alternatives fails in the same place. None of them treats the class that really happened as the source of truth. They all depend on someone entering something by hand at some point.

What these alternatives are missing

The data about teacher hours already exists inside the school. Every class has a scheduled time, a teacher in charge, and a student. Every class that happened has a start and an end. Every class that did not happen has a reason. That data is all there, scattered across three places at once, and nobody pulls it together.

What is missing is a system that does two things at the same time. First, it records the class the moment it is scheduled and marked as taught, without the teacher having to write down anything extra. Second, it lets the coordinator look up the data by teacher and by period, whenever they want, without asking anyone for a spreadsheet.

That system has to understand that the basic unit is not "hours worked," it is "classes taught." It has to record real duration, not agreed-upon duration. It has to tell a class that happened apart from a class that was cancelled. And it has to do all of this without becoming one more chore for the teacher, because every extra minute of paperwork is a minute less available for teaching.

The coordinator should be able to open the system, pick a teacher, pick a month, and see: 47 classes taught, 38 hours and 20 minutes total, split across 12 students. Done. That is the finish line.

How Noladi handles teacher hour tracking

Noladi is an online teaching platform where every class at the school is recorded by the system itself. The teacher joins the room, teaches the class, and leaves. The record of a class taught does not depend on anyone filling in a spreadsheet afterward, because the live class is part of the platform itself. The start and end of every class are saved automatically.

Whoever runs the school can view the multi-teacher schedule by teacher and by period. They see how many classes each one taught in the month, with which students, at what times. They also see what is scheduled for next week, what was cancelled, what has not happened yet. All in one place, without switching tools.

Each teacher at the school has their own profile inside the system, with the permissions the coordinator sets. The system knows who taught which class because it was the teacher themselves who led the live session. There is nothing to dispute. The source of truth for teacher hours stops being the teacher's memory and becomes the school's actual calendar.

One thing worth separating out. Noladi shows hour tracking so the coordinator can close out the month, double-check it, talk it over with the teacher, and build the next schedule. It does not run payroll, it does not issue pay stubs, and it does not integrate with HR software. What it delivers is clean data on how many hours each person taught, with the confidence of something recorded class by class. The pay calculation stays with the school, now backed by the right number.

Get to know Noladi

A language school on Noladi starts at R$499 per month, with a multi-teacher schedule, live classes, student management, and reports. See how it works at noladi.app/school.