The data model is shared
Admissions, academics, finance, communication, and operations do not compete to define the truth.
Why SquareCampus
Not a rebranded ERP. Not a bundle of point tools.
SquareCampus is school management software built as a connected School OS. Admissions, academics, fees and communication share one record, and the approvals, owners and audit history that connect them sit on that record too.
How to evaluate
Five things to check in any school management system
Differences you can verify in a demo, including in ours.
| Dimension | Ask any vendor to show you | How SquareCampus is designed to answer |
|---|---|---|
| Concession approvals | Grant a sibling concession above the desk's limit. Who approves it, and where is that approval recorded? | Concessions follow the institution's limits; anything above a limit goes to a named approver and is recorded on the fee record's audit trail. |
| Cross-campus permissions | Sign in as a campus principal, then as a trust administrator. What can each one see? | Access is scoped by role and by campus: a trust role sees across its campuses, a campus role sees its own. |
| Exception ownership | Show an attendance exception. Who owns it, and what closes it? | Each exception is routed to a named owner and stays open until it is closed with a recorded reason. |
| Migration validation | How are migrated balances and records checked before the old system is switched off? | Trial imports reconcile against agreed checks, and a parallel run continues until finance and academic owners sign off. |
| Exports and exit | What can we take out when we leave — in what format, by when, and at what cost? | Export scope, format, timing and charges are agreed in the order form, not left for the day you leave. |
Comparing against a named product? Our comparison pages list each competitor’s genuine strengths and when it is the better fit.
What the label commits us to
What “School OS” means in practice
Four properties you can ask to see in a demo. If a system cannot show them, the label does not apply.
The workflows are connected
Approvals, communication, attendance, dues, and reporting happen in a coordinated sequence rather than across disconnected tabs.
The institution is visible now
Leaders operate with current signals, not after-action exports assembled under pressure.
The trust posture is product-level
Auditability and access control are part of the product design, and availability and recovery are documented in writing during security review.
Why institutions move
Where the conversation usually starts
Usually with one pressure point — fees, reporting, admissions, communication or compliance. Underneath it, the work is often split across tools that do not share a record.
Common switch triggers
The institution wants fewer tools without losing admissions, fees, exams or reporting capability.
Leadership wants live visibility instead of delayed reporting rituals.
Finance and compliance teams need controls that survive real scrutiny.
Parents and staff need one clear place for notices, dues and follow-ups instead of several apps and message threads.
What “different” looks like in practice
One system replaces fragmented vendor management and repeated internal workarounds.
Audit-friendly operations stop depending on who remembered to export or forward the right spreadsheet.
Fee deadlines, inspections and board reviews are handled from one record instead of a scramble for spreadsheets.
See it in context
Compare the School OS model against your current stack.
The most useful demo is usually a direct comparison between your current operating reality and the connected model SquareCampus is designed to provide.