KursOS: lesson schedule, collections and teacher earnings on one record

A school management system is software that keeps an educational institution's timetable, student records and lesson packages, teacher assignments, room usage, collections and teacher payments in a single database. In art and music schools the distinctive requirements are the recurring weekly lesson series, room-type requirements and the number of lessons deducted from a package. KursOS is a multi-tenant school management system that delivers this structure under the institution's own brand.

• Art schools and studios: painting, ceramics, sculpture and design studios; capped groups, room-type requirements, term packages.
• Music schools and conservatoire preparation: one-to-one lessons, teacher assignment by instrument, room conflicts.
• Language courses and tutoring centres: level groups, absences, assignments and parent updates.
• Sports and hobby academies: recurring weekly timetable, trial lessons, waitlists.

Calendar and recurring lesson series

A lesson is defined as a series: once a week, at the same time, with the same teacher. When you change one day, the system asks for one of three scopes: only this lesson, this and the following ones, or the whole series. The change does not spill beyond the scope you chose.

The calendar has five views: day, week, month, teacher and room. The room view shows a conflict before it is placed; the teacher view shows at a glance whose week is full.

Studios, rooms and capacity

Each service carries its own duration, capacity and required room type. The ceramics studio needs the room with the kiln, the painting studio the one with daylight; the system does not let an unsuitable room be scheduled. Preparation and clean-up time can be defined between lessons, so two studio sessions that fit back to back on paper do not end up not fitting in practice.

In an institution with branches, each branch has its own working hours and holiday calendar. No lesson can be written into closed hours; a branch-specific holiday stops only that branch.

Students, teachers and packages

A student is attached to a lesson package; the number of remaining lessons drops with each completed lesson. For a student who does not turn up, the institution's policy applies: the lesson is forfeited or turns into credit. Teachers see only their own students.

Waitlist and trial lessons

When capacity is full, the enrolment goes onto the waitlist. When a place opens, an offer goes to the next person; if they do not reply in time, the offer passes to the following one. A trial lesson is a separate record type and is not deducted from a package.

Assignments, announcements and the portal

Teachers set assignments and attach files; students upload their submissions. Institutional announcements go to the relevant group. Students and parents see the timetable, remaining lessons, assignments and outstanding balance on their own portal.

Finance: collections, balances and earnings

Payments are recorded and the outstanding balance is visible per student. There is a rule that blocks lesson scheduling when a payment is overdue; the institution can keep it on or off.

Teacher earnings are calculated under one of three models: a fixed amount per lesson, a percentage of collections, or salaried. All three models can be used side by side in the same institution; each teacher is calculated under their own model. Collections, balances and earnings are taken from the same report screen.

The mobile app: four roles, one app

Coordinator, teacher, student and parent all use the same app; whoever signs in gets their own role's screens. The thing a teacher does most in the room — taking the register — is one tap away, with lessons, announcements, assignments and packages on their own tabs. A teacher or parent attached to more than one institution switches between them from a list.

The app has a demo sign-in: one button for each of the four roles opens a sample institution, and the demo data is refreshed to today on every sign-in, so the dates are never stale.

Messaging and reminders

WhatsApp is connected through the institution's own Meta account. Incoming messages are collected in one inbox and handed to a coordinator when needed. Lesson reminders go out through approved templates; the system keeps a ledger of approved templates and lists as warnings any templates a reminder needs but that have not been approved.

KursOS is a product name; it is not the name your students and teachers will see. The system was built multi-tenant from the start and no single institution's name is hard-coded anywhere. The deployment carries your brand in three places at once:

So the address, the interface and the brand your students see are yours. Several business units can also run under the same institution: an art school and a music department stand with separate timetables, separate teaching staff and separate service lists, while student and payment records are shared.

Tenant isolation is enforced at database level: a query with no tenant returns no data. Permissions are role-based and re-read on the server with every request; when a permission is revoked, it takes effect on the next operation. Who changed what and when remains in the audit log.

Deployment and licensing

It is enough to contact us with your institution's name, the number of students and teachers, and your main way of working (one-to-one or group); your enquiry is answered with proposed times for a live demo.