School Management System and Parent App: What to Build First, and What It Costs

Most private schools don't lack technology. They have too much of it, in too many places: a WhatsApp group per class, a fee spreadsheet in the accounts office, SMS for absences, a ministry system for grades, and printed notices that never make it out of the school bag. Parents don't know where to look, and teachers send the same message three times.

A school management system should reduce that noise, not add one more login. This page is for owners and principals of private and international schools, nurseries and learning centers in the Gulf, Egypt and beyond. It covers how to decide the first version, what to leave for later, how to handle government systems and children's data, and what it costs.

Design for three people, in this order

The parent opens the app for under a minute and wants an answer: did my child arrive, is there homework, is there an announcement, what do I still owe? With two or three children at the school, they want to switch between them in one tap.

The teacher wants to take attendance in under a minute at the start of a lesson, post homework to a whole class once, and enter grades without typing them twice.

The administration wants the whole picture: attendance by class, fees collected and overdue, which announcements were read, and the reports the authorities ask for.

Design for the parent first and the system gets used. Design only for the office, and it becomes something staff type into and nobody reads.

The first version: what goes in, what waits

Direct parent–teacher chat looks like a small feature, but it changes a teacher's job: messages at night and on weekends, with an expectation of instant replies. Many schools prefer messages routed through the office, or set reply hours. Decide the policy before we build it.

Government systems: complement, don't duplicate

In many countries, the ministry of education runs an official system for student records, attendance and grades. In Saudi Arabia, for example, that's the Noor system. Your school system does not replace the official one, and it shouldn't make teachers enter the same data twice.

In practice we:

• agree with you exactly what is entered in the official system and what goes into yours;
• build tools to reduce double entry where the official system allows exports or file imports;
• otherwise focus your system on what the official one doesn't do: parent communication, fees, announcements and day-to-day follow-up.

We won't promise an automatic connection to a government system until we've confirmed it's available and permitted.

Children's data needs stricter rules

A school system holds data about minors: names, photos, addresses, grades, behavior notes and sometimes health information. The rules we apply:

• Each parent sees only their own children; each teacher sees only their classes.
• Photos and attachments are stored privately, and class photos are never public.
• No ads and no marketing trackers in an app for parents and students.
• Behavior and health notes sit behind narrower permissions than the rest.
• A clear privacy policy and parent consent at registration.

Data protection laws in Saudi Arabia, the UAE, Egypt and elsewhere apply to this data, and the school is the party responsible for it. We build the controls, explain them, and help you write the requirements into the scope. For Saudi schools, our guide to the Saudi PDPL for app owners is a useful start.

Parent app or web portal?

For parents, an app has one real advantage: push notifications. An absence alert that arrives within minutes matters more than any other screen.

• A small school or learning center: a mobile-friendly web portal with SMS or WhatsApp notifications is enough to start.
• A school with hundreds of students: a parent app on both stores, with a web dashboard for teachers and the office.

The middle path is to build the full web system for staff first, then add the parent app on the same data without redoing anything. Our web app vs mobile app guide explains the trade-offs.

Fees and online payment

Showing fees due and paid, with receipts parents can download, saves the accounts office a lot of calls. Online payment can be added through a local payment gateway in the school's name, chosen for your country. One note: we don't build late-payment charges that grow as a percentage over time, or installment plans with interest. Splitting fees into fixed installments is normal and is what we recommend.

A launch plan that fits the school year

1. Scope in spring or early summer, when staff have time to answer questions.
2. Preview within 72 hours, tested by a few teachers and parents.
3. Import student and parent data from your spreadsheets; if it's organized, this is usually included and stated in the scope.
4. Pilot with one grade or section a few weeks before term starts.
5. Roll out at the start of the year, with a short registration push from the school itself. Mid-term launches rarely go well.

What our experience is based on

We haven't published a complete school management system in our portfolio yet. The closest thing we've built is Lawh Academy, a Quran and Arabic learning platform with a student app and a tutor app, live on both stores: lesson progress, session booking, tutor calendars and availability, and a tutor dashboard, with the admin behind it. Those pieces are very close to a school's daily follow-up.

We also built the website of Strathclyde International College in the UK, with programs, certificate verification and enquiries. If your project is closer to an online academy or tutoring service than a school, see e-learning platform development, and for booking classes or sessions, booking app development. A school system can also grow into part of a wider back office; see custom ERP development.

Prices and timelines

We price in USD; local amounts are approximate.

Every project starts with a written scope and fixed price; projects over $500 start with a 30% down payment, then 40% and 30% at milestones, each paid after you see it working. For what drives the cost of bigger systems, read how much an ERP costs.

When we're not the right fit

• A public school or a school network that needs a formal tender and a locally registered vendor.
• A school well served by ready-made school software on an annual plan. Ask for a trial first; if it covers your needs, it's the cheaper choice.
• A project that needs a team on campus to train teachers in person on an ongoing basis. We work remotely and train over video calls and written guides.

FAQ

Can one parent follow several children?

Yes, and it's a core part of the design. A parent sees all their children in one account and switches between them, and every notification names the child it's about.

How does a teacher take attendance quickly?

The class list opens with everyone marked present, and the teacher taps only the absent students. It takes under a minute, and the absence notification can go to the parent right after.

Does it work in Arabic and English?

Yes. International schools often need both, and each parent chooses their language. We build the Arabic interface properly from the start, with right-to-left layouts, not as a translation added later.

Can we add bus tracking later?

Yes, as a later phase: an app for the bus supervisor or driver sends the location, and parents get a notice as the bus approaches. We've built live map tracking before in the DriveX rider and captain apps, but it's added scope with its own cost.

Who owns the student data?

The school does. The database, hosting and code are set up in the school's name from day one, and we sign an NDA before you share details if you'd like.

How do I start?

Tell us the number of students and stages, the systems the school uses now, and what parents complain about most. Within 24 hours you'll get a written scope and fixed price, free and with no obligation. You can start with the project planner.