Model the school
Set the identity, class ladder and term structure from the records your team already uses.
Bring admissions, fees, feeding, attendance and terminal reports into one dependable system for the office, the classroom and the family phone.
Nothing has been written. Read the classes, the pupil counts and the money, then go on to step 3.
A pupil should not become a different spreadsheet when the day moves from class to office. EduControl keeps the thread intact.
Akosua is entered once — her class, her guardian, her term calendar. Nothing after this asks for her details a second time.
See this stepOne run issues her invoice alongside 407 others, after the whole thing has been previewed and nothing has been written.
See this stepBasic 4 A is marked in the classroom on a teacher’s phone, and it holds on the device until the signal comes back.
See this stepFeeding is planned against the days she is actually in, so the kitchen and the bill both follow the real calendar.
See this stepMarks, remarks and class positions are checked, then published as a snapshot that reprints identically next year.
See this stepBalance, receipts, attendance and results, in a browser, with nothing for the family to install.
See this step01 of 6 · before the term
Staff see the pages they need to finish the day. Families see only what the school has made available to them.
Preview a billing run, issue immutable invoices, allocate payments by fee type, and correct errors without erasing history.
Explore bursar workflowsA register is taken standing up, often on weak data. If the product fails there, the school goes back to paper. So this workflow starts with the hard conditions.
Offline where it mattersAttendance queues locally per class and day, then syncs when a signal returns.
Pesewas all the way downMoney is stored as whole pesewas and formatted in GHS only at the screen edge.
Isolation is structuralEvery school-scoped table carries a tenant and database policies enforce the wall.
The real Ghanaian termFees, feeding and attendance follow actual school days and three-term calendars.
We begin with the school’s real calendar, class ladder and approved fee sheet. That keeps setup practical and makes the first live day familiar.
Your working records become the starting point, so setup feels like recognition rather than reinvention.
How implementation worksSet the identity, class ladder and term structure from the records your team already uses.
Review pupils, guardians, approved fees and discount rules together before anything goes live.
Give each person the right access, then begin with workflows that already feel familiar.
This is the head teacher’s dashboard, drawn with the components the application itself uses. Collection measured against what the term actually billed, ten days of registers, and the pupils who need a word before assembly.
Collected week by week since the run was issued
A 30-minute walkthrough using your class ladder, fee types and term calendar—not a generic slide deck.