Madrasa management software: what teachers and administrators use

A madrasa needs four things from one app: a private group for each class, a progress target for each child that only their parent can see, weekly assignments that accept audio recitation, and parent updates that arrive without anyone chasing. The National Resource Centre for Supplementary Education estimates there are several thousand supplementary schools in the UK teaching children outside mainstream hours — madrasas are a large, mostly volunteer-run slice of that, and almost none of them have the office a purpose-built management system assumes.

What does a madrasa actually need from management software?

The short answer: a private space per class where attendance, each child's target, the week's assignment, and the parent updates all live together, rather than spread across a paper register, a stack of progress cards, and a row of WhatsApp groups.

Most madrasas reach for software only after the admin starts to hurt. A class WhatsApp group for each set of parents, a staff group on top, a paper register, a hand-ruled progress card per child — it works until it doesn't, and the point it stops working is usually a parent asking, on a Sunday night, how their child is getting on.

Four capabilities cover almost every madrasa, from a single Saturday class of fifteen to a six-class weekend school of a hundred.

1. A private group per class. Each class is its own closed space. The children, the targets, and the parents attached to it are scoped to that class and invisible to the others.
2. One individual goal per child. A single, concrete target — a named surah, a juz, a qaida lesson number — that the child, their parent, and the teacher can see, and nobody else.
3. Weekly assignments that take audio. Recitation is the work. The child records the week's portion at home and submits it; the teacher listens during the week rather than spending the first ten minutes of class hearing recitations one at a time.
4. Parent updates and teacher coordination that push. Absence notes, progress nudges, and one weekly summary delivered as notifications — and a single staff space where teachers and the head teacher sort out cover and timetable changes.

Notice what is missing from that list: a fees-billing engine, a full timetabling module, a public-facing website builder. They can be useful at scale. They are not what separates a madrasa that feels organised from one that feels chaotic.

Should a madrasa run one group or one group per class?

One group per class, with the head teacher holding an overview across all of them.

It is tempting to run a single group for the whole madrasa because it looks simpler — one place, everyone in it. In practice it is the thing that makes a madrasa feel disorganised. The beginners' qaida parents see the Arabic class's announcements, the register mixes children who were never in the same room, and every child's progress sits in a stream of progress that has nothing to do with them.

We'd argue the right structure is firmer than most heads expect: split by class from day one, and resist the urge to teach every class yourself. A head teacher who sits inside all six class chats answering everything becomes the bottleneck the whole school waits on. In Bitir the head teacher takes a role that spans the class groups — visibility into every class's attendance and progress — while each class teacher manages their own group's assignments, goals, and register. The overview is real; the micromanagement is gone.

The only madrasa that should run a single group is the one with a single weekly class, where the group is the school. The moment a second class exists, it earns its own group.

How do madrasa teachers track each child's progress?

Give each child one individual goal set to their termly target, update it weekly, and keep it private to the child, their parent, and the teacher.

The vague "keep going with your hifz" of the WhatsApp era gives nobody a finish line. A concrete, named target — "complete Surah Al-Mulk by half term", "reach qaida lesson 18", "memorise the second half of Juz Amma" — gives the child something to practise towards and the parent something to ask about. When the target is visible to the parent without the teacher photographing a paper card in bad light, the parent stops asking and starts encouraging.

Recitation belongs in audio assignments. A teacher who reviews a week's submissions on their own phone, at their own pace, hears every child properly — not just the three who happened to be at the front when time ran out. Bitir assignments accept audio attachments, so the recording, the teacher's feedback, and the completion tick all sit on the one assignment.

Keeping each child's target private matters more than it sounds. Madrasa heads we speak to often say the same thing: "I'm a teacher, not an office, and the last thing I want is a class where the slowest child's progress is on display to everyone." Visibility to the whole class turns a madrasa into a leaderboard, and the child who is behind quietly stops trying. Celebrate the shared milestones out loud; keep the individual targets quiet.

How do you keep madrasa parents informed without chasing every family?

Make the update a push, not a feed the parent has to remember to open.

Parents do not scroll back through a class chat to find the line about their own child, and they do not read a termly newsletter. They do read a short notification that says their child was marked absent this Saturday, or that their child has just met the memorisation goal set in September. Tie the update to something the madrasa already records — the register, the goal, the assignment — and the chasing disappears.

This also does a quiet safeguarding job. The Department for Education's code of practice for out-of-school settings expects providers to keep an accurate attendance record and a clear line to parents. A child marked absent in the app can prompt an automatic note to that family — exactly the line the code asks you to keep — without the teacher writing a single message.

A worked example: Sister Khadija Yusuf runs Al-Huda Saturday Madrasa in Bradford — 80 children across six classes, taught by four teachers on a single Saturday morning. In Bitir she runs six groups, one per class, and holds the head-teacher overview across all of them. Each child has a termly target only their parent sees. Teachers take the register in the first two minutes; a child absent twice running sends their parent an automatic note. Once a week each teacher posts a two-line summary. Khadija's own Saturday-night admin — chasing cover, copying the register, answering parent messages — went from most of an evening to about twenty minutes, because the progress is already recorded and the parents can already see it.

Do small madrasas need a dedicated madrasa management system?

Usually not, and buying one early is the most common mistake.

Purpose-built madrasa MIS products are real and some are good, but they are priced per student per year and built around a full-time office — timetabling, fees, attendance, reporting, all assuming someone whose job is to run them. A weekend madrasa where the head teacher teaches, manages, and locks up does not have that person. The software ends up half-configured and resented.

Start with the four jobs that matter and add weight only when the school is genuinely big enough to employ an administrator. A private group per class with goals, audio assignments, attendance, and parent updates covers the day-to-day, and it can begin at no cost. The same one-group-per-class rule scales up cleanly when you grow, which is the structure we set out for any small school in the supplementary school toolkit, and the single-class teaching detail lives in how Quran teachers manage classes without WhatsApp.

Related reading: how a Manchester Saturday madrasa cut no-shows and lifted parent satisfaction, and how a Birmingham Quran centre replaced nine WhatsApp groups with one space per class.