Admission to enrolment
- The work
- Enquiries, applications, documents and offers move through stages, with an owner at each step.
- The result
- An accepted offer becomes the student record that attendance, fees and communication use.
School management software for Indian schools and trusts
Run daily operations. See what needs attention.
Admissions, attendance, fees, exams and parent communication in one connected system — with clear responsibilities for school teams and one shared view for leadership across campuses.
Admin & trust command centre
Illustrative example — synthetic data- Exception queueEach item has an owner and a status, so nothing waits for someone to notice it.
- Today's positionAttendance and term collections from the records campuses work in.
- AEGISA leadership question answered in plain language, inside the asker's permissions.
- Exceptions get an owner before term end.
- Current state, not stitched reports.
- Every override stays auditable.
- Ownership survives staff changes.
What school teams do in SquareCampus
The daily work, from first enquiry to results
Each workflow has an owner at every step and ends on the same school record, so nothing is re-typed between departments.
Attendance to follow-up
- The work
- Teachers mark class or period attendance; absences and patterns are flagged for follow-up.
- The result
- Guardians are informed, and each exception has an owner until it is resolved.
Fees to reconciliation
- The work
- Fee plans, concessions and reminders follow the institution's rules; payments from every channel post to one ledger.
- The result
- Receipts and reconciliation sit on the same record, with approvals and refunds on the audit trail.
Exams to results
- The work
- Datesheet, marks entry and moderation run as handovers between named roles.
- The result
- Report cards come from the marks entered, and every change is recorded.
Notice to acknowledgement
- The work
- Circulars, reminders and notices are addressed from the student record, in the family's language where supported.
- The result
- Delivery and acknowledgement are recorded against the student; replies reach a named owner.
Campus to leadership view
- The work
- Policy is set once at trust level and carried out by each campus, with local variation where allowed.
- The result
- Leadership sees every campus from the records the campuses run on.
This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when.
What institutions actually feel
The problem is rarely a missing feature. It is delayed visibility and unclear ownership.
Recurring school cycles break in predictable places. Each one has a hidden cost, a remedy, an accountable owner, and something a pilot can measure.
Fee reconciliation
Collection records, bank statements and spreadsheets each hold part of the picture.
Finance spends the first week of every cycle rebuilding a number that should already exist.
One governed fee cycle carrying reconciliation state, ownership and escalation on the same record.
- Accountable owner
- Finance lead, with escalation to the trust office
- Pilot measures
- Time from collection close to a reconciled, signed-off position.
Attendance drift
Patterns are noticed once they have already become a term-level problem.
Intervention happens after the point where it would have changed the outcome for the student.
Threshold-based detection, routed ownership and follow-up recorded against the student record.
- Accountable owner
- Class teacher, escalating to the head of section
- Pilot measures
- Days between a threshold breach and a recorded follow-up.
Report-cycle delay
Compilation, correction, approval and publication collapse into the same fortnight.
Senior staff are pulled into chasing rather than reviewing, every single cycle.
Explicit stages, named owners, deadlines and exceptions that block publication.
- Accountable owner
- Examination officer, with principal approval
- Pilot measures
- Elapsed days across the full result cycle, and the number of blocked stages.
Decision latency
Leaders spend their time assembling context before they can decide anything.
The institution reacts at the speed of its reporting, not the speed of its problems.
Governed operational context with an explicit next-action layer behind it.
- Accountable owner
- Principal or trustee, depending on the decision
- Pilot measures
- Time from a signal appearing to a decision being recorded.
Record versus decision
A system of record stores what happened. A decision layer shows what requires attention, why it matters, who owns it, and what happens next.
SquareCampus helps school leadership know what requires attention today, who owns it, and what happens next.
The command centre
Management sees the institution the way a board expects to
Institution view
Illustrative product preview using synthetic data.
Attendance, fee exposure, and exceptions — before the review meeting.
Leadership reads current signals across campuses instead of waiting for stitched reports assembled after the fact.
Attendance by grade
Synthetic dataGrade 10
96%
Grade 9
91%
Grade 8
94%
Grade 7
88%
Grade 6
97%
Campus roll-upExceptions flagged
Fee collection
Synthetic data72%Collected
Collected 72%
Pending 20%
Overdue 8%
Governance model
Trust-level governance. Campus-level autonomy.
01
Set policy once
Fee rules, approval chains, academic calendars, and access boundaries are defined at the trust level — not re-invented per campus.
02
Campuses execute with autonomy
Principals and campus teams run their day inside clear guardrails, with local variation where the institution allows it.
03
Exceptions surface early
Attendance drift, fee exposure, and stalled approvals escalate to the right desk while they are still small.
04
Every action stays accountable
Approvals, overrides, and edits land on one auditable timeline — who, what, when, and in which campus context.
Sovereignty
Your institution's data, under your institution's governance
Sovereign does not mean rigid.
Parent-facing communication is designed to reach each family in its preferred language while the institution keeps consistent controls, reporting, and audit-ready records underneath.
Preferred language
Parent-facing updates flex by audience without fragmenting the institutional record.
EnglishHindiKannada
Structured underneath
Circulars, dues, acknowledgements, and audit history stay attached to the same student and family context.
Deployment on your terms
Managed cloud on Microsoft Azure in India by default; Enterprise private deployment on AWS, in a private cloud or on premises as a scoped service.
India-first residency posture
The platform is designed to keep institutional data in an Indian cloud region, with the posture documented in writing during evaluation.
Your data, your exit rights
Role-scoped access and essential auditability across plans, with institution-owned data, supported exports and documented offboarding.
Deployment details
What managed cloud and Enterprise private deployment each involve, with the status of every option, is set out on the services page.
Governed intelligence
AEGIS is the governed intelligence layer inside SquareCampus
AEGIS inside SquareCampus
Ask AEGIS. Don’t chase reports.
Leaders ask in plain language; AEGIS answers from the school’s own records, inside their permissions. It is read-only: it suggests, people decide, and every question is on the audit trail.
Operational questions answered from the institution's own records
Same trust boundaries, same role-aware controls
Signals and anomalies surfaced across finance, academics, and operations
Roles and access
Trustees, principals, finance, teachers, parents
Admissions
Applications, documents, offers, enrollment
Attendance
Classroom signal, staff follow-through, exceptions
AEGIS · Governed intelligence
Institution records in.
Governed answers out.
AEGIS is designed to read each record where it already lives, without exporting or re-keying it, inside the same permissions and audit trail as the rest of the School OS.
Role-aware answersException detectionAudit-ready by default
Governance checks
IllustrativeTenant boundaryCheckingApplied
Role-scoped answersCheckingApplied
Audit trail per questionCheckingApplied
Read-only: no actions takenCheckingApplied
How AEGIS is designed to answer. Not a measurement of any institution.
Finance ledger
Dues, receipts, concessions, approval history
Communication
App messages, circulars, acknowledgements
Leadership view
Campus health, branch risk, cross-team visibility
Rollout & trust
Switching systems is an institutional decision. We treat it that way.
Guided rollout
Migration, role-based training, and go-live are sequenced around admissions, fee cycles, and exam windows — with named counterparts, not ticket queues.
Parallel validation
Critical workflows run in parallel with your current systems until finance, academic, and admin teams trust the numbers.
Trust posture
Role-based access, encryption in transit and at rest, and audit trails are product design — and security documentation is shared in writing on request.
Operational calm
The outcome that matters: fee deadlines, inspections, and board reviews handled from one system, without the end-of-term scramble.
Founding institutional partners
Don't just adopt the School OS. Help shape it.
There are exactly two Founding Institutional Partner positions, ever: one school or eligible school institution, and one university. Once both positions are allocated, the programme closes permanently. A Founding Institutional Partner is not an ordinary customer. The position involves a strategic capital commitment under a separately executed agreement, material participation in product validation, and structured roadmap input.
Scope, success measure and commercial terms are agreed in writing before work begins.
Next move
See whether SquareCampus can govern your institution.
Bring your current stack. We will map it against the governed operating model and walk through rollout, controls, and institutional fit.