How to choose a school management system for a group
Most school management systems were designed for one school and later stretched to cover several. The questions below are the ones that separate the two, and they are worth asking any vendor, including this one. Classbell's own answer is given under each — including the places where the answer is no.
Set up your school in minutes and go live.
1. Is campus scope enforced in the data, or in the interface?
Ask what happens if someone requests a record from another campus directly rather than through a screen. If scope is only applied in the interface, hiding a menu item is the whole security model. Classbell applies group and campus scope in the data-access layer, so an out-of-scope record cannot be returned.
2. Can two campuses run different academic years?
Groups spanning hemispheres or national systems genuinely need this, and it is hard to retrofit. Classbell models an academic year as belonging to the group or to a single campus, with the campus record shadowing the group default.
3. Does every money figure say what currency it is in?
A group total that silently sums several currencies is worse than no total. Ask to see a group finance figure and check whether it states its currency and the exchange-rate date. Classbell states both on every aggregate and shows local beside converted.
4. What happens to issued invoices when fees change?
If a fee change can reprice an invoice already sent, nobody can answer a parent's question about what they were charged. Classbell versions fee structures with an effective date and never reprices an issued invoice.
5. Can a payment be deleted?
The answer should be no. Ask what a correction looks like. In Classbell a payment is reversed with a compensating entry and a mandatory reason, requires a group administrator, and the voided receipt keeps its number in sequence.
6. What can a student see, and what can a parent see?
Ask to log in as each. This is where systems adapted from a single-school design tend to leak — school-wide receivables on a parent dashboard, other pupils' records in a student view. In Classbell students see no school finances and no other students, and parents see only their own child's balance.
7. Is there an audit trail, and what is in it?
"We log changes" is not an answer. Ask whether it records the value before and after, who made the change, and how long it is kept. Classbell records all of that, immutably, and retains it for seven years.
8. Can the vendor show you the controls, not just describe them?
Ask for specifics you can verify in a trial rather than a badge. Classbell publishes exactly how tenant isolation, credential handling, audit logging and financial integrity work, and several of those controls are structural — an administrator cannot weaken them, because the code offers no way to. Ask any vendor to show you the same at that level of detail.
9. What does leaving look like?
Ask how data comes out, and what happens when you switch a module off. In Classbell turning a module off retains its data rather than deleting it, and data can be exported — a module you disable in June is intact when you re-enable it in September.
10. How quickly does the vendor act on what you ask for?
A large vendor's roadmap is set by its largest customers, and a school of four hundred is rarely one of them. Ask who decides, and how long a reasonable request actually takes. With Classbell a request reaches the person who writes the code, and you get an honest answer about whether it can be built and roughly when.
11. What does the system refuse to do?
An underrated question, and one almost nobody asks. Software that stores whatever it is given will eventually store a timetable with a clash in it, a register dated next December, and a report card published before anybody checked it. Ask the vendor what the system will not let you do. Classbell refuses a conflicting timetable slot at the point of writing, a register in the future or outside every term, a publication before moderation is complete, a package smaller than the campuses you run, and a subject whose assessment weights do not total one hundred per cent — each with the reason named rather than a control silently greyed out.
Common questions
What is the single biggest difference between single-school and multi-campus systems?
Whether campus scope is part of the data model or a filter applied afterwards. Everything else — separate calendars, separate currencies, group reporting — follows from that choice, and it is the one thing that cannot be added later without a rebuild.
Should we expect a free trial?
Not necessarily, and its absence is not a red flag on its own. What matters is whether you can see the system configured with your own structure before committing. Classbell has no trial and is not free to run: you complete setup — campuses, grades, currencies — and then pay to go live.
How much should a multi-campus system cost?
Self-serve products for school groups are typically priced per month against limits on campuses, students and staff. Classbell publishes its packages and limits on its pricing section rather than quoting on request.
How do we test campus isolation in a demonstration?
Ask the vendor to sign in as an administrator scoped to one campus and open a record belonging to another. You want the record to be unreachable, not merely absent from a list — if it is only hidden, the interface is the security model.
What should we ask about data if we ever leave?
Two separate questions, because they get different answers: how data is exported, and what happens when a module is switched off. In Classbell disabling a module retains its data and it returns intact when re-enabled.