How to Manage a Nigerian School With Multiple Classes and Over 300 Students

There is a size threshold in Nigerian private schools where the informal systems stop working. Below roughly 150 students, a proprietor can know every child by name, the bursar can manage fees in a notebook without too much trouble, and the principal can keep track of which teachers showed up by walking the corridors in the morning.

Past 300 students that is no longer true. The school is now an organisation, not a community, and it needs to be managed like one.

The problems that emerge at this scale are predictable. Fee collection becomes genuinely difficult to reconcile. Parent communication breaks down because there are too many phone numbers to manage manually. Attendance data gets lost between what teachers record and what admin sees. Results take a week to compile instead of two days. New staff are added without a proper onboarding process.

None of this is a crisis but it compounds quietly. By the time a proprietor notices the school feels chaotic, the disorganisation has usually been building for two or three terms.

The Fee Problem at Scale

At 80 students, one bursar with a notebook can manage fee collection reasonably well. At 350 students across multiple arms, the same approach produces a mess. There are too many partial payments, too many informal arrangements, and too many students whose balance nobody is confident about.

The core problem is that a notebook is a write-only system. You can add entries but you cannot query it. You cannot quickly answer the question "how many students in JSS 2 have an outstanding balance this term" without manually reading through every entry and checking.

A school management system answers that question in two seconds. Every payment is linked to a student. Every student has a running balance. At any moment the bursar, the admin, and the proprietor can see the full fee picture — who has paid, who owes, how much in total is outstanding across the school.

For a school with 350 students where 40% have a partial payment situation, the difference between a notebook and a system is roughly 10 hours of reconciliation work per term versus about 20 minutes of reviewing a dashboard.

Attendance Across Multiple Classes

A school with 350 students might have 10 or 12 class arms. Getting reliable attendance data from all of them requires a process that works even when the class teacher is running late, distracted, or absent themselves.

Paper-based attendance in a large school has a specific failure mode: the register is filled in but nobody looks at it until something goes wrong. A child is absent for three days before anyone realises. A parent calls to ask why their child was marked absent on a day they were present and the school cannot find the register to check.

Digital attendance solves the visibility problem. When each teacher marks their class in the system, the data is immediately visible to admin. The morning attendance dashboard shows which classes have been marked and which have not. A class that has not been marked by 8:30am flags automatically. Parents of absent students get a WhatsApp message within minutes of the teacher submitting.

For a school this size, the attendance data is also the foundation of parent trust. A parent paying ₦300,000 per year in fees expects to know if their child did not come to school that day. At 350 students, manual phone calls to absent parents are not feasible. Automated WhatsApp alerts are.

Staff Coordination

A 350-student school typically has 15 to 25 teaching staff plus support staff. Keeping track of who is present, who is covering which class, and who is responsible for which subject across multiple arms requires more structure than most Nigerian schools build in.

The practical problems show up at specific moments. A teacher is absent and nobody covers the class because the vice principal assumed someone else would. A subject teacher teaches the wrong topic in one arm because there is no shared scheme of work. Two teachers give conflicting information to parents about an exam date.

The minimum viable coordination system for a school this size is: a digital staff list with roles and assigned classes, a shared academic calendar visible to all teaching staff, and a daily check-in that confirms who is present before the first period begins.

None of this requires sophisticated technology. It requires the data to exist in one place rather than in different people's heads.

Results at Scale

At 350 students, end-of-term result compilation is a significant administrative project. If each student takes 10 subjects and scores are submitted on paper, someone is manually entering 3,500 numbers into a spreadsheet or report card template. Errors are inevitable. The process takes days.

The alternative is a system where teachers enter scores directly — from their phone or laptop, subject by subject, class by class — and the system calculates totals, grades, and positions automatically. The admin reviews and publishes. Parents receive a WhatsApp notification and access the report card directly.

The time saving is not marginal. A school that previously spent four days on results can complete the same process in one day. The error rate drops to near zero because the arithmetic is handled by the system rather than by a tired admin person entering numbers at 10pm before results day.

The Parent Communication Problem

At 350 students you have at least 500 unique parent phone numbers. Sending a school announcement, a fee reminder, or an exam timetable to all of them manually is not possible. Some schools maintain a parent WhatsApp group but at this size those groups become unmanageable — hundreds of messages, parents responding to announcements with unrelated questions, important information buried under chat.

The right approach for a large school is one-way broadcast communication for announcements, and individual parent conversations for specific student issues. The school sends to parents — parents do not send to the school via the same channel. This keeps announcements visible and removes the noise.

A system that lets admin select a class, a year group, or the whole school and send a message to all relevant parents in one action — with delivery tracked — handles this without anyone maintaining a spreadsheet of phone numbers.

The Proprietor's Role Changes

In a school of 80 students the proprietor is often the most informed person in the building. At 350 students that is no longer true or sustainable. The proprietor needs to shift from being the person who knows everything to being the person who can see everything.

That shift requires data. Fee collections, attendance rates, staff punctuality, results trends — these should be visible in a dashboard, not in a conversation with the bursar. When the proprietor can see the data, they can manage strategically. When they have to ask for it, they are always reacting.

---

Akada is built for Nigerian schools at every scale — from 50 students to over 1,000. Attendance, fees, results, parent communication, and staff management in one platform.

Start your free term at getakada.com | View pricing for your school size