Schools adopt SchoolDeck to solve specific problems rather than to buy software: raising fee collection, cutting teacher administrative load, running admissions at scale, going paperless, managing several branches on one set of books, meeting NEP 2020 and audit requirements, and making the board’s reports reproducible.
Nobody buys a school ERP because they want a school ERP. There is a specific thing that broke — a collection rate that will not move, a teacher shortage made worse by paperwork, an inspection that went badly — and the software is the response to it.
These pages are organised by that problem rather than by module, because that is how the conversation actually starts.
What schools tell us they are trying to change, and the lever that turns out to matter.
| The problem | What usually causes it | What moves it |
|---|---|---|
| Fee collection stuck below 85% | Reminders sent on a calendar, not against instalments | Reminders tied to the instalment, stopping the moment payment posts |
| Teachers doing administration | Attendance and marks entered twice, on paper then in a system | Entry once, on a phone, offline-tolerant |
| Admissions capacity | Enquiries handled by whoever answers the phone | One enquiry record with a source, so you learn which channel converts |
| Branches that disagree | Each branch keeping its own register and format | One student record and one fee structure definition across branches |
| Inspections and audits | Reports rebuilt by hand each time from moving data | A dated snapshot and a full audit trail on every record |
Worth saying before a demo rather than after. A system will not raise collection at a school whose fee structure is genuinely unaffordable for its families, and it will not reduce teacher load at a school that is short of teachers. It removes duplicated work and makes the position visible; it does not change the underlying position.
The schools that get the most out of this are the ones that already know which number they are trying to move, and can say what it is today.
Phrased the way they arrive, answered so each one stands on its own.
The mechanical part — reminders tied to instalments and a defaulters list the office trusts — takes effect within one fee cycle. Structural causes, such as an instalment schedule that does not match when families are actually paid, take a year to correct because you cannot change the schedule mid-term.
They use it where it saves them a step. Attendance on a phone that works without signal gets adopted; anything that duplicates a register they already keep on paper does not. Implementation should remove the paper step, not add a screen on top of it.
Yes, and this is the common case for groups. Branches share the student record and fee structure definitions while keeping their own books, so consolidation at trust level does not require a merge step.
Checked by the Implementations desk on 1 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.