Student Tracking App for KHDA-Aligned Dubai Schools

Who this is for: Dubai schools with 800+ students, school groups operating multiple Dubai campuses, schools with significant SEND population, and schools preparing for KHDA inspection cycles. Less suited to schools with under 500 students - those are well-served by generic SIS student tracking; custom app is for schools where unified whole-student view and KHDA-aligned reporting justify bespoke build.

Six connected capability areas: (1) Unified student-level data across attendance, attainment, behaviour, wellbeing, pastoral, SEND. (2) KHDA reporting alignment native. (3) SEND and Inclusion workflow embedded. (4) Parent communication informed by student data. (5) Intervention planning and tracking. (6) Phase-specific workflow across KG to Post-16.

SIMS, iSAMS, ManageBac, Engage, PowerSchool, Veracross, and similar are mature global SIS platforms with student tracking modules and UAE deployment. These handle core student information, attainment, attendance, and behaviour at scale.

Custom student tracking apps for KHDA are designed to sit alongside these platforms, closing UAE-specific gaps - whole-student view unified across modules, KHDA Wellbeing Census workflow native, KHDA Inclusion framework SEND workflow, KHDA reporting shapes embedded, and parent communication informed by student data context. The global SIS retains core student authority; the custom app handles KHDA-aligned student tracking depth.

Generic SIS platforms structure student data by module - attendance module, attainment module, behaviour module, wellbeing module, pastoral notes, SEND register. Cross-module student view requires manual assembly.

The unified data layer treats student as the organising principle. Attendance, attainment, behaviour, wellbeing, pastoral care, SEND, and intervention planning unified per student. Form tutor and pastoral lead view shows whole student in one place with appropriate phase-specific layout. Cross-dimension trends visible - attendance pattern affecting attainment trajectory, behaviour incidents affecting wellbeing scores, SEND plan progressing or stalling. Trigger workflows when patterns emerge - attendance dropping triggers pastoral lead notification, behaviour escalation triggers intervention review.

KHDA expects specific reports including Wellbeing Census, attainment data submissions, SEND data, attendance reports for inspection. Generic platforms ship report templates as configuration; schools spend significant effort customising and validating.

The KHDA-aligned reporting layer treats KHDA report shapes as native. Wellbeing Census workflow embedded with appropriate question banks per phase and aggregation per KHDA expectations. Attainment data submissions structured per KHDA shape with appropriate validation. SEND data per KHDA Inclusion framework. Attendance reporting aligned with KHDA expectations including authorised and unauthorised absence categorisation. Inspection visit data continuously available rather than assembled per visit. Reports updated automatically as student data updates.

KHDA Inclusion framework defines expectations for SEND students. Generic platforms support SEND register but treat plan and intervention workflow as parallel.

The embedded SEND workflow covers full lifecycle. SEND identification workflow with appropriate stages - referral, assessment, identification, plan creation. Individual Education Plan (IEP) and Inclusion plan creation with template per need type. Plan review cycles automated. Intervention tracking with effectiveness measurement against plan. Progress against plan visible continuously. Parent involvement in plan workflow embedded. Transition planning across phases supported. KHDA Inclusion framework alignment continuous rather than per-review-meeting. External professional involvement (educational psychologist, speech and language therapist, occupational therapist) tracked.

Parents expect informed communication. Generic communication platforms operate in parallel to SIS; conversations happen with stale data.

The informed communication layer surfaces student data context at point of communication. Form tutor messages with attendance, attainment, and behaviour visible inline. Pastoral notes accessible (per school policy on parent visibility). Attainment updates with appropriate context. Intervention plan progress visible to parents. Parent-teacher conference workflow with pre-meeting data automatically assembled. Termly cycle automated with phase-specific content. Parent reading of communications and engagement tracked for follow-up where appropriate.

Custom student tracking apps typically sit inside a wider school technology stack.

SIS platforms - the software is designed to sit alongside SIMS, iSAMS, ManageBac, Engage, PowerSchool, Veracross for core student information authority.

Assessment and learning platforms - integrates with Google Classroom, Microsoft Teams for Education, Seesaw, Toddle for academic evidence authority.

Wellbeing and pastoral platforms - integrates with KHDA Wellbeing Census infrastructure and pastoral platforms.

Parent communication platforms - integrates with parent apps and communication platforms for messaging authority.

Discovery runs four to six weeks. Working with your principal, vice principal pastoral, and inclusion lead, we map current student tracking, KHDA reporting workflow, SEND and Inclusion practice, and parent communication. Output is a detailed report covering current-state map, platform architecture, integration scope per existing platform, phased implementation plan, and fixed-price build proposal.

Build for a core student tracking app runs ten to fourteen weeks from discovery completion. Full unified student data, KHDA reporting alignment, SEND and Inclusion workflow, and parent communication rollout phases in over six to twelve months depending on school scope and integration breadth.

Pricing varies by school size, SEND population complexity, and integration scope. A bracket isn't published; discovery produces a fixed-price proposal with no obligation to proceed.