Progress Tracking App for KHDA SEF at Dubai Schools

Who this is for: Dubai schools with 800+ students, school groups operating multiple Dubai campuses, and schools running multiple curricula preparing for KHDA inspection cycles. Less suited to schools with under 500 students - those are well-served by generic SIS progress tracking; custom app is for schools where SEF descriptor alignment and continuous evidence capture justify bespoke build.

Six connected capability areas: (1) SEF descriptor-aligned progress evidence. (2) Phase-specific tracking native - KG to Post-16. (3) Teacher workflow embedded in classroom practice. (4) Parent and student voice integrated. (5) Cross-curriculum mapping - UK, IB, US, MoE. (6) Inspection-ready evidence pack assembly.

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

Custom progress tracking apps for KHDA SEF are designed to sit alongside these platforms, closing UAE-specific gaps - SEF descriptor alignment at point of capture, phase-specific workflow native (KG to Post-16), teacher workflow embedded in classroom practice rather than end-of-term reporting, parent and student voice integrated with progress evidence. The global SIS retains core student authority; the custom app handles KHDA SEF-specific evidence depth.

KHDA SEF Students' Achievement and Personal and Social Development standards have specific descriptors per phase. Generic SIS progress tracking captures attainment grades, attendance, and behaviour but doesn't tag against SEF descriptors.

The descriptor-aligned evidence layer captures progress against SEF descriptors at point of entry. Teachers tag evidence with applicable descriptor and curriculum mapping. Curriculum-aware mapping for UK (NC), IB (PYP, MYP, DP), US (Common Core, AERO), and MoE curricula onto SEF descriptors. Attainment, progress, and personal development tracked with descriptor tagging at capture rather than retrospectively. Evidence pack assembled continuously per student, per class, per phase, ready for inspection visit.

KHDA SEF assesses across phases - KG (early years), Primary, Middle, Secondary, Post-16. Each has its own descriptors, evidence expectations, and curriculum-specific reality. Generic platforms ship cross-phase tracking as single workflow.

The phase-specific layer treats each phase with appropriate workflow. KG tracking aligned with early years frameworks (UK EYFS, IB PYP early years, MoE early years). Primary tracking aligned with KS1-KS2 or equivalent. Middle tracking aligned with KS3 or equivalent. Secondary tracking aligned with KS4 or equivalent including IGCSE, MYP, and equivalent. Post-16 tracking aligned with A Level, IB DP, AP, and equivalent. Phase transition workflow with appropriate handover documentation. Cross-phase trajectory visible across student journey.

Inspection-grade progress evidence comes from teachers in classroom practice. Generic SIS platforms support teacher data entry but treat it as end-of-term reporting task. Teachers re-enter data into spreadsheets; evidence quality suffers.

The classroom workflow layer is mobile-first for teacher use. Quick capture during lesson - lesson observation, formative assessment, behaviour tracking, intervention notes. Structured capture at lesson end with curriculum and SEF descriptor tagging surfaced. Workload reduction over manual reporting through structured capture rather than free-form notes. Department head and phase leader visibility into capture compliance and evidence quality. School leadership dashboards aggregate across teachers without surveillance overhead.

KHDA SEF includes parent voice and student voice as evidence inputs. Generic platforms support survey workflow but don't tag responses against SEF descriptors and student progress.

The integrated voice layer captures parent surveys, student voice, and parent-teacher conference outcomes with SEF tagging and student linking. Termly voice cycle with appropriate phase-specific workflow - younger phases via parent input, older phases via student voice directly. Voice findings linked to individual student progress evidence rather than aggregate. Voice findings drive intervention planning - where parent voice flags a concern, intervention plan generated and tracked. Inspection visit shows voice integrated with progress evidence rather than parallel data.

Custom progress 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 and attainment authority.

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

Curriculum platforms - integrates with curriculum-specific platforms (PYP-MYP-DP via ManageBac, A-Level via SIMS, MoE via approved platforms) for curriculum mapping.

Communication platforms - integrates with parent communication apps and survey platforms for voice authority.

Discovery runs four to six weeks. Working with your principal, vice principal academic, and inspection coordinator, we map current progress tracking workflow, SEF descriptor alignment, phase-specific reality, and teacher capture practice. 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 progress tracking app runs ten to fourteen weeks from discovery completion. Full SEF descriptor alignment, phase-specific workflow, teacher classroom workflow, and voice integration rollout phases in over six to twelve months depending on school scope and integration breadth.

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