Multi-campus management: one picture of every location
Admissions, academics, fees, and daily operations across several campuses — built for staff who are not IT specialists and have no time to be trained.
every stage measured, per campus, by staff who are not IT
- Campus and institution ERP
- Admissions management
- Learning platforms
- Best when
- Several campuses run on separate systems, and staff have no time to be trained.
- Not a fit when
- A single campus already served by a product that fits.
- First thing you get
- Admissions and fees live for one campus, then the roll-up.
What is a multi-campus school ERP?
A multi-campus school ERP is administration software that runs admissions, academics, fees, scheduling and communication across several campuses from one system, with a combined view for management. It is used by teachers, office staff and parents with no time for training. We build it to keep campuses consistent without forcing them to operate identically.
This software is used by people with no time and no appetite for training — teachers between classes, office staff at the start of term, parents on a phone. If a task cannot be completed quickly and obviously, it will not be completed at all.
We build for that on both sides of it: administration systems that keep a campus running, and learning platforms that deliver content and live classes to students. The hard part is rarely any single feature — it is keeping several campuses consistent without forcing them to operate identically.
What this includes
- 01
Campus and institution ERP
Admissions, academics, fees, attendance, and daily operations across multiple campuses.
- 02
Admissions management
Enquiry capture through follow-up to admission, with conversion actually measured.
- 03
Learning platforms
Course delivery, study material, and progress tracking for students.
- 04
Live classes
Scheduled live sessions students join from web or a phone.
- 05
Fee management
Fee structures, collection, outstanding balances, and online payment.
- 06
Parent and student apps
Mobile access to attendance, results, fees, and communication.
Situations we see most often
Multiple campuses, multiple systems
Each branch running differently, with group-level reporting assembled by hand.
Enquiries go cold
Enquiries arriving with no tracked follow-up and no measured conversion.
You are adding online learning
Extending to recorded courses and live classes alongside in-person teaching.
Fee collection is manual
Reconciliation by hand and no clear picture of outstanding balances.
What to know before you start
How do you keep campuses consistent without forcing them to be identical?
Shared structures with local settings. Admissions stages, fee heads, academic terms and reports follow one group-wide model, so management gets comparable numbers. Each campus then configures what genuinely differs, such as timetables, local fee items or holidays, without breaking the roll-up.
Campus staff see only their own campus; group-level roles see everything, side by side.
How are admissions enquiries kept from going cold?
Every enquiry, whether from the website, a phone call or a walk-in, lands in one pipeline with an owner and a next step. Follow-ups are scheduled automatically, parents get timely messages, and counsellors see which enquiries are waiting on them.
Management sees conversion by campus, source and stage, which shows where families drop off and which marketing actually brings admissions.
How do online learning and live classes fit with administration?
In the same system, so they share students, classes and timetables. Live classes are scheduled against real sections, attendance is captured automatically, and recorded sessions and materials are available to the students who should see them.
Teachers do not maintain two lists of students, and parents see academic progress and attendance in one place.
How is fee collection automated?
Fee structures are defined per campus and class, invoices and reminders go out on schedule, and parents pay online, including by UPI. Receipts are issued instantly and payments reconcile against fee records automatically, so the office no longer matches bank statements by hand.
How do parents stay informed?
Through a parent app and messages tied to real events: attendance marked, results published, fees due, a circular issued. Parents see their own children's information in one place, and staff send announcements to a class, campus or the whole group in a few taps.
Fewer phone calls to the office is usually the first change schools notice.
What drives the cost of a multi-campus school ERP?
Cost follows the modules you need and how differently your campuses work. These factors move it most.
| Factor | Effect | Why it matters |
|---|---|---|
| Modules | High | Admissions, academics, fees, timetables, communication and learning are each substantial modules. |
| Campus variation | High | The more campuses differ in fees, schedules or processes, the more configuration the system needs. |
| Learning platform and live classes | Medium | Content delivery and live classes add video, scheduling and attendance capture. |
| Parent and student apps | Medium | Mobile apps for attendance, results, fees and messages add clients to build and maintain. |
| Data migration | Medium | Moving student records, fee history and balances from existing systems needs careful reconciliation. |
| Payment integration | Low | Online fee payment with UPI and automatic receipts is well understood and modest to add. |
What a typical engagement looks like
- 011–3 weeks
Discover
Process map
- 022–4 weeks
Design
Interactive prototype
- 03two-week cycles
Build
Working software each cycle
- 04ongoing
Ship & support
Automated pipeline
What we build it with
- Platform
- WebParent and student appsLive classes
- Payments
- Online fee paymentUPIReceipts
Where we have done this
Questions we get asked
01Do we have to start from nothing?
No. We have built multi-campus administration and learning delivery before, so the common ground — admissions, fees, academics, live classes — is well understood. What differs between institutions is configured rather than rebuilt.
02Can it handle multiple campuses under one group?
Yes — multi-campus is the default model rather than an add-on. Records are scoped per branch, and group-level roles see the combined roll-up without campus staff seeing each other's data.
03Can parents and students get mobile access?
Yes. Attendance, results, fees, and communication are available through mobile apps, which is where parents actually check them.
04Is it easy for teachers and office staff to use?
That is the main design constraint. Frequent tasks, such as marking attendance or recording a fee, take seconds and need no training, because the people using it have no time to learn software.
05Can we roll it out one campus at a time?
Yes, and we recommend it: admissions and fees live at one campus first, then further campuses and modules, with the group roll-up growing as each joins.
06Does it support board-specific report cards?
Yes. Grading schemes, assessment structures and report card formats are configured per board and class, so CBSE, state board and other curricula can run side by side across campuses.
07Can it manage transport and hostels?
Yes, as optional modules: routes, stops and student assignments for transport, and rooms and allocations for hostels, linked to the same student records and fees.
08Can each campus have its own branding on documents?
Yes. Receipts, report cards and letters can carry each campus's own details and logo, while the group's records and reports stay consolidated underneath.
Adjacent capabilities
Tell us what you are building.
Share the problem and we will come back with an approach, a rough shape of the work, and what it would take to deliver it.