Network-level deployment

Designed for groups, not retrofitted from a single-school product.

Lumii is built for multi-school deployment from the architecture up. Each school operates independently within its own data boundary, but the platform supports network-level visibility, comparability, and consistency where you need it.

Group dashboards, network-wide reporting, cross-school theme analysis, and structured contribution to ECA's Early Intervention Framework data pillar are all available without compromising school-level autonomy or pupil privacy.

What network-level looks like

Cross-school comparability without cross-school data leak.

  • School-level data boundaries preserved at all times
  • Group-level emotional trends, alert distributions, and theme patterns
  • Comparability across schools without identifying individual pupils
  • Network-wide reporting suitable for board, trust, and regulator submissions
  • Consistent safeguarding architecture across every school in the network
  • Centralised insight, decentralised action

For inspection cycles, network-level reports are generated from real data captured across every school in the network — exportable per school, per cluster, or per network. Group-level governance teams see what their schools actually did, in the same format the schools' SLTs see, ready for any of the UAE inspection frameworks.

Governance at network scale

How decisions get made across a multi-school deployment.

One of the operational challenges of group-level wellbeing programmes is keeping standards consistent without removing school-level judgement. Lumii's governance model is designed to do both.

At school level

  • School-level safeguarding policy governs every alert response
  • The school's DSL has final authority on every Red and Purple alert
  • Authorised staff list is set and managed by the school
  • Pupil identity remains exclusively held by the school

At network level

  • Group-level standards for safeguarding response timing and process
  • Network-wide reporting and trend analysis
  • Consistent training and onboarding for all schools in the network
  • Aggregated insight contributing to network strategy and inspection submissions

A common group operator question — answered directly

"What happens when a Red alert appears at School A — does the group MD see it?"

No. At every level, individual pupil alerts remain visible only to the named school's authorised staff. Group leadership sees aggregated patterns across the network — never individual pupils, individual alerts, or individual conversations. This is structural, not a configuration choice.

Regulatory alignment

Where Lumii sits within the UAE landscape.

Lumii is built for the UAE regulatory environment from the architecture up. The frameworks below are not aspirational — they shape the platform's design.

ADEK

  • SPIRE Wellbeing Mark — direct mapping to all five dimensions and 15 indicators
  • Mandatory for Abu Dhabi schools since September 2025
  • Irtiqa'a inspection — structured wellbeing data and audit trails

ECA

  • Early Intervention Framework 2026–2028 — Lumii maps to five of the eight pillars
  • ECI Data pillar — daily pupil voice as structured early intervention contribution
  • Aligned with ECA's framework refresh

Federal frameworks

  • UAE Federal Decree-Law No. 26 of 2025 (Child Digital Safety Law) — enforcement Jan 2027; architecture aligned
  • UAE Federal Decree-Law No. 45 of 2021 (PDPL)
  • Wadeema's Law (Federal Law No. 3 of 2016)
  • UAE MoE Generative AI Classroom Framework

Other emirate regulators

  • KHDA / DSIB (Dubai)
  • SPEA (Sharjah)
  • APEA (Ajman, alongside MoE)
  • RAKDOK (Ras Al Khaimah, alongside MoE)
Data residency

All data stays in the UAE.

Every interaction, every alert, every trend — all of it is hosted in the UAE. There are no cross-border data transfer issues to manage, no jurisdictional grey areas to argue, no foreign hyperscaler dependencies. For procurement teams working under PDPL and CDS Law, this is a material differentiator.

Group operators using cloud-hosted EdTech regularly hit procurement friction over data residency. With Lumii, the question does not arise.

Working with us — how groups typically engage

From first conversation to network-wide rollout.

The path below reflects how Lumii has rolled out across school groups to date. Timing varies, but the structure is consistent.

01

Initial conversation

Map your network, regulatory context, and the framework alignment that matters to you.

02

Pilot deployment

Two to three schools across the network to surface real evidence before broader commitment.

03

Group review

Pilot data reviewed against your network priorities — safeguarding outcomes, inspection readiness, pastoral capacity.

04

Scale across network

Roll out with consistent governance, comparable data, and group-level reporting in place.

For regulators and policy stakeholders

Daily pupil voice as structured contribution to early intervention data.

UAE early intervention frameworks — from ECA's 2026–2028 refresh through ADEK's wellbeing mandate — call for structured, longitudinal data on child wellbeing. Most existing approaches rely on periodic surveys, intermittent referrals, or reactive safeguarding records. None capture daily pupil voice as it happens.

Lumii does. The platform is, in effect, a continuous early intervention data layer — anonymised, longitudinal, and at scale across the schools deploying it.

What this contribution looks like

  • Anonymised, structured wellbeing data across thousands of pupils daily
  • Longitudinal trend visibility across terms and years
  • Alignment with ECA's ECI Data pillar
  • Data hosted in the UAE, governed by PDPL
  • Transparent methodology, open to regulatory review
Procurement

What groups typically ask about.

Commercial

  • Group pricing available — based on aggregate cohort across the network
  • Annual licence, billed in AED
  • Pilot terms designed to reduce risk before network commitment
  • Transparent — no hidden setup fees, no per-seat surprises

Compliance

  • Data Processing Agreement available
  • Privacy notice templates for parent communications
  • Breach notification procedure documented
  • Regulatory alignment statements available for ADEK / KHDA / SPEA / ECA / MoE
  • Legal review of DPA and privacy notice typically completes within 2–3 weeks of first procurement conversation

Multi-school deployment, done properly.

A two-week pilot. Network-level visibility. UAE-hosted data.