The answers you need before this reaches procurement
You will be asked where the data lives, who can see it, how it comes back out, and what breaks during migration. Here is all of it up front rather than after three calls.
What the week actually looks like
You inherit whatever was signed
The decision is usually made on features and lands on IT to implement, integrate and support — including the parts nobody asked about during the demo.
Export turns out to be a negotiation
Plenty of systems make data easy to put in and awkward to get out. That only becomes visible at renewal, which is the worst possible moment to discover it.
Permissions are coarser than the school needs
A single "teacher" role is not enough when medical notes, safeguarding records and inclusion plans all live in the same system.
Migration scope is discovered, not planned
Data condition determines timeline more than school size does, and most projects find that out halfway through rather than at the start.
What changes
- Student data held in UAE-based infrastructure, not replicated to other regions
- Role-based permissions applied per module, with sensitive categories restricted separately
- Open-format export available on request at any time, including at exit
- Access to student records logged, so who-viewed-what is answerable
- Migration scope assessed against your actual data before a timeline is committed
The modules this role lives in
Student Information System
One record per student — profiles, guardians, sections, documents and full academic history, built for UAE schools and school groups.
Reports & Analytics
See attendance trends, academic progress and operational data across every campus, with scheduled exports your leadership team can act on.
Parent Portal & Communication
Give parents one place for attendance, report cards, notices, consent forms and direct messaging with school — on both web and mobile.
Timetable & Scheduling
Build clash-free timetables for classes, teachers and rooms — cover, substitution and room booking handled in one scheduling system.
Questions this role asks
Where is the data stored?
In UAE-based infrastructure. Student records are not replicated to other regions.
How do we get our data out?
Open-format export, on request, at any time — including if you leave. It is a standard function rather than something to negotiate at renewal.
How granular are permissions?
Role-based and applied per module, with sensitive areas such as medical, safeguarding and inclusion records restricted separately rather than bundled into a general staff role.
What determines how long migration takes?
The condition of your existing data far more than the size of your school. A clean export from a modern system moves quickly; years of inconsistent spreadsheets take longer. We assess which situation you are in early rather than at the end.
Bring the problem you actually have
A demo built around your school beats a product tour. Tell us what your week looks like and we will show you the part that matters.
Book a demo