Platform
One record of the term, read three ways
Hiilu is not a suite of separate tools stitched together. A class, its roster, its sessions, its work and its money are the same record, seen from wherever you happen to be standing.
Catalogue
Categories, programs and courses, with the class offerings scheduled under them. The structure a school already describes itself with, rather than a flat list.
Enrolment
Places, capacity and rosters. A class knows how many seats remain, and an enrolment knows whether it has been paid for.
Schedules
Recurring sessions generated from a class schedule, a school-wide calendar, and per-student and per-teacher views of the same week.
Attendance
A register per session, taken in one pass. Rates are reported with the number of sessions behind them, never as a bare percentage.
Private lessons
Teachers publish availability in their own timezone; students book a real slot and pay for it at the point of booking.
Tuition
Plans priced for a course or for the school, checkout for a reserved place, and a clear state for every enrolment — paid, pending, or past due.
Assignments
Work set against a class, submissions collected as private files, marks entered once and visible to the student who earned them.
Announcements
School-wide, by role, or to a single class — with a bell that counts only what a reader has not already seen.
Reporting
Enrolment, attendance, submissions and teacher earnings. Every figure is computed from records, and an incomplete one says so.
What we do not do
Honest about the edges
Hiilu does not keep your general ledger, run payroll, or replace an accountant. It reports what teachers are owed and what students have paid; moving the money is done where money is already moved. There is no marketing automation and no CRM. The scope is the school term, on purpose.
See Hiilu with your own school’s shape
A short walkthrough, using the programs and classes you actually run — not a generic demo dataset.