For IB and international schools
Edda helps a school become genuinely digital: teachers developed and confident, AI woven into real learning, and every tool and policy governed properly. Teachers ask her in Claude, in plain language. Your digital lead runs the record in her app. And because the record is real, the compliance evidence writes itself.
The moment
Three pressures have landed together. The deadline is what gets this on the agenda. What your students and teachers become is what it is actually for.
Regulators now require AI literacy across K to 12. For Abu Dhabi schools, the ADEK framework lands by September 2026, and coverage has to be shown rather than asserted.
Students and staff use AI every day, and most schools have had little training or guidance. The question is no longer whether to engage with it. It is how to do that well.
Your units sit in a planning tool, but which competencies are genuinely taught, and where the gaps are, is nobody's clear view. Tags cannot be trusted.
What Edda does
Most tools do one of these. Schools have all three at once, and they feed each other: the plan develops the teachers, the teachers transform the classrooms, and the evidence an inspector needs falls out of work that was worth doing anyway.
Digital leadership
A baseline assessment and gap analysis become a dated playbook, and the playbook becomes a live execution board. Tasks the app can verify complete themselves: adopt a policy and the board already knows. The rest carries the paper trail, with minutes and sign-offs attached, so completion means evidence rather than assertion.
Alongside it: staff capability measured honestly and grown through a sequenced CPD plan; the nine policies your regulator expects, audited clause by clause and fixable in the app; a governed tool register; and an inspection view where every claim ends in something you can open.
AI literacy
The regulator's AI-literacy framework, mapped against the curriculum you already teach. Edda shows where each competency can live inside an existing unit, drafts the classroom touchpoint, and keeps the delivery record as staff build, teach, and evidence each one. The submission drafts itself from what actually happened.
Curriculum
Edda has read the whole curriculum, so coordinators can see coherence and coverage honestly, and teachers can plan, differentiate, assess, and reflect with materials grounded in their own units. Everything is a proposal for professional judgement, delivered in chat, taken away as a finished document.
Meet Edda
A colleague who has already read every unit in the school.
Edda knows your units and lessons inside out, so she can answer a question, draft with your own materials, or show you exactly where you stand. She reads the curriculum you have already built in your planning system, so there is nothing to migrate and nothing to re-enter. Her name comes from the Eddas, the old books that held a people's whole store of knowledge. That is what she does. She keeps your curriculum's memory and hands it back when you ask.
Every answer comes from your school's real units and lessons, never generic advice. She shows the source and links straight to it.
She maps your curriculum against the frameworks that matter, including the ADEK AI-literacy requirements, and shows the real gaps. She reads the content, not the tags.
You ask in Claude, in your own words. There are no dashboards to learn and no exports to wrangle. Take anything away as a finished Word document.
How it works
Setup takes about two minutes. Edda lives inside Claude as a secure connector, next to the planning tools you already use.
Settings, Connectors, Add custom connector, paste the address, and confirm.For your role
Edda shows each person the handful of things that are genuinely theirs to do, and leaves out the rest. Here is what each can ask her for.
Coordinators
Ask “How coherent is Year 4?”
Teachers
Ask “Plan a lesson for this line of inquiry.”
AI & Digital Leads
Ask “Where do we stand on ADEK?”
Leadership
Ask “Are we ready for ADEK?”
What you get out
Edda turns a scattered curriculum into a picture you can act on and share. Everything is a proposal for your judgement, and nothing changes without you.
For each year and each framework, it shows where every AI-literacy competency can be built. It is an honest map of the work still to do, not a reassuring dashboard.
As staff build and teach each touchpoint, they record it. The map becomes the evidence trail your regulator asks for.
A phased, dated plan that reaches the deadline, built from your real curriculum and ready to share as a Word document.
The point
No school became a great digital school by passing an inspection. It happens the other way round: teachers grow confident, technology serves learning, students leave AI-literate, and the inspection takes care of itself. Edda is built in that order. She develops the people and improves the curriculum, and keeps the evidence as a by-product of real work, never as a performance for the regulator.
Capability is measured with scenarios rather than self-ratings, grown through a sequenced CPD plan, and supported daily: a colleague to plan with, differentiate with, and ask anything.
AI literacy lands inside real units as classroom moments, not as a bolt-on scheme. The measure is what students can actually do, tier by tier, year by year.
Because the plan, the work, and the record are one system, proving it requires no extra work. The school that did the job can always show the job.
The ground rules
These hold on every interaction. They are how Edda is built.
Every output is a proposal for your professional judgement. Nothing in your planning system is altered, and Edda never writes back to it.
Curriculum and staff planning only. Edda works with your units, lessons, and frameworks, never children's records.
She shows the real gaps rather than a reassuring dashboard. A map of the work that remains is worth more than a claim that it is done.
Under it all sits a connected knowledge base: nine international AI and digital frameworks, every indicator by year group with its assessment criteria, every citation tested to resolve before a release ships. How Edda knows →
Sign-in is restricted to school email addresses, and each school's Edda sees only its own curriculum. It is hosted in your region, on your school's own connection.
Questions
No. She reads the curriculum you have already built and works alongside it. Nothing is migrated, and she never writes back to your planner.
Edda works only with curriculum and staff planning: your units, lessons, and frameworks. She does not touch student records.
No. Edda maps your curriculum against whichever frameworks matter to you. ADEK is one; the coordinator and teacher work applies to any IB or international school.
Edda is a secure connector inside Claude. Your team asks her in plain language in an ordinary chat. There is nothing new to install or learn.
No. Every output is a proposal for your professional judgement. You decide what to use, and nothing is altered without you.
PYP, MYP, DP, and CP, across the year groups you teach.
Both, by design. Your digital lead runs governance in Edda's app: the plan, the policies, the tool register, the evidence. Everyone else just asks in chat. Teachers never need another login.
About two minutes per person to connect. Getting your school's curriculum ready is a short guided step we run with you.
We start every school with a pilot rather than a price list. Book a demo and we will scope it to your size and needs.
A few staff, your real curriculum, a couple of weeks. See where you stand on AI literacy, and what it takes to close the gap, before you commit to anything.
Book a demo