How Bright Horizons School Group Digitized Admissions, Attendance, and Fees Across 3 Campuses

Bright Horizons School Group runs three campuses across Bengaluru, but until early last year, those three campuses operated like three completely separate businesses. Each one kept its own paper admission files, its own Excel sheets for attendance, and its own fee ledger — and none of it talked to each other. When the group's leadership asked a simple question like "how many seats are open across all campuses this term?", getting an answer meant phone calls to three different front-office coordinators and a few hours of manually reconciling spreadsheets.

The pain was sharpest during admissions season. Every application arrived as a physical form, was manually entered into a campus-specific spreadsheet, and then cross-checked by hand against available seats — a process that stretched to nearly three weeks per intake cycle. Attendance wasn't much better: 140+ teachers marked paper registers every morning, which admin staff then re-typed into Excel at the end of each day, introducing errors and a 24-hour lag before anyone could act on an attendance concern.

Parents felt the disconnect most directly. There was no way to check a child's attendance, see term grades, or confirm a fee payment without calling the school office directly — and during peak admission or exam season, those calls could mean a 15-20 minute hold. Report cards, meanwhile, were compiled manually in Word documents by teachers, consuming two to three full working days every term that could have gone toward actual teaching.

We started by spending three weeks physically embedded across all three campuses — sitting with front-office staff during live admissions, watching teachers mark attendance, and following a fee payment from collection to reconciliation. That groundwork mattered more than any line of code: it surfaced edge cases (sibling discounts, mid-term transfers between campuses, partial fee waivers) that a requirements document alone would have missed.

The result was a single, unified school ERP built around six core modules: online admissions with automated seat allocation, RFID-based attendance capture that syncs in real time, structured fee management with an integrated payment gateway, a digital gradebook that generates report cards automatically, a parent-facing mobile portal, and a group-wide dashboard for school leadership.

Rather than launching everything at once, we shipped in priority order — admissions first, timed to be ready ahead of the next intake cycle, followed by attendance and fees, and finally the parent portal. We piloted the complete system on the flagship campus for six weeks, running it in parallel with the old paper process, before rolling it out group-wide. That parallel-run caught a handful of edge cases in fee proration that would have been painful to fix after a full launch.

Training was deliberately hands-on and small-batch: rather than one big rollout session, we trained front-office staff and teachers at each campus in small groups, backed by a dedicated support hotline for the first month. That investment paid off — the system carried the school group through its first full admission and exam cycle without a single reported data-loss incident.