What a school actually needs before it buys an ERP
A school ERP demo is designed to impress a trustee. The system is then used, eight hours a day, by a fee clerk, a class teacher and an exam coordinator — none of whom were in the room. Almost every failed rollout we have been called in to rescue traces back to that gap.
2 min readOadbox
Count the registers before you count the modules
Walk the campus and list every register, ledger and spreadsheet currently in use. Not the ones the office says it uses — the ones actually being written in. In most schools the list runs past twenty: admission enquiry, fee day book, concession register, attendance, leave, substitution, transport route sheets, hostel mess count, library issue, exam marks, TC issue, staff attendance.
That list is your real requirement document. A module you cannot map to a register somebody is filling today is a module you are buying on speculation.
- Which register is written in daily, and by whom?
- Which one is reconciled at month end, and against what?
- Which one has ever been produced for an audit or an inspection?
- Which one exists only because a parent once complained?
Fees are the load-bearing wall
Every other module can go live late. Fees cannot. If fee collection is wrong for one term, the school loses trust with parents and the finance office quietly goes back to the old book — and once that happens, the rest of the rollout is dead.
Test the fee engine against your hardest cases before you sign, not after. Sibling concessions, staff-ward waivers, part payments across two heads, a mid-term transport route change, a late fee that the principal waived verbally, an RTE student whose reimbursement comes from the state. If a demo cannot model those in front of you, it will not model them in production.
The teacher decides whether it survives
Attendance and marks entry are the two things that must happen without training. A teacher between two periods has four minutes and a phone, not fifteen minutes and a desktop. If marking a section takes more taps than the paper register took strokes, teachers will keep the register and the office will key it in twice.
We measure this directly: time a real teacher marking a real section on the second day of use. Under thirty seconds and the system holds. Over two minutes and you have bought a data entry job for your office staff.
Ask what happens in year three
Board results, promotion, transfer certificates and alumni lookups all depend on data that was entered years earlier by someone who has since left. Ask to see a student record from a school that has been live for three years — the full history on one screen, not a report you have to request.
Ask, too, who answers the phone in March when the exam module misbehaves during board practicals. The answer to that question is worth more than half the feature list.
Eduplux was built against this order of operations — fees and attendance first, everything else inherited from the same student record.
Written by the Oadbox team. Something here not match how it works in your business? We would genuinely like to hear it — connect@oadbox.com.