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 platform
Every school workflow on one shared record.
Admissions, attendance, fees, exams and parent communication run as connected workflows. What staff do in one reaches the others without re-typing, and every step has an owner.
Daily operations
Synthetic data
One login and one governed record for admissions, academics, finance, and communication.
Institution-aware structure for schools, colleges, and multi-campus organizations.
Parent-facing communication in families' languages, with institutional reporting kept consistent.
AEGIS answers leadership questions from the same records, inside the same permissions.
Supported workflows
What staff do, and what they get
Each workflow runs from the first step to a recorded result, and links to a page that covers it in depth.
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.
Underneath the workflows
Four layers make the workflows connect
Records, workflows, governance and intelligence share one foundation. Each layer changes something specific about how the institution runs.
01
System of Record
One shared school record.
Students, staff, fees, attendance, assessments and documents live on one model, so a question has one answer rather than one answer per tool.
What that includes
- Student, staff and guardian records
- Admissions and enrolment
- Timetable, attendance and assessment
- Fees, concessions and receipts
- Documents and institutional history
02
System of Workflow
Work moves with an owner.
Admissions, collections, results, approvals and parent concerns run as workflows with stages, owners and deadlines — not as tasks held in someone's memory.
What that includes
- Stages, owners and deadlines per cycle
- Exception routing and escalation
- Approvals and overrides
- Parent and staff communication
- Transport, hostel and campus operations
03
System of Governance
Every exception is accountable.
Policy, approval chains, role boundaries and audit history are institutional configuration, so exceptions escalate to a named desk and leave a trail.
What that includes
- Role-based access and campus scope
- Trust and campus hierarchy
- Approval and governance chains
- Audit history and advanced audit exports
- Institutional identity: SquareCampus-managed sign-in, separately quoted Microsoft Entra ID single sign-on across plans, identity governance under Enterprise
04
System of Intelligence
Leadership sees what requires attention.
AEGIS reads the governed operational context and returns permission-scoped, source-grounded answers about what changed, why it matters and who owns the response.
What that includes
- Operational analytics and command views
- Threshold detection across cycles
- Permission-scoped, source-grounded answers
- Auditable question and answer history
Operating domains
The cycles the backbone has to carry
The school cycles each record passes through, from first enquiry to fees, results and campus services.
Admissions to academics
From inquiry, documents, and enrollment through timetable, attendance, exams, and report publishing.
Finance to compliance
Fees, concessions, receipts, auditability, and institution-level oversight in the same operating model.
Communication as infrastructure
Parents, students, staff, and administrators receive the right information through the right channels without disconnected tools.
Operations as part of the core
Transport, services, assets, and campus workflows stay linked to the same institutional identity and timeline.
Shared core
The system underneath the UI matters
Every surface works from one identity, data and workflow core, so a change made once reaches the rest without an export, a sync job or a second copy of the record.
Shared identity
Users, permissions, and organizational boundaries are defined once and respected everywhere.
Shared data model
A record created in admissions becomes the same record used by academics, finance, and communication.
Shared operating timeline
Approvals, updates, dues, parent communication, and staff actions roll into one auditable sequence.
Shared observability
Leaders see the institution through dashboards built on current records instead of stitched reports and spreadsheet exports.
Product surfaces
Designed for the people who actually run the institution
SquareCampus is not just an admin layer. Each audience gets a purpose-built surface, but the institution still runs on one connected operational model.
Admin command center
Branch health, role controls, rollout visibility, finance oversight, and policy enforcement from one place.
Teacher workspace
Attendance, lesson delivery, remarks, assessments, communication, and action queues without context switching.
Parent and student app
Fees, receipts, circulars, attendance, academic visibility, and service requests, designed for the family's preferred language.
Leadership visibility
Board reviews, campus-level dashboards, fee risk, academic exceptions, and operational exposure from current records.
Governed intelligence
AEGIS is embedded where context already exists.
AEGIS works inside SquareCampus, not beside it. It reads the same timelines, permissions and records the School OS already holds, so there is no second system to reconcile.
Role-aware suggestions
Exception detection from current records
Institution-safe answers inside the same guardrails