Performance Review Platform
Department KPIs and ministerial compliance — evidenced, approved and surfaced on smart dashboards
A shared workspace that measures Aseer schools against education-department KPIs and the ministry’s compliance indicators (formerly the Educational Affairs Platform). Support providers measure their assigned schools and attach an evidence link per item; the department reviews and approves, and approved results flow automatically into department KPIs, leadership dashboards and the AI assistant.
- 3,381
- Schools in the directory
- 9
- Compliance items
- 4
- KPI input types
- PWA
- Installable
Department KPIs lived in scattered files with no common evidence or approval cycle, so leadership could not tell which figure was approved, who supports which school, or what difference support services made to school results.
One cycle per item — draft → submitted → approved or returned with a reason — with versioned KPIs, assignments approved by the excellence-support unit, role-based dashboards, an Aseer governorate map, a performance card per school, and an AI assistant that analyses Nafs, external evaluation and platform KPIs within each role’s permissions.
Key capabilities
Evidence & approval
Yes/no, ratio, count or verification score — an evidence link per item and a full approval cycle
Ministerial compliance
9 items (CO-01…CO-09) scored 2/1/0 and banded high/medium/low
Assignments & impact
Excel import with conflict and high-performer alerts, and a continuous impact index per support provider per cycle
Governorate map
Shade governorates by Nafs, external evaluation, support coverage or satisfaction, then drill into schools
AI assistant
Analyses a school or the region and proposes improvement priorities, sending only aggregated data — no names or IDs
Security & signed updates
Forced password change, lockout after 5 attempts, audit log, and digitally signed updates with rollback
Every dashboard figure is an approved result with an owner, evidence and a version; changing a KPI definition creates a new version without touching past results, and sample verification turns any mismatch into a gap with an owner and a due date. Evidence stays in the unit’s own repository, satisfaction is stored only as averages and respondent counts, and exports exclude national IDs and contact details.