# SquareCampus — Full public website context Public, indexable marketing pages rendered as Markdown. Each document carries its canonical URL. Navigation, forms, scripts and decorative media are omitted by the site's existing Markdown converter. # SquareCampus > SquareCampus is a School Operating System for schools, educational trusts, multi-campus school groups and higher-education institutions in India, focused on connected operations, institutional governance, accountability and operational visibility. - Category: School management software for Indian schools and trusts. 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. - Intended institutions: Standalone schools with governance, identity or audit requirements; Educational trusts and multi-campus school groups; Church-run and society-run school chains; Private universities and multi-school higher-education groups, as a governed operating layer over the systems they already run. - Geography: India-first. The platform is hosted on Microsoft Azure in India. Enterprise private deployments are available on AWS, in a private cloud or on premises, subject to scoping. - Deployment: 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. Running in the institution's own cloud account (BYOC) is not offered today. - Availability: This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. - Core distinction: A system of record stores what happened. SquareCampus also carries the workflows, ownership, exceptions, approvals and audit history that turn records into accountable operations, and shows leadership what requires attention, who owns it and what happens next. - Competes on: operational governance, workflow ownership, exception management, institutional visibility, accountability, auditability, multi-campus command, interoperability, institutional control, long-term operational quality. It is not designed to be the cheapest attendance, fees and report-card product, and will look expensive to an institution that needs only that. - Plans: Starter — The complete generally available core platform, including multi-campus operations, with essential dashboards and campus-level administration. Pro — The same complete core platform and multi-campus operations, with enhanced analytics, allowances and workflow sophistication. Enterprise — Institutional governance, cross-campus command, advanced controls, deeper integration, identity governance and advanced auditability for larger or more complex institutions. - Core platform: Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. - Security baseline: Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. - Data ownership: The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. - Launch pilot: Subscription pricing is communicated before pilot activation, with a commercial review before the 90-day pilot expires. At completion, the institution chooses to subscribe or discontinue. Initial launch outreach focuses on Kotdwara and surrounding areas. Enquiries are reviewed individually; this outreach focus is not a published geographic eligibility restriction. - Pricing availability: The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. - Retention: Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. - Identity: Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. Single sign-on is optional. An institution is not required to adopt it, and is not required to move between Google Workspace and Microsoft to use SquareCampus. - Founding Institutional Partner programme: 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. - Deployment: a bounded deployment can run alongside the institution's current ERP, LMS, payment portal and identity provider, which stay authoritative; consolidation is a later choice and never a precondition of starting. - Evidence: SquareCampus publishes no customer counts, rankings, uptime figures, measured outcomes, testimonials or named institutional customers. Statements on the site describe what the product is designed to do, not results that have been measured in production. Product screenshots use synthetic data and are labelled as such. - Website source: the code for this site is public at https://github.com/fairhelmsystems/squarecampus.com - Operator: Fairhelm Systems (OPC) Private Limited (CIN U62099KA2026OPC225579, GSTIN 29AAHCF1819L1ZA), Bangalore, Karnataka, India. SquareCampus™ trademark registration pending. ## Evaluate SquareCampus - [What is SquareCampus](https://squarecampus.com/what-is-squarecampus/index.md): The canonical definition, the four layers (record, workflow, governance, intelligence), what School OS, governance, exception ownership and accountability mean here, and the direct answer to whether it is an ERP - [Pricing](https://squarecampus.com/pricing/index.md): How the licence is structured (one annual institutional licence, calculated on progressive student-volume bands and shaped by the plan (Starter, Pro or Enterprise), the institution's complexity and its deployment profile), what is included versus separately scoped, what Enterprise adds beyond ERP modules, identity options by plan, and who it is not the right fit for. The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. - [SquareCampus Enterprise](https://squarecampus.com/enterprise/index.md): Institutional governance, cross-campus command, identity, audit and deployment requirements; shared foundations and proposal-led scoping - [Platform](https://squarecampus.com/platform/index.md): How the School OS is structured: four layers, the operating cycles it carries, the shared institutional core and the product surfaces - [Security and identity](https://squarecampus.com/security/index.md): Design posture for encryption, role-based access, auditability and India-first hosting; sign-in options by plan and why authorisation stays inside SquareCampus. Documentation is shared through the security review process - [Rollout and deployment paths](https://squarecampus.com/rollout/index.md): Guided implementation sequenced around the academic calendar, and the two deployment paths: coexistence alongside the current stack, and later consolidation if the institution chooses - [Why SquareCampus](https://squarecampus.com/why-squarecampus/index.md): The comparison against module-based school ERPs, by operating outcome - [Compare](https://squarecampus.com/compare/index.md): Head-to-head comparisons against named school ERP products (Entab, Fedena, Teachmint), each naming the competitor's genuine strengths and who should choose them - [FAQ](https://squarecampus.com/faq/index.md): Getting started, features, security and data, pricing and support, in the words buyers ask ## Institutional requirements One page per buyer question. Each opens with a direct definition, then the workflows as they run, India-specific realities, a vendor-neutral evaluation list and a FAQ. - [Multi-campus school management software](https://squarecampus.com/multi-campus-school-management-software/index.md): Trust-level policy, campus-level execution, roles scoped by campus, and a table on how multi-campus governance differs from merely supporting several campuses - [School ERP software](https://squarecampus.com/school-erp-software/index.md): The school ERP category answered honestly, then reframed as connected workflows on one governed record - [School management system](https://squarecampus.com/school-management-system/index.md): The category page for buyers using that terminology: modules as workflows, India-first fees and compliance, implementation sequence, pricing model - [Fee management software for schools](https://squarecampus.com/fee-management-software-for-schools/): Term plans, concessions, transport slabs, GST receipts, reminders and month-end reconciliation on one ledger - [School attendance management system](https://squarecampus.com/school-attendance-management-system/): Attendance as an early-warning workflow with thresholds, owners and follow-up, not only a register - [School admission management software](https://squarecampus.com/school-admission-management-software/): Enquiry to enrolment as a staged workflow with owners, document verification and seat allocation - [School exam management software](https://squarecampus.com/school-exam-management-software/): Datesheet to report card as a chain of handovers, with marks entry, moderation and re-evaluation on an audit trail - [Parent communication app for schools](https://squarecampus.com/parent-communication-app-for-schools/): Addressed communication with acknowledgement, replies routed to a named owner, in the family's preferred language where supported - [School management software for CBSE schools](https://squarecampus.com/school-management-software-for-cbse-schools/): CBSE-specific operations: assessment structure, board records and compliance as configuration - [School management software for ICSE schools](https://squarecampus.com/school-management-software-for-icse-schools/): ICSE-specific operations as configuration rather than customisation - [School management software for state board schools](https://squarecampus.com/school-management-software-for-state-board-schools/): State-board operations: regional languages, state levies and board formats - [Higher education](https://squarecampus.com/launch-partners/higher-education/index.md): For private universities and multi-school groups: a governed operating layer that runs alongside the existing ERP, LMS, payment and identity systems. Not a university ERP, SIS or LMS - [Data and integration services](https://squarecampus.com/services/): Scoped integrations with existing tools (no pre-built connector catalogue), ETL pipelines, Enterprise private deployment ## Intelligence - [AEGIS](https://squarecampus.com/aegis/index.md): AEGIS is the governed intelligence layer inside SquareCampus. It produces permission-scoped, source-grounded and auditable operational answers from institutional context. Boundaries: read-only, rbac-scoped, source-grounded, auditable, human-controlled ## Commercial programmes - [Selected Institutional Launch Pilot](https://squarecampus.com/pricing/index.md): Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. Separate from paid subscriptions and founding partnerships; scope, consumption and pricing are agreed before activation. - [Founding Institutional Partner programme](https://squarecampus.com/launch-partners/index.md): 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. Entitlements under the executed agreement: defined roadmap influence, protected 40% enterprise discount, white-labelled mobile apps, other agreed founding privileges ## Company and trust - [About](https://squarecampus.com/about/): Fairhelm Systems (OPC) Private Limited, Bangalore, Karnataka, India. CIN U62099KA2026OPC225579, incorporated 5 August 2026; GSTIN 29AAHCF1819L1ZA. Founder-led - [Contact](https://squarecampus.com/contact/): Registered office, corporate identity and contact channels - [Infrastructure](https://squarecampus.com/infrastructure/): Microsoft Azure in India, encryption in transit and at rest, India data-residency posture, Enterprise private deployment on AWS; documentation through security review - [Privacy policy](https://legal.fairhelmsystems.com/squarecampus/privacy-policy/): How personal data is collected, used, retained and protected - [Terms of service](https://legal.fairhelmsystems.com/squarecampus/terms-of-service/): Subscription terms, acceptable use and the order form that governs commercial terms - [Data retention](https://legal.fairhelmsystems.com/squarecampus/data-retention/): Institutional responsibilities, agreed export and offboarding arrangements, and the distinction between available facilities and retention controls still being built - [Data processing addendum](https://legal.fairhelmsystems.com/squarecampus/data-processing-addendum/): Processor obligations, sub-processors, security measures, return or deletion - [Data retention](https://legal.fairhelmsystems.com/squarecampus/data-retention/): Who is responsible for retaining institutional data, what determines retention, how export, deletion and preservation requests are handled, and what is confirmed today versus awaiting confirmation - [AI policy](https://legal.fairhelmsystems.com/squarecampus/ai-policy/): Commitments on how AEGIS uses institutional data - [PGP key](https://squarecampus.com/pgp/): Security contact and public key ## Optional Selected buyer guides, vendor-neutral where the question is neutral. The blog index lists every published article. - [Full public website context](https://squarecampus.com/llms-full.txt): Complete text of indexable public pages, including Enterprise, generated from the same production HTML - [Blog](https://blogs.squarecampus.com/): All published guides and articles, with an RSS feed - [How to Choose a School Management System in 2026: A Buyer's Guide for Indian Schools](https://blogs.squarecampus.com/how-to-choose-school-management-system/): A vendor-neutral framework for Indian schools and school groups: the questions that actually separate vendors, the red flags procurement should treat as disqualifying, and a 25-point demo checklist. - [AI in School ERPs: How to Tell Governed Intelligence from a Chatbot Bolted On](https://blogs.squarecampus.com/ai-in-school-erp-governed-intelligence-vs-chatbot/): Every school ERP now claims AI. Five tests separate intelligence that lives inside the system from a chatbot answering off a copy of your data, and the questions to ask in the demo. - [The ₹18,000 School ERP: How a Quote Becomes 20x by the Time It Goes Live](https://blogs.squarecampus.com/eighteen-thousand-rupee-school-erp-true-cost/): A worked example of how an ₹18,000-a-year school ERP quote grows into a multi-lakh commitment by go-live, line by line, and the clauses that stop it from happening to your school. - [What a School ERP Implementation Actually Involves (And What Your School Must Bring to It)](https://blogs.squarecampus.com/school-erp-implementation/): What a school ERP implementation actually involves: the phases, the data work your staff will own, and how to sequence the change around the academic year. - [What Happens to Your Data When You Leave a School ERP](https://blogs.squarecampus.com/school-erp-data-exit/): What a school ERP data export must include, why vendor lock-in is usually structural rather than malicious, and the exit clauses to settle before you sign. - [Student Data Security for Schools: A DPDP Act Readiness Checklist](https://blogs.squarecampus.com/student-data-security-dpdp-checklist/): A practical school data security checklist for the DPDP Act: what the law asks of schools, what to fix internally, and what to ask every vendor in writing. - [Running Multi-Campus School Groups: Centralised Control vs Campus Autonomy](https://blogs.squarecampus.com/multi-campus-school-governance/): Why school groups swing between head-office bottlenecks and campus drift, the governance model that resolves the tension, and what it demands from software: policy at trust level, execution at campus level. - [What an Education Trust Board Should Actually See Every Month](https://blogs.squarecampus.com/trust-board-monthly-reporting/): A concrete monthly education trust board reporting pack: exceptions, owners, ageing, and decisions — adoptable by any school trust, with or without software. - [What a Founding Institutional Partner Pilot Actually Involves](https://blogs.squarecampus.com/founding-institutional-partner-pilot/): What a founding pilot with SquareCampus actually involves: a paid, scoped 60–90 day engagement, a written baseline, one success measure, and a real way to stop. --- Source: https://squarecampus.com/school-management-system/ --- title: "School Management System in India | SquareCampus School OS" description: "SquareCampus is a school management system built for Indian schools and school groups: admissions, fees, academics, attendance, transport, exams, and parent communication in one governed system of record. Book a demo." canonical: https://squarecampus.com/school-management-system/ describedby: https://squarecampus.com/llms.txt --- School management system # School management system built for Indian schools. A school management system should be the operating manual of your campus — not a stack of disconnected tools. Sometimes labeled school ERP software, SquareCampus is a School OS built for India: admissions, attendance, fees, exams, communication, transport, and compliance stay connected so nothing slips. Guided rollout One governed record Audit-ready by design [Book a demo](https://squarecampus.com/demo/) · [See how workflows connect](https://squarecampus.com/ecosystem/) One view, zero chaos Live workflow Admins, teachers, and finance teams share the same source of truth. No swivel chairing, no manual reconciliations, no “who updated this?” mysteries. ![SquareCampus school management system dashboard preview for Indian schools](https://squarecampus.com/images/marketing/dashboard.webp) Time to launch Guided rollout Modules included Unified platform Support Human + product Definition ## What is a school management system? It is the operating core that coordinates academics, finance, and communication. In India, you might also hear it called school ERP software or school management software. A true school management system connects attendance with fees, ties assessments to promotion decisions, and keeps parents and staff aligned without duplicate data entry. SquareCampus treats this definition as engineering spec, not marketing copy. Operating loop Admissions initiate fee plans and onboarding. Attendance powers compliance and billing. Assessments connect to promotion decisions. Communication follows every workflow step. When one workflow moves, the rest follow automatically — no re-entry, no drift. ## Why schools need a unified system Fragmented tools create data drift, parent confusion, and audit risk. A unified OS keeps every update consistent, triggers the right follow-up, and makes compliance a side-effect of normal work — not an afterthought. Attendance flows directly into fee rules and reports. Communication is tied to context — class, term, fee status, or incident. Exams, grading, and promotions stay in sync with academic calendars. Transport, hostels, and inventory stay reconciled without extra spreadsheets. Parents see one story: attendance, dues, announcements, and results. Staff permissions are scoped by role, location, and workflow step. Leadership tracks trends in collections, learning, and risk in one place. Every action is logged for admins, auditors, and compliance reviewers. Solutions by need ## Start from the question you actually have Each page opens with a direct answer, then the workflow as it runs, the India-specific realities, and what to check in any vendor. [School ERP software · What is school ERP software? Read the answer](https://squarecampus.com/school-erp-software/) · [Fee management software for schools · What is fee management software? Read the answer](https://squarecampus.com/fee-management-software-for-schools/) · [School attendance management system · What is a school attendance management system? Read the answer](https://squarecampus.com/school-attendance-management-system/) · [School admission management software · What is school admission management software? Read the answer](https://squarecampus.com/school-admission-management-software/) · [Multi-campus school management software · What is multi-campus school management software? Read the answer](https://squarecampus.com/multi-campus-school-management-software/) · [School management software for CBSE schools · What should CBSE school management software include? Read the answer](https://squarecampus.com/school-management-software-for-cbse-schools/) · [School exam management software · What is school exam management software? Read the answer](https://squarecampus.com/school-exam-management-software/) · [Parent communication app for schools · What is a parent communication app for schools? Read the answer](https://squarecampus.com/parent-communication-app-for-schools/) · [School management software for ICSE schools · What should ICSE school management software include? Read the answer](https://squarecampus.com/school-management-software-for-icse-schools/) · [School management software for state board schools · What should state board school management software include? Read the answer](https://squarecampus.com/school-management-software-for-state-board-schools/) Modules as workflows ## Modules inside SquareCampus, explained as workflows Feature lists hide the real question: does the work actually connect? Here is how each module is designed to connect. ### Admissions to Enrolment Inquiry → application → document verification → fee collection → section allocation. Parents see status; admins see where each application is stuck. ### Attendance to Fees Daily attendance updates fee rules, transport billing, and alerts to guardians. Exceptions are logged with reasons and approvers. ### Exams to Promotions Schedule exams, capture marks, publish results, and roll promotions with auditability. Grade templates match CBSE/ICSE norms. ### Approvals to Audit Trails Leave, concessions, refunds, procurements, and gate passes run through RBAC-backed workflows with time-stamped approvals. ### Communication to Resolution Role-aware messaging to parents, staff, and students with templates, delivery status, and escalation paths. ### Transport to Compliance Vehicle, route, and driver management with attendance sync and safety checks documented for audits. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. India-first ## Built for Indian schools: fees, compliance, multi-campus ### Operational reality - Handles complex fee plans, concessions, transport slabs, and arrears. - GST-ready invoicing, receipts, and exports to accounting tools. - Region-aware attendance rules and academic calendars. - Designed for India data-residency expectations, with audit logs built in. - Multi-branch hierarchies with shared services and campus-level autonomy. ### Security, RBAC & audit trails - Role-based access with fine-grained scopes by campus, department, and module. - Encryption in transit and at rest for sensitive records. - Activity timelines on every record: who changed what, when, and from where. - Export controls designed to prevent data leakage. - Change logs tied to user identity and timestamps. - Designed to support DPDP Act obligations and education data guidelines. [Request Security & Compliance Pack](mailto:security@squarecampus.com?subject=Security%20%26%20Compliance%20Pack%20Request%20-%20%5BSchool%20Name%5D&body=Hello%20SquareCampus%20Security%20Team%2C%0A%0AWe%20would%20like%20to%20request%20your%20Security%20%26%20Compliance%20Pack.%0A%0ASchool%20name%3A%20%5BYour%20School%20Name%5D%0AContact%20name%3A%20%5BYour%20Name%5D%0ARole%3A%20%5BTitle%20%2F%20Department%5D%0AEmail%3A%20%5BWork%20Email%5D%0APhone%3A%20%5BPhone%20Number%5D%0AStudent%20count%3A%20%5BApproximate%5D%0ACampuses%3A%20%5BNumber%20of%20Campuses%5D%0ASpecific%20requirements%3A%20%5BOptional%5D%0A%0AThank%20you%2C%0A%5BYour%20Name%5D) Rollout & pricing ## A launch that respects the academic calendar ### Implementation sequence 1. Scope confirmation, data templates shared, owners assigned. 2. Data import dry run, key workflows configured, access provisioned. 3. Parallel run with real data, teacher and admin training. 4. Go-live with rollback plan, success metrics, and support channel. 5. Post-launch review, fee-rule tuning, recurring tasks automated. ### Pricing philosophy - One annual institutional licence — no per-module surprises. - Standard parent and staff mobile apps included; no hidden 'parent app' fees. - Calculated on active enrolled students in progressive volume bands, not usage penalties. - Data migration included from Pro; optional lines are priced before signature. - The model is published on the pricing page; figures follow a written proposal after discovery. The comparison ## SquareCampus vs legacy school ERPs Choose architecture, not nostalgia. This is the difference between one OS and stitched-together software. Architecture SquareCampus: One unified institutional data model, shared workflows, consistent UX. Legacy ERPs: Multiple products bolted together with custom scripts. Implementation SquareCampus: Guided rollout with parallel run and live training. Legacy ERPs: Months of customization tickets and delays. Pricing SquareCampus: All modules included; mobile apps included; transparent renewals. Legacy ERPs: Per-module upsells, per-user fees, hidden mobile costs. Support SquareCampus: Human-first, context-aware support with product and ops in the same room. Legacy ERPs: Ticket queues with generic replies and slow escalations. [Read the full breakdown](https://squarecampus.com/why-squarecampus/) FAQs ## Questions procurement teams ask ### What is a school management system? A school management system is a unified platform that runs daily operations like admissions, attendance, fees, exams, communication, and compliance. SquareCampus is a school management system designed specifically for Indian schools so every stakeholder works from one source of truth. ### How is SquareCampus different from legacy school ERPs? Legacy ERPs bolt modules together and feel like separate products. SquareCampus is architected as one operating system: a unified institutional data model, consistent workflows, and human support included. ### Does SquareCampus handle Indian fee structures and compliance? Yes. We support complex fee terms, concessions, transport, late fees, GST, audit exports, and compliance-friendly audit trails. Multi-campus structures are built-in, not custom scripts. ### How fast can we go live? Rollout is guided and sequenced around your academic calendar. We import historical data, run a parallel dry run, train admins and teachers, and then go live with a rollback plan ready. Timelines depend on data complexity and are agreed before we start. ### Is there a mobile experience for parents and staff? Yes. Parents get attendance, fees, transport, messages, and results in one app. Staff handle attendance, approvals, communication, and tasks without desktop friction. ### How is data secured inside the school management system? Role-based access, scoped permissions, encryption in transit and at rest, activity logs, and export controls are part of the product design. Every action is traceable to a user and timestamp. ### How is school data protected and accessed securely? Access is role-based and scoped by campus, department, and workflow. Data is encrypted in transit and at rest, and audit trails show every change with user and timestamp. ### Can we see documentation for your security posture? Yes. We can share a security and compliance pack with data flow summaries, subprocessors, and incident response overview upon request. ### Do you support single sign-on with our identity provider? Every plan includes SquareCampus-managed credentials with role-based access. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. ### What does pricing look like? The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. One annual institutional licence, calculated on progressive student-volume bands and shaped by the plan (Starter, Pro or Enterprise), the institution's complexity and its deployment profile. Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. The licence covers the plan's platform capability, the standard SquareCampus parent and staff mobile apps, self-serve reporting, implementation and support, and a monthly usage allowance. Pro and Enterprise also include data migration. Anything optional, such as custom integrations, is shown in the proposal before signature. ### Can SquareCampus integrate with our existing tools? Yes, as scoped work. There is no catalogue of pre-built connectors: each integration is assessed during discovery and confirmed in writing. ### Will teachers and admins need heavy training? No. Interfaces follow existing workflows, not abstract menus. We deliver role-based onboarding, videos, and live sessions until adoption is steady. School management system ## Ready to run every campus day from one operating system? Book a demo, see your workflows mapped, and launch with a timeline that respects the academic calendar. [Book a demo](https://squarecampus.com/demo/) · [Request Security & Compliance Pack](mailto:security@squarecampus.com?subject=Security%20%26%20Compliance%20Pack%20Request%20-%20%5BSchool%20Name%5D&body=Hello%20SquareCampus%20Security%20Team%2C%0A%0AWe%20would%20like%20to%20request%20your%20Security%20%26%20Compliance%20Pack.%0A%0ASchool%20name%3A%20%5BYour%20School%20Name%5D%0AContact%20name%3A%20%5BYour%20Name%5D%0ARole%3A%20%5BTitle%20%2F%20Department%5D%0AEmail%3A%20%5BWork%20Email%5D%0APhone%3A%20%5BPhone%20Number%5D%0AStudent%20count%3A%20%5BApproximate%5D%0ACampuses%3A%20%5BNumber%20of%20Campuses%5D%0ASpecific%20requirements%3A%20%5BOptional%5D%0A%0AThank%20you%2C%0A%5BYour%20Name%5D) --- Source: https://squarecampus.com/school-erp-software/ --- title: "School ERP Software for Indian Schools | SquareCampus" description: "School ERP software that connects admissions, fees, attendance, exams and communication on one governed record. Built for Indian schools and school groups." canonical: https://squarecampus.com/school-erp-software/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/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. Principals Trust administrators IT coordinators Finance officers [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) 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](https://squarecampus.com/what-is-squarecampus/). 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. ### 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. ### 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. 1. 1 The admissions desk accepts an offer; the student record is created once. 2. 2 The class section, fee plan and guardian contacts are set on that same record. 3. 3 Attendance, fees and parent communication all start from it — nothing is re-typed. 4. 4 Each 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. 1. 1Does a change in admissions, attendance or fees appear everywhere else without re-entry? 2. 2Can you see who approved an exception and why, months later, without asking the vendor? 3. 3Is pricing one institutional licence on student-volume bands with modules and the standard mobile apps included, or per-module with add-ons? 4. 4What does the rollout involve: migration, parallel run, role-based training, and a rollback plan? 5. 5Will the vendor answer an infrastructure and security questionnaire in writing? 6. 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. ### Is SquareCampus a school ERP? 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. ### Can school ERP software run alongside the tools we already use? 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. ### How is pricing structured? 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. ### What does implementation involve? 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. ### How does the platform handle security and data access? 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](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Platform · The four layers every module sits on](https://squarecampus.com/platform/) · [School management system · The category page, modules as workflows](https://squarecampus.com/school-management-system/) · [SquareCampus vs Fedena · Managed School OS against an open-source ERP](https://squarecampus.com/compare/squarecampus-vs-fedena/) · [How to choose a school management system · A vendor-neutral buyer's checklist](https://blogs.squarecampus.com/how-to-choose-school-management-system/) · [Pricing · The licensing model; figures by proposal](https://squarecampus.com/pricing/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/fee-management-software-for-schools/ --- title: "Fee Management Software for Schools in India | SquareCampus" description: "Fee management software for Indian schools: term plans, concessions, transport slabs, GST receipts, reminders and reconciliation on one governed ledger." canonical: https://squarecampus.com/fee-management-software-for-schools/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · Fee management software for schools # Fee management that closes the month without a spreadsheet. Fee collection in an Indian school is not one number. It is term plans, concessions, transport slabs, late fees, partial payments and a reconciliation that someone does by hand every month. SquareCampus keeps all of it on one ledger with an owner against every exception. Finance officers Bursars Trust accountants Principals [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What is fee management software? Fee management software is the part of a school system that defines fee structures, raises dues per student, records payments across channels, applies concessions and late fees, issues receipts and reconciles collections against the bank. Done well, it is a ledger the whole school shares rather than a collection module that finance reconciles against everything else. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Fee plans per student Term plans, optional components, sibling and staff concessions and transport slabs resolve into one due amount per student, with the rule that produced it visible. ### Collection across channels Online payments, counter cash, cheques and bank transfers post to the same ledger and issue receipts from one sequence. ### Reminders with an acknowledgement Dues reminders go to parents in context, and the record shows what was sent, when, and whether it was seen. ### Concessions and refunds as approvals Every concession, waiver and refund runs through a role-scoped approval with a reason, so the finance trail is complete before an audit. ### Reconciliation and audit exports Collections reconcile against settlements and bank statements, with exports in the formats auditors and trust boards ask for. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. A worked example ## A sibling concession above the desk's limit How the workflow is designed to run, step by step, and where configuration, scoping or separate quotes apply. 1. 1 The accounts desk applies a sibling concession larger than its approval limit. 2. 2 The request routes to the approver the institution named for that limit, with the reason attached. 3. 3 Once approved, the fee plan, the next invoice and the receipt reflect it; if refused, nothing changes. 4. 4 The approval, the approver and the reason stay on the student's fee record for audit. Configured, scoped or quoted separately - Fee heads, instalments, concessions and late-fee rules are configured from your current structure during implementation. - Payments run through your institution's own gateway account; SquareCampus never handles the money, and gateway fees are between you and the gateway. - Connections to accounting software are scoped integration work, assessed per package; there is no pre-built connector. - Historical dues and receipts are migrated from Pro and validated in a parallel run; anything the old records cannot support is flagged before go-live. 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 - GST-aware receipts for taxable components such as transport and hostel. - Partial payments and instalment plans without losing the original due. - Late-fee rules that respect board holidays and school-specific grace periods. - Trust-level visibility across campuses with campus-level execution. - Follow-up on overdue fees as a workflow with an owner, not a printed list. 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. 1. 1Can one student carry a term plan, a concession and a transport slab without a manual override? 2. 2Do online, counter and bank payments land on the same ledger and the same receipt sequence? 3. 3Is every concession and refund approved by a named role with a recorded reason? 4. 4How long does month-end reconciliation take, and who does it? 5. 5Can the trust board see collections across campuses without a prepared report? Questions ## Fee management software for schools: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Does the fee module support Indian fee structures? Yes. Term plans, concessions, transport slabs, late fees, partial payments and GST-aware receipts are part of the fee model rather than customisations. ### Which payment methods are supported? Online payments through a payment gateway, counter cash, cheques and bank transfers post to one ledger. Gateway options are confirmed during scoping. ### How is follow-up on overdue fees handled? Outstanding dues become a follow-up workflow with reminders in context, an owner, and a record of every contact, so leadership sees the state without chasing the office. ### Can finance keep its existing accounting software? Yes. Collections and receipts export in accounting-friendly formats, and a bounded deployment can run alongside the existing finance stack. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [School fee reconciliation · Why the month-end takes so long, and what fixes it](https://blogs.squarecampus.com/school-fee-reconciliation/) · [School management system · Fees inside the wider operating loop](https://squarecampus.com/school-management-system/) · [SquareCampus vs Entab CampusCare · An honest comparison for finance-led evaluations](https://squarecampus.com/compare/squarecampus-vs-entab-campuscare/) · [Rollout · Parallel run on the fee ledger before go-live](https://squarecampus.com/rollout/) · [Pricing · Student-volume bands, modules included](https://squarecampus.com/pricing/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/school-attendance-management-system/ --- title: "School Attendance Management System | SquareCampus" description: "Attendance management for Indian schools that turns daily marks into early warnings, parent alerts, fee rules and a record every exception is owned in." canonical: https://squarecampus.com/school-attendance-management-system/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · School attendance management system # Attendance that raises a hand before term end. Attendance is the earliest signal a school has about a student, a section or a teacher. Most systems store it. SquareCampus acts on it: an absence pattern becomes an exception with an owner, a guardian alert, and a line in the leadership view the same day. Principals Class teachers Academic coordinators Parents [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What is a school attendance management system? A school attendance management system records daily and period-wise presence for students and staff, notifies guardians, produces the registers and percentages that boards require, and flags patterns that need follow-up. The difference between a register and a system is what happens after the mark: whether an exception is assigned to someone and tracked to resolution. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Quick marking Class and period attendance from the teacher app or a device at the gate, with late arrivals and early departures captured with a reason. ### Guardian alerts in context Absence and late notifications reach parents through the app with the date, period and a way to respond, and the response is recorded. ### Early-warning exceptions Consecutive absences, falling percentages and section-wide dips surface as exceptions with a named owner rather than a figure in a month-end report. ### Attendance to fees and transport Attendance feeds transport billing and fee rules where the school configures it, so the office is not reconciling two registers. ### Registers and board formats Class registers, percentage reports and board-specific formats are produced from the same record, ready for inspection. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - Board-required attendance percentages and registers in the expected layouts. - Staff attendance and substitution recorded against the timetable. - Transport attendance per route and stop, reconciled with the classroom mark. - Alerts to guardians on the channels Indian parents actually read. - Multi-campus dashboards for trusts that need one view across schools. 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. 1. 1Does an absence pattern become a task for someone, or only a number on a report? 2. 2Can a teacher mark a class in under a minute from a phone? 3. 3Are guardian alerts recorded with delivery and acknowledgement? 4. 4Do transport and classroom attendance reconcile automatically? 5. 5Can the principal see today's attendance across campuses without asking? Questions ## School attendance management system: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### How is attendance marked? From the teacher app, a shared classroom device, or an integrated gate device, per class or per period, with late and early-leave reasons captured in place. ### Are parents notified automatically? Yes. Absence and late notifications go to guardians through the parent app with context, and the acknowledgement is recorded against the student. ### What counts as an attendance exception? Rules the school sets: consecutive absences, a percentage falling below a threshold, or a section-wide dip. Each becomes an exception with an owner and a resolution trail. ### Does it support staff attendance and substitutions? Yes. Staff attendance is recorded against the timetable, and substitutions are assigned and logged so cover is visible to the coordinator. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Attendance as an early-warning system · The patterns worth acting on, and when](https://blogs.squarecampus.com/attendance-early-warning-system/) · [Ecosystem · Teacher, parent and student surfaces](https://squarecampus.com/ecosystem/) · [School management system · Attendance inside the operating loop](https://squarecampus.com/school-management-system/) · [AEGIS · Ask which sections need attention today, in plain language](https://squarecampus.com/aegis/) · [SquareCampus vs Teachmint · Operations-first against classroom-first](https://squarecampus.com/compare/squarecampus-vs-teachmint/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/school-admission-management-software/ --- title: "School Admission Management Software | SquareCampus" description: "Admission management software for Indian schools: enquiry to enrolment with document verification, fee plans, section allocation and a status parents can see." canonical: https://squarecampus.com/school-admission-management-software/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · School admission management software # Admissions with a status every parent can see. An admissions season is hundreds of applications moving through verification, interaction, offer, fee and allocation, with parents phoning the office to ask where theirs is. SquareCampus runs the sequence with an owner on every step and a status the parent sees without calling. Admissions coordinators Front office Principals Parents [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What is school admission management software? School admission management software runs the enquiry-to-enrolment sequence: capturing enquiries, issuing application forms, collecting and verifying documents, scheduling interactions, issuing offers, collecting admission fees and allocating sections. Its job is to make every application's status visible to the office and the parent, and to turn a confirmed admission into a student record 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Enquiry capture Enquiries from the website, walk-ins and calls land in one queue with source, class sought and a follow-up owner. ### Application and documents Parents complete forms and upload documents online; the office verifies against a checklist, and gaps go back to the parent as a request, not a phone call. ### Interaction and offer Interaction slots, outcomes and offers are recorded in sequence, with offer letters issued from the record. ### Admission fee to enrolment A paid admission fee confirms the seat, creates the student record, attaches the fee plan and allocates a section in one step. ### Leadership view of the season Applications by stage, class and campus are visible daily, with stalled applications surfaced as exceptions. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - Class-wise seat matrices with sibling and staff-ward priorities. - Document checklists that match board and state requirements. - Admission, registration and caution-deposit fees handled as distinct components. - Transfer-certificate and previous-school records captured at enrolment. - Multi-campus seasons run centrally with campus-level execution. 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. 1. 1Can a parent see their application's stage without calling the office? 2. 2Does a confirmed admission create the student, the fee plan and the section allocation together? 3. 3Are document gaps requested from the parent in the system, with a record? 4. 4Can leadership see stalled applications today, by class and campus? 5. 5What happens to the enquiry list after the season, and who owns it? Questions ## School admission management software: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Can parents apply online? Yes. Parents complete the application and upload documents from the app or the web, and see the stage their application is at throughout. ### How are seats and priorities handled? Class-wise seat matrices with the priorities the school defines, such as siblings and staff wards, applied consistently and visibly. ### What happens once an admission is confirmed? The student record, fee plan and section allocation are created from the application in one step, so nothing is typed twice. ### Can we run admissions for several campuses centrally? Yes. A trust can run one season across campuses with central visibility and campus-level execution. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [The admissions-to-enrolment gap · Where applications stall, and the fix](https://blogs.squarecampus.com/admissions-to-enrolment-gap/) · [School management system · Admissions as the first step of the loop](https://squarecampus.com/school-management-system/) · [Fee management · The fee plan the admission creates](https://squarecampus.com/fee-management-software-for-schools/) · [Rollout · Going live before the next season](https://squarecampus.com/rollout/) · [FAQ · Common evaluation questions answered](https://squarecampus.com/faq/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/multi-campus-school-management-software/ --- title: "Multi-Campus School Management Software for Trusts | SquareCampus" description: "Multi-campus school management software for trusts and school groups: policy at the trust level, execution at each campus, one governed view across all of them." canonical: https://squarecampus.com/multi-campus-school-management-software/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · Multi-campus school management software # One trust, many campuses, one governed view. School groups swing between two failures: a head office that becomes the bottleneck for every decision, and campuses that drift into their own processes. SquareCampus is modelled on trust, school and campus from the start, so policy is set once and executed locally. Trustees Group CEOs and directors Head-office finance Campus principals [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What is multi-campus school management software? Multi-campus school management software runs several schools or campuses on one system with a shared institutional model. The trust or head office sets policy, fee structures, academic calendars and approval limits; each campus executes within them; and leadership sees attendance, collections, admissions and exceptions across all campuses in one view without consolidating reports. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Policy at the trust level Fee structures, concession rules, approval limits and academic calendars are defined once and inherited by campuses, with local variations recorded as exceptions. ### Execution at the campus Each campus runs its own admissions, attendance, fees and communication inside the trust's rules, with its own owners and its own audit trail. ### Roles scoped by campus A campus principal sees their campus; a trust finance officer sees collections everywhere; a trustee sees exceptions across the group. Scope is a property of the role. ### Cross-campus exceptions Collections behind plan, attendance dips and stalled approvals surface as exceptions with an owner, whichever campus they belong to. ### Board reporting from the record Monthly trust-board views come from the same data the campuses run on, so there is nothing to reconcile before the meeting. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. Governance versus support ## Multi-campus governance is not the same as supporting multiple campuses. Most school software can hold several campuses' records. The buyer question is whether policy, scope, exceptions and board reporting cross campuses without consolidation. This is the difference, dimension by dimension. Multi-campus governance is not the same as supporting multiple campuses. | Dimension | Supports multiple campuses | Multi-campus governance | | --- | --- | --- | | Structure | Each campus is a separate instance or a branch code on the same records | Trust, school and campus are one hierarchy in the institutional model | | Policy | Head office circulates a policy; each campus configures its own version | Policy is set once at the trust level and inherited; local variation is recorded as an exception with a reason | | Access | Campus users are separated by login | Scope is a property of the role: a principal sees one campus, a trust officer sees across campuses, on every screen, report and AEGIS answer | | Exceptions | Each campus escalates by phone or email | Collections behind plan, attendance drift and stalled approvals surface as owned exceptions, whichever campus they belong to | | Reporting | Campus reports are consolidated before the board meeting | Board views come from the records the campuses run on, with nothing to reconcile first | 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 - Trust, society and company structures with campuses under different boards. - Campus-specific fee schedules within a trust-level policy. - Consolidated collections and outstanding across campuses for the trust accountant. - Staff transfers between campuses with history intact. - Central communication to all parents with campus-level sending. 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. 1. 1Is the trust-campus hierarchy part of the data model, or a workaround with separate instances? 2. 2Can head office set a fee policy once and see where campuses deviate? 3. 3Are roles scoped by campus, so a principal never sees another school's data? 4. 4Can the board see today's state across campuses without a prepared pack? 5. 5How does adding a campus work: configuration or a new implementation? Questions ## Multi-campus school management software: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Does each campus need its own instance? No. Trust, school and campus are one model. Campuses share the trust's policies and run their own operations inside them. ### Can campuses have different fee structures? Yes. Campus-specific schedules sit within trust-level policy, and any deviation is visible to head office as a recorded exception. ### How is access separated between campuses? Roles carry a scope. A campus role sees its campus; trust roles see across campuses. The scope applies to every screen, report and AEGIS answer. ### Can we add a campus later? Yes. A new campus is configured under the trust and inherits its policies, with its own rollout sequence for migration and training. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Centralised control vs campus autonomy · The governance model that resolves it](https://blogs.squarecampus.com/multi-campus-school-governance/) · [Trust-board monthly reporting · From report packs to a live view](https://blogs.squarecampus.com/trust-board-monthly-reporting/) · [Founding Institutional Partners · The programme for school groups](https://squarecampus.com/launch-partners/) · [AEGIS · Cross-campus questions, answered in scope](https://squarecampus.com/aegis/) · [School management system · The category page](https://squarecampus.com/school-management-system/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/school-management-software-for-cbse-schools/ --- title: "School Management Software for CBSE Schools | SquareCampus" description: "School management software for CBSE schools: grading templates, attendance registers, report formats and the records CBSE affiliation and inspections expect." canonical: https://squarecampus.com/school-management-software-for-cbse-schools/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · School management software for CBSE schools # Built around the CBSE calendar, not adapted to it. A CBSE school runs on the board's rhythm: registration, internal assessment, term reports, board exam records and the documentation an affiliation inspection asks for. SquareCampus carries those formats and cycles as configuration, so the office is not maintaining them in spreadsheets on the side. ICSE and state-board schools run on the same platform with their own configuration. CBSE school principals Examination in-charges Academic coordinators Administrators [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What should CBSE school management software include? School management software for CBSE schools should carry the board's grading and assessment structure, produce term reports in the expected formats, keep attendance registers and student records the way affiliation and inspection require, and handle the board's registration and examination cycles as part of the academic year rather than as separate spreadsheets. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Assessment structure as configuration Internal assessment components, weightages and grading scales are configured per class and session, and the report card follows from them. ### Term reports and report cards Marks entry, moderation and publication produce report cards in the school's CBSE-aligned format, with a record of every change. ### Registration and examination records Student data required for board registration is kept complete from admission, so the annual export is a check rather than a scramble. ### Attendance registers for inspection Registers and percentages are produced from the daily record in the layouts inspections expect. ### Timetable and substitution Period allocation, teacher load and substitutions run against the academic calendar, with cover visible to the coordinator. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - Grading scales and assessment components aligned to current CBSE guidance, maintained as configuration. - Report card formats per class group, from primary to senior secondary. - Student master data kept complete for board registration from the day of admission. - Documentation trails that help an affiliation or inspection visit. - Fee, transport and communication running on the same record as academics. 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. 1. 1Are assessment components and grading scales configuration, or a custom build per session? 2. 2Can report cards be produced without exporting marks to a spreadsheet? 3. 3Is student master data complete enough for board registration without a data drive? 4. 4Do attendance registers come out in the layout an inspection expects? 5. 5Does academics share a record with fees and communication, or sit in its own module? Questions ## School management software for CBSE schools: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Does SquareCampus support CBSE grading and report cards? Yes. Assessment components, weightages and grading scales are configured per class and session, and report cards are produced from them in the school's CBSE-aligned format. ### Can we run other boards at the same trust? Yes. Campuses under different boards run on one trust with board-specific academic configuration per campus. ### How is board registration data handled? Student master data required for registration is captured at admission and kept complete, so the annual export is a verification step. ### Will teachers need to learn a new grading workflow? Marks entry follows the school's existing assessment structure. Role-based training during rollout covers the examination workflow end to end. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Board-specific school software · What differs between CBSE, ICSE and state boards](https://blogs.squarecampus.com/board-specific-school-software/) · [Exam and result operations · From schedule to publication without drift](https://blogs.squarecampus.com/exam-and-result-operations/) · [Exam management · The examination workflow in detail](https://squarecampus.com/school-exam-management-software/) · [School management system · The category page](https://squarecampus.com/school-management-system/) · [For ICSE schools · The same platform, configured for CISCE](https://squarecampus.com/school-management-software-for-icse-schools/) · [For state-board schools · State formats, languages and calendars](https://squarecampus.com/school-management-software-for-state-board-schools/) · [Rollout · Sequenced around the academic calendar](https://squarecampus.com/rollout/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/school-exam-management-software/ --- title: "School Exam Management Software | SquareCampus" description: "Exam management software for Indian schools: schedules, marks entry, moderation, report cards, results publication and promotion on one auditable record." canonical: https://squarecampus.com/school-exam-management-software/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · School exam management software # From exam schedule to results without a single re-typed mark. Examinations are the most audited thing a school does and usually the most spreadsheet-driven. SquareCampus runs the cycle as one sequence, schedule, marks, moderation, publication and promotion, with every change attributed and every result traceable to its entry. Examination in-charges Subject teachers Academic coordinators Principals [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What is school exam management software? School exam management software schedules examinations, allocates rooms and invigilators, captures marks per subject and component, applies grading and moderation rules, produces report cards and result sheets, publishes results to parents, and rolls students into the next class. Its value is an unbroken record from the mark entered to the result published, so any question later has an answer. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Schedule and allocation Exam dates, rooms, seating and invigilation are planned against the timetable, with clashes surfaced before they reach a notice board. ### Marks entry by role Subject teachers enter marks for their allocation only; entries are timestamped and attributable, and late or missing entries surface as exceptions. ### Grading and moderation Weightages, grading scales and moderation rules apply consistently, with every override recorded with a reason and an approver. ### Report cards and publication Report cards are produced in the school's format and published to parents through the app, with re-issues tracked. ### Promotion and the next session Promotion decisions roll students into the next class and carry their record forward, so the new session starts clean. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - Board-aligned assessment structures for CBSE, ICSE and state boards. - Report card formats per class group, including remarks and co-scholastic areas. - Result sheets and toppers lists in the layouts schools publish. - Re-evaluation and re-test handling as recorded workflows. - Multi-campus examination calendars with campus-level execution. 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. 1. 1Can a teacher enter marks only for their own allocation, with each entry attributed? 2. 2Are overrides and moderation recorded with a reason and an approver? 3. 3Can report cards be produced without exporting to a spreadsheet? 4. 4How are re-tests and re-evaluations handled and traced? 5. 5Does promotion carry the full record into the next session? Questions ## School exam management software: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Can teachers enter marks from their phones? Yes. Marks entry is available from the teacher app for the teacher's own allocation, with entries timestamped and attributable. ### How are report card formats handled? Formats are configured per class group and board, including remarks and co-scholastic areas, and produced directly from the marks record. ### What if a result needs to be corrected after publication? Corrections run as a recorded workflow with a reason and an approver, and the re-issued report card is tracked against the original. ### Does it handle promotion to the next class? Yes. Promotion decisions roll students into the next session with their record intact, including pending dues and documents. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Exam and result operations · The failure points in a typical exam cycle](https://blogs.squarecampus.com/exam-and-result-operations/) · [For CBSE schools · Board-aligned configuration](https://squarecampus.com/school-management-software-for-cbse-schools/) · [School management system · Exams inside the operating loop](https://squarecampus.com/school-management-system/) · [Ecosystem · Teacher and parent surfaces](https://squarecampus.com/ecosystem/) · [What is SquareCampus? · The canonical definition](https://squarecampus.com/what-is-squarecampus/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/parent-communication-app-for-schools/ --- title: "Parent Communication App for Schools in India | SquareCampus" description: "A parent communication app that ties every message to context: attendance, fees, results and circulars, with delivery and acknowledgement recorded." canonical: https://squarecampus.com/parent-communication-app-for-schools/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · Parent communication app for schools # Parent communication with a record, not a broadcast. Schools do not lack ways to message parents. They lack a record of what was sent, to whom, about what, and whether it was seen. SquareCampus attaches every message to the student, class, fee state or incident it concerns, and keeps the acknowledgement. Principals Class teachers Front office Parents [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What is a parent communication app for schools? A parent communication app is the channel through which a school sends circulars, attendance and fee notifications, results, event notices and individual messages to guardians, and through which parents respond, acknowledge and pay. The difference between a messaging tool and a communication system is context and record: each message belongs to something, and the school can see delivery and acknowledgement. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Notifications in context Absence, dues, results and incident notifications carry the student, date and detail they concern, and link to the action a parent can take. ### Circulars with acknowledgement Circulars go to the right classes and campuses, and the school sees who has read and acknowledged them. ### Two-way, role-aware messaging Parents reach the class teacher or office through the app; messages route to the right role and are recorded against the student. ### Consent and permissions Trip consents, medical updates and photo permissions are collected as recorded responses, not paper slips. ### Escalation paths Unanswered or unresolved messages escalate to the coordinator or principal on rules the school sets. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - Notifications on the app with fallbacks on channels Indian parents actually read. - Apps, circulars and notifications designed for each family's preferred language; available languages confirmed in the proposal. - Fee reminders that link to payment and record the acknowledgement. - Multi-campus sending with trust-level oversight. - Communication logs that help when a dispute or inspection asks what was communicated. 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. 1. 1Is every message attached to a student, class or event, or is it a broadcast list? 2. 2Can the school see delivery and acknowledgement per parent? 3. 3Do parents have a way to respond that reaches the right role? 4. 4Are consents and permissions recorded as responses? 5. 5Is communication on the same record as attendance, fees and results? Questions ## Parent communication app for schools: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Is the parent app included? Yes. Parent and student apps are part of the licence, not a per-user add-on. App availability is confirmed during scoping. ### Can parents reply to messages? Yes. Replies route to the right role, such as the class teacher or the office, and are recorded against the student. ### How do circular acknowledgements work? A circular can require acknowledgement. The school sees who has read and acknowledged it, and follows up the rest as a task. ### Can communication be sent in more than one language? Yes, that is the design: the parent and student apps, circulars and notifications are built so each family can use the language it is comfortable in, while the institution keeps one record. The languages available to your institution are confirmed in your proposal. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Parent communication in schools · Why broadcasts fail and what replaces them](https://blogs.squarecampus.com/parent-communication-schools/) · [Ecosystem · The parent and student apps](https://squarecampus.com/ecosystem/) · [Attendance · The alerts parents receive most](https://squarecampus.com/school-attendance-management-system/) · [Fee management · Reminders that link to payment](https://squarecampus.com/fee-management-software-for-schools/) · [Contact · Speak to the team](https://squarecampus.com/contact/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/school-management-software-for-icse-schools/ --- title: "School Management Software for ICSE Schools | SquareCampus" description: "School management software for ICSE and ISC schools: CISCE-aligned assessment, internal marks, report cards, registers and the records affiliation expects." canonical: https://squarecampus.com/school-management-software-for-icse-schools/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · School management software for ICSE schools # Configured for CISCE, from internal assessment to ISC. ICSE and ISC schools carry a heavier internal-assessment load than most boards, with project work, practicals and continuous evaluation feeding the final record. SquareCampus holds the CISCE structure as configuration, so marks, moderation and report cards follow the board's shape without a spreadsheet beside them. ICSE school principals Examination in-charges Academic coordinators Administrators [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What should ICSE school management software include? School management software for ICSE schools should carry the CISCE assessment structure for ICSE and ISC, including internal assessment components, project and practical marks, and grading scales; produce report cards in the school's format; keep attendance registers and student records the way affiliation requires; and treat the board's registration and examination cycles as part of the academic year rather than as separate spreadsheets. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### Internal assessment as configuration Components, weightages and grading scales for ICSE and ISC are configured per class and session; project and practical marks sit alongside written papers in one record. ### Marks, moderation and report cards Subject teachers enter marks for their allocation, moderation rules apply consistently, and report cards are produced in the school's CISCE-aligned format with every change attributed. ### Registration and examination records Student data required for board registration is kept complete from admission, so the annual export is a verification step. ### Attendance registers for affiliation Registers and percentages are produced from the daily record in the layouts an affiliation visit expects. ### Timetable, practicals and substitution Period allocation, laboratory sessions and substitutions run against the academic calendar, with cover visible to the coordinator. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - ICSE and ISC assessment structures maintained as configuration, not a build per session. - Report card formats per class group, including internal assessment and co-scholastic areas. - Student master data kept complete for CISCE registration from the day of admission. - Parent and student apps designed for the family's preferred language; available languages confirmed in the proposal. - Fees, transport and communication on the same record as academics. 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. 1. 1Can internal assessment, project and practical marks live in the same record as written papers? 2. 2Are ICSE and ISC grading scales configuration, or a custom build per session? 3. 3Can report cards be produced without exporting marks to a spreadsheet? 4. 4Is student master data complete enough for board registration without a data drive? 5. 5Does academics share a record with fees and communication, or sit in its own module? Questions ## School management software for ICSE schools: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Does SquareCampus support ICSE and ISC assessment? Yes. Internal assessment components, project and practical marks, weightages and grading scales for ICSE and ISC are configured per class and session, and report cards are produced from them. ### Can a trust run ICSE and CBSE campuses on one system? Yes. Campuses under different boards run on one trust with board-specific academic configuration per campus, and one view for leadership. ### How are report card formats handled? Formats are configured per class group in the school's CISCE-aligned layout, including internal assessment and co-scholastic areas, and produced directly from the marks record. ### Will teachers need to learn a new grading workflow? Marks entry follows the school's existing assessment structure. Role-based training during rollout covers the examination workflow end to end. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Board-specific school software · What differs between CBSE, ICSE and state boards](https://blogs.squarecampus.com/board-specific-school-software/) · [Exam management · The examination workflow in detail](https://squarecampus.com/school-exam-management-software/) · [For CBSE schools · The same platform, configured for CBSE](https://squarecampus.com/school-management-software-for-cbse-schools/) · [For state-board schools · State formats, languages and calendars](https://squarecampus.com/school-management-software-for-state-board-schools/) · [School management system · The category page](https://squarecampus.com/school-management-system/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/school-management-software-for-state-board-schools/ --- title: "School Management Software for State Board Schools | SquareCampus" description: "School management software for state-board schools in India: state formats and calendars, parents reached in their language, fees and registers on one record." canonical: https://squarecampus.com/school-management-software-for-state-board-schools/ describedby: https://squarecampus.com/llms.txt --- [School management system](https://squarecampus.com/school-management-system/) · School management software for state board schools # Your state's formats, your families' languages, one record. State-board schools serve the widest range of families in India, and the office pays for it in translated circulars, hand-filled state registers and fee structures that follow local rules. SquareCampus is designed to carry state formats and calendars as configuration and to reach parents in the languages they read, while the institution keeps one governed record underneath. State-board school principals Administrators Class teachers Parents [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Direct answer ## What should state board school management software include? School management software for state-board schools should carry the state's assessment scheme, report formats, registers and academic calendar as configuration; communicate with parents in the languages they read; handle local fee rules, concessions and government scheme records; and keep attendance and student records in the shape district and board inspections expect, all on one record shared with fees and communication. 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](https://squarecampus.com/what-is-squarecampus/). 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. ### State assessment and report formats Grading schemes, report layouts and promotion rules for the state board are configured per class and session, and report cards follow from the marks record. ### Registers for inspection Attendance, admission and fee registers come out of the daily record in the layouts district and board inspections expect. ### Parent communication in families' languages Circulars, dues reminders, results and notices reach families in the language they read, with delivery and acknowledgement recorded against the student. ### Fees under local rules Fee structures, concessions and scheme-linked waivers follow the state's rules, with receipts and reconciliation on one ledger. ### Leadership view Principals and management see attendance, collections and exceptions across sections and campuses with an owner against each item. This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. 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 - State-board assessment schemes, report formats and calendars as configuration. - Apps, circulars and notifications designed for each family's preferred language; available languages confirmed in the proposal. - Scheme and concession records kept against the student for audits and claims. - Registers in the layouts district inspections ask for. - Trusts running state-board, CBSE and ICSE campuses on one system. 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. 1. 1Are the state's report formats and registers configuration, or a custom build? 2. 2Can parents receive every notice in the language they read, with acknowledgement recorded? 3. 3Do fee rules, concessions and scheme records live on the same ledger as collections? 4. 4Can registers for inspection be produced from the daily record without re-typing? 5. 5Does the vendor support the state boards you run, and say so in writing? Questions ## School management software for state board schools: common questions Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth. ### Which state boards does SquareCampus support? State-board assessment schemes, report formats and calendars are configuration. The boards an institution runs are confirmed during scoping and set up during rollout. ### Which languages are available for parents? The parent and student apps, circulars and notifications are designed so each family can choose its language while the institution keeps one record. The languages available to your institution are confirmed in your proposal. ### Can we run a state-board school and a CBSE school under one trust? Yes. Campuses under different boards run on one trust with board-specific configuration per campus and one leadership view. ### How are government scheme records handled? Scheme eligibility, concessions and waivers are recorded against the student and reflected on the fee ledger, so claims and audits draw from one record. More on evaluation, security and rollout in the [FAQ](https://squarecampus.com/faq/). Related ## Keep reading The pages a buyer on this question usually reads next. [Parent communication · Messages in the family's language, with a record](https://squarecampus.com/parent-communication-app-for-schools/) · [Fee management · Concessions and scheme rules on one ledger](https://squarecampus.com/fee-management-software-for-schools/) · [For CBSE schools · The same platform, configured for CBSE](https://squarecampus.com/school-management-software-for-cbse-schools/) · [For ICSE schools · The same platform, configured for CISCE](https://squarecampus.com/school-management-software-for-icse-schools/) · [Board-specific school software · What differs between the boards](https://blogs.squarecampus.com/board-specific-school-software/) 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](https://squarecampus.com/about/). The licensing model is published; figures follow a written proposal. [Book a demo](https://squarecampus.com/demo/) · [How pricing works](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/ --- title: "SquareCampus | School Management Software for Indian Schools and Trusts" description: "School management software built as a connected School OS: admissions, attendance, fees, exams and parent communication on one record for Indian schools." canonical: https://squarecampus.com/ describedby: https://squarecampus.com/llms.txt --- 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. [Book a demo](https://squarecampus.com/demo/) · [See how it works](https://squarecampus.com/platform/) - 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. ### 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. [Admission management](https://squarecampus.com/school-admission-management-software/) ### 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. [Attendance management](https://squarecampus.com/school-attendance-management-system/) ### 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. [Fee management](https://squarecampus.com/fee-management-software-for-schools/) ### 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. [Exam and results management](https://squarecampus.com/school-exam-management-software/) ### 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. [Parent communication](https://squarecampus.com/parent-communication-app-for-schools/) ### 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. [Multi-campus management](https://squarecampus.com/multi-campus-school-management-software/) 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. [What is SquareCampus?](https://squarecampus.com/what-is-squarecampus/) The command centre ## Management sees the institution the way a board expects to Trust-level governance with campus-level autonomy: policy is set once, campuses execute inside guardrails, and exceptions reach the right desk early. 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 data Grade 10 96% Grade 9 91% Grade 8 94% Grade 7 88% Grade 6 97% Campus roll-up Exceptions flagged Fee collection Synthetic data 72% Collected Collected 72% Pending 20% Overdue 8% ![Modern campus courtyard](https://squarecampus.com/images/editorial/campus-courtyard.webp) Who it is for Trustees, principals, finance teams and campus operators, on one record. Governance model ## Trust-level governance. Campus-level autonomy. Every campus ### Set policy once Fee rules, approval chains, academic calendars, and access boundaries are defined at the trust level — not re-invented per campus. ### Campuses execute with autonomy Principals and campus teams run their day inside clear guardrails, with local variation where the institution allows it. ### Exceptions surface early Attendance drift, fee exposure, and stalled approvals escalate to the right desk while they are still small. ### 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 means the institution stays in control: where the platform runs, who can see what, and how the data leaves if you ever want it to. ## 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. English Hindi Kannada Structured underneath Circulars, dues, acknowledgements, and audit history stay attached to the same student and family context. ![Institution building for India-first operations context](https://squarecampus.com/images/editorial/school-building-delhi.webp) Circular delivery ENG HIN Fee reminder queued in the family's language Same due date, same receipt trail, same operator view. Language adapts without rewriting the underlying workflow. India-aware operating model Language stays flexible while the institution stays operationally strict. ## 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. [See deployment options](https://squarecampus.com/services/) Governed intelligence ## AEGIS is the governed intelligence layer inside SquareCampus AEGIS is the intelligence that lives inside SquareCampus, not a chatbot bolted onto an ERP. It surfaces what needs attention across the institution, inside the same permissions and audit trails as everything else. 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 [Meet AEGIS](https://squarecampus.com/aegis/) Rollout & trust ## Switching systems is an institutional decision. We treat it that way. The move is sequenced around your academic calendar, validated in parallel, and governed by the same trust posture the platform runs on. ## 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. [See the rollout model](https://squarecampus.com/rollout/) · [Review the trust posture](https://squarecampus.com/security/) 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. [See the programme terms](https://squarecampus.com/launch-partners/) · [Request a partnership diagnosis](https://squarecampus.com/launch-partners/#request-diagnosis) A separate launch programme ## Selected Institutional Launch Pilot Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. [Review launch-pilot eligibility](https://squarecampus.com/pricing/#pilot) 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. [Book a demo](https://squarecampus.com/demo/) · [View platform architecture](https://squarecampus.com/platform/) --- Source: https://squarecampus.com/what-is-squarecampus/ --- title: "What is SquareCampus? | School Operating System and Decision Layer" description: "SquareCampus is a School Operating System and institutional decision layer for Indian schools and educational trusts, connecting school cycles to ownership, exceptions, auditability and leadership decisions." canonical: https://squarecampus.com/what-is-squarecampus/ describedby: https://squarecampus.com/llms.txt --- Category and definition # What is SquareCampus? SquareCampus is a School Operating System and institutional decision layer for schools, educational trusts and multi-campus groups in India. It includes the operational systems of record institutions expect, but its primary purpose is to connect recurring school cycles to ownership, exception handling, auditability and leadership decisions. [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) The distinction that matters 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. At a glance ## What it is, who it serves, what it includes. **What it is** 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. **Who it serves** - Standalone schools with governance, identity or audit requirements - Educational trusts and multi-campus school groups - Church-run and society-run school chains - Private universities and multi-school higher-education groups, as a governed operating layer over the systems they already run **What it includes** - [Admission management](https://squarecampus.com/school-admission-management-software/) - [Attendance management](https://squarecampus.com/school-attendance-management-system/) - [Fee management](https://squarecampus.com/fee-management-software-for-schools/) - [Exam and results management](https://squarecampus.com/school-exam-management-software/) - [Parent communication](https://squarecampus.com/parent-communication-app-for-schools/) - [Multi-campus management](https://squarecampus.com/multi-campus-school-management-software/) - [AEGIS, the read-only intelligence layer](https://squarecampus.com/aegis/) Your written proposal confirms which modules, apps, languages and integrations you get. **How it relates to ERP** It covers the record-keeping and workflows expected from school ERP software; the difference is that ownership, approvals and audit history sit on the same record. [School ERP software, explained](https://squarecampus.com/school-erp-software/) **How it is organised** Four layers — record, workflow, governance and intelligence. [See the platform](https://squarecampus.com/platform/#layers) Dashboard versus decision layer ## A bar chart shows a condition. A decision layer explains what to do about it. This is the difference between reporting that describes the institution and an operating layer that moves it. ![A record becomes an exception, the exception is routed to a named owner, the owner acts with a recorded reason, and the action is committed to an append-only audit timeline.](https://squarecampus.com/motion/operating-signal-to-action-light.4fbbfbc7.webp) A dashboard tells you - Attendance decreased - Fees remain pending - Reports are overdue A decision layer tells you - Which campus crossed the threshold - When the deviation started - Which workflow is blocked - Who owns the response - What evidence supports the conclusion - What leadership should review next AEGIS AEGIS is the governed intelligence layer inside SquareCampus. It produces permission-scoped, source-grounded and auditable operational answers from institutional context. - Read-only — AEGIS answers questions, it does not act on the institution's behalf - RBAC-scoped — a person only ever sees what their role already permits - Source-grounded — every answer points back to the records it came from - Auditable — questions and answers are recorded like any other institutional action - Human-controlled — decisions remain with the people accountable for them What the words mean here ## School OS, governance, exception ownership, accountability. These terms are used across the site with specific meanings. This is what each one commits SquareCampus to. **School Operating System (School OS)** The connected backbone an institution runs on. It holds the records a school expects, and it also carries the workflows, ownership, approvals, exceptions and audit history that turn those records into accountable day-to-day operations. The distinction from an ERP is factual: every cycle has stages, an owner and a deadline; every exception is routed to a named desk; every override is recorded with a reason. **Governance** Policy, approval chains, role boundaries and audit history held as institutional configuration rather than as habits. A concession limit, a refund approval or a campus-level deviation from trust policy is defined once, enforced on every record, and visible to the people accountable for it. **Exception ownership** When a record leaves its expected state (collections behind plan, attendance under a threshold, an approval overdue) the deviation becomes an exception with a named owner, a position and a due date, rather than a line in a report that someone may notice. **Accountability** Every approval, override and closure is attributed to a role and a person, recorded with the reason, and kept on an append-only timeline. Leadership can see not only what happened but who decided it and on what basis. **Institutional visibility** Leadership sees the current position of the institution from the records the campuses run on, without a department preparing a report first: what requires attention, why it matters, who owns it and what happens next. **Multi-campus governance** More than supporting several campuses. Trust, school and campus are one hierarchy; policy is set once and executed locally; scope is a property of the role; exceptions and board views cross campuses without consolidation. Multi-campus governance versus supporting multiple campuses How multi-campus governance differs from software that merely supports several campuses. | Dimension | Supports multiple campuses | Multi-campus governance | | --- | --- | --- | | Structure | Each campus is a separate instance or a branch code on the same records | Trust, school and campus are one hierarchy in the institutional model | | Policy | Head office circulates a policy; each campus configures its own version | Policy is set once at the trust level and inherited; local variation is recorded as an exception with a reason | | Access | Campus users are separated by login | Scope is a property of the role: a principal sees one campus, a trust officer sees across campuses, on every screen, report and AEGIS answer | | Exceptions | Each campus escalates by phone or email | Collections behind plan, attendance drift and stalled approvals surface as owned exceptions, whichever campus they belong to | | Reporting | Campus reports are consolidated before the board meeting | Board views come from the records the campuses run on, with nothing to reconcile first | Direct answers ## The questions people ask before they know what to call it. **Is SquareCampus an ERP?** Yes, in the sense buyers usually mean. 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. "School OS" describes how it is built: school cycles, ownership, exceptions, governance and leadership visibility share one institutional model. **What is a School Operating System?** A School Operating System is the connected operating backbone an institution runs on. It holds the records a school expects, but it also carries the workflows, ownership, approvals, exceptions and audit history that turn those records into accountable day-to-day operations. **What is an institutional decision layer?** 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 is built to do both, so leadership does not have to assemble context before acting. **Who is SquareCampus built for?** Indian schools, educational trusts, church-run school groups and multi-campus institutions, and higher-education institutions as a governed layer over the systems they already run. It suits institutions that care about operational control, accountable ownership and leadership visibility — whether they run one campus or many. It is not designed for an institution that needs only basic attendance, fees and report cards at the lowest possible price. **Is AEGIS a chatbot?** No. AEGIS is the governed intelligence layer inside SquareCampus. It produces permission-scoped, source-grounded and auditable operational answers from institutional context. It is read-only, constrained by the asker's existing role permissions, and does not take autonomous decisions. **Can SquareCampus replace our existing school ERP?** Institutions commonly move to SquareCampus from a school ERP, a set of disconnected tools, or a mix of both. Migration scope, sequencing and how long the existing system runs alongside are agreed during discovery rather than assumed. **What does SquareCampus mean by governance, exception ownership and accountability?** Governance is policy, approval chains, role boundaries and audit history held as institutional configuration. Exception ownership means a deviation from the expected state becomes a routed item with a named owner, a position and a due date. Accountability means every approval, override and closure is attributed to a person and a role, recorded with the reason, on an append-only timeline. **How does multi-campus governance differ from supporting multiple campuses?** Supporting multiple campuses means the software can hold several campuses' records. Multi-campus governance means trust, school and campus are one hierarchy: policy is set once and executed locally with deviations recorded as exceptions, access scope is a property of the role, and exceptions and board views cross campuses from the same records without consolidation. Next step ## The fastest way to understand a School OS is to point it at a real bottleneck. Bring one cycle that consistently costs your institution time — collections, results, attendance follow-up or parent escalations — and we will map what a governed version of it looks like. [Book a demo](https://squarecampus.com/demo/) · [See the commercial model](https://squarecampus.com/pricing/) --- Source: https://squarecampus.com/enterprise/ --- title: "SquareCampus Enterprise | Institutional Governance" description: "Explore SquareCampus Enterprise for institutional governance, cross-campus command, identity and audit requirements, with deployment and commercial scope agreed during discovery." canonical: https://squarecampus.com/enterprise/ describedby: https://squarecampus.com/llms.txt --- SquareCampus Enterprise # Run every campus. Govern them as one. For trusts, school groups and standalone institutions with deeper governance, identity or audit requirements. Define central policy, campus accountability and the controls your institution needs in one agreed operating scope. [Discuss Enterprise](https://squarecampus.com/contact/) · [Compare the plans](https://squarecampus.com/pricing/#plans) The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. Institutional governance One institutional policy Identity · Authority · Audit requirements Campus A Local scope Campus B Local scope Campus C Local scope Central governance. Defined local responsibility. Illustrative governance model. The proposal confirms available controls and deployment scope. The Enterprise dimension ## Institutional governance, across the operating model. Enterprise is selected for the governance requirement. Discovery establishes the available capabilities, institutional boundaries and delivery scope for each dimension. ### Institutional structure Advanced trust-school-campus governance requirements: inherited policy and recorded local exceptions, subject to scoping ### Command Trust-level command-view requirements, scoped against available reporting capabilities ### Governance Advanced approval and exception-ownership requirements across workflows and campuses, scoped during discovery ### Identity Identity governance: multi-directory requirements, group-to-role mappings, SSO enforcement policy and lifecycle controls, scoped during discovery ### Auditability Advanced policy controls and audit-export requirements; institution-owned data and supported portability apply to every plan ### Intelligence Governed AEGIS access requirements and allowances, confirmed against available capabilities ### Deployment and integration Managed cloud, private-cloud or on-premises eligibility, enterprise integrations and implementation governance This is how SquareCampus is designed to work. Your written proposal confirms what your institution gets, and when. Identity and authority ## Institutional sign-in. SquareCampus-governed access. The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone. Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Standard sign-in authenticates identity only. It does not require access to email, files, Teams, SharePoint or other Microsoft 365 data. [Review identity and access](https://squarecampus.com/security/#identity) ### Your Microsoft environment Stays under your administration 1. Your administrator approves SquareCampus in your Microsoft Entra ID tenant. 2. Staff sign in with their existing institutional Microsoft accounts. 3. Your MFA, Conditional Access and user-assignment policies continue to apply. ### SquareCampus authorisation Governed inside the School OS 1. SquareCampus validates that the sign-in came from your approved tenant. 2. It resolves the person's institution membership and campus scope. 3. It applies role, record and workflow permissions defined in SquareCampus. 4. A secure SquareCampus session is issued. Available separately on any plan Microsoft Entra ID verifies who the user is. SquareCampus determines what the user may access and perform. Single sign-on is chosen by the institution, never required. Chosen by requirement ## Enterprise control is not reserved for large institutions. Enterprise is selected by governance requirement, not merely by enrolment. A standalone school may require institution-managed identity, advanced approvals, executive visibility, stricter auditability or governed intelligence even without operating a large campus network. Identity governance beyond single sign-on: enforcement, group-to-role mappings, lifecycle Deeper approval chains and exception ownership Board or trustee command views Stricter access governance and audit exports Most institutions are well served by Starter or Pro. Enterprise exists for institutions whose governance, identity or audit requirements genuinely sit above them — not as a safer version of the same product. The shared foundations ## A complete core. A common security baseline. ### Every plan starts with the core Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. Implementation and support are included in every plan, and every institution gets the same rollout: there is no paid fast track. SquareCampus is designed to need little or no training. Only a custom SLA, such as 24×7 cover or guaranteed response times, is quoted. ### Institution-owned data and defined terms Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. [How retention works](https://legal.fairhelmsystems.com/squarecampus/data-retention/) Define the operating scope ## Bring the governance question. Share your campus structure, identity requirements, approval boundaries and audit expectations. We establish the supported scope and deployment responsibilities, then document the commercial terms in a written proposal. Everything optional is priced in the proposal before you sign, and usage beyond the allowance is prepaid, so the proposal you sign is the bill you get. [Discuss Enterprise](https://squarecampus.com/contact/) --- Source: https://squarecampus.com/why-squarecampus/ --- title: "Why SquareCampus | School OS vs Traditional School ERPs" description: "Why school groups choose a School OS over stitched ERP modules and point tools: one governed system of record, connected workflows, live visibility, and clear accountability." canonical: https://squarecampus.com/why-squarecampus/ describedby: https://squarecampus.com/llms.txt --- 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. [Book a demo](https://squarecampus.com/demo/) · [View platform](https://squarecampus.com/platform/) How to evaluate ## Five things to check in any school management system Differences you can verify in a demo, including in ours. Evaluation criteria to check in any school management system, and how SquareCampus is designed to answer each. | 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](https://squarecampus.com/compare/) 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 data model is shared Admissions, academics, finance, communication, and operations do not compete to define the truth. ## 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. [Book a demo](https://squarecampus.com/demo/) · [See rollout model](https://squarecampus.com/rollout/) --- Source: https://squarecampus.com/compare/ --- title: "Compare School Management Systems | SquareCampus" description: "Honest, side-by-side comparisons of SquareCampus with Entab CampusCare, Fedena, Teachmint, and other school ERPs — plus a framework for evaluating any school management system for India." canonical: https://squarecampus.com/compare/ describedby: https://squarecampus.com/llms.txt --- Compare # Evaluating school management systems? Start here. Honest, side-by-side comparisons of SquareCampus with the school ERPs you’re likely weighing — including where each alternative is the better fit — plus a framework for evaluating any of them. [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/school-management-system/) Head to head ## SquareCampus compared Entab CampusCare alternative ## [SquareCampus vs Entab](https://squarecampus.com/compare/squarecampus-vs-entab-campuscare/) Entab's CampusCare is one of India's most established school ERPs, in use across thousands of schools. If you're evaluating it against SquareCampus, here's the honest breakdown — including where Entab may be the better call. Read the comparison Fedena alternative ## [SquareCampus vs Fedena](https://squarecampus.com/compare/squarecampus-vs-fedena/) Fedena is a widely used, plugin-extensible school ERP with an open-source core. The real choice between Fedena and SquareCampus is about who runs the system — you, or us. Here's the honest comparison. Read the comparison Teachmint alternative ## [SquareCampus vs Teachmint](https://squarecampus.com/compare/squarecampus-vs-teachmint/) Teachmint built its name on teaching and content, then added ERP through acquisition. SquareCampus starts from operations. If your priority is running the institution — not just the classroom — here's the honest comparison. Read the comparison Evaluation framework ## Six questions to ask any school ERP vendor Whether or not SquareCampus makes your shortlist, these are the questions that separate a real platform from a demo that falls apart in production. ## Is it one system or many modules? Ask whether every module writes to the same record, or whether integrations keep separate products in sync. Sync gaps are where data drift and reconciliation work come from. ## Can you verify the infrastructure? Ask for the hosting region, the uptime SLA, and the audit posture — in writing. A vendor that publishes these is easier to trust than one that answers 'it's secure.' ## Is the pricing transparent? Ask what's included versus billed separately: mobile apps, each module, support, training. One institutional licence with the standard apps included and the separately scoped lines stated up front is easier to budget than per-module upsells. ## Who runs and secures it? Self-hosted means your team owns hosting, security, and upgrades. Managed means the vendor does. Decide which your institution actually has the capacity for. ## What does the intelligence layer actually do? Ask whether 'AI' means a governed layer that respects roles and logs every query, or a chatbot bolted onto reports. Governance is what makes it safe for a school. ## How long, really, to go live? Ask for a week-by-week rollout plan with migration, training, and a parallel run — not a vague 'a few months.' A concrete plan is a sign the vendor has done it before. Skip the spreadsheet ## Bring your shortlist. We’ll map SquareCampus against it, honestly. [Book a demo](https://squarecampus.com/demo/) · [Why SquareCampus](https://squarecampus.com/why-squarecampus/) --- Source: https://squarecampus.com/compare/squarecampus-vs-entab-campuscare/ --- title: "SquareCampus vs Entab CampusCare — School ERP Comparison" description: "SquareCampus vs Entab CampusCare for Indian schools: architecture, AI, pricing transparency, deployment, and where each fits. An honest alternative guide." canonical: https://squarecampus.com/compare/squarecampus-vs-entab-campuscare/ describedby: https://squarecampus.com/llms.txt --- [Compare](https://squarecampus.com/compare/) · Entab CampusCare alternative # SquareCampus vs Entab CampusCare Entab's CampusCare is one of India's most established school ERPs, in use across thousands of schools. If you're evaluating it against SquareCampus, here's the honest breakdown — including where Entab may be the better call. [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/school-management-system/) The honest version ## What Entab is genuinely good at A comparison you can trust starts by being fair about the alternative. A long track record and a large installed base across Indian schools. A broad, mature module suite — admissions, biometric attendance, exams, fees, and transport with GPS. Established parent, teacher, and management apps that schools already know. Side by side ## SquareCampus vs Entab CampusCare, by dimension | Dimension | SquareCampus | Entab CampusCare | | --- | --- | --- | | Architecture | One unified institutional data model — every module reads and writes the same record. | Established cloud ERP with a suite of modules for admissions, attendance, exams, fees, and transport. | | Intelligence layer | AEGIS — governed, role-scoped answers and exception detection with audit trails. | Reporting and analytics dashboards. | | Pricing | Model published: annual licence on student-volume bands, modules and standard apps included; figures by written proposal after discovery. | Not publicly listed; quote on request. | | Infrastructure transparency | Region and residency posture published; documentation shared in writing during evaluation. | Available on request. | | Deployment | Managed cloud (Microsoft Azure, India) by default; Enterprise private deployment on AWS, a private cloud or on premises as a scoped service. | Cloud (SaaS). | | Data residency | India — Microsoft Azure regions in India; documentation on request. | India-based (per vendor). | Where SquareCampus is different ## The differences that actually matter ## One unified institutional data model, not stitched modules Every SquareCampus module reads and writes the same institutional record. An admission confirmed flows into academics, fees, and communication automatically — no connectors to maintain between separate products. ## AEGIS — governed intelligence, not a bolt-on chatbot AEGIS answers operational questions inside the same RBAC scopes and audit trails as the rest of the platform. Leadership asks; the system answers from live records, and every query is logged. ## Infrastructure questions answered in writing We name our cloud and region (Microsoft Azure in India) on the infrastructure page and answer infrastructure questionnaires in writing during evaluation. Ask any vendor for the same detail and compare the answers. ## A published licensing model Like most vendors, we issue figures after scoping — but the model is published up front: one annual institutional licence on student-volume bands with the platform's modules and the standard parent and staff apps included, no per-module upsells and no hidden 'parent app' fees. Implementation and support are included; custom integrations are scoped as their own lines. Which one fits you ## An honest recommendation Choose Entab when - You want a long-established vendor with a very large installed base. - Your evaluation team is comfortable with quote-only, non-public pricing. - Your current processes are already built around CampusCare's specific workflows. Choose SquareCampus when - You want one connected system instead of a suite of modules to keep in sync. - You want a governed AI layer (AEGIS) and an infrastructure posture answered in writing. - You want a published licensing model with the standard mobile apps included, separately scoped lines stated up front, and a guided go-live. FAQ ## SquareCampus and Entab, answered ### Is SquareCampus a good Entab CampusCare alternative? SquareCampus is a modern School OS built on one unified institutional data model with a governed intelligence layer (AEGIS), a published infrastructure posture, and a published licensing model on student-volume bands. Schools evaluating CampusCare often shortlist SquareCampus when they want a single connected system and an infrastructure posture they can question in writing. We support guided migration from existing school ERPs. ### Can we migrate from Entab CampusCare to SquareCampus? Yes. We provide guided migration of student records, fee history, attendance, academic records, and staff data, with a parallel run before go-live. Anything the old system cannot supply is flagged before go-live, not discovered after. See it on your own numbers ## The fastest way to compare is to see SquareCampus run your workflows. [Book a demo](https://squarecampus.com/demo/) · [See all comparisons](https://squarecampus.com/compare/) Comparison based on publicly available information as of July 2026. [Entab CampusCare](https://www.entab.in/) and other names are trademarks of their respective owners, used here for identification and comparison only. Details change — verify current features and pricing with each vendor. Spotted something out of date? Email contact@squarecampus.com and we’ll correct it. --- Source: https://squarecampus.com/compare/squarecampus-vs-fedena/ --- title: "SquareCampus vs Fedena — School Management Software Comparison" description: "SquareCampus vs Fedena: managed School OS versus open-source, plugin-based ERP. Architecture, AI, deployment and pricing compared honestly for schools." canonical: https://squarecampus.com/compare/squarecampus-vs-fedena/ describedby: https://squarecampus.com/llms.txt --- [Compare](https://squarecampus.com/compare/) · Fedena alternative # SquareCampus vs Fedena Fedena is a widely used, plugin-extensible school ERP with an open-source core. The real choice between Fedena and SquareCampus is about who runs the system — you, or us. Here's the honest comparison. [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/school-management-system/) The honest version ## What Fedena is genuinely good at A comparison you can trust starts by being fair about the alternative. An open-source core (Apache 2.0) you can self-host and modify. A large global install base and a wide catalogue of modules and plugins. A free starting point, with Fedena Pro for paid features and support. Side by side ## SquareCampus vs Fedena, by dimension | Dimension | SquareCampus | Fedena | | --- | --- | --- | | Architecture | One unified institutional data model — modules are one system, not separately configured plugins. | Modular, plugin-extensible core; capabilities added via plugins and integrations. | | Intelligence layer | AEGIS — governed, role-scoped answers and exception detection with audit trails. | Reporting dashboards and configurable dashlets. | | Who runs it | Fully managed by us (or your cloud with our playbooks). | Self-hosted (open-source) means your team owns hosting, security, and upgrades. | | Pricing | Model published: annual licence on student-volume bands, modules and standard apps included; figures by proposal. | Free open-source core; Fedena Pro is paid / plan-based. | | Deployment | Managed cloud (Microsoft Azure, India) by default; Enterprise private deployment on AWS, a private cloud or on premises as a scoped service. | Cloud or self-hosted. | | Infrastructure transparency | Region and residency posture published — because we run it. | Depends on your own hosting when self-hosted. | Where SquareCampus is different ## The differences that actually matter ## One unified institutional data model, not stitched modules Every SquareCampus module reads and writes the same institutional record. An admission confirmed flows into academics, fees, and communication automatically — no connectors to maintain between separate products. ## AEGIS — governed intelligence, not a bolt-on chatbot AEGIS answers operational questions inside the same RBAC scopes and audit trails as the rest of the platform. Leadership asks; the system answers from live records, and every query is logged. ## Infrastructure questions answered in writing We name our cloud and region (Microsoft Azure in India) on the infrastructure page and answer infrastructure questionnaires in writing during evaluation. Ask any vendor for the same detail and compare the answers. ## A published licensing model Like most vendors, we issue figures after scoping — but the model is published up front: one annual institutional licence on student-volume bands with the platform's modules and the standard parent and staff apps included, no per-module upsells and no hidden 'parent app' fees. Implementation and support are included; custom integrations are scoped as their own lines. Which one fits you ## An honest recommendation Choose Fedena when - You have in-house IT and want open-source control or full self-hosting. - You want a free starting point and are comfortable owning maintenance and security. - You need to fork and customize the source code for a very specific workflow. Choose SquareCampus when - You want the operating system run for you, with security and upgrades handled. - You want a governed AI layer and one connected model instead of assembling plugins. - You want predictable pricing and a fast, guided go-live rather than a self-managed build. FAQ ## SquareCampus and Fedena, answered ### Is SquareCampus a good Fedena alternative? If you want a fully managed School OS rather than a self-hosted, plugin-based system, SquareCampus is a strong Fedena alternative. You get one unified institutional data model, the AEGIS intelligence layer, managed infrastructure, and included mobile apps — without owning hosting, security, and upgrades yourself. ### Does SquareCampus offer self-hosting like Fedena's open source? No. SquareCampus is delivered as a managed platform on our Microsoft Azure infrastructure in India. Institutions that need their own boundary can scope an Enterprise private deployment on AWS, in a private cloud or on premises. Running it in the institution's own cloud account (BYOC) is not offered today, and there is no open-source self-hosting. See it on your own numbers ## The fastest way to compare is to see SquareCampus run your workflows. [Book a demo](https://squarecampus.com/demo/) · [See all comparisons](https://squarecampus.com/compare/) Comparison based on publicly available information as of July 2026. [Fedena](https://fedena.com/) and other names are trademarks of their respective owners, used here for identification and comparison only. Details change — verify current features and pricing with each vendor. Spotted something out of date? Email contact@squarecampus.com and we’ll correct it. --- Source: https://squarecampus.com/compare/squarecampus-vs-teachmint/ --- title: "SquareCampus vs Teachmint — School Platform Comparison" description: "SquareCampus vs Teachmint: a governed School OS versus an LMS-and-content-first platform. Architecture, AI and operations compared honestly for Indian schools." canonical: https://squarecampus.com/compare/squarecampus-vs-teachmint/ describedby: https://squarecampus.com/llms.txt --- [Compare](https://squarecampus.com/compare/) · Teachmint alternative # SquareCampus vs Teachmint Teachmint built its name on teaching and content, then added ERP through acquisition. SquareCampus starts from operations. If your priority is running the institution — not just the classroom — here's the honest comparison. [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/school-management-system/) The honest version ## What Teachmint is genuinely good at A comparison you can trust starts by being fair about the alternative. Strong teaching, LMS, and content tooling, including a large question bank. A mobile-first experience and wide language coverage. A large global user base across schools and countries. Side by side ## SquareCampus vs Teachmint, by dimension | Dimension | SquareCampus | Teachmint | | --- | --- | --- | | Starting point | Operations first — a School OS for admissions, fees, attendance, and compliance. | Teaching and content first — an integrated platform combining LMS, content, and ERP. | | Architecture | One unified institutional data model built for operations. | Integrated platform; ERP capabilities strengthened via the MyClassCampus acquisition. | | Intelligence layer | AEGIS — governed, role-scoped operational answers with audit trails. | Analytics and reporting across teaching and administration. | | Pricing | Model published: annual licence on student-volume bands, modules and standard apps included; figures by written proposal after discovery. | Quote-based. | | Infrastructure transparency | Region and residency posture published; documentation shared in writing during evaluation. | Available on request. | | Deployment | Managed cloud (Microsoft Azure, India) by default; Enterprise private deployment on AWS, a private cloud or on premises as a scoped service. | Cloud (SaaS). | Where SquareCampus is different ## The differences that actually matter ## One unified institutional data model, not stitched modules Every SquareCampus module reads and writes the same institutional record. An admission confirmed flows into academics, fees, and communication automatically — no connectors to maintain between separate products. ## AEGIS — governed intelligence, not a bolt-on chatbot AEGIS answers operational questions inside the same RBAC scopes and audit trails as the rest of the platform. Leadership asks; the system answers from live records, and every query is logged. ## Infrastructure questions answered in writing We name our cloud and region (Microsoft Azure in India) on the infrastructure page and answer infrastructure questionnaires in writing during evaluation. Ask any vendor for the same detail and compare the answers. ## A published licensing model Like most vendors, we issue figures after scoping — but the model is published up front: one annual institutional licence on student-volume bands with the platform's modules and the standard parent and staff apps included, no per-module upsells and no hidden 'parent app' fees. Implementation and support are included; custom integrations are scoped as their own lines. Which one fits you ## An honest recommendation Choose Teachmint when - Your top priority is classroom teaching, LMS, and ready-made content. - You want a mobile-first learning experience more than admissions, fees and multi-campus administration. - You're primarily digitizing teaching rather than back-office operations. Choose SquareCampus when - Your priority is running the institution: admissions, fees, attendance, compliance, multi-campus. - You want a governed operational AI layer and one connected operating model. - You want an infrastructure posture answered in writing and predictable, all-inclusive pricing, with operations built as the core. FAQ ## SquareCampus and Teachmint, answered ### Is SquareCampus a good Teachmint alternative? For institutions that want admissions, fees, attendance, compliance and multi-campus control on one record, SquareCampus is a strong Teachmint alternative because operations are the core of the product, not an addition. Teachmint remains a strong choice when teaching, LMS, and content are the primary need. ### Does SquareCampus handle teaching and academics too? Yes. SquareCampus covers attendance, timetables, grading, assessments, and academic records as part of the connected operating model. Where a school also needs a dedicated LMS, SquareCampus can integrate with it over APIs. See it on your own numbers ## The fastest way to compare is to see SquareCampus run your workflows. [Book a demo](https://squarecampus.com/demo/) · [See all comparisons](https://squarecampus.com/compare/) Comparison based on publicly available information as of July 2026. [Teachmint](https://www.teachmint.com/) and other names are trademarks of their respective owners, used here for identification and comparison only. Details change — verify current features and pricing with each vendor. Spotted something out of date? Email contact@squarecampus.com and we’ll correct it. --- Source: https://squarecampus.com/platform/ --- title: "School Management Platform | SquareCampus" description: "The SquareCampus school management platform: admissions, attendance, fees, exams and parent communication as connected workflows on one record, and the four layers underneath." canonical: https://squarecampus.com/platform/ describedby: https://squarecampus.com/llms.txt --- 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. [Book a demo](https://squarecampus.com/demo/) · [See rollout](https://squarecampus.com/rollout/) Daily operations Synthetic data ![The SquareCampus daily operations console: fee follow-up drifting past its reminder window with an owner assigned, admissions waiting on document verification, attendance below the policy threshold escalated, and a concession request awaiting trust sign-off.](https://squarecampus.com/motion/platform-operations-screen-light.8c2bd86e.webp) Teacher workspace Synthetic data ![A teacher marking the morning register on a phone, with a third absence in the week raised as an exception that routes to a named owner.](https://squarecampus.com/motion/phone-attendance-screen-light.06b6a5d1.webp) Shared data model Every surface reads and writes the same institutional record. 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. ### 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. [Admission management](https://squarecampus.com/school-admission-management-software/) ### 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. [Attendance management](https://squarecampus.com/school-attendance-management-system/) ### 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. [Fee management](https://squarecampus.com/fee-management-software-for-schools/) ### 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. [Exam and results management](https://squarecampus.com/school-exam-management-software/) ### 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. [Parent communication](https://squarecampus.com/parent-communication-app-for-schools/) ### 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. [Multi-campus management](https://squarecampus.com/multi-campus-school-management-software/) 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. ### 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 ### 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 ### 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 ### 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. Admissions, academics, finance, communication and operations act on one identity, data and workflow core, so a change made once needs no export to reach the rest. ## 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. [Meet AEGIS](https://squarecampus.com/aegis/) Role-aware suggestions Exception detection from current records Institution-safe answers inside the same guardrails --- Source: https://squarecampus.com/aegis/ --- title: "AEGIS: AI for School Operations | SquareCampus" description: "AEGIS is the intelligence inside SquareCampus, not a chatbot on an ERP: read-only, plain-language answers from the institution's own records, in role scope, with an audit trail on every question." canonical: https://squarecampus.com/aegis/ describedby: https://squarecampus.com/llms.txt --- Adaptive Enterprise Governance & Intelligence System # Ask AEGIS. Don’t chase reports. The AI inside SquareCampus, not a chatbot bolted onto an ERP. Ask in plain language; it answers from your school’s records, inside your permissions, on the audit trail. It suggests — people decide and act. [Book a demo](https://squarecampus.com/demo/) · [Explore the platform](https://squarecampus.com/platform/) Inside SquareCampus Answers in role scope Read-only What AEGIS does, and does not do ## Answers and suggestions. People decide and act. AEGIS is the AI assistant inside SquareCampus. School leaders ask questions in plain language and get answers from their own school records, limited to what their role can already see. It suggests follow-ups; it does not change anything. - Read-only — AEGIS answers questions, it does not act on the institution's behalf - RBAC-scoped — a person only ever sees what their role already permits - Source-grounded — every answer points back to the records it came from - Auditable — questions and answers are recorded like any other institutional action - Human-controlled — decisions remain with the people accountable for them The examples on this page are illustrative and use synthetic data. Your written proposal confirms which modules, apps, languages and integrations you get. Three example questions ## What an answer is drawn from, and where AEGIS stops How AEGIS is designed to answer three everyday questions. Each answer stays inside the asker's permissions, shows its sources and when the data was last updated, and ends with a suggestion rather than an action. Principal ### “Which Class 8 sections had attendance below 85% this week?” **Answer scope** Attendance records for the principal's own campus only. **Sources and as-of time** Each section in the answer links to the attendance entries behind it, with the time the data was last updated. **Limit** It can suggest raising the pattern with class teachers. It does not message anyone. Finance & accounts ### “How much of this term's fees is overdue by more than 30 days, and in which classes?” **Answer scope** The fee ledger for the campuses the finance role is permitted to see. **Sources and as-of time** Totals link to the invoices and receipts they are built from, as of the last posted payment. **Limit** It does not send reminders or change any fee record; a person does that in the fees workflow. Trust leadership ### “Which campuses have approvals waiting longer than a week?” **Answer scope** Approval records across the campuses under the trust administrator's role. **Sources and as-of time** Each item names the approval, its owner and how long it has waited, with an as-of time. **Limit** It cannot approve, reassign or escalate. It shows who owns each item. Governance first ## Intelligence that strengthens control instead of leaking it AEGIS is designed governance-first: the permission check happens before an answer exists, not after it. Scope is applied before an answer exists. Records outside the asker's tenant and role are refused rather than summarised, and the query itself becomes an audit entry. ## Role-based, always AEGIS answers within the same RBAC scopes as the rest of SquareCampus. A principal sees their campus; a trust admin sees the trust. No side doors. ## Tenant boundaries respected Institutional data stays inside institutional boundaries. AEGIS reads your live operating records — it doesn't pool them into someone else's model. ## Auditable by default Every question and answer is recorded on the audit trail. Suggested follow-ups are for people to act on through normal workflows — AEGIS never carries them out itself. ## Decision support, not noise AEGIS is not a generic chatbot. It is a controlled intelligence layer that helps management ask sharper questions and act with operational clarity. Context is the moat ## AEGIS works because the operating system underneath is connected AEGIS is designed to work from the records your institution already runs on in SquareCampus — who may see what, timelines, fee state and communication history — rather than guessing. Before and after ## The report-chasing era is over If your current ERP's answer to every leadership question is 'we'll prepare a report', the comparison below will feel familiar. Legacy ERP reporting Ask the office to prepare a report, wait days, get a spreadsheet that's already stale. With AEGIS Ask AEGIS in plain language and get an answer from the institution's own records. Legacy ERP reporting Exceptions surface at term end, when the damage is already done. With AEGIS Attendance, fee, academic, and communication exceptions are flagged against thresholds the institution sets. Legacy ERP reporting Every export is another uncontrolled copy of student data floating around. With AEGIS Answers stay inside role-based permissions, tenant boundaries, and audit trails. Legacy ERP reporting Leadership sees each campus through a different lens, stitched by hand. With AEGIS One governed, trust-level view across campuses — with campus-level accountability intact. What AEGIS helps with ## From data to defensible decisions Identify attendance, fee, academic, and communication exceptions early. Give leadership a trust-level view across campuses without flattening accountability. Support principals and administrators with contextual operational insight. Preserve governance through RBAC, audit trails, and controlled access. Turn school data into actionable intelligence without compromising ownership or privacy. Help management ask sharper questions and act with better operational clarity. See it on your own numbers ## Bring one question you currently wait days to answer. In a guided demo we’ll walk through how AEGIS is designed to answer it, what it would draw on in your records, and where its limits are. [Book a demo](https://squarecampus.com/demo/) · [Review the trust posture](https://squarecampus.com/security/) --- Source: https://squarecampus.com/services/ --- title: "Integration, Data & Deployment Services | SquareCampus" description: "SquareCampus services: scoped integrations with the school tools you keep, ETL/ELT pipelines into one custom dashboard, and Enterprise private deployment — each assessed and confirmed in writing." canonical: https://squarecampus.com/services/ describedby: https://squarecampus.com/llms.txt --- Integration, data & deployment services # Your existing tools don’t have to be dead ends. Beyond the School OS, we scope connections to the systems you already run, unify their data into one dashboard, and deploy on our managed cloud or a dedicated Enterprise environment. [Book a demo](https://squarecampus.com/demo/) · [Explore the platform](https://squarecampus.com/platform/) Systems integration ## Connect the fragmented tools you already have Replacing everything on day one isn't always realistic. Where a system offers a documented API, we assess and scope a bridge so it stops being an island. ## Scoped connectors Where a tool offers a documented API — a biometric device, payment gateway, LMS, accounting package or government portal — we assess whether and how it can connect, and scope the bridge before anything is built. ## Agreed direction and frequency Each integration states which system owns which record, which way data moves, how often, and how errors are validated and retried — agreed in writing rather than assumed. ## Built as workflows Integrations are designed around your operating logic — for example, an admission confirmed in one system starting fee setup in another — where both systems allow it. ## Development APIs for your own apps Institutions that want their own portal, frontend or mobile apps can scope access to SquareCampus development APIs. Access follows the same role-based permissions and audit trail, and is granted after a compliance review. In plain words: if your fingerprint machines, fee gateway or accounts software offer an API, we can scope a bridge between them. Each one is assessed and quoted on its own. Integration status SquareCampus does not publish a catalogue of pre-built connectors. Connecting another system is scoped work: we assess each tool during discovery, and what connects, in which direction, how often and at what cost is confirmed in writing before any build. **Sign-in By plan** SquareCampus-managed credentials in every plan; Microsoft Entra ID single sign-on from Pro, subject to technical onboarding. **Payment gateway, SMS and WhatsApp Scoped service** Payments run through your institution's own gateway account, and SquareCampus never handles the money. SMS and WhatsApp come with a monthly allowance; usage beyond it is prepaid. **Accounting software, biometric devices, LMS and government portals Scoped service** Assessed tool by tool. There is no pre-built connector; each one is scoped, quoted and confirmed in writing. **Development APIs for the institution's own apps Scoped service** Scoped per institution and granted after a compliance review, inside the same role-based permissions and audit trail. Before any integration is built - The other system must offer a documented API or a data export the institution is licensed to use. - Vendor access, vendor-side charges and the vendor's own limits remain the institution's. - Sync direction, frequency, error handling and ownership of each record are agreed per integration. Data engineering ## ETL/ELT pipelines and one dashboard that answers to leadership Scattered systems mean scattered truth. We consolidate your data into one governed model and one custom dashboard your leadership actually uses. ## ETL / ELT pipelines We extract from your fragmented sources — legacy ERPs, spreadsheets, standalone apps — transform them into one consistent model, and keep them flowing on schedule. ## One custom dashboard Leadership gets a single dashboard built around your institution's questions: collections, attendance, academics, operations — not a generic BI template. ## Your servers or our cloud Pipelines and the dashboard run on our Microsoft Azure setup in India or on infrastructure you already own, as agreed in the scope. In plain words: the numbers from the tools in scope, in one screen your principal can read with morning tea. Deployment options ## SquareCampus runs where your governance says it should Managed cloud is the default. A dedicated Enterprise environment is a scoped service, with the same role-based access and audit design. Default ## Managed cloud SquareCampus on our Microsoft Azure infrastructure in India, operated and maintained by us. Every plan starts here. Scoped service ## Enterprise private deployment A dedicated SquareCampus environment on AWS, in a private cloud or on premises, for institutions with strict segregation requirements. Enterprise only; scope, responsibilities and charges are agreed in writing. Not offered today ## Your own cloud account (BYOC) Running SquareCampus inside the institution's own cloud account is not offered today. If your governance requires it, raise it during scoping. In plain words: our cloud by default, or a dedicated Enterprise environment on AWS, a private cloud or your own premises. Same role-based access and audit design in every model Hosted on Microsoft Azure in India by default Start with an integration audit ## Bring your current tool list. We’ll map what connects. In one session we identify which systems can integrate, what the pipeline looks like, and which deployment model fits your institution’s governance. [Book a demo](https://squarecampus.com/demo/) · [Email the services team](mailto:contact@squarecampus.com?subject=Integration%20%26%20Data%20Services) --- Source: https://squarecampus.com/rollout/ --- title: "School ERP Implementation & Migration | SquareCampus" description: "How a SquareCampus implementation runs: what the school provides, what we deliver and when each stage is done — from blueprint and data migration to parallel runs and go-live." canonical: https://squarecampus.com/rollout/ describedby: https://squarecampus.com/llms.txt --- Rollout model # Go live like an institution, not a software experiment. Schools and colleges do not have the luxury of chaotic launches. SquareCampus rollout is designed around migration discipline, role-based training, parallel validation, and predictable go-live support. [Book a demo](https://squarecampus.com/demo/) · [See the platform](https://squarecampus.com/platform/) Migration is treated as an operating exercise, not only a data import. Training is role-specific so the platform lands in real institutional behavior. Parallel runs reduce risk for finance, attendance, communication, and reporting. Success is measured after go-live, not only at handover. Parallel validation Synthetic data ![Parallel validation during a rollout: the collection register, the daily attendance register and guardian circular delivery reconciled against the institution's existing system, with one admissions discrepancy under review and the agreed success measure tracked.](https://squarecampus.com/motion/rollout-parallel-run-screen-light.fe49f319.webp) Two paths, one product ## Coexistence first. Replacement only when the institution chooses it. Nothing has to be switched off for a SquareCampus deployment to begin, and nothing is replaced on a vendor’s schedule. Path one · Coexistence ## A bounded deployment runs alongside the current stack. One campus, or one workflow bundle. The existing ERP, LMS, payment portal and identity provider stay in place and stay authoritative. SquareCampus governs the workflow that runs across them — routing exceptions, assigning ownership, recording what was decided — while critical numbers are validated in parallel. Path two · Consolidation ## A later rollout may replace selected fragmented tools. When the institution decides to — after the evidence exists, and workflow by workflow. Consolidation is an outcome an institution can choose, never a precondition of starting. There is no compulsory rip-and-replace at any point. Six stages ## What each stage needs, delivers and signs off A stage is complete only when its criteria are met, so nothing moves forward on a date alone. Timelines are agreed in writing during scoping. Stage 1 ### Institution blueprint **The school provides** Current systems, campus structure, roles, approval paths and the academic calendar. **SquareCampus delivers** A written blueprint of the workflows in scope, their owners and the go-live sequence. **Done when** The institution signs off the blueprint and the sequence. Stage 2 ### Data migration **The school provides** Exports from current systems, and a named person to answer questions about the data. **SquareCampus delivers** Mapping, cleaning and trial imports, with a list of issues for the institution to resolve. **Done when** Trial imports reconcile against the checks agreed in the blueprint — for example student counts and dues totals — and the data owner signs off. Stage 3 ### Role-based training **The school provides** Staff time by role, scheduled around the calendar. **SquareCampus delivers** Training on the workflows each role will actually use. **Done when** Each role has completed its sessions and can carry out its core tasks. Stage 4 ### Parallel validation **The school provides** The current system kept running for the workflows in scope, and people to compare results. **SquareCampus delivers** Side-by-side runs and a list of every difference with its cause. **Done when** Finance and academic owners agree the results match on the agreed checks. Stage 5 ### Go-live under guardrails **The school provides** Approval of the go-live date, and escalation contacts on each side. **SquareCampus delivers** A staged launch with named counterparts and an agreed escalation path. **Done when** The workflows in scope run in SquareCampus, and the old system is retired or kept read-only, as agreed. Stage 6 ### Adoption follow-through **The school provides** Feedback from each role after launch. **SquareCampus delivers** Follow-up where teams slip back into spreadsheets and side channels. **Done when** The success measures agreed at the start are reviewed together. Migration dependencies Migration moves as fast as your data and your current vendor’s exports allow. It is included from Pro and quoted on Starter. Anything the old system cannot supply is flagged before go-live, and the parallel run ends when the checks pass, not on a date. Operator confidence ## What a switch has to protect Admissions, fees and results cannot pause for a system change, so the rollout is sequenced around them. What the rollout must protect Admission teams cannot lose pipeline visibility during switch-over. Finance teams need confidence around dues, receipts, and approval trails. Academic leaders need continuity across attendance, assessments, and communication. Institution leadership needs a single owner for coordination and escalation. ## Who owns the rollout? SquareCampus runs a guided process with named counterparts so institutions are not left coordinating vendors and spreadsheets alone. ## How do we avoid disruption? By sequencing migration, training, and dry runs around real calendar pressure points such as admissions, fee cycles, and exam windows. ## What about multiple campuses? The structure is designed to support institution-wide policy, branch-level variation, and phased launches without creating separate systems. Next step ## Bring your current patchwork and launch constraints to the table. We can map your institution’s current operating stack, outline a rollout path, and show where SquareCampus would sit alongside what you already run — and where it would eventually replace complexity, without destabilizing the term in motion. [Book a demo](https://squarecampus.com/demo/) · [Why SquareCampus](https://squarecampus.com/why-squarecampus/) --- Source: https://squarecampus.com/ecosystem/ --- title: "School Apps & Integrations | SquareCampus" description: "The SquareCampus ecosystem: admin console, teacher workspace, and parent and student apps on one record, with integrations to the tools you keep scoped and confirmed in writing." canonical: https://squarecampus.com/ecosystem/ describedby: https://squarecampus.com/llms.txt --- Apps & Integrations # An app for every role, on one school record. Parents, students, teachers, the office and leadership each get the screens their work needs. Everything they do lands on the same record, and the tools you keep can be connected as scoped work. [Book a demo](https://squarecampus.com/demo/) What connects One institutional record Synthetic data ![One institutional record acted on from every surface: a guardian acknowledging a fee reminder, a teacher marking a register, finance applying an approved concession, transport notifying a route change, and the trust view already current without an export.](https://squarecampus.com/motion/ecosystem-surfaces-screen-light.4150b45f.webp) Guardian app Synthetic data ![A guardian's view of a term fee on a phone: tuition and transport due, an approved concession recorded, and the previous term's receipt available.](https://squarecampus.com/motion/phone-fees-screen-light.e995233b.webp) By audience ## What each person does, and where The standard parent and staff mobile apps are included in the licence; staff and leadership also work on the web. ![Parents, teachers, principals, finance teams and trustees connected to one institutional record, each seeing the part their role owns.](https://squarecampus.com/motion/ecosystem-core-surfaces-light.6d17cfe4.webp) Mobile app ## Parents - Attendance and absence alerts - Fee dues, payments and receipts - Circulars and acknowledgements - Progress and results Mobile app ## Students - Timetable and the day's classes - Assignments due - Notices - Results Mobile app and web ## Teachers and staff - Class and period attendance - Marks entry and remarks - Messages to parents - Their own queue of follow-ups Web ## Administrators and office - Admissions and student records - Fee plans, concessions and reconciliation - Campus setup, roles and approvals - Circulars and communication logs Web ## Principals, trustees and leadership - Current position across campuses - Open exceptions and who owns them - Approvals waiting on them - Questions to AEGIS, inside their permissions App-store availability, supported device versions and the modules in each app for your institution are confirmed in writing in your proposal. White-labelled apps under your own branding are a separately scoped option. Integrations ## What connects, and on what terms SquareCampus does not publish a catalogue of pre-built connectors. Connecting another system is scoped work: we assess each tool during discovery, and what connects, in which direction, how often and at what cost is confirmed in writing before any build. **Sign-in By plan** SquareCampus-managed credentials in every plan; Microsoft Entra ID single sign-on from Pro, subject to technical onboarding. **Payment gateway, SMS and WhatsApp Scoped service** Payments run through your institution's own gateway account, and SquareCampus never handles the money. SMS and WhatsApp come with a monthly allowance; usage beyond it is prepaid. **Accounting software, biometric devices, LMS and government portals Scoped service** Assessed tool by tool. There is no pre-built connector; each one is scoped, quoted and confirmed in writing. **Development APIs for the institution's own apps Scoped service** Scoped per institution and granted after a compliance review, inside the same role-based permissions and audit trail. Prerequisites, pipelines into one dashboard and deployment options are set out on [data and integration services](https://squarecampus.com/services/#integration-scope). Next step ## See the apps for the roles in your institution. Tell us which roles and tools matter most. We will show the relevant screens and map which of your current tools could connect. [Book a demo](https://squarecampus.com/demo/) · [Security](https://squarecampus.com/security/) --- Source: https://squarecampus.com/pricing/ --- title: "SquareCampus Pricing | School OS Plans for Schools and Trusts" description: "Explore Starter, Pro and Enterprise plans for SquareCampus. Every plan includes the generally available core platform and multi-campus operations. Review optional enhancements and the selected 90-day complimentary launch pilot." canonical: https://squarecampus.com/pricing/ describedby: https://squarecampus.com/llms.txt --- Commercial model # Pricing that scales with the institution — not with software complexity. One annual institutional licence, calculated on student-volume bands and shaped by the plan you choose. The three plans are below; figures follow in a written proposal after a short discovery. [Request a proposal](https://squarecampus.com/contact/) Compare the plans No hidden module wall. No compulsory rip-and-replace. Scope, ownership and success measures agreed before deployment. How pricing works Student numbers set the scale. The plan sets how much operational and governance control you get. The two are decided separately. **Licence** Annual, institutional **Calculated on** Student-volume bands **Shaped by** The plan chosen and the institution's complexity Plan architecture ## Three levels of institutional command, not three feature bundles. Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Plans differ in agreed messaging and AI allowances, analytics depth, workflow sophistication, identity and integration options, customisation and advanced governance. Standard implementation and support remain included in every plan; any custom SLA is separately agreed. Specific inclusions and consumption limits are documented in the proposal. ### Starter The complete generally available core platform for institutions operating one campus or many. Depth 1 of 3 Best for: Schools replacing fragmented spreadsheets and disconnected tools ### Pro Operational command for institutions that need deeper visibility and accountability. Depth 2 of 3 Best for: Growing schools taking on more operational complexity ### Enterprise Selected by governance need Institutional governance, cross-campus command and advanced controls for larger or more complex institutions. Depth 3 of 3 Best for: Educational trusts and multi-campus groups Starter in detail The problem it solves Records, attendance, fees and results live in separate tools, so every question needs a person to reconcile an answer by hand. Best suited for - Schools replacing fragmented spreadsheets and disconnected tools - Institutions that need reliable core workflows before anything else - Institutions beginning on managed SquareCampus Cloud Deployment Managed SquareCampus Cloud, with implementation and support included. Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. [How retention works](https://legal.fairhelmsystems.com/squarecampus/data-retention/) Core platform and plan depth Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. - Complete generally available core platform - Multi-campus operations and campus-level administration - Role-aware operational workflows - Parent and staff mobile apps - Secure sign-in and role-based access - Audit history - Standard operational dashboards - Self-serve reports: saved views, charts and Excel, CSV or PDF export Scoped separately - Data migration and cleaning - Custom integrations - A custom SLA, such as 24×7 cover - Usage beyond the monthly allowance, prepaid What we need for a proposal [Request a Starter proposal](https://squarecampus.com/contact/) Pro in detail The problem it solves The core runs, but leadership still cannot see what is slipping, who owns it, or whether an exception was ever closed. Best suited for - Growing schools taking on more operational complexity - Institutions that need management dashboards and workflow governance - Institutions introducing cross-functional accountability Scoped separately - Custom integrations beyond the standard set - A custom SLA, such as 24×7 cover - Usage beyond the monthly allowance, prepaid What we need for a proposal Deployment Managed SquareCampus Cloud, with implementation and support included. Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. [How retention works](https://legal.fairhelmsystems.com/squarecampus/data-retention/) Core platform and plan depth Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. - Everything represented in Starter - Owner command views - Richer operational analytics - Advanced exception routing requirements - Workflow performance and escalation requirements - Expanded operational audit requirements - Separately quoted institutional single sign-on - Standard integration requirements confirmed during discovery - AEGIS access and allowances confirmed during scoping - Data migration from your current system #### Institutional single sign-on Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. - Optional, never mandatory - Institution's own Entra ID tenant - Customer MFA and Conditional Access apply - SquareCampus-governed authorisation The same separately quoted Entra SSO option can be requested on Starter. Supported sign-in methods are confirmed before activation; single sign-on does not replace SquareCampus authorisation. [Request a Pro proposal](https://squarecampus.com/contact/) Enterprise in detail The problem it solves Central policy and local accountability pull against each other, identity and audit requirements outgrow ordinary controls, and no single view reconciles what every campus is actually doing. Best suited for - Educational trusts and multi-campus groups - Church-run school chains - Institutions balancing central policy with local accountability - Standalone schools with governance, identity or audit requirements Scoped separately - Private-cloud or on-premises deployment - Custom integrations and engineering - A custom SLA, such as 24×7 cover - Usage beyond the monthly allowance, prepaid What we need for a proposal Deployment Managed cloud, private-cloud or on-premises eligibility, with full implementation and support included. Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. [How retention works](https://legal.fairhelmsystems.com/squarecampus/data-retention/) Core platform and plan depth Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. - Everything represented in Pro - Advanced trust-level governance requirements - Cross-campus command requirements - Sophisticated approval and exception ownership requirements - Advanced policy and audit requirements - Identity governance requirements, scoped during technical discovery - Deeper and custom integrations, scoped separately - Governed AEGIS access and allowances, subject to scoping - Advanced audit-export requirements; data portability in every plan - Data migration from your current system #### Identity governance Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. - Multi-campus and multi-directory requirements - Directory-group to role mappings - SSO enforcement policy - Lifecycle and identity audit controls Enterprise is not Pro with more modules. It is selected when governance, identity, audit or cross-campus requirements sit above what ordinary controls provide. Identity governance requirements are established during technical discovery and set out in the proposal. [Request an Enterprise proposal](https://squarecampus.com/contact/) ### At a glance SquareCampus plan comparison across operational scope, visibility, accountability, structure, integrations, intelligence, deployment and support. The licensing model is published; figures are issued in a written proposal after institutional discovery. | Dimension | Starter | Pro | Enterprise | | --- | --- | --- | --- | | Operational scope | Complete generally available core platform | Complete generally available core platform | Complete generally available core platform | | Leadership visibility | Standard operational dashboards | Owner command views and richer analytics | Advanced analytics and trust-level command requirements | | Accountability model | Role-based access and audit history | Enhanced routing and operational audit requirements, scoped | Advanced governance and policy requirements, scoped | | Institutional structure | Multi-campus operations with campus-level administration | Multi-campus operations with enhanced workflows | Multi-campus operations with advanced central governance | | Sign-in and identity | Optional Entra SSO, separately quoted | Optional Entra SSO, separately quoted | Identity governance: multi-directory, group-to-role mappings, enforcement policy, lifecycle (scoped) | | Integrations | Standard configuration | Standard integration requirements confirmed during discovery | Enterprise and custom integration requirements scoped | | Mobile apps | Parent and staff apps included | Parent and staff apps included | Parent and staff apps included | | AEGIS intelligence | Scope and additional usage assessed separately | Controlled access and allowances agreed in proposal | Governed access within an agreed allowance | | Baseline security | Tenant isolation, secure authentication, role-based access and essential auditability | Tenant isolation, secure authentication, role-based access and essential auditability | Tenant isolation, secure authentication, role-based access and essential auditability | | SMS, WhatsApp and email allowances | Inclusions and usage boundaries specified in proposal | Inclusions and usage boundaries specified in proposal | Inclusions and usage boundaries specified in proposal | | Institution-owned data and supported exports | Documented for every deployment | Documented for every deployment | Documented for every deployment | | Chosen because | The core needs to work as one system | Leadership needs visibility and accountability | Governance, identity or audit requirements — at any enrolment | | Deployment | Managed SquareCampus Cloud | Managed SquareCampus Cloud | Managed, private-cloud or on-premises eligibility | | Implementation and support | Standard onboarding and support | Implementation and support included, with best-effort data migration | Implementation and support included; a custom SLA is quoted separately | Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Advanced capability themes are indicative; availability, inclusions, limits and service levels are confirmed in the proposal and signed order form. Your plan does not determine your legal retention obligations. Storage and archive arrangements are specified in your proposal and order form. [How retention works](https://legal.fairhelmsystems.com/squarecampus/data-retention/) How the licence is composed ## Four inputs, agreed openly, before any number is issued. The annual platform licence is not a module count. It is the sum of institutional scale, the plan selected (how much operational and governance control it includes), the complexity of the institution and how the platform is delivered. Proposal inputs Annual platform licence One annual institutional licence, assessed against these four inputs during scoping. Migration, integrations and other separately quoted services remain distinct lines. **Scale** Active enrolled students **Depth** Starter, Pro or Enterprise **Complexity** Campuses, workflows, roles and governance **Delivery** Deployment, integrations and support ### Scale Active enrolled students Student volume sets the platform baseline. Larger enrolments sit in progressively better volume bands, so the marginal rate reduces as the institution grows. ### Depth Starter, Pro or Enterprise The plan reflects how much operational and governance control the institution needs — from connected core operations through to trust-level command. ### Complexity Campuses, workflows, roles and governance Multiple campuses, deeper approval chains and wider role structures change the shape of the rollout and the shape of the commercial. ### Delivery Deployment, integrations and support The deployment profile, integrations and support model are set out explicitly rather than folded into an unstated blended rate. Migration is included from Pro. What Enterprise adds ## Enterprise is not Pro with more modules. An ordinary ERP grows by adding modules. Enterprise grows by adding institutional governance: the structure, command, identity, audit and deployment controls a trust or a complex institution actually has to run on. What Enterprise adds beyond ordinary ERP modules, by dimension. | Dimension | Ordinary ERP modules | SquareCampus Enterprise | | --- | --- | --- | | Institutional structure | Several schools run as separate instances or branches | Advanced trust-school-campus governance requirements: inherited policy and recorded local exceptions, subject to scoping | | Command | Consolidated reports prepared from each branch | Trust-level command-view requirements, scoped against available reporting capabilities | | Governance | Approval steps inside individual modules | Advanced approval and exception-ownership requirements across workflows and campuses, scoped during discovery | | Identity | User accounts per instance | Identity governance: multi-directory requirements, group-to-role mappings, SSO enforcement policy and lifecycle controls, scoped during discovery | | Auditability | Change logs per module | Advanced policy controls and audit-export requirements; institution-owned data and supported portability apply to every plan | | Intelligence | Reports and dashboards | Governed AEGIS access requirements and allowances, confirmed against available capabilities | | Deployment and integration | Vendor cloud, standard connectors | Managed cloud, private-cloud or on-premises eligibility, enterprise integrations and implementation governance | The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone. [Sign-in options by plan](https://squarecampus.com/security/#identity) Fit ## Who SquareCampus is priced for, and who it is not. SquareCampus is priced for institutions that want governance, workflow ownership, exception management, visibility and auditability. To one that needs only the cheapest attendance, fees and report-card product it will look expensive — and that reading is correct. Best suited to - Institutions where leadership wants to know what requires attention today, who owns it and whether it was closed - Trusts and groups balancing central policy with campus-level accountability - Institutions that need auditability, approval chains and role-scoped access as institutional configuration rather than as favours from a vendor - Institutions that expect their systems to interoperate rather than to be replaced wholesale SquareCampus may not be the right fit if - The requirement is limited to basic attendance, fee collection and report cards - The lowest possible licence price is the dominant selection criterion - The institution does not need workflow ownership, exception management, governance or cross-campus visibility - Leadership wants a tool for one office rather than an operating system for the institution Volume-based pricing ## The marginal rate reduces as enrolment grows. Student volume sets platform scale, and larger volumes use the shared platform foundation more efficiently. The commercial model reflects those economies rather than imposing a flat rate for every institution. The institution benefits from its own scale SquareCampus maintains one shared platform baseline — capacity, security, observability, workflow infrastructure and the operations behind them. That baseline does not multiply with every additional student. Larger institutions therefore receive the benefit of platform economies of scale. The marginal rate reduces as enrolment grows, while the selected plan reflects the workflow, analytics, governance and deployment depth required. An institution is not charged the entry rate indefinitely for growing. Platform foundation Shared capacity, security and operations. Greater utilisation Larger enrolments use that foundation more fully. Lower marginal rate The benefit returns to the institution. Pricing uses progressive, volume-based student bands. The chart shows the direction of the marginal rate as enrolment grows — the bands themselves are set out in your proposal. What shapes the proposal ## The inputs we establish during institutional discovery. A proposal is only useful if it reflects the institution as it actually operates. These are the dimensions mapped before commercial terms are issued. ### Active student count The billable enrolment basis for the term. ### Number of campuses Single campus, group, or trust hierarchy. ### Workflows selected Which operational areas move onto the platform. ### Migration volume and data quality How much history moves, and in what state, so we can say early what cannot. ### Integrations Accounting, identity, payments and existing institutional systems. ### Deployment profile Managed cloud, private cloud, or on-premises. ### Support and SLA requirements Response expectations and escalation structure. ### Governance and approval depth Approval chains, policy controls and audit expectations. ### AEGIS usage Whether governed intelligence is in scope, and at what depth. ### Communication and storage requirements Messaging volume and document storage. Exact commercial terms are issued after a short institutional discovery. [Request a proposal](https://squarecampus.com/contact/) Included versus separately scoped ## No hidden subsidies. No surprise implementation bill. The licence already covers your plan, the apps, self-serve reports, implementation and support, a monthly usage allowance and, from Pro, data migration. Anything else is optional and priced in the proposal before you sign. ### In every licence #### Your plan's platform Every capability theme listed for your plan. #### Parent and staff apps The standard SquareCampus apps, at no extra charge. #### Your own reports Filter, group, total and chart your tables, save views and export to Excel, CSV or PDF. #### Implementation and support In every plan, with no paid fast track. Designed to need little or no training. #### Monthly usage allowance SMS, WhatsApp and storage, plus AEGIS where your plan includes it. #### Data migration — Pro and Enterprise Everything your current system can export in usable form. Anything that cannot move is shown before go-live. White-labelled Android and iOS apps under your own branding carry one charge for the whole agreed term. Founding Institutional Partners receive them without it. ### Institutional identity Available separately Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. ### White-labelled mobile apps Separately quoted enhancement Institution-branded parent and staff apps and store listings are quoted separately. The existing single charge covers the agreed term; founding-partner treatment follows its separate agreement. Delivery readiness is confirmed during scoping. ### Messaging and consumption Allowances and usage charges Every plan includes the agreed monthly SMS, WhatsApp and storage allowances, and AEGIS where included. Usage beyond the allowance is prepaid at proposal rates, never billed after the fact. Email and other external-service scope are confirmed separately; no universal quotas or unlimited-use entitlements are published. ### Analytics, branding and identity lifecycle Contact sales to assess requirements Discuss advanced analytics, additional AI credits, extended branding, provisioning and federation requirements. Product availability, plan eligibility and commercial treatment require confirmation; confirm the supported scope with sales before commitment. ### Custom integrations and migration Custom-quoted professional services Data migration is included in Pro and Enterprise and quoted on Starter, on a best-effort basis against usable source exports. Custom integrations and engineering are quoted as project work. Consumption beyond agreed allowances is prepaid. ### Enhanced support and deployment Contact sales for a scoped proposal Enhanced support, contractual SLA options and specialised deployment requirements are assessed separately. Response commitments, service levels and eligibility exist only where agreed in the contract. Three commercial paths ## Choose the engagement that fits your institution. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. ### Standard Commercial Subscription The normal paid SquareCampus subscription, with plan entitlements, consumption allowances and separately quoted requirements agreed in the proposal and order form. [Compare plans](https://squarecampus.com/pricing/#plans) ### Selected Institutional Launch Pilot Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. [Review the launch pilot](https://squarecampus.com/pricing/#pilot) ### Founding Institutional Partner programme 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. Its paid, scoped founding engagements and negotiated privileges are separate from the complimentary launch pilot. [Review founding partnerships](https://squarecampus.com/launch-partners/) 90 days ### Selected Institutional Launch Pilot Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. Initial launch outreach focuses on Kotdwara and surrounding areas. Enquiries are reviewed individually; this outreach focus is not a published geographic eligibility restriction. Modules, workflows, deployment coverage, institutional counterparts and documented success criteria are agreed before activation. Messaging, AI, storage, integrations and external-service consumption have defined boundaries agreed before activation. Custom development, bespoke integrations and unrestricted engineering support are not included. Any separately chargeable work or consumption must be agreed in writing. Subscription pricing is communicated before pilot activation, with a commercial review before the 90-day pilot expires. At completion, the institution chooses to subscribe or discontinue. [Request launch-pilot review](https://squarecampus.com/contact/) Founding pilots are paid, scoped commercial engagements. Scope, success measures, fees and conversion terms are agreed in writing before implementation begins. Founding pilots run for 60–90 days, with the choice to convert, extend or stop. Common foundations ## Security and data ownership apply to every plan. Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. Procurement questions ## The commercial questions institutions ask before signing. Answers here describe how the model works. The signed order form governs the specific terms for your institution. **Is pricing public?** The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. One published figure would be wrong for most institutions, in both directions. **What does Enterprise add beyond ordinary ERP modules?** Enterprise is selected by governance requirement, not by enrolment or module count. Advanced institutional governance, cross-campus command, analytics, integrations, expanded audit controls and specialised deployment or support requirements are assessed during discovery and documented against available capabilities. Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. **Is SquareCampus appropriate if we only need attendance and fees?** Usually not. SquareCampus is priced for institutions that want governance, workflow ownership, exception management, visibility and auditability. To one that needs only the cheapest attendance, fees and report-card product it will look expensive — and that reading is correct. **Can we keep our existing ERP during the pilot?** Yes. A pilot covers one campus or one workflow bundle, and your ERP keeps running and stays authoritative. Replacing anything is a later decision, taken on evidence. **Is migration included?** Data migration is included in Pro and Enterprise, and quoted on Starter. We move everything your current system can export in usable form. If it lacks data SquareCampus needs, or is too fragmented to reconcile, we show you what cannot move before go-live instead of guessing. **Do custom reports cost extra?** Reporting is self-serve in every plan: staff filter, group, total and chart their tables, save views for the team and export to Excel, CSV or PDF. A fixed-format document made only for your institution, such as your own report-card layout, is quoted; a format many schools need becomes a standard report at no charge. **What does implementation cost?** Nothing extra. Implementation and support are included in every plan, and every institution gets the same rollout: there is no paid fast track. SquareCampus is designed to need little or no training. Only a custom SLA, such as 24×7 cover or guaranteed response times, is quoted. **Can the price grow after we sign?** Not by surprise. Everything optional is priced in the proposal before you sign, and usage beyond the allowance is prepaid, so the proposal you sign is the bill you get. Enrolment growth is reconciled through the agreed true-up. **Can SquareCampus run in our own cloud account?** Not today. Enterprise can scope a dedicated deployment on AWS, in a private cloud or on premises, with responsibilities set out before implementation. **Which sign-in options does each plan have?** Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Enterprise: Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. **Does SquareCampus access our Outlook or Microsoft 365 data?** No. Entra ID sign-in authenticates identity only; no access to email, files, Teams or SharePoint is needed. **Does single sign-on automatically create and remove users?** No. Single sign-on authenticates. Automated provisioning and joiner-mover-leaver controls are identity governance, part of Enterprise and established during technical discovery. **Is GST included?** Quoted commercial figures are exclusive of applicable taxes unless the proposal states otherwise. Applicable Indian taxes are shown on the order form and on tax invoices issued by Fairhelm Systems (OPC) Private Limited under GSTIN 29AAHCF1819L1ZA. **How is AEGIS usage handled?** Not included in Starter; in Pro when the proposal includes it; in Enterprise within an agreed monthly allowance. Usage beyond the allowance is prepaid, so it never becomes a surprise bill. **Can a trust contract cover multiple campuses?** Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. A trust-level agreement can cover agreed campuses; advanced central policy and governance requirements are scoped separately. **How many Founding Institutional Partner positions exist?** 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. **Do all plans include the core platform and multi-campus operations?** Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. Available modules, workflows and deployment scope are confirmed before activation. A plan entitlement does not imply that an unreleased capability is available. **Can Starter request Microsoft Entra single sign-on separately?** Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. **Are security and data portability restricted to Enterprise?** Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. **Is there a trial or pilot option?** Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. Messaging, AI, storage, integrations and external-service consumption have defined boundaries agreed before activation. Custom development, bespoke integrations and unrestricted engineering support are not included. Any separately chargeable work or consumption must be agreed in writing. Subscription pricing is communicated before pilot activation, with a commercial review before the 90-day pilot expires. At completion, the institution chooses to subscribe or discontinue. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. **Where is the launch pilot available?** Initial launch outreach focuses on Kotdwara and surrounding areas. Enquiries are reviewed individually; this outreach focus is not a published geographic eligibility restriction. **Can we buy one enhancement without changing our whole plan?** Yes, where the capability and commercial eligibility are confirmed. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Other enhancements, consumption and professional services are assessed and quoted separately; their availability is not implied by appearing in a scoping discussion. Next step ## Talk through your institution's requirements. Bring your campus structure, workflows and governance needs. Commercial terms follow a written proposal. [Contact the team](https://squarecampus.com/contact/) --- Source: https://squarecampus.com/launch-partners/ --- title: "Founding Institutional Partners | SquareCampus" description: "A measured, founder-led programme for schools, school groups and education trusts that want to shape SquareCampus against a real operating bottleneck." canonical: https://squarecampus.com/launch-partners/ describedby: https://squarecampus.com/llms.txt --- Founding institutional partner programme # Build the School OS with us—against a real institutional problem. Founding Partners do not receive a generic beta account. We establish a baseline, deploy around one measurable operational bottleneck, validate the result with your team, and use that evidence to decide what should scale next. [Request a partnership diagnosis](https://squarecampus.com/launch-partners/#request-diagnosis) See the 60–90 day pilot Measured pilot · Founder-led implementation · No compulsory rip-and-replace What a founding pilot is One measurable bottleneck, a written baseline, and a decision taken against evidence. **Positions** Two, ever: one school, one university **Window** 60–90 days **Scope** One campus or one workflow bundle **Close** Convert, extend or stop The programme, precisely ## Two Founding Institutional Partner positions. Then the programme closes. 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. The two positions 1. One school or eligible school institution 2. One university Once both positions are allocated, the Founding Institutional Partner programme closes permanently. What a Founding Partner receives, under the executed agreement **Defined roadmap influence** Structured, written consideration of the partner's operating requirements in roadmap planning, as defined in the executed agreement. **Protected 40% Enterprise discount** A protected 40% discount on Enterprise commercial terms, as set out in the executed agreement. **White-labelled mobile apps** The SquareCampus parent and staff apps published under the institution's own branding and store listings, without the standard white-label charge. **Other agreed founding privileges** Any further privileges are those explicitly agreed in the executed agreement, and no others. What founding status is not - Roadmap influence is not a veto, ownership of the roadmap, product or architectural control, ownership of intellectual property, or an entitlement to unlimited custom development. - SquareCampus retains final product, architecture, security and engineering authority unless a signed agreement explicitly states otherwise. - Founding status does not create exclusivity or territory rights. - Entitlements are governed by the executed agreement. This page describes the programme; it is not an offer. What founding status changes ## Ordinary customers buy the platform. Founding Partners help shape how it reaches the institution. Three pillars, not a wall of feature cards. Each one is bounded by the executed agreement. ### Better execution The implementation is run, not handed over. - Founder-led institutional discovery - A named implementation counterpart - Parallel validation with current systems - Scoped migration and integration planning - Peak-cycle capacity planning and escalation ### Better economics The commercial structure is agreed up front and holds. - A protected 40% discount on Enterprise commercial terms under the executed agreement - White-labelled Android and iOS apps under the institution's own branding, without the standard white-label charge - Clearly bounded implementation and digital-campus allowances - No hidden module wall or surprise pass-through markup ### Better influence The institution's operating reality reaches the roadmap. - Defined roadmap influence under the executed agreement - Material participation in product validation - Early access to selected capabilities - Written consideration of major workflow proposals - Direct operating feedback with Fairhelm leadership The managed digital campus ## Your public digital estate can run with the same operational discipline. Where it is part of the agreed scope, Fairhelm can design, build and operate the institution's group website, campus websites and admissions microsites—connecting enquiries and forms to SquareCampus instead of leaving them in disconnected inboxes. - Group and campus websites - Admissions and campaign microsites - Enquiry forms connected to institutional workflows - Managed hosting, SSL, CDN and backups - Role-controlled publishing for campus teams - English/Hindi content support where required - Analytics, performance and accessibility foundations - Domain and institutional content ownership retained by the school Site count, design system, page migration, traffic, storage and change allowances are defined in the proposal. The programme is not an unlimited creative-services retainer. Partnership path ## Start with evidence. Expand only when it earns the right. Four stages. Each one has to produce something the next stage can be judged against. ### Diagnose Choose one operating bottleneck whose current cost, delay or ownership problem can be observed. ### Baseline Write down the workflow, accountable owners, starting position and one success measure before implementation begins. ### Run the pilot Deploy one campus or one agreed workflow bundle for 60–90 days, with named counterparts and parallel validation where needed. ### Decide on evidence Convert, extend or stop against the agreed measure. If it works, expand through the protected founding-partner commercial structure. 60–90 day pilot The same sequencing, migration discipline and parallel validation described on the [rollout page](https://squarecampus.com/rollout/), run with founder-level involvement. Paid, scoped engagement Founding pilots are paid, scoped commercial engagements. Scope, success measures, fees and conversion terms are agreed in writing before implementation begins. The university position ## The second Founding Partner position is reserved for a university. The same 60–90 day evidence model applies, but the wedge is usually an exception queue between systems that already exist — admissions-to-enrolment, payment-to-ERP reconciliation, interdepartmental approvals — rather than a school's day-to-day operations. [Read the higher-education lane](https://squarecampus.com/launch-partners/higher-education/) Who should apply ## Designed for institutions willing to participate, not merely observe. Founding partnership asks for something from the institution as well. These are the signals that a pilot will produce usable evidence. Good-fit signals - A principal, trustee, director or group leader will act as executive sponsor - There is a real workflow bottleneck that leadership wants to measure - Campus teams can participate in discovery and weekly implementation reviews - The institution can provide legitimate exports or process documentation needed for the agreed scope - Leadership wants a multi-year operating relationship if the pilot succeeds - The institution is prepared to make a strategic capital commitment under a separately executed agreement - The institution values governance, accountability and cross-campus visibility—not merely a cheaper attendance app What founding status is not Founding status does not create exclusivity, ownership of SquareCampus intellectual property, veto rights, product or architectural control, or an unlimited bespoke-engineering commitment. SquareCampus retains final product, architecture, security and engineering authority unless a signed agreement explicitly states otherwise. Exact entitlements are governed by the executed agreement. [How the licence is composed](https://squarecampus.com/pricing/) · [Review the trust posture](https://squarecampus.com/security/) Before you commit ## The questions a board asks before it says yes. None of these have flattering answers, so here are the accurate ones. ### Is this the complimentary launch pilot? The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. Founding pilots are paid, scoped commercial engagements. Scope, success measures, fees and conversion terms are agreed in writing before implementation begins. ### You are a new company. Why would we depend on you? You would not — not at first. A pilot is scoped to one campus or one workflow bundle, runs alongside the system you already have, and is judged against a measure written down before it starts. The institution keeps its existing system throughout, and agrees supported export and offboarding arrangements before activation, regardless of the outcome. ### What happens if the pilot fails? You stop. Convert, extend and stop are the three published outcomes, and stopping is not a failure state we argue you out of — it is the reason the baseline is written down first. You leave with the measurement, the process documentation and your data. ### We cannot afford disruption during admissions or fee cycles. Neither can the pilot. Sequencing around admissions, fee deadlines, examinations and results is part of the rollout method, not an accommodation. Critical workflows run in parallel until finance and academic teams trust the numbers. ### Who actually does the work? A named counterpart, with founder-level involvement in discovery and implementation. That is a consequence of there being only two founding positions, and it is one of the things a Founding Partner is trading for. ### Who owns the data, and can we get it out? The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. ### What does it cost to find out? Scope, success measure and commercial terms are agreed in writing before any work begins, so the cost is known before you commit rather than discovered afterwards. The first conversation is a 30-minute diagnosis and costs nothing. ### What does a Founding Partner actually receive? Under the executed agreement: defined roadmap influence, a protected 40% discount on Enterprise commercial terms, white-labelled mobile apps without the standard white-label charge, and any other privileges explicitly agreed. Roadmap influence is structured input, not a veto or control over the product, its architecture or its intellectual property. The first conversation ## Bring one bottleneck. We will map the operating path around it. Tell us where visibility arrives late, ownership becomes unclear, or staff rebuild the same truth by hand. We will determine whether it belongs in a Founding Institutional Partner pilot. SquareCampus may sit above or alongside your existing ERP, LMS, payment, identity and communication systems during the pilot. One bounded workflow or one campus, a written baseline, and one agreed success measure. Founding pilots are paid, scoped commercial engagements, agreed in writing before implementation begins. No commitment · 30-minute institutional diagnosis [Review rollout and trust](https://squarecampus.com/rollout/) Request a diagnosis ### Describe the bottleneck, not the wishlist. Tell us where visibility arrives late, ownership becomes unclear, or staff rebuild the same truth by hand. The more precise the bottleneck, the more useful the first conversation. A separate launch programme ## Selected Institutional Launch Pilot Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. [Review launch-pilot eligibility](https://squarecampus.com/pricing/#pilot) --- Source: https://squarecampus.com/launch-partners/higher-education/ --- title: "Founding Partners for Higher Education | SquareCampus" description: "A governed operating layer that runs alongside a university's existing ERP, LMS, payment and identity systems. One bounded workflow, a written baseline and a 60–90 day evidence model." canonical: https://squarecampus.com/launch-partners/higher-education/ describedby: https://squarecampus.com/llms.txt --- Founding institutional partners · Higher education # Your systems are not the problem. The space between them is. Private universities and multi-school groups rarely lack software. They run an ERP, an LMS, one or more payment portals, an identity provider and several communication channels — and lose weeks in the gaps between them, where a case is stalled, unowned, and visible to nobody until someone escalates. SquareCampus is the governed layer across that space. [Request a partnership diagnosis](https://squarecampus.com/launch-partners/#request-diagnosis) See where a pilot starts Runs alongside your existing ERP, LMS, payment and identity systems · One bounded workflow · Paid, scoped pilot The 60–90 day evidence model One bounded workflow, a written baseline, and a decision taken against evidence. **Scope** One workflow or one non-clinical department **Window** 60–90 days **Sponsor** One named executive owner **Close** Convert, extend or stop What this is, precisely ## Not a university ERP. A governed operating layer over the one you have. It is worth being exact about this before anything else, because the wrong expectation wastes both sides' time. What it is not - Not a replacement for your student information system or ERP of record - Not a learning management system, and not a competitor to the one you run - Not a payment gateway, an identity provider, or a finance ledger - Not a clinical, hospital or patient-care system, and not proposed for one What it is - A governed layer that watches the workflow across those systems - An exception queue with a named owner and a due position for every open case - An append-only record of who decided what, when, and on what basis - A leadership view of a bounded operational workflow that is current without an export Where a pilot starts ## Five wedges that produce evidence inside one term. Each one is bounded, already measurable today, and does not require switching off anything the institution depends on. ### Admissions-to-enrolment exception ownership Applications that clear one stage and stall at the next — document verification, fee confirmation, seat allocation, registration. The exception gets an owner and a position instead of living in an inbox. ### Payment-success-to-ERP reconciliation Payments that succeed at the gateway and do not land cleanly against the record. The mismatch is raised as an exception, routed, and closed with a recorded reason rather than reconciled by hand at month end. ### Interdepartmental approvals and stalled cases Requests that cross academic, finance, registry and administrative boundaries and lose their owner at each handover. Latency becomes visible while it is still recoverable. ### Leadership visibility across one bounded workflow A current view of one workflow — what is open, who owns it, what is overdue and what was decided — without a department preparing a deck for it. ### Evidence collection and accountable closure Administrative and operational workflows outside clinical and hospital systems, where a decision needs a recorded reason and an auditable close. Explicitly out of scope Clinical and hospital information systems are outside the suggested pilot scope. Where an institution operates a teaching hospital, the pilot is scoped to non-clinical administrative workflows only, and SquareCampus makes no medical, patient-care, accreditation or regulatory claim. How it sits ## Above or alongside. Nothing is switched off to find out whether this works. During the pilot the institution's ERP, LMS, payment portals, forms and identity provider stay exactly where they are and stay authoritative. SquareCampus governs the workflow that runs across them. ### Systems of record stay in place The ERP or SIS remains the record. SquareCampus does not ask to become it, and does not require a migration to start. ### The workflow is governed across them A case is tracked from the event that starts it to the decision that closes it, regardless of how many systems it touches on the way. ### Ownership is explicit, not implied Every open exception has a named accountable owner and a position. Nothing sits in a shared mailbox waiting to be noticed. ### The decision is recorded Approvals, overrides and refusals land on an append-only timeline with the reason attached, scoped to the role that took them. A later rollout may replace selected fragmented tools, when and if the institution decides to. That is a separate decision, taken after the evidence exists — never a precondition of the pilot. The 60–90 day evidence model ## The same discipline as every founding pilot, scoped to a university. The same sequencing, migration discipline and parallel validation described on the rollout page, scoped to one university workflow. ### One bounded scope One workflow, or one non-clinical constituent school or department. Not the institution, and not a phased programme dressed up as a pilot. ### One written baseline The current position — volumes, delays, ownership gaps — written down before implementation, so the result is measured rather than argued. ### One named executive sponsor A Registrar, Dean, Finance lead, COO or CIO who owns the outcome internally and can convene the people the workflow crosses. ### Parallel validation where needed Anything finance or registry teams must trust runs alongside the existing process until the numbers agree. ### Convert, extend or stop Judged against the measure agreed at the start. Stopping is a published outcome, not a failure state we argue you out of. Paid, scoped engagement Founding pilots are paid, scoped commercial engagements. Scope, success measures, fees and conversion terms are agreed in writing before implementation begins. [How the licence is composed](https://squarecampus.com/pricing/) and [how a rollout runs](https://squarecampus.com/rollout/). Who this has to convince ## Five people, five different questions. A pilot at a university needs several people to agree. They are not agreeing to the same thing. President / Vice Chancellor ### What does this change at my level? One bounded workflow stops arriving as an escalation and starts arriving as a current position. The pilot is small enough to stop and specific enough to judge. Registrar ### Does this add another system for my office to run? It governs the ones you already run. The registry keeps its system of record; what changes is that a stalled case has an owner and a position instead of a follow-up email. Dean / Academic leader ### Will this reach into academic judgement? No. The scope is administrative and operational workflow — where a case is, who owns it, and whether a decision was recorded. Academic decisions stay with the people who make them. Finance leader ### What happens to reconciliation? Mismatches between payment success and the record become routed exceptions with a recorded closure, and run in parallel with the existing process until finance trusts the numbers. CIO / IT leader ### What is the integration and data burden? Scoped to the workflow in the pilot, agreed in writing before implementation, and read-oriented where the existing system stays authoritative. Access is role-scoped; supported export and offboarding arrangements are documented before activation. One position ## One university Founding Institutional Partner position exists. 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. **Defined roadmap influence** Structured, written consideration of the partner's operating requirements in roadmap planning, as defined in the executed agreement. **Protected 40% Enterprise discount** A protected 40% discount on Enterprise commercial terms, as set out in the executed agreement. **White-labelled mobile apps** The SquareCampus parent and staff apps published under the institution's own branding and store listings, without the standard white-label charge. **Other agreed founding privileges** Any further privileges are those explicitly agreed in the executed agreement, and no others. The first conversation ## Bring one bottleneck. We will map the governed path around it. A 30-minute diagnosis of one workflow: where it stalls, who should own it, what a bounded pilot would cover, and whether the university Founding Partner position is the right fit at all. No commitment · 30-minute institutional diagnosis [Request a partnership diagnosis](https://squarecampus.com/launch-partners/#request-diagnosis) · [The full founding partner programme](https://squarecampus.com/launch-partners/) · [Review the trust posture](https://squarecampus.com/security/) A separate launch programme ## Selected Institutional Launch Pilot Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. [Review launch-pilot eligibility](https://squarecampus.com/pricing/#pilot) --- Source: https://squarecampus.com/security/ --- title: "Security & Trust | SquareCampus School Operating System" description: "How SquareCampus approaches security for school data: encryption in transit and at rest, role-based access, audit trails, and an India-first hosting posture. Documentation available on request." canonical: https://squarecampus.com/security/ describedby: https://squarecampus.com/llms.txt --- Trust and security # Security answers for the people who review school software. Access control, audit history, encryption, hosting, backups and how to report an issue — stated plainly, with the evidence behind each one shared in writing during security review. [Book a demo](https://squarecampus.com/demo/) · [Contact security](mailto:security@squarecampus.com) Audit timeline Synthetic data Control domains ## The trust posture is designed for institutional accountability Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. ## Access control Access is role-based and scoped by campus. Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Authorisation is always decided inside SquareCampus, never by an email domain. ## Audit history Approvals, overrides and record changes are designed to be recorded with who made them, what changed and when, in the campus context they happened in. ## Encryption Data is encrypted in transit and at rest as part of the platform's baseline design. Implementation details are shared during security review. ## Hosting 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. Hosting details and data-flow documentation are given in writing during evaluation. ## Backups and recovery Availability, backup and recovery design are documented in writing during security review. We do not publish uptime, backup or recovery figures. ## Reporting a security concern Email security@squarecampus.com with a description, steps to reproduce and the likely impact. Sensitive reports can be encrypted with our PGP key. Identity and access ## Your identity environment remains yours The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone. All plans ### Secure sign-in and authorisation Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Available separately ### Institutional single sign-on Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Enterprise ### Identity governance Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. ### Your Microsoft environment Stays under your administration 1. Your administrator approves SquareCampus in your Microsoft Entra ID tenant. 2. Staff sign in with their existing institutional Microsoft accounts. 3. Your MFA, Conditional Access and user-assignment policies continue to apply. ### SquareCampus authorisation Governed inside the School OS 1. SquareCampus validates that the sign-in came from your approved tenant. 2. It resolves the person's institution membership and campus scope. 3. It applies role, record and workflow permissions defined in SquareCampus. 4. A secure SquareCampus session is issued. Available separately on any plan Microsoft Entra ID verifies who the user is. SquareCampus determines what the user may access and perform. Single sign-on is chosen by the institution, never required. Sign-in modes the institution chooses between 1. Mode 1 SquareCampus-managed credentials, subject to deployment readiness 2. Mode 2 Credentials alongside institutional single sign-on, where supported by the agreed configuration 3. Mode 3 Institution-enforced single sign-on, where the institution's policy requires it and the configuration supports it - Single sign-on is optional. An institution is not required to adopt it, and is not required to move between Google Workspace and Microsoft to use SquareCampus. - Standard sign-in authenticates identity only. It does not require access to email, files, Teams, SharePoint or other Microsoft 365 data. - Single sign-on authenticates users; it does not create or remove them. Automated provisioning and deprovisioning are a lifecycle requirement scoped under Enterprise. - Where institution-enforced single sign-on is configured, SquareCampus credentials are designed not to act as an ordinary alternative route around the institution's identity policy. Documents on request ## What we share in writing during a security review Ask for any of these by email. They are shared under the security review process, not published. - Completed vendor security questionnaires - Hosting and data-flow documentation - Availability, backup and recovery design - Encryption and access-control implementation notes - The Data Processing Addendum and data retention approach - Identity and sign-in configuration for your plan [Data Processing Addendum](https://legal.fairhelmsystems.com/squarecampus/data-processing-addendum/) · [Data retention](https://legal.fairhelmsystems.com/squarecampus/data-retention/) · [Infrastructure](https://squarecampus.com/infrastructure/) · [PGP key](https://squarecampus.com/pgp/) Security questions ## What review teams ask first **Where is data hosted?** SquareCampus is designed with an India-first hosting posture. Hosting details and data-flow documentation are shared during the security review process. **How is data encrypted?** Data is encrypted in transit and at rest as part of the platform's baseline design. Implementation details are available under the security review process. **Who can access data?** Access is role-based and least-privileged by design, with administrative access logged and traceable. **Do you support vendor security questionnaires?** Yes. We provide questionnaire support and can share security documentation and summaries on request. **Can an institution use normal SquareCampus credentials?** Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. **Can staff sign in with our own Microsoft accounts?** Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. **What identity options does Enterprise add?** Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. **Is baseline security included in every plan?** Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. **Who owns institutional data, and what happens when we leave?** The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. **Who decides what a signed-in user may do?** The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone. Security review ## Bring your questionnaire, policy concerns, or institutional requirements. The right trust conversation covers the real product controls, the operating posture, and how the institution can stay confident after go-live. [Book a demo](https://squarecampus.com/demo/) · [Email security](mailto:security@squarecampus.com) --- Source: https://squarecampus.com/infrastructure/ --- title: "Infrastructure | SquareCampus" description: "How SquareCampus infrastructure is designed: Microsoft Azure in India, encryption in transit and at rest, an India data-residency posture, and Enterprise private deployment on AWS — with documentation available through the security review process." canonical: https://squarecampus.com/infrastructure/ describedby: https://squarecampus.com/llms.txt --- Infrastructure # Infrastructure, stated plainly. SquareCampus is hosted on Microsoft Azure in India. This page describes how the platform is designed — and anything it does not answer, we will answer in writing during your evaluation. Cloud Microsoft Azure Region India Residency India-first posture Encryption Transit & at rest See the comparison [Security posture](https://squarecampus.com/security/) Why managed cloud ## Why Azure in India? Why not “own servers”? Data residency isn't defined by who makes the servers — it's defined by where they physically sit and how access is governed. Choosing Microsoft Azure in India is an engineering decision. ## The “own servers” reality check In this market, “own servers in India” can mean very different things: Rented racks in shared co-location facilities A VPS from a hosting provider, sometimes outside India A single server in a locked room on consumer hardware “Own” hardware leased from a local hosting company None of these are automatically bad — but they are different risk profiles, and an institution deserves to know which one it is buying. The useful move is to ask every vendor, including us, the same infrastructure questions in writing. The comparison ## Managed cloud design vs unspecified “own servers” What we run, next to the questions worth asking any vendor. Data residency SquareCampus · Azure, India Microsoft Azure, India The platform is hosted on Microsoft Azure in India. The specific regions and data flows are named in writing during evaluation. Typical unspecified claims “India” (unspecified) Often vague: an India endpoint can sit in front of infrastructure hosted anywhere. Ask every vendor: Which region and provider, in writing? Reliability design SquareCampus · Azure, India Documented resilience High availability, backup and recovery design are documented in writing and shared during evaluation, so the answer is specific to your deployment rather than a marketing line. Typical unspecified claims Single location One facility means one point of failure and manual recovery. Ask every vendor: What is your recovery plan if the building fails? Physical security SquareCampus · Azure, India Microsoft Azure data centres Azure facilities carry independent certifications (published by Microsoft). Our application-level controls are documented separately and shared on request. Typical unspecified claims “Secure” (undefined) Varies widely; sometimes a locked room with no third-party attestation. Ask every vendor: Can you share any third-party attestation? Scalability SquareCampus · Azure, India Cloud auto-scaling Capacity can be added for admission season and exam-week load without hardware purchases, in the same region. Typical unspecified claims Hardware bottleneck Physical servers must be ordered, shipped, and installed to grow. Ask every vendor: How do you handle a 10x load spike? Transparency SquareCampus · Azure, India Questions answered in writing We answer infrastructure questionnaires in writing and share architecture documentation during the security review process. Typical unspecified claims Vague claims “Own servers” without documentation is a marketing line, not an architecture. Ask every vendor: Will you put your answers in writing? Design decisions ## What this design means for your institution These are the architectural commitments the platform is built around. The specifics behind each one are documented for security reviews. ## Built to stay available The platform runs on a hyperscale cloud designed so that a problem in one facility does not take daily campus operations down. The availability design for your deployment is documented during security review. ## Backups by design Backup cadence, retention and restore procedures are documented in writing and shared during security review. ## Encryption as baseline Data is encrypted in transit and at rest as baseline infrastructure, with access controlled by roles and administrative activity logged. ## India residency posture The platform is designed to keep institutional data in Microsoft Azure regions in India. Enterprise private deployments on AWS, in a private cloud or on premises are scoped with the same residency expectations. ## Layered network protections Application servers are designed to sit behind managed network protections rather than being directly exposed to the internet. ## Documentation on request Architecture summaries, data-flow documentation, and questionnaire responses are available to evaluating institutions through the security review process. [Request documentation](mailto:security@squarecampus.com?subject=Infrastructure%20Documentation%20Request) Due diligence ## Questions worth asking every vendor — including us Use these during your evaluation and compare the answers in writing. ### What region and provider host our data? Why it matters: “Hosted in India” without a named region and provider is unverifiable. Our answer: Microsoft Azure in India. The specific regions and data flows are documented in writing during evaluation. ### What happens when a facility fails? Why it matters: This separates a real architecture from a single server in a rack. Our answer: Availability design, recovery objectives and procedures are part of the documentation we share during security review. ### Can you share third-party attestations? Why it matters: Anyone can say “secure”. Attestation and documentation are what procurement can rely on. Our answer: Microsoft publishes Azure's facility certifications. Our application-level security documentation is shared on request, and we support vendor questionnaires. ### Will you answer these questions in writing? Why it matters: Verbal assurances do not survive procurement or audits. Our answer: Yes — every answer above, in writing, addressed to your institution. Infrastructure FAQ ## The technical questions, answered plainly ### Why a hyperscale cloud instead of “own servers”? Data residency is defined by where data physically sits and how access is governed — not by who owns the racks. Microsoft Azure in India gives us mature managed services, availability zones within an Indian region, and independently certified facilities, which is a stronger foundation than self-managed hardware for a platform schools depend on daily. Institutions that need their own boundary can scope an Enterprise private deployment on AWS, in a private cloud or on premises. ### How do we verify where our data is hosted? Ask us in writing. During evaluation we share architecture documentation describing the region, the residency controls, and the data flows, and we support vendor security questionnaires. We would rather answer specific questions than ask you to take a marketing page on faith. ### What happens if a data centre has an outage? Availability, recovery objectives and procedures are documented in writing and shared during the security review process. ### Is our data encrypted? Yes — in transit and at rest, as part of the platform's baseline design. Key management and implementation details are covered in the security documentation we share on request. ### Can you complete our security questionnaire? Yes. Send it to security@squarecampus.com. We answer infrastructure and security questionnaires in writing as part of institutional procurement. Infrastructure review ## Ask us the hard questions. Bring your security questionnaire, your IT committee, or your auditor. We answer infrastructure questions in writing as part of an evaluation. [Book a demo](https://squarecampus.com/demo/) · [Email security](mailto:security@squarecampus.com?subject=Infrastructure%20Questions) --- Source: https://squarecampus.com/pgp/ --- title: "PGP Public Key | SquareCampus" description: "SquareCampus PGP public key for secure communications, vulnerability reports, and message verification." canonical: https://squarecampus.com/pgp/ describedby: https://squarecampus.com/llms.txt --- Secure communication # PGP public key. Use this key to send encrypted messages to our security team or verify communications from SquareCampus. Email security@squarecampus.com Algorithm RSA 4096-bit Created 2026-01-17 Expires 2028-01-17 ## Key fingerprint Always verify before trusting `5258 EF81 53BA A48E 9C97 A545 6B78 F402 61C5 208E` Key ID: 0x61C5208E When to use this key ## Security vulnerability reports Report security issues privately and securely. We take responsible disclosure seriously. ## Sensitive communications Share confidential information that requires end-to-end encryption. ## Verify our messages Confirm that emails claiming to be from the SquareCampus security team are authentic. Public key [Download.asc](https://squarecampus.com/squarecampus-security.asc) ``` -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBGlrWnQBEACkFwg/ZJVeKmb+sNlbHHOC+k+GtPFEl+KnM4MI9VcZh8gu37or OvJeXwSxrkvtW8aigZZAA1z7hgbPPiNnIX0A3tzOje7A6fxMQZ55xiNqSD5KaLwY aSwph/n3u/FhMnqAYk9MjGmniVnccCS4H3ypSEW8lw7Gn6SXR54XSIB4Oa89HP20 ... (55 more lines)... 0RciJsoOhVjELGPOmR/QrC/MdJh0bq0T22+RZ5aijH8MLEqjDhacjRwZpV6VTGHY w6YBetF5h8rgimZ+rZUg6RVJKA== =G5SA -----END PGP PUBLIC KEY BLOCK----- ``` How to use 1 ### Download the key Download the.asc file or copy the public key block below. `curl -O https://squarecampus.com/squarecampus-security.asc` 2 ### Import into your keyring `gpg --import squarecampus-security.asc` 3 ### Verify the fingerprint Ensure it matches: 5258 EF81 53BA A48E 9C97 A545 6B78 F402 61C5 208E 4 ### Encrypt your message `gpg --encrypt --armor -r security@squarecampus.com message.txt` ### Important security notes - Always verify the fingerprint through a separate channel before trusting this key. - We will never ask for passwords, tokens, or sensitive credentials via email. - For security vulnerabilities, email security@squarecampus.com with your encrypted report. - This key is rotated periodically. Check this page for the latest version. [Security overview](https://squarecampus.com/security/) · [Infrastructure](https://squarecampus.com/infrastructure/) · [Contact security team](mailto:security@squarecampus.com) --- Source: https://squarecampus.com/about/ --- title: "About SquareCampus | Building the Operating System for Indian Education" description: "SquareCampus is a School Operating System for schools, educational trusts and multi-campus groups in India, built by Fairhelm Systems (OPC) Private Limited. Founder-led, focused on connected operations, governance and accountability." canonical: https://squarecampus.com/about/ describedby: https://squarecampus.com/llms.txt --- About SquareCampus # A founder-led company building software for Indian schools. SquareCampus is built by Fairhelm Systems (OPC) Private Limited, in Bangalore. It exists to put admissions, academics, fees and communication on one record, with a clear owner for every exception — for standalone schools, school groups and education trusts. [Book a demo](https://squarecampus.com/demo/) · [Explore the platform](https://squarecampus.com/platform/) **Company** Fairhelm Systems (OPC) Private Limited **CIN** U62099KA2026OPC225579 **Registered office** Bangalore, Karnataka **Founder** Mohit Gupta, Founder & CTO **Product** SquareCampus™ (trademark registration pending) Our story ## Built for campuses that can't afford chaos Institutions rarely struggle because people don't work hard. They struggle because data is scattered, processes are inconsistent, and every department runs its own system of record. ## One system of record for daily operations. Decisions get made on partial context, and the office ends up firefighting instead of planning. SquareCampus gives schools and colleges one connected system where every workflow is connected, auditable, and simple enough to use every day. We built SquareCampus because institutions deserve - Software that flows like thought, not clicks like paperwork - Systems that anticipate needs, not wait for tickets - Automation that gives time back to teaching, not admin - Data that tells stories, not just sits in rows - Technology that delights users, not frustrates them 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. Founder-led SquareCampus, a product of Fairhelm Systems (OPC) Private Limited, is built by a founder-led, product-first team focused on building something that can sit at the center of your institution for years, not months. MG Mohit Gupta · Founder & CTO Leads product and platform engineering. Built systems processing 100M+ records daily and brings that reliability mindset to every workflow. The shared goal: a platform that doesn’t just look good in demos, but survives timetables, fee seasons, inspections, and everything in between. ### What we build - Infrastructure that runs admission to alumni - Workflows designed around fee season, results and inspections - Software built for Indian institutional reality - A sustainable business that respects its team What we optimise for ## Less friction for the institution. More trust in the data. Every feature, integration, and workflow inside SquareCampus is measured against that single question. ## Reliability over decoration SquareCampus is built for the days that matter most — fee deadlines, results, inspections. Availability and recovery design are documented in writing during security review, not promised on a web page. ## Real-world operations first We design for paperwork, habits, audits, and constraints as they exist today, not how a hypothetical perfect campus might work. ## Radical clarity for admins Everyone works from the same governed record: who is present, what is pending, and what needs action now. Institutional fit ## How SquareCampus fits into your institution SquareCampus doesn't arrive as a rigid template. It adapts to your workflows while giving you the structure you need to scale without losing control. From standalone schools to multi-city groups. ## Built for Indian institutions - Ready for multi-campus, multi-branch structures. - Handles complex fee setups, terms, and concessions. - Respects your existing processes instead of forcing a reset. A single operating system instead of stitched tools. ## Digitizing every corner - Connects admissions, academics, and finance into one flow. - Turns paper-based approvals into clear, trackable workflows. - A change made once reaches the shared record, instead of being re-keyed into another system. Not just charts — actual decisions. ## Data you can act on - Shows what changed, who changed it, and when. - Highlights trends in attendance, performance, and collections. - Keeps insights role-based so everyone sees what matters to them. “Indian schools and colleges don’t need another shiny dashboard — they need software that understands the messy, beautiful chaos of running real institutions in this country. SquareCampus absorbs that complexity so institutions can stop firefighting and focus on what actually matters: education.” Next step ## Ready to see SquareCampus in action? Share how your institution operates today, and we’ll walk you through how SquareCampus can simplify, connect, and de-risk your daily workflows. [Book a demo](https://squarecampus.com/demo/) · [Explore the platform](https://squarecampus.com/platform/) --- Source: https://squarecampus.com/faq/ --- title: "Frequently Asked Questions | SquareCampus School Operating System" description: "Answers to common questions about SquareCampus, the School Operating System for Indian schools and trusts: core-platform plans, multi-campus operations, optional enhancements, security, data ownership and the selected 90-day complimentary launch pilot." canonical: https://squarecampus.com/faq/ describedby: https://squarecampus.com/llms.txt --- Frequently asked questions # The questions institutions actually ask. Getting started, modules, security, data ownership, pricing, and what support looks like after go-live. If it isn’t answered here, the demo covers it. ### What does SquareCampus actually replace? SquareCampus connects institutional operations on one governed system of record. Available workflows and the rollout scope are agreed with the institution; existing systems can remain authoritative during a bounded deployment. ### Who is SquareCampus for? Schools, educational trusts, multi-campus school groups and, as a governed operating layer over the systems they already run, higher-education institutions in India. It suits institutions that want operational governance, accountable ownership and leadership visibility, whether they run one campus or many. It is not designed for an institution that needs only basic attendance, fees and report cards at the lowest possible licence price. ### How fast can we go live? We provide migration support, role-based training, and a dedicated success partner to configure your policies and timelines. Rollout is sequenced around your academic calendar, and the timeline is agreed during scoping based on your data complexity. ### How do we get started? Book a guided demo. We map your workflows, share a rollout plan, and align on timelines and commercial terms. After discovery you receive a written proposal with the licence, any optional lines such as custom integrations, the training schedule and go-live milestones. ### What data can be migrated from our existing systems? We support migration of student records, fee history, attendance data, academic records, staff information, and communication history. Our team works with you to map your existing data structure to SquareCampus and validates the migration with a parallel run before go-live. Migration is included in Pro and Enterprise. If your current system lacks data SquareCampus needs, or it is too fragmented to reconcile, we show you what cannot move before go-live. ### What modules are included in SquareCampus? Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Available modules, workflows and deployment scope are confirmed before activation. A plan entitlement does not imply that an unreleased capability is available. ### Will it integrate with our existing systems? Where they offer a documented API, usually yes — as scoped work. SquareCampus does not publish a catalogue of pre-built connectors. Connecting another system is scoped work: we assess each tool during discovery, and what connects, in which direction, how often and at what cost is confirmed in writing before any build. ### Can we build our own frontend or mobile apps on SquareCampus? Development API access and supported interfaces are assessed during discovery. Authorisation, compliance review, commercial eligibility and delivery scope are agreed before development; a complete API surface for every workflow is not assumed. ### Do you have mobile apps? Standard SquareCampus parent and staff mobile-app access is included in every plan at no additional charge. Supported app workflows, devices, languages and delivery readiness are confirmed before activation. White-labelled apps are a separately quoted enhancement, with founding-partner treatment governed by its own agreement. ### Can we customize workflows and forms? Available workflow and form configuration is reviewed during scoping against the institution's policies. Supported options, extended branding and any bespoke engineering are distinguished in the proposal before activation. ### How does the multi-campus feature work? Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. Plans differ in agreed messaging and AI allowances, analytics depth, workflow sophistication, identity and integration options, customisation and advanced governance. Standard implementation and support remain included in every plan; any custom SLA is separately agreed. Specific inclusions and consumption limits are documented in the proposal. ### How often is the product updated? Updates ship continuously, covering new capabilities, performance improvements, and security patches. Releases are planned to avoid disrupting school hours, and admins are notified of significant updates through in-app announcements. ### How secure is our data? Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. Security documentation and implementation details are shared during the security review process. ### Where is our data stored? The platform is designed with an India-first hosting posture, keeping institutional data in an Indian cloud region. Hosting details and backup design are documented and shared during security review. ### What compliance standards do you follow? SquareCampus is designed with privacy-by-default principles and to support institutions' obligations under the IT Act 2000, the DPDP Act and education-sector requirements. Retention, preservation and export are handled as set out on our Data Retention page, which separates what is available today from what is still being built. ### Can we control who sees what data? The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone. ### What happens to our data if we leave? The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. Your institution owns its data. What happens at the end of a contract is set by your agreement and the Data Processing Addendum: data is returned where export is agreed, or deleted or anonymised, subject to what the law requires to be kept. Export scope, formats, timing and any charges are agreed in the order form. ### Can an institution use normal SquareCampus credentials? Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Single sign-on is optional. ### Does Pro support institutional single sign-on? Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. The institution chooses the sign-in mode: SquareCampus-managed credentials, subject to deployment readiness; Credentials alongside institutional single sign-on, where supported by the agreed configuration; Institution-enforced single sign-on, where the institution's policy requires it and the configuration supports it. ### Does SquareCampus access our Outlook or Microsoft 365 data? No. Standard Microsoft Entra ID sign-in is used to authenticate identity. Access to email, files, Teams, SharePoint or other Microsoft Graph data is not required for sign-in. ### Does single sign-on automatically create and remove users? No. Single sign-on authenticates users. Automated provisioning, deprovisioning and joiner-mover-leaver lifecycle controls are identity governance requirements scoped under Enterprise rather than part of SSO. ### What identity governance does Enterprise add? Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone. ### Can Starter request Microsoft Entra single sign-on separately? Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. ### Where is the complimentary launch pilot focused? Initial launch outreach focuses on Kotdwara and surrounding areas. Enquiries are reviewed individually; this outreach focus is not a published geographic eligibility restriction. Modules, workflows, deployment coverage, institutional counterparts and documented success criteria are agreed before activation. ### Can we buy an enhancement without changing our entire plan? Where availability and eligibility are confirmed, an enhancement can be quoted separately. Included entitlements, additional consumption, professional services and any eligibility conditions are distinguished in the proposal. Contact sales to assess your requirement. ### Is pricing public? The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. One annual institutional licence, calculated on progressive student-volume bands and shaped by the plan (Starter, Pro or Enterprise), the institution's complexity and its deployment profile. ### What is included, and what is scoped separately? Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. The licence covers the plan's platform capability, the standard SquareCampus parent and staff mobile apps, self-serve reporting, implementation and support, and a monthly usage allowance. Pro and Enterprise also include data migration. Migration on Starter, custom integrations and engineering, fixed-format documents made for one institution, private-cloud or on-premises deployment, a custom SLA and usage beyond the allowance are quoted as their own lines, not folded into the licence. There is no hidden module wall inside the licence, and every separately scoped line appears in the proposal before you sign. ### What happens as enrolment grows? Billable enrolment is the active enrolled students agreed in the order form. The per-student rate falls as enrolment moves up through the volume bands; growth is reconciled through an agreed true-up, and reductions are normally considered at renewal. ### Is SquareCampus appropriate if we only need attendance and fees? Usually not. SquareCampus is priced for institutions that want governance, workflow ownership, exception management, visibility and auditability. To one that needs only the cheapest attendance, fees and report-card product it will look expensive — and that reading is correct. ### How many Founding Institutional Partner positions exist? 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. Under the executed agreement a Founding Partner receives defined roadmap influence, a protected 40% discount on Enterprise commercial terms, white-labelled mobile apps without the standard white-label charge, and any other privileges explicitly agreed. ### Is the mobile app charged separately? No. The SquareCampus parent and staff mobile apps are included in every plan at no additional charge. A white-labelled Android and iOS build, published under your institution's own branding and store listings, carries a single charge that covers the entire agreed term, whether that is one year or many. Founding Institutional Partners receive the white-labelled build without the standard white-label charge. ### What about support after launch? You get a named success partner, live chat/email support during business hours, and proactive health checks. We help with new session rollovers, audits, policy tweaks, and any questions that arise. Implementation and support are included in every plan; only a custom SLA, such as 24×7 cover, is quoted. ### How is value measured? SquareCampus publishes no measured outcomes. A pilot is designed to measure one agreed metric against a written baseline: for example, days between an attendance threshold breach and a recorded follow-up, or the time from collection close to a reconciled position. The value case is specific to the institution and is judged on that evidence, not on a vendor's percentage. ### Is there a trial or pilot option? Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. Messaging, AI, storage, integrations and external-service consumption have defined boundaries agreed before activation. Custom development, bespoke integrations and unrestricted engineering support are not included. Any separately chargeable work or consumption must be agreed in writing. Subscription pricing is communicated before pilot activation, with a commercial review before the 90-day pilot expires. At completion, the institution chooses to subscribe or discontinue. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges. Still deciding? ## Bring the unanswered questions to a guided demo. We map your current stack, show how the operating model changes daily work, and answer the specifics for your institution. [Book a demo](https://squarecampus.com/demo/) · [Explore the platform](https://squarecampus.com/platform/) --- Source: https://squarecampus.com/demo/ --- title: "Book a School Management Software Demo | SquareCampus" description: "Book a guided SquareCampus demo and see how the School OS maps to admissions, academics, finance, communication, and institutional operations." canonical: https://squarecampus.com/demo/ describedby: https://squarecampus.com/llms.txt --- Book a demo # See SquareCampus with your school’s workflows. A guided session built around the workflows you choose and how your institution runs them today. You leave knowing where SquareCampus would fit and what a first rollout would involve. For schools, school groups and trusts in India. Useful for principals, trustees, administrators, finance and IT. Covers rollout and how SquareCampus would sit beside what you already run. Considering the Founding Institutional Partner programme? It has its own diagnosis request. [Request a partnership diagnosis](https://squarecampus.com/launch-partners/#request-diagnosis) Book a demo ## Tell us what to cover. Name the areas that matter most — admissions, attendance, fees, exams, parent communication or reporting — and the session is planned around them. What the session covers ## Your workflows, your questions, your next step The session is planned around the workflows and systems you describe in the form. ### Platform walkthrough The workflows institutions compare vendors on — admissions, academics, fees, communication, visibility and controls — shown against the areas you chose. ### Where it would sit Bring your current systems, spreadsheets or pain points. We map where SquareCampus would sit beside them, and what a first rollout would realistically involve. ### The right people in the room Principals, trustees, operations, finance and IT usually care about different things. The session can be structured around each of them. ### Rollout, honestly Go-live sequencing, training, what stays in place while adoption happens, and what your institution would need to do to move responsibly. After the session ## A clear next step. Your team should know where SquareCampus would sit against the systems you already run, what a first rollout would involve, and what a proposal would need from you. [How pricing works](https://squarecampus.com/pricing/) Where SquareCampus would sit beside the systems you already run. What a first rollout would involve around your academic calendar. What a proposal needs: enrolment, campuses and the workflows in scope. --- Source: https://squarecampus.com/contact/ --- title: "Contact | Registered Office and Enquiries | SquareCampus" description: "Registered office, corporate identity, and contact channels for Fairhelm Systems (OPC) Private Limited, the company behind SquareCampus." canonical: https://squarecampus.com/contact/ describedby: https://squarecampus.com/llms.txt --- Contact # Talk to the company behind SquareCampus. The right mailbox for what you need, a demo when you are ready to see the system, and the company's registered particulars. Reach the right desk Sales and general enquiries [contact@squarecampus.com](mailto:contact@squarecampus.com) Customer support [support@squarecampus.com](mailto:support@squarecampus.com) Privacy and data requests [privacy@squarecampus.com](mailto:privacy@squarecampus.com) Press and media [press@squarecampus.com](mailto:press@squarecampus.com) Evaluating SquareCampus? A guided walkthrough is the fastest way to judge whether the system fits how your institution actually runs. [Book a demo](https://squarecampus.com/demo/) · [See pricing model](https://squarecampus.com/pricing/) Registered office FAIRHELM SYSTEMS (OPC) PRIVATE LIMITED No. 33, 4th Floor, 1st Main, Road 3, Ganganagar, R T Nagar, Bangalore North, Bangalore – 560032, Karnataka, India **CIN** U62099KA2026OPC225579 **Incorporated** 5 August 2026 **GSTIN** 29AAHCF1819L1ZA **GST registered** 22 September 2026 **Telephone** Email is the fastest route to us today. Incorporated in India on 5 August 2026 under the Companies Act, 2013 · One Person Company. These particulars are published under section 12(3) of the Companies Act, 2013.