School software should connect each learner record to accountable operations
A school management platform brings admissions, enrollment, classes, attendance, assessment, guardians, fees, staff, timetables, documents and operational resources around a governed student record. It should reduce duplicate registers while preserving who may see, change, approve and report each item.
Authorized education leaders, teachers, finance, safeguarding, legal and administrative owners must approve admission, curriculum, assessment, progression, fee, attendance, privacy and disclosure rules. Software applies approved policy; it does not decide a learner’s eligibility, grade or welfare response independently.
Admissions, enrollment and student identity
- Applications, required documents, review, decision and acceptance
- Student identifier, name, date information and approved demographic fields
- Guardian or authorized contact relationships and communication preferences
- Campus, programme, grade, class, section, year and enrollment status
- Transfers, withdrawals, re-entry, completion and history
- Restricted health, safeguarding or support information where justified
Duplicate resolution and corrections need controlled evidence. The institution should identify which record is authoritative and how changes reach finance, attendance and reporting.
Academic structure, curriculum and timetable
The system can organize academic years, terms, grades, subjects, curriculum versions, classrooms, teachers, periods and timetables. Scheduling rules may detect conflicts, but school owners decide teaching assignments, room suitability, workload and approved exceptions.
Attendance, absence and follow-up
Attendance may be captured by authorized teachers or approved devices with date, class, status, reason and correction history. Notifications and escalation should follow the school’s policy and verified guardian channels. Attendance data should not be used for high-impact decisions without review, context and correction rights.
Assessment, marks, report cards and progression
Assessment definitions can include subject, component, weight, maximum mark, rubric, examiner and period. Marks may pass through entry, review, approval, publication and correction stages. Grade calculation, promotion, repetition and completion rules require academic authorization and version control.
A calculated total does not prove that an assessment is fair, valid or complete. Teachers and academic leaders retain professional responsibility.
Fees, discounts, collections and accounting
Where applicable, the platform can connect fee plans, installments, scholarships or approved discounts, invoices, receipts, refunds, outstanding balances and statements. Finance approves currency, accounting, waivers and write-offs. Academic access and learner welfare should not be changed by an automated balance rule unless authorized policy explicitly allows it.
Teachers, staff and responsibility
Staff records may connect roles, assignments, attendance inputs, leave, documents, training and payroll interfaces. Access should follow responsibility and separate academic, finance, safeguarding and system-administration duties. HRMIS and payroll can integrate without exposing unnecessary employee information to school users.
Communication, portals and documents
Student, guardian and staff portals can provide approved schedules, attendance, results, fees, notices and documents. Recipient identity, language, channel, consent or notice, delivery failure and sensitive-content rules need definition. Certificates, report cards and letters should use controlled templates and verification where required.
Library, inventory, transport and facilities
Optional modules may manage library loans, textbooks, uniforms, devices, consumables, classrooms, buses, routes, stops and maintenance. Student transport and custody information requires restricted access and clear handover procedures. Inventory and purchasing can connect with the institution’s approved finance controls.
Institution system and education-sector EMIS
A school ERP manages daily institutional operations. A ministry or sector EMIS may collect governed administrative data across many schools for planning and reporting. They are related but not identical. Any exchange should define official identifiers, required fields, reporting periods, validation, corrections, privacy and the responsible authority.
Implementation, migration and continuity
Implementation defines school types, academic structures, policies, roles, reports, languages, devices and integrations. Migration should prioritize current students, guardians, staff, enrollment, opening fee balances and required history after deduplication and approval. UAT should cover admissions, transfers, attendance corrections, result approval, fee adjustments, portal access and network interruptions.
Education-data reference
The distinction between institutional operations and sector reporting was cross-checked against UNESCO’s Operational Guide to Using EMIS to Monitor SDG 4, which emphasizes governed administrative data and data-quality processes. This is a planning reference, not UNESCO endorsement.