Admissions & students
From enquiry to enrolled, with the paperwork attached rather than filed somewhere.
- Enquiry to admission pipeline
- Online application and document upload
- Unique admission number per branch
- Transfer between branches with history
كل فرع، وكل صف، وكل رسم — في مكان واحد
Running several school branches usually means running several schools that happen to share a name. Admissions numbers arrive by email, fee collection is reconciled at month end, and no one can answer a simple question about attendance across the group without three phone calls.
This is one system with branch-level autonomy. Each branch runs its own sections, timetable, staff and fee structure, while the trust sees admissions, collections, attendance and results across every campus in real time.
كل فرع، وكل صف، وكل رسم — في مكان واحد
اطلب عرضاً توضيحياً وعرض سعرأو راسل quote@iiwebs.com
Every module below is included. Anything you do not need can be switched off for your deployment rather than cluttering the screens your team uses every day.
From enquiry to enrolled, with the paperwork attached rather than filed somewhere.
The scheduling and record-keeping that consumes most of a coordinator's week.
Daily attendance that parents see the same morning, not at the end of term.
The part of a school that most often runs on a parallel spreadsheet.
Marks entry to report card without a single re-typed number.
One channel that parents actually read, instead of five they ignore.
Trust-level visibility without taking autonomy away from each principal.
The full academic and fee cycle without enterprise complexity.
Lighter workflows for attendance, fees and daily parent updates.
Hostel, mess, transport and visitor management alongside academics.
We host it on our own NVMe infrastructure, monitored around the clock, with backups, SSL and updates handled. Most clients choose this and never think about servers again.
Deployed on hardware or a cloud account you control, for organisations whose policy or regulator requires data to stay in a specific place.
The parts of the system that belong on a phone go on a phone — field staff, approvals, dashboards and anything captured away from a desk.
Source code, data and documentation are handed over on full payment. No lock-in, no per-user licence that grows into a tax on your own growth.
We map your existing process first and shape the system around it. You should not have to change how your business works to suit software you paid for.
Your existing data — masters, balances, history — is mapped, trial-imported and reconciled against records you already trust before anything goes live.
Your team is trained on the workflows they actually use, with documentation, and we stay close through the first month of live running.
Agents and automation can be layered on afterwards — document reading, reminders, reporting on demand — once the core system is running and proven.
Ongoing maintenance with agreed response windows, updates and monitoring, from the same team that built it.
Every system below shares the same core, so two of them running side by side share one login, one stock table and one set of reports rather than becoming two islands.
القبول والشؤون الأكاديمية والامتحانات والحسابات للتعليم العالي
View systemالمجموعات والرسوم والنتائج لنشاط قائم على النتائج
View systemنظام واحد لكل مستشفى ووحدة وقسم تديره
View systemYes. Fee heads, amounts, instalment dates and concession rules are defined per branch and per class, while collection reporting rolls up to the trust automatically.
Route, stop and vehicle management with fee linkage is included, as is hostel allocation, mess and visitor logging. Both are modules you can switch on per branch rather than paying for everywhere.
Tell us how many branches, roughly how many users and what you run today. Within two working days you get a written scope, a timeline and a fixed price — and a demo on your own data if you want one.