SchoolLedger
The whole school. One connected system.
schoolledger.app
2026
Development recorded in the project repository. Earlier work may predate this history; this is not a confirmed launch date.Business systems
Inside SchoolLedger
Actual SchoolLedger dashboard with fictional demonstration data.
The problem
A school can become a collection of separate systems for admissions, the classroom, attendance, families, transport, communication and finance. The same person may be a parent, employee, donor or supplier, yet each tool records a different version of them and staff repeatedly bridge the gaps by hand.
The full problem is running the school as one organisation: keeping the school day and the money aligned across households and legal entities while giving office staff, teachers, families and drivers only the information and actions relevant to them.
The solution
SchoolLedger is the school's operating system. It connects people and households to admissions, enrolment, timetables, homework, grades, report cards, attendance, conduct, health, library, meals, parent evenings and transport, then connects the same relationships to tuition, donations, payments, expenses, payroll, banking and double-entry accounting.
The office app, family portal, driver screen, public site, messaging, document storage, support desk and tenant control plane share one governed record. Important rules sit in the database as well as the interface, including access boundaries and protections against duplicate billing or bookings. Hebrew and Gregorian dates run through the workflows, and AI-assisted changes are journalled and undoable.
The decisions behind it
- Relationships before screens
- A household, a student and a payer are related records with different responsibilities. The data model keeps those roles connected without treating them as interchangeable.
- Operations meet accounting
- A usable office screen must still preserve allocations, accounting entries and legal-entity boundaries. Financial rules cannot depend only on what a form allows.
- Different people, different access
- Families, office staff and drivers work from the same platform through distinct views and permissions.
- Student records, enrolment and attendance
- Tuition, donations and multi-entity accounting
- Family portal, transport and staff workflows