A management system for a training centre

In a training centre the most expensive loss is the one nobody sees.

A student misses two classes, then does not turn up for a third, and gradually disappears. Nobody looked for them, because nobody noticed - the register sits with the teacher, payments with the administrator, and contact with the parent nowhere at all.

A month later the group has halved and the reason is unclear.

Where students are lost

The first week. A prospective student attends a trial class but never enrols. Their contact details are recorded nowhere.

When attendance drops. Two missed classes trigger no alert. After a third, returning becomes psychologically harder.

At the payment date. A parent forgets, no reminder arrives, and the student stops coming.

At the end of a course. The course finishes and nobody invites them to the next one. They enrol somewhere else.

Each of the four is preventable, but only when the data sits in one place.

What the system covers

The last line matters most, and it is usually missing. Without a retention figure it is impossible to tell whether the centre is growing or standing still.

The parent portal has the largest effect

This module delivers more than expected and it is usually left until last.

In the portal a parent sees which classes their child attended, which were missed, the payment status and any comment from the teacher.

That changes three things:

Fewer phone calls. An administrator answers dozens of "how is my child doing" questions a day. The portal absorbs most of that work.

Attendance improves. A parent learns about a missed class the same day rather than at month end.

Payments arrive on time. Reminders go out automatically and arrears fall.

Attendance: who marks it and how

This is an organisational question, not a technical one.

The teacher should mark it from a phone at the start of the class - a matter of seconds. If it stays in a paper register and the administrator enters it later, the data arrives late and loses its value.

Practical requirements:

• The teacher marks from a phone, not from a computer
• The group list fits one screen and the task completes in three steps
• Marking an absence sends a notification to the parent
• Two consecutive absences raise an alert for the administrator
• If the connection drops, the data is stored and synced afterwards

The fourth is the most valuable. That alert is what prevents a student from being lost - call in time and most of them come back.

Payments and arrears

Payment models vary: monthly, per course, per class, or a pass.

The system needs to handle all of them, but something else matters more - visibility of arrears.

In practice what happens is this: the student keeps attending, the payment slips, the administrator feels awkward chasing it, and three months later the amount is substantial.

The system closes that: a reminder goes out automatically three days before the due date, overdue accounts appear as a list for the administrator, and beyond a set threshold the student's status changes.

The reminder being automatic matters - it is impersonal and therefore causes no awkwardness.

How the rollout runs

The second step generates the most resistance. Teachers are used to a paper register and marking from a phone feels awkward at first. The interface must not exceed three steps, or they will go back to paper.

What to measure

The first and last are the key ones. Acquiring a new student costs several times more than keeping an existing one.

What it costs

For most training centres the first option is enough - the processes are similar. A custom build is justified for online learning, video content or a distinctive assessment model.

In our experience over 10,000 students are active in education systems we have built.

In summary

A training centre system is not for managing a timetable. It is for not losing students.

Practical steps:

1. Calculate what share of students completed your last three courses
2. Bring attendance and payments into one place - the alert comes from there
3. Test the teacher interface with a teacher, not with an administrator
4. Launch the parent portal early
5. Make the "two consecutive absences" alert mandatory