An administrator at the school we worked in spent two hours of every day copying paper attendance sheets into Excel. Not two hours a week: two hours a day. Digitising a language school almost always starts exactly there, with the task everybody can see.
We removed it. The centre's admin workload did not go down.
This is what happened next, why we had picked the wrong starting point, and how to spot the task that is really eating your team's evenings. At the end there is the order we would follow today, and why attendance is almost never the thing to digitise first, however visible it is.
The two hours we did measure
The routine was the one every centre without a system runs. Teachers took the roll on paper, in class. Somebody collected the sheets at the end of the day. Then somebody sat down and typed them up by hand, line by line, into a spreadsheet.
Those two hours were easy to measure for three reasons: the task had a name, it had a person attached to it, and it happened at the same time every day. When a task meets those three conditions, anyone who walks through the door notices it in their first week.
So we built the obvious thing. Attendance was taken digitally and arrived where it needed to arrive on its own. It worked. The two hours of typing genuinely disappeared.
And that was exactly the mistake.
What we did not measure: tomorrow's sheet
We had measured the two hours of re-typing. We had never measured what came after them.
Because that spreadsheet was not a record of what happened yesterday. It was the plan for tomorrow. It had to be rebuilt every afternoon so that the next day's registers showed the right students, in the right room, with the right teacher.
And in a language school students change level constantly. Mid-week, not at the end of term. Every change meant editing the following day's classes by hand without breaking anything else: take the student out of one group, put them into another, check that the receiving group still fits its room, tell the teacher who is about to get them.
Nobody had ever counted those hours, because they were not an official task. They had no name and no owner. They simply ate the evening of whoever was nearest.
So we made the data entry disappear, and the hard part did not move an inch. The real problem was never the typing. The typing was just where the problem surfaced.
The four things that have to line up
When we finally looked at the work that was left, it was obvious. For tomorrow's class to exist, four things have to agree with each other, and in a school without a system they live in different places:
Which teacher, and from which date to which date.
Which level they are teaching in that period.
Which room they have been given, and in which slot.
Which students are enrolled on that level, and from when until when.
All four are bounded by dates. A teacher who starts on the 14th, a student who withdraws on the 30th, a group that moves room next week. Change any one of them and tomorrow's classes are wrong, and nobody finds out until a teacher walks into an occupied room or takes the roll from a register that is missing half the class.
Reconciling those four relationships was the real cause of the two hours. The attendance register was the output of that reconciliation, not its source. Digitising the output changed nothing fundamental, because we were still rebuilding the source by hand every afternoon.
What we built next was the room and timetable system: one place where those four relationships are declared once, with their dates, and where changing one thing recalculates the rest. That was the exact moment this stopped being a script that saved somebody some typing and started being a product. If that part is what interests you, we go into it in timetabling for language academies.
Why this hits language schools harder than it hits a K-12 school
A school builds its timetable once a year and barely touches it. A student who moves group mid-year is an exception, handled by hand, and nothing breaks.
A language academy works the other way round. Intakes are rolling: new students arrive every week or every fortnight. Placement carries on all year, and a student who progresses does not wait for the next term to change group. What is an exception in a school is normal operation in an academy.
That produces a very concrete problem when you go shopping for tools: most school software assumes the group is stable for the duration of a course. When the group moves every week, that assumption does not fail with a visible error — it fails as manual work that somebody quietly absorbs. It is the same reason there is a real difference between generic school software and a system built for language academies.
How to find your own invisible hours
If you are about to digitise your centre, the risk is not choosing the wrong supplier. It is choosing the wrong problem, which is what happened to us. These five questions find the work that appears on nobody's task list.
1. Follow the data, not the task
Pick one piece of data: a new student's name. Ask where it is written for the first time, and how many times it is written again afterwards — on the enrolment sheet, the group sheet, the register, the fees sheet, the email that goes to the teacher. Every rewrite is time, and it is a place where two versions can stop agreeing.
2. Look for the work that happens after closing
Invisible tasks nearly always happen outside opening hours, when nobody is coming through the door any more. Ask your team what they do in the last hour of the day. That is usually where tomorrow's rebuild lives.
3. Run the mid-week change test
It is the fastest test I know. Take a real change — a student moving up a level on a Wednesday — and count how many places have to be touched for it to be correct: the group, the room, the teacher's register, the attendance record, the fee if the level is priced differently. If it is more than two, you do not have a data entry problem. You have a duplicated data problem.
4. Count the tasks with no owner
If you ask who does something and the answer is "it depends" or "whoever is around", you have just found an invisible task. The cost you can see is the one with a name and a person attached to it. The one actually hurting you tends to be spread across everybody's evenings, which is precisely why nobody has ever added it up.
5. Measure a week, not an impression
For five days, have each person note what they did and how long it took, in fifteen-minute blocks. No more ceremony than that is needed. The list that comes out looks surprisingly little like the one you would have written from memory, and it is the one that should decide where you start. If your centre currently runs on spreadsheets, this pairs well with reading how a school attendance spreadsheet is built: first understand what the sheet is doing, then decide what to replace.
The order worth digitising in
With all that on the table, the order we would recommend today is close to the reverse of the one we followed.
First, the data everything else uses. One student record with its history: which levels they have taken, from when, until when. While the student lives on four different sheets, anything you build on top will need somebody keeping those sheets in sync by hand.
Then the assignments, with their dates. Teacher, level, room and period. It is the boring part and it is the part that produces tomorrow's timetable. Once it is declared in one place, moving a student up a level goes from an evening's work to one action with the right consequences.
Then what rests on that. Attendance, assessment, progress reports. This is where you do win the two hours, and you win them properly, because tomorrow's register is already correct without anyone assembling it. That is what academic management covers when it is set up in the right order.
Last, what faces outwards. Family communication, fee collection, the student portal. Not because they matter less — they are usually the most noticed — but because they feed on the three points above. A portal showing figures somebody is correcting by hand costs more than having no portal.
Centres that made the change in this order tend to report something odd at the start: for the first few weeks it does not feel like you are saving time. That is normal. What you are doing is stopping the daily rebuild of the foundation, and that saving shows up later — the first busy intake week when nobody is still there at eight in the evening. There are several worked examples in our customer stories.
Frequently asked questions
So is digitising attendance not worth it?
Of course it is. What does not work is treating it as the starting point. Digital attendance is a consequence of having groups, levels and dates properly resolved. Digitise it before that and you have automated the copying of a figure you are still producing by hand.
How do I tell a data problem from a process problem?
A process problem is fixed by changing who does what and when, and sometimes that is enough. A data problem is still there after you reorganise the team, because the same information lives in several places and somebody has to keep them agreeing. The mid-week change test separates them well: if touching one thing forces you to touch four, it is data.
How long does it take to digitise a language school?
It depends far more on the state of your data than on the software. A centre whose students and groups are tidy in spreadsheets starts operating quickly; one whose records are spread across emails, paper and two people's memory needs a clean-up first, and no tool does that for you. Which is why the clean-up is worth doing before you choose a supplier, not during.
What if all I have right now is spreadsheets?
That is a perfectly reasonable starting point, and up to a certain size the spreadsheet is the right tool. What matters is recognising the moment it stops being right, which is rarely when the sheet gets big — it is when there start to be several versions of the truth. We walk through that move step by step in migrating from spreadsheets to a school system.
What I took away from it
Being close to a problem helps you spot it. It does not automatically hand you the right solution. We worked in the school, we watched those two hours happen every day, and we still built the wrong piece first, because we measured the thing that had a name.
If you are digitising your centre this year, spend a week looking at the work that has no name before you look at any tool. And if you want to see how a system designed around that problem behaves — groups that move, students changing level mid-week, dates everywhere — you can try KMPUS free with your own data and run the Wednesday test on it.
