Every branch, every dirham, every class — on one screen.
You are accountable for the whole school, but the answers live in five places: an assistant's notebook, a teacher's WhatsApp, a receipt book, a spreadsheet, and your own memory. Mujtahid puts all of it in one place that is always current, because it is where the work actually happens.
The month-end scramble
Every principal we have worked with runs the same loop at the end of the month: call each branch, wait for numbers, discover a gap, and reconcile by hand. The numbers were never wrong on purpose — they were just never in one system.
- Each branch reports on its own format, so nothing adds up without rework.
- Overdue fees surface weeks late, when the student has already stopped coming.
- Teacher pay is recalculated from scratch because nobody trusts last month's file.
- Nobody can answer "how is Grade 9 actually doing?" without asking four people.
What you get on day one
Not a reporting layer bolted onto someone else's process — the place your staff already work, which is why the numbers are live.
The whole school, and each branch
Principals see across every branch at once; assistants see only theirs. Switch from the school view to a single branch without changing tools or losing the comparison.
Revenue you can trust
Fees due, fees collected, what is overdue and by how long — per branch, per class, per student, updated the moment your assistant records a payment.
Staff, roles and real permissions
Promote a student to teacher, an assistant to principal, block an account, hand out a single access key. Every one of those is enforced on the server, not hidden in the interface.
Academic results, not just attendance
Exercise attempts, retakes, level tests and unit progress roll up per class and per subject, so a weak group is visible in week three instead of at the exam.
Capacity and spend
Live minutes, AI credits and storage are visible as tanks with a remaining figure. You always know what is left before it runs out, and nothing bills you by surprise.
Your school's identity
Your own subdomain or custom domain, your logo, your director's word and signature on printed documents, and a public catalogue page you can send to a parent.
Fees collected against fees due, by branch
The single view that ends the month-end call round — the same figures your assistants are entering, grouped the way you think about the school.
- Collected
- Still due
Illustrative figures — the shape of the report, not anyone's real numbers.
How the month runs
Four moves, and the reporting is a by-product of the work rather than a task.
- 1
Open your branches
Each branch gets its own students, timetable, staff and support contact. You decide which ones are active.
- 2
Set who can do what
Assistants get access keys per area — enrolment, payments, schedules. Teachers get their classes. Nobody gets more than you granted.
- 3
Watch the month build
Payments, attendance, results and usage land as your team works. There is no reporting step, because there is no separate report.
- 4
Close it in one pass
Print receipts and payroll, review overdue, compare branches, and carry the decisions into next month.
Why this works when generic school software doesn't
Most platforms model one school with one campus and one currency of trust. Moroccan schools are not that, and the difference is not cosmetic.
Multi-branch is the model, not a plugin
Scoping runs through the whole system: a principal's action covers the school, an assistant's covers their branch. That distinction is deliberate role behaviour, tested, and never blurred to make a screen simpler.
Offline payment is a first-class flow
Fees arrive as cash and bank transfers, so the product treats a hand-reviewed payment as normal: quotes are frozen when you submit, and a school never pays for the days it spent waiting in a review queue.
Authorisation is checked on the server
Hiding a button is not security. Every mutation re-checks the caller's role and that the record belongs to their school, so a curious student cannot reach another branch's data by guessing.
Capacity you buy is capacity you keep
Minutes and credits are a cumulative tank, not a monthly allowance that evaporates. If a subscription lapses, the balance is frozen, never zeroed — it is waiting when you come back.
What principals ask first
- Can I see one branch without losing the school view?
- Yes. The school view compares branches side by side, and one click drills into a single branch with the same figures. Assistants only ever see their own branch.
- What happens if we stop paying for a month?
- After a two-day grace period the school surface closes for everyone until the subscription is renewed. Your data and your purchased capacity are untouched — nothing is deleted and no credits are burned.
- Can I use our own domain?
- Yes. Every school gets yourschool.mujtahid.ma, and you can point your own domain at it. Your logo and signature carry through to printed receipts and lesson sheets.
- How do we move the data we already have?
- You do not do it alone. We open the school space with you, help you shape branches, subjects and classes, and stay with you through the first enrolment run.
Keep reading
The parts of the platform this page touches.
See your own school in this shape
Create an account, and we will set up your school space with you.