Product
One database, not seven integrations.
Most school software is a set of products that talk to each other on a schedule. SchoolOS is one application over one database, which is why a child admitted this morning appears on this afternoon's register without anyone copying anything.
The administrator dashboard. Figures shown are sample data for a school of about 1,300 students.
What integration usually means
A school buys an admissions tool, a fee package and an attendance app. Each keeps its own copy of the student list. Somebody exports a spreadsheet on Friday to make them agree, and by Monday they disagree again.
The cost is not the licence fees. It is the hour a week each office spends reconciling, and the confidence lost when two screens show different numbers in front of a parent.
What SchoolOS does instead
There is one student record. The fee module reads it, the register writes to it, the transport module points a bus stop at it, and the report card is generated from marks attached to it.
Because there is nothing to synchronise, there is nothing to fall out of sync. A correction made in the office is the correction everyone sees.
Who sees what
Everyone signs into the same system and gets a different application. A parent reaches their own children. A teacher marks their own classes. An accountant sees the fee ledger and not the medical notes.
That separation is enforced when the data is read, not by hiding menu items — a link typed by hand returns nothing rather than someone else’s record.
Enter it once. It is right everywhere, immediately, without anybody being asked to keep two systems in step.
Records
Students and academics
Profiles, parents, classes, attendance, homework, examinations and report cards.
Read moreOperations
Fees, staff and communication
Fee structures, invoicing, collection, staff records, leave, notices and the school mailbox.
Read moreBuses
Routes and live tracking
Fleet records, routes and stops, driver trips, boarding and parent tracking.
Read moreNext step
Ready to run your school on one platform?
Tell us how your school runs today — what is on paper, what is in spreadsheets, what your current software does badly. The demonstration follows that rather than a script, and we will be straightforward about the modules that are not built yet.
What a demonstration involves
- Thirty to forty minutes, on a call, with your screen or ours
- Roughly how many students and staff you have
- What you use today for fees and attendance
- Whether you run one campus or several
No obligation, and no pricing pressure on the first call. If SchoolOS is the wrong fit for your school we would rather say so then.