Project Details
Home/Project Details
EduCore
Project description
School administration that survives term start
The Challenge
A school runs on registers, records and reports that are produced by hand each term. Enrollment, attendance and results are three separate books, and the question a head teacher actually asks — how is this student doing — requires reading all three.
The people using it are teachers and administrators, not software operators, and they are using it between classes. Anything that adds steps to a register is abandoned by the second week, so entry has to be faster than the paper it replaces.
The Solution
One student record that attendance, results and enrollment all relate to, so the report is a view rather than a compilation. The interface is organised by the task a staff member is doing — take the register, enter results, look up a student — rather than by the database table underneath.
Skills and deliverables
Features delivered
The hard part
Getting the data model right for a domain with genuinely irregular rules: a term is not a month, a class is not a year group, and a student can belong to several groupings at once. Modelling those honestly at the start is what stops the reports being wrong later.
The Impact
Deployed with students, staff, attendance and records running together. It is a SaaS build with the multi-tenant model behind it rather than a single-school install.
