In Turkish schools the software conversation usually starts from the wrong question: "we already have the ministry’s e-Okul, why add another system?" The better question is which work e-Okul actually does, and which work still runs on spreadsheets, WhatsApp and paper. This article draws that line and says where to start.
A school management system doesn’t replace the ministry’s records
e-Okul is the Ministry of National Education’s official record system: a student’s formal enrolment, grades and absences live there and stay there. Software of your own doesn’t take that over. What it does is gather the daily work the official record doesn’t cover: your own mock exams, homework tracking, parent communication, transport and canteen, fee collection and teacher duties.
We know of no public connection that pushes data into e-Okul from outside. So if a vendor promises automatic transfer between the two, ask in detail how it would work technically. The realistic setup is two systems running separately, with the work divided so that as little as possible has to be typed into both.
Which data is authoritative where?
The way out of double entry is to name a source of truth for each kind of data. If a piece of information sits in both systems, write down at the start which one wins. The split below is a typical starting point in schools.
| Data | Source of truth | Why |
|---|---|---|
| Enrolment, report-card grades, official absence | e-Okul | The record with legal effect lives there |
| Your own mock exams and learning-outcome analysis | Your system | e-Okul does not produce this analysis |
| Homework, study sessions, in-house attendance | Your system | Daily tracking and parent updates come from here |
| Parent communication and message history | Your system | Who was told what, and when, has to stay on record |
| Fees, instalments and balances | Your system or your accounting software | The finance side is the school’s own business |
| Transport and canteen | Your system | Daily operations, with no bearing on official records |
Four things that make schools different from tutoring centres
School and tutoring-centre software overlap in most modules; they part company over the timetable and the class structure. A school day is divided into periods, and each period has its own attendance, teacher and room.
The timetable
Classes, teachers and rooms have to be scheduled without clashes, and a change in the timetable ripples into attendance, homework and parent updates.
Attendance by period
Attendance every period rather than once a day. A teacher has to be able to do it in ten seconds, or it won’t happen.
Marks and reports
Written, performance and project marks gathered across the term. The official report card comes from e-Okul; your system holds the working record behind it.
Transport, canteen, fees
The operations a tutoring centre doesn’t have. They usually sit outside the first version and arrive in a second phase.
Where should a first version start?
Pick the work that repeats most often in a term and is done most by hand. In schools that is usually one of two things: analysing mock-exam results, or the updates that go to parents. Both run on spreadsheets and WhatsApp today, both repeat every week, and both end up in front of a parent.
- 01
Start with one flow
2-4 weeksBuild the path from a mock-exam result to the parent report. The teacher’s and the admin’s screens are designed around that flow.
- 02
Pilot with one year group
The system runs on real data with a single year group first. Screens that slow teachers down get simplified here.
- 03
Add attendance and homework
Once the flow settles, attendance by period and homework tracking follow. Parent updates are generated from the same record.
- 04
Finance and operations
Fees, transport and the canteen come last. They don’t stop a school, but putting them in the first version stretches the project.
What we learned from our own product
We built Hippotenus around the day-to-day running of an education institution: it analyses mock-exam results at learning-outcome level, surfaces the topics a student is weak on, and ties homework and student tracking to the same record. Admins, teachers, parents and students all see the same data. It runs on a pool of more than 300,000 questions with over a thousand active users.
Three lessons from it apply just as well to client projects. First, each role needs its own screen: an admin comparing the whole institution and a parent looking at one child do not fit on the same page. Second, a system that pushes data entry onto teachers gets abandoned; what you ask of a teacher should be a few taps. Third, payments and subscriptions hurt when they are bolted on late. We built the virtual POS and subscription payments in Hippotenus with iyzico, and learned that this part belongs in the plan from the start.
An off-the-shelf package or software of your own?
For a single-campus school running in a standard way, a ready-made school management package is often enough and costs less. Custom software earns its place when you have your own mock-exam system, your own report formats, several campuses, or an accounting setup the package can’t connect to. We say plainly on the first call which one suits you; our projects start at US$1,000 and below that we recommend a ready-made product.
Cost and timeline guide
Budget bands, rates by role and the timeline for each scope tier, on one page.
Software for education
Student tracking, mock-exam analysis, homework and parent updates; our industry page.
Frequently asked questions
Do we need another system when we already have e-Okul?
e-Okul holds the official record. In-house mock-exam analysis, homework tracking, parent updates, transport and fee collection are outside it. If that work runs on spreadsheets and WhatsApp today, a system of your own helps. If it runs fine, there is no hurry.
Will we type the same data into two systems?
Some of it, yes, and it is better to accept that up front. You reduce double entry by naming a source of truth for each kind of data and keeping your own system from becoming a copy of the official record. The table above shows a typical split.
Will teachers actually use it?
That depends on how long it takes them. If attendance and homework take a few taps, it gets used; if it turns into form-filling, it gets dropped. What we measure in design is how many seconds one task takes.
How long does it take and what does it cost?
A first version with one flow is working in 2-4 weeks and sits in the US$3,500-9,000 band, excluding VAT. Roles, a parent portal and integrations push it to 6-12 weeks and the US$9,000-25,000 band.
Can we switch mid-term?
You can, but it is not what we would suggest. Timing the switch for a few weeks before term starts, or for the mid-year break, makes both the data migration and the teachers’ adjustment easier.