On Friday 14 November 2025, Dubai's early years landscape took a significant step forward. The Knowledge and Human Development Authority launched the Quality Framework for Early Childhood Care and Education in Dubai, developed over time with international experts and shaped by the voices of Dubai's early years sector itself.
I was in the room. More than 400 leaders, educators and managers were there with me, and the mood was not the mood of a sector being handed a checklist.
What follows is what the framework says, and then the harder question it opens up: quality means something different to every person who walks through a nursery door, and a shared framework does not make those differences disappear. It gives us a common language for a conversation that is still genuinely contested.
What is the KHDA Quality Framework for Early Childhood Care and Education?
The KHDA Quality Framework for ECCE is Dubai's citywide reference for quality in early childhood settings serving children from birth to six years. Launched on 14 November 2025, it is structured around five interconnected domains and is designed as a reflective tool for settings to evaluate and improve their own practice. It is the first citywide framework dedicated entirely to early childhood.
It applies to nurseries, preschools and early years departments within schools. It aligns with Dubai's Education 33 Strategy and the Dubai Social Agenda, and it sets out to blend international benchmarks with Dubai's own cultural context rather than importing a standard wholesale.
What is 'The Dubai Child'?
The Dubai Child is the vision at the centre of the framework: "A global child, leading a local life" — an active, capable, curious, happy and inquiring learner, growing in identity, language and culture, and contributing as a valued citizen to the UAE.
The phrasing repays attention. It positions the child as a contributor rather than a recipient, which is not decorative language. It sets the standard against which the five domains are then written. A setting that treats children as things to be processed that will meet none of the domains well, whatever its paperwork says.
What are the five domains of the KHDA quality framework?
The framework is structured around five interconnected domains:
- Learning and Curriculum
- Partnership
- Learning Environment
- Health, Safeguarding and Wellbeing
- System Leadership
Each domain is explored through two elements:
- Element A — Provision: the practices that must be established and sustained by every setting.
- Element B — Impact: the outcomes of that provision for children, families, educators, leaders and wider stakeholders.
The A/B structure is the most important design decision in the document, and the one I would not want settings to skim past. It refuses to let provision stand as its own evidence. Having a policy is not the same as the policy changing anything, and the framework asks for both.
Neither. KHDA has been explicit that this is a collaborative journey rather than a compliance exercise, working in partnership with early years settings and offering support and dialogue rather than inspection. The approach is rooted in trust and shared learning. Further implementation guidance and supporting documentation will follow.
This distinction gets missed, so it is worth being blunt about it. Dubai nurseries already operate under a real licensing regime: premises, ratios, safeguarding, staff qualifications, health requirements, and renewal. That has not changed, and it is not what this framework is. The ECCE framework sits alongside licensing as something different in kind, and a setting that responds to it in the way it responds to a licensing requirement will produce a folder of evidence and no improvement.
To support implementation, the framework offers exemplars: illustrative guidance to help settings picture what each element might look like in practice. These are not prescriptive checklists. They are reflective tools designed to spark dialogue.
Settings are invited to ask:
- What does quality provision truly look like here?
- How do we know it is making an impact?
- How can we evolve our practice to serve our learning community better?
Why do children, parents, staff, regulators and owners define quality differently?
Because each group measures quality against a different outcome and detects failure through a different signal. Children register belonging. Parents register communication. Educators register working conditions. Regulators register consistency across settings. Owners register enrolment. All five are looking at the same nursery and seeing five different things.
The table below maps those definitions against the framework's domains.
How do children experience quality in a nursery?
Children do not experience quality as curriculum or compliance. They experience it as warmth, familiarity and access to play. A child experiences a high-quality setting as one where a known adult greets them by name, where the space invites exploration, and where their ideas are taken seriously. For children, quality is emotional before it is educational.
This is not a soft point. A child with a secure sense of belonging takes more risks, sustains attention longer, and engages more deeply with everything the curriculum is trying to do. Belonging is the precondition, not the reward. It is why Learning Environment stands as its own domain rather than sitting in the background of the others.
What do parents look for when judging nursery quality?
Parents judge quality through two channels: the development they see in their child, and the quality of communication from the setting. They want progress that aligns with their own beliefs about learning, whether that means academic foundations, creativity or emotional resilience. Above all they want evidence that their child is safe, happy, and understood.
Communication does disproportionate work here, and the framework's Partnership domain is sharper on this than most people expect. It asks settings to move beyond service delivery for families toward working with them: shared decision-making, collaboration, mutual respect. That is a higher bar than an app update at 3 pm.
The framework calls this partnership architecture: the structures and relationships that sustain a thriving learning community. Worth asking:
- What does your learning community look like today?
- Where are the opportunities to strengthen the connection?
- How can you embed partnership into everyday practice, rather than bolting it on?
A setting delivering excellent provision but communicating poorly will be perceived as lower quality than a mediocre setting that keeps families genuinely involved. Parents cannot observe the classroom. They can only observe what you choose to share.
Why does staff wellbeing determine the quality of care?
Educators define quality through their working conditions, not their curriculum. They need secure employment, fair conditions, and leadership that treats their professional judgement as worth hearing. When educators feel valued, teaching quality rises without intervention. When they feel overlooked, quality falls regardless of how strong the curriculum or environment is.
Staff wellbeing is not adjacent to quality. It is the mechanism through which every other quality input reaches a child. A well-designed curriculum delivered by an exhausted educator working their notice period is not a well-designed curriculum in any sense a three-year-old would recognise.
The framework's emphasis on reciprocal relationships extends here. It asks practitioners to see relationships with children as two-directional, with children participating in adult life and adults engaging meaningfully in the lives of children. An adult with nothing left to give cannot hold up their end of that.
What does the framework ask of owners and operators?
System Leadership asks owners for something more demanding than compliance: the conditions in which good practice is possible. Owners define quality through reputation, enrolment and viability, and those are lagging indicators. The framework's Element B (Impact) asks them to evidence outcomes, which means seeing what is happening before it shows up in registrations.
The gap between owners and educators is rarely one of values. It is one of the aspects of visibility. An educator sees the leading indicators daily and often has no route to escalate them. An owner sees the lagging ones and, by the time they move, the cause is months old.
Where do these definitions conflict?
The framework gives us shared language. It does not dissolve the tensions, and pretending it does is how quality initiatives stall.
- Cost control vs. ratios. Staffing is simultaneously the largest operating cost and the largest determinant of care quality. Every efficiency here is paid for in the room.
- Evidence vs. time. Demonstrating impact consumes the hours that produce impact. The framework's reflective posture helps, but reflection also takes time nobody has budgeted.
- Parent expectations vs. pedagogy. Families asking for worksheets and early literacy outcomes are asking for something that developmentally appropriate practice will not deliver on their timeline.
- Shared standards vs. setting identity. A common framework raises the floor across a diverse sector. It also asks distinctive settings to describe themselves in a shared vocabulary.
A high-quality setting is not one where these tensions are absent. It is one where they are named out loud, arbitrated deliberately, and revisited — rather than settled by default in favour of whoever escalates loudest.
How should a setting respond to the framework?
Start with Element B. Most settings can evidence provision; far fewer can evidence impact. Take one domain, ask what changed for children, families or educators as a result of what you already do, and be honest when the answer is that you do not know. That gap is the work.
The exemplars are there to make this concrete rather than to grade you. Used properly, they turn "are we good?" into "what would better look like here, for these children, this year?"
Where technology helps is narrow and worth being honest about: it can shorten the distance between the person who sees a problem and the person who can act on it, and it can reduce the documentation load that eats reflection time. illumine is built for that. It is a visibility problem, not a values problem, and no platform substitutes for the judgement of whoever is making the call.
