The pattern was there for months. Nobody joined the dots.
Chaimount started when a class teacher noticed - too late - that a student had been slipping since the second week of term. The attendance was in one register, the grades in another, and neither system talked to the other until report cards went out. We are building the thing that talks to both.
Three things we hold to
Early warnings from combined signals, not one metric alone.
A single attendance number and a single grade number, read separately, tell you almost nothing. Read together they tell you a lot. Chaimount is built around that fact.
Timetabling that does not start from a blank spreadsheet every term.
Rebuilding the school schedule from scratch every term is not a rite of passage - it is a task the software should have handled.
Parents kept informed consistently, not just at report card time.
The families who ask the loudest should not be the only ones who hear from the school. Coverage evens out when the mechanism is automated.
The lines we hold
Surveillance features
No browsing tracking, no keystroke logging, no location capture. That is not a school-management problem to solve.
Facial recognition attendance
Attendance is a class-list workflow. Facial recognition solves a problem that mostly is not there, and creates several that are.
Selling data to third parties
Student, parent, and school data is not a product line. It is the school's data - Chaimount is a custodian.
Talk to the team.
The registered office and full contact details are on the contact page.
Tell us your school.
Watch the grid draw itself.
Move the sliders. The grid on the right rebuilds at your scale, and one cell flags amber - an illustrative view of the signal you would see on your own school if a student began falling behind.
An illustrative view based on typical patterns - not a live read of your actual school data.