Services · Mobile app development · Education AI agents
Codeeo provides education AI agent development UK trusts, school groups, colleges and education suppliers can roll out across many sites. We build staff side agents for admissions, timetabling and cover, parent communication, attendance, SEND paperwork and marking support, designed for the rules of England, Scotland, Wales and Northern Ireland. Each agent works from approved sources, keeps a full audit trail and routes safeguarding, complaints and individual decisions to people, so automation supports staff without making choices about learners.
Education is devolved, so an agent that works for an academy in Kent may give the wrong answer in a Glasgow secondary or a Welsh medium primary. We plan for those differences from the start rather than discovering them after rollout.
200+ companies servedFrom a first store to an ADX listed developer
Capabilities for national rollouts
Running AI agents for one school is a contained project. Running them for a trust with schools in several regions, a college group or a supplier serving thousands of settings is different. The rules change between nations, admissions processes differ by local authority, management information systems vary by school, and data protection duties under UK GDPR apply everywhere. In England, the Department for Education has published guidance on generative AI in education and product safety expectations for AI tools used in schools and colleges, and Keeping Children Safe in Education sets filtering and monitoring standards. Scotland, Wales and Northern Ireland each have their own education departments, inspectorates and guidance. These are the capabilities we build into platforms meant to work across that variety, in the order most organisations need them.
Each site is tagged with its nation and local authority, and the agent draws only on the rules, templates and guidance that apply there. A placing request question from a Scottish parent gets a different answer from a coordinated admissions question in England, and Welsh language letters are handled for settings that need them.
No school receives guidance written for a different part of the UK.
Trusts often run SIMS in some schools, Arbor or Bromcom in others, and something else again in an acquired academy. We build connectors through each system's approved integration route, map the fields into one model and request only the data each agent needs.
Agents behave the same way whichever system a school uses.
One versioned store holds trust wide policies, with local addenda for each school. Staff questions are answered with a citation to the paragraph used, and the agent refuses to answer from a superseded version once a policy has been replaced.
Every site works from the current policy, and leaders can prove it.
Admissions agents load each local authority's scheme and each school's arrangements for the year. They explain processes to families, collect in year applications for staff to assess and never predict or decide on a place. Scotland's placing request process and Northern Ireland's post primary transfer arrangements are loaded separately from English schemes.
Admissions teams receive complete applications and fewer repeat calls.
From staffing, rooms and curriculum plans, the agent drafts timetable options and daily cover plans for each site, explaining which constraints each option meets, so timetablers can compare choices quickly and keep control of the final version. Sites that share staff, such as a trust with peripatetic music or SEND specialists, can see cross site clashes before they happen.
Planning time drops without taking decisions away from timetablers.
Teachers get draft feedback against mark schemes for practice work. For assessed work, the agent follows JCQ rules in England, Wales and Northern Ireland and the relevant Scottish qualification rules, which normally means it is not used on that work.
Teachers save time while centres protect qualification integrity.
Drafted replies to parent messages in English, Welsh and other home languages, using each school's published information. Complaints, safeguarding concerns and data requests are recognised and sent to named staff, never answered automatically. Each school controls which message types may be sent after approval and which always need a phone call.
Routine replies speed up and sensitive messages reach people.
We configure agents to work with your filtering and monitoring arrangements, log activity for your designated safeguarding leads and block the agent from handling disclosures. Settings are documented against the standards your nation's guidance sets.
Safeguarding leads can see and evidence how the agents behave.
Every request, source, draft, edit and approval is logged. We supply the technical detail your data protection officer needs for the DPIA, records of processing and responses to ICO enquiries or subject access requests. Logs are retained for the period your records policy sets, then deleted.
Accountability under UK GDPR is backed by records, not assurances.
Central teams see request volumes, staff edit rates, refusals and response times by school and by agent, without access to individual pupil content, so they know which sites need training and which agents need work. Boards receive a termly summary they can include in risk and governance papers.
Rollout decisions rest on evidence from every site.
Who this is for
National and multi region organisations face problems a single school does not: inconsistent systems, different rules by nation and authority, and the need to prove to boards and regulators that automation is controlled. The four profiles below cover most of the organisations we speak to across the UK. Each needs a platform rather than a single agent, and each has a different first site to pilot with.
Trusts that grew by taking on academies in different regions inherit different systems, local authorities and habits. A shared platform with nation and authority aware rules, a central policy service and per school data separation gives the trust consistent practice while letting each head keep local settings. We usually pilot in two contrasting schools before rolling out. Lessons from the pilot shape the rollout guide every later school receives.
Pilot in schools that differ, so problems show up early.
School groups with sites in England and Scotland, or day and boarding schools under one owner, need registry, parent communication and policy agents that respect each school's identity. We build one platform with separate branding, admissions documents and approval routes, and central reporting for the group's leadership. Scottish and English schools in the group follow different admissions and qualification rules, and the platform keeps those apart.
College groups formed by mergers often run several campuses with different course offers. Course enquiry, enrolment, placement and exam administration agents can share one knowledge store while answering from each campus's own prospectus. Funding and learner support questions always reach advisers. Exam administration agents follow the awarding bodies each campus uses, and results week support can be switched on for every site at once.
Student records remain in the college's own system.
Companies selling software or services to UK schools increasingly want agent features inside their product. We build those features with the safety, data protection and audit controls schools will ask about, documented against the DfE product safety expectations in England and the equivalent expectations of buyers in the other nations. We can work under your brand, in your repositories and inside your release process.
How we work together
Smaller trusts sometimes start with a fixed scope core and one agent. Larger trusts, college groups and suppliers more often take a phased programme across several terms, or a dedicated team that works alongside their own staff. As an education AI agent development company UK organisations work with remotely, we run every stage by video call. Codeeo has delivered 200+ projects across the UAE and the US, and our team of 80+ is based in Dubai, Riyadh and Karachi. We do not have a UK office and do not make site visits. At handover your staff receive admin training, written runbooks and access to every repository.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We work with the cloud and productivity platforms your organisation already licenses, whether Microsoft 365 and Azure or Google Workspace and Google Cloud, choose models that meet your data protection requirements and keep hosting in the UK where your policies demand it.
01Mobile
02Data and cloud
03Marketing and tracking
Shared core first, then one agent at pilot sites, then phased rollout.
We start by mapping every site's nation, local authority and information system, then build the common pieces once: connectors, a policy store, approval routing, safeguarding detection and logging. The first agent is piloted in a few contrasting schools or campuses, and other sites join in waves. This avoids rebuilding for every school and finds rule differences early. Rollout waves are timed around each nation's term dates, which differ between Scotland and the rest of the UK, so no site goes live during its exam season or the first weeks of the school year.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio