The best school management system for a multi-campus group

1. Isolation — can one campus reach another's data?

Test it rather than ask about it. Have the vendor log in as a campus administrator and try to open a record from another campus. What you are looking for is whether the record is absent or merely hidden. In Classbell scope is applied in the data-access layer on every read, so the record cannot be returned at all — and administrative privilege only ever narrows, because a role is bound to the invitation that created it and cannot be self-selected.

• Group and campus scope applied on every read, in the data layer
• Out-of-scope records are not found rather than filtered out
• Roles bound to the invitation, never chosen by the recipient
• An administrator cannot invite above their own level

2. Divergence — how much can campuses differ before it breaks?

Groups are not uniform, and the ones that are today will not be after the next acquisition. Ask how much a campus can differ from the group before the system stops coping. In Classbell currency, academic year, terms, grade list, working days and teaching periods are all per campus, each with a group default a new campus inherits and can then diverge from — so adding a branch is not re-entering everything, and a campus opting out of the group year does not unset it for the others.

• Per-campus currency, academic year, terms and grade list
• Per-campus working days and teaching periods
• A group default that a new campus inherits automatically
• One campus diverging does not disturb the others

3. Aggregation — can you trust a group number?

The hard part of group reporting is not producing a total, it is producing one that means something across currencies. Ask to see a group finance figure and look for two things: the currency it is expressed in, and the exchange-rate date it used. Classbell states both on every aggregate and shows each campus in its own currency beside the converted total, so nobody has to guess whether a number has been converted or merely added.

• Every money aggregate states its currency and exchange-rate date
• Local currency shown beside the converted figure
• A campus switcher that genuinely narrows the figures, not just the heading
• Group-wide search, notices and reporting across campuses

4. Financial integrity — what cannot be undone quietly?

This is what an auditor will ask about and what most demonstrations skip. The properties worth insisting on are gapless receipt numbering per campus, duplicate detection before the ledger is written, and reversal-with-reason instead of deletion. In Classbell all three are structural rather than procedural — the ledger has no update or delete path in the code, so they are not controls an administrator can weaken.

• Gapless, sequential receipt numbering within each campus
• Concurrent cashiers cannot be issued the same receipt number
• Duplicate payments detected before anything is written
• Reversal with a mandatory reason, requiring a group administrator

5. Privacy — what do families and pupils actually see?

Ask for a real parent login and a real pupil login in the demonstration, not screenshots. Systems adapted from a single-school design leak here more often than anywhere else: school-wide receivables on a parent dashboard, other pupils' records in a pupil view. In Classbell pupils see no school finance and no other pupil, parents see only their own children and their own balance, and medical or safeguarding data is permission-gated and appears on no published document.

• Pupils see no school-wide finance and no other pupil's record
• Parents see only their own children and their own balance
• Medical and safeguarding data permission-gated
• Report cards carry no fee and no medical information

6. Refusal — does the system stop you making a mess?

An underrated criterion, and the one that separates software that helps from software that merely stores. Ask what the system refuses. Classbell refuses a timetable slot that would double-book a teacher or a room, a register dated in the future or outside every term, a report card publication before moderation is complete, a package smaller than the number of campuses you actually run, and a subject whose assessment weights do not total one hundred per cent. Each refusal names the reason rather than disabling a control silently.

• A conflicting timetable slot is refused when written, not at publish
• A register cannot be dated in the future
• Publication is refused until moderation is complete
• A package too small for your campus count is refused at purchase

7. Fit over time — who decides what gets built?

A large vendor's roadmap is set by its largest customers, and a group of four hundred pupils 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 the answer you get is whether it can be built and roughly when — not a promise to build anything asked for, which would be the same failure in the opposite direction.

Where Classbell will not be the right answer

If your procurement requires a formal security certification, or you need single sign-on with your identity provider, or you need a self-serve bulk import to move several hundred records this term, those are real constraints and worth establishing early rather than at contract stage. The interface is currently English, though right-to-left layout is built and the translation groundwork is in place. We would rather you knew now.