Admissions to enrolment
An enquiry becomes an application, a verified document set, a fee plan and a section allocation, with each hand-off owned by a named person and visible to the parent.
School management system · School ERP software
School ERP software that behaves like one system, not seven.
Most school ERP software is a set of modules sold together. SquareCampus is built the other way round: one institutional record, one workflow engine, one audit trail, and the modules a school expects sitting on top of it.
PrincipalsTrust administratorsIT coordinatorsFinance officers
Direct answer
What is school ERP software?
School ERP software is the system a school uses to run its recurring operations: admissions, student records, attendance, fees, examinations, timetables, transport and parent communication. The term comes from enterprise resource planning. In practice the useful question is not which modules exist but whether they share one record, so a change in one place is reflected everywhere else without re-entry.
SquareCampus is school management software built as a connected School OS. It covers the record-keeping and workflows schools expect from school management and ERP software, and connects them with owners, approvals and audit history on one institutional record. Read the canonical definition.
How it runs in SquareCampus
Each step has an owner and leaves a record
A module list hides the real question: does the work connect? These are the workflows as SquareCampus is designed to run them.
Attendance to fees and alerts
Daily attendance feeds fee rules, transport billing and guardian alerts. Exceptions carry a reason and an approver rather than a note in a register.
Exams to results and promotion
Schedules, marks entry, moderation, publication and promotion run as one sequence with a record of who changed what and when.
Approvals with an audit trail
Leave, concessions, refunds, purchases and gate passes move through role-scoped approvals, so the trail exists before an auditor asks for it.
Communication tied to context
Messages to parents and staff attach to the class, term, fee state or incident they concern, with delivery status and escalation paths.
Leadership view
Trustees and principals see what requires attention across campuses today, with an owner against each item, instead of a monthly report pack.
This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when.
A worked example
A confirmed admission, followed through
How the workflow is designed to run, step by step, and where configuration, scoping or separate quotes apply.
- 1The admissions desk accepts an offer; the student record is created once.
- 2The class section, fee plan and guardian contacts are set on that same record.
- 3Attendance, fees and parent communication all start from it — nothing is re-typed.
- 4Each hand-off has an owner, and each change is recorded with who made it.
Configured, scoped or quoted separately
- Modules, apps and languages for your rollout are confirmed in writing in your proposal.
- Board-specific report formats and fee rules are set up as configuration during implementation.
- Integrations with tools you keep are scoped work with stated prerequisites; nothing connects automatically.
- Data migration is included from Pro (quoted on Starter) and validated in a parallel run before the old system is retired.
Built for India
The realities Indian schools run on
Boards, fee structures, trusts and parent channels are configuration here, not customisation projects.
India-first specifics
- Fee structures with term plans, sibling and staff concessions, transport slabs, late fees and GST-aware receipts.
- CBSE, ICSE and state-board grading templates and report formats.
- Parent and student apps designed for the family's preferred language; available languages confirmed in the proposal.
- Multi-campus and trust-level structures as a first-class model, not a customisation.
- Parent communication over the app, with other channels such as SMS or WhatsApp scoped per institution and acknowledgements recorded.
- Hosted on Microsoft Azure in India, with hosting details given in writing during evaluation.
What to check in any vendor
Ask these of every vendor you evaluate, including us. The answers separate a connected system from a set of modules.
- 1Does a change in admissions, attendance or fees appear everywhere else without re-entry?
- 2Can you see who approved an exception and why, months later, without asking the vendor?
- 3Is pricing one institutional licence on student-volume bands with modules and the standard mobile apps included, or per-module with add-ons?
- 4What does the rollout involve: migration, parallel run, role-based training, and a rollback plan?
- 5Will the vendor answer an infrastructure and security questionnaire in writing?
- 6What happens to your data when you leave, in what format, and by when?
Questions
School ERP software: common questions
Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth.
SquareCampus is school management software built as a connected School OS. It covers the record-keeping and workflows schools expect from school management and ERP software, and connects them with owners, approvals and audit history on one institutional record.
Yes. A bounded deployment can run next to an existing ERP, LMS, payment portal or identity provider, governing the workflow that crosses them. Consolidation is a later choice, never a precondition.
One annual institutional licence calculated on student-volume bands, with the platform's modules and the standard parent and staff mobile apps included. The model is published on the pricing page; figures are issued in a written proposal after discovery, implementation and support are included, and custom integrations are scoped as their own lines.
A guided rollout sequenced around the academic calendar: institution blueprint, data migration, a parallel run on anything finance or academic teams must trust, role-based training, then go-live.
Access is role-based and scoped by campus, department and workflow step; actions are logged with user and timestamp; data is designed to be encrypted in transit and at rest. Documentation is shared on request.
More on evaluation, security and rollout in the FAQ.
Related
Keep reading
The pages a buyer on this question usually reads next.
Next step
Bring one real bottleneck. We will show how it runs.
A guided demo on your own scenario, followed by a written scope, from a founder-led team. The licensing model is published; figures follow a written proposal.