Schools add each campus once in a single system, give staff rights only to the campuses they need, and switch campus from the top bar to see campus-wise reports. Owners can view every campus or all of them combined.
What does multi-campus school management mean?
A school group with several branches has two problems at once. Each campus needs its own classes, staff and routines. The head office needs one reliable picture of admissions, fees, attendance and cash across all of them.
Running a separate system or spreadsheet per branch solves the first problem and breaks the second. A single system with campus as a built-in setting solves both: the data is entered once, filtered by campus, and combined when the owner wants the whole view.
How are campuses, classes and sections set up?
In EDUBase, School Setup & Multi-Campus is where this starts. You can add any number of campuses, and each one has its own settings, SMS device and bank routing.
You then decide which classes run at which campus and which sections each class has. Sessions, the optional Academic Duration and the reference lists used by the admission form are set once and reused everywhere.
- Campuses and cities, each with its own settings
- Classes, sections and campus-classes, so each branch runs only its own classes
- Sessions and the Holiday Calendar shared across the school
- Admission Capacity and Roll Number Series, set per class or per section
How do staff move between campuses without seeing everything?
Access is controlled in Users, Privileges & Activity Log. Rights are granted per user, per screen and per action, and a user sees only the campuses granted to them.
Staff with rights to several campuses switch from the navbar. Owners see all campuses. A vice principal at one branch can therefore work on their own students and fees without opening another branch's records.
The User Logging page records who created, changed or deleted a record, so head office can check activity at any campus.
How do admissions, fees and attendance work across campuses?
Students are admitted into a campus and class, and can be moved later. Batch transfer and promotion lets you move students between sections and campuses in one action, so nobody is retyped. Siblings can be linked under one family number even when fee vouchers and payments are handled per family.
Fee challans can be generated for a campus, a class or the whole school. Fee automation can use campus and class scope for scheduled generation. Bank collection is enabled per school and per bank, and campus bank routing is part of campus settings.
Attendance follows the same logic. Bulk attendance marks several classes or the whole campus on one screen, and geo-location attendance lets you pin each campus on a map with a radius for staff marking from the Teacher App.
- Admit to a campus, then transfer in one action when needed
- Generate challans per campus, class or the whole school
- Each campus can use its own SMS device, sending campus by campus
- Pin each campus on a map for staff geo-attendance
How does the owner see all campuses together?
The Owner Dashboard & Reports page and the Owners App show today's income, expenses and net balance, attendance percentage, new admissions and leavers, fee defaulters and staff attendance. You can switch campus or view all of them.
Approvals can also be handled on the phone, including advance salary, increments, salary plans and leave. For school groups, white-label parent apps are available on Google Play.
What about data safety across branches?
Every school has its own separate database, so your records are never mixed with another school's. Campuses within your group share that one database, which is what lets group-wide reports work. Staff sign in with the school code, a username and a password, and parents log in with a one-time code.
How should a group move its campuses onto one system?
Start with School Setup so campuses, classes and sections are correct. Then load students from the Excel template, with campus and fee details included. Grant campus-wise rights before staff begin work. The EDUBase team handles the first upload during onboarding, and old dues can be loaded so the first challan is right.
Separate branch systems compared with one multi-campus system
| Criterion | Separate system per branch | One system with campuses |
|---|---|---|
| Student records | Kept in different files or databases, hard to compare | One record set, filtered by campus |
| Moving a student between branches | Re-entered at the new branch | Batch transfer between sections and campuses |
| Staff access | Often shared logins or full access | Rights per user, screen and action, limited to granted campuses |
| Fee reporting | Collected manually from each branch | Campus-wise reports, or all campuses combined |
| Owner view | Wait for branch reports | Dashboard and Owners App with campus selection or all |
| Settings | Repeated for each branch | Shared sessions and lists, with campus-specific settings where needed |
| Audit trail | Different at each branch | User Logging shows who changed what |
Related modules
- School Setup & Multi-Campus — Campuses, classes, sections, sessions, academic year and reference lists, set once and reused everywhere.
- Users, Privileges & Activity Log — Give each staff member exactly the screens and actions they need, and see who changed what.
- Student Management & Admissions — Every student record, from first enquiry to leaving certificate, in one place.
- Fee Management & Challans — Fee plans, monthly challans, discounts, family payments and receipts, without spreadsheets.
- Fee Automation — Let the system generate challans, apply late fees and chase defaulters on schedule.
- Owner Dashboard & Reports — Daily P&L, collections, attendance and strength at a glance, on the web and in the Owner App.
- Bulk Data Import & Onboarding Tools — Move from registers or another system by Excel: students, fee plans, old dues and past payments.
- Cloud Hosting, Backups & Data Isolation — Your school's data in its own database, on managed cloud servers, backed up and monitored.