Services · Mobile app development · School apps

School apps for trusts and schools in all four UK nations.

Codeeo offers school app development UK schools and trusts can run as one product: a parent app, a staff app and an admin panel connected to the management information system you already hold. Absence reporting, consent, messages, payments and safeguarding records follow the rules of the nation each school sits in, because England, Wales, Scotland and Northern Ireland each publish their own guidance.

The app does not replace your MIS or your safeguarding software. It gives parents one place to act, gives staff fewer inboxes to watch, and gives trust leaders a single view across sites that may answer to different inspectorates. Schools keep their own identity inside it.

Built for
Multi-academy trusts, school groups, independent school foundations and local authority teams running schools in more than one part of the UK.
Typical timeline
Agreed after discovery, once the MIS platforms, nations and number of schools in scope are known, and written into a phased rollout plan before design begins.
What you own
The source code, both app store listings, the admin panel and all pupil and parent data, held in accounts your trust or school controls.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What a national school app includes

Features that hold up when one app serves many schools.

A single school can live with a messaging tool bolted onto its MIS. A trust with schools in several local authorities, or a group operating on both sides of a border, cannot. Data formats differ, statutory guidance differs and parents expect the same quality everywhere. We design the app around a shared core: identity, messaging, consent and payments built once. Each school then switches on the modules and wording that match its phase, its nation and its MIS. A Welsh primary, an English secondary academy and a Northern Irish grammar can sit on the same codebase without one school seeing another school's settings, pupils or policies. The list below is where most national school projects start, ordered by how often trusts ask for each piece in the first release.

Explain your project
  • MIS connectors per nation

    English schools commonly run SIMS, Arbor or Bromcom. Scottish council schools sit on SEEMiS, and Northern Irish schools work through the C2k service. We build an integration layer that reads timetables, classes, contacts and attendance from each source through the routes its owner permits. Each connector is tested against a copy of real data before it goes live.

    One app, fed by whichever MIS each school already trusts.

  • Nation-aware safeguarding settings

    Keeping Children Safe in Education applies to schools in England, and its 2026 edition took effect on 1 September 2026. Wales, Scotland and Northern Ireland publish separate guidance. Role permissions, retention rules and staff prompts are configured per school so each follows the guidance it is actually bound by.

    Safeguarding settings that match the law each school works under.

  • Absence reporting and register sync

    Parents report absence with a reason code in a few taps, and the record lands in the register for the attendance team to confirm. For English state schools, the app keeps the MIS accurate, which matters now that daily register data is shared with the Department for Education and the local authority.

    Fewer first-day phone calls and cleaner registers.

  • Staff concern handoff

    Teachers on a trip or at the gate sometimes need to record a worry before they reach a desk. The staff app captures a short note and passes it straight to the designated safeguarding lead through the recording system your school already uses, rather than storing a parallel copy that nobody audits.

    Concerns reach the right person without creating a second safeguarding record.

  • Consent records that stand up

    Trips, photographs, medical treatment and biometric catering each need their own consent. In England and Wales, biometric processing needs parental consent under the Protection of Freedoms Act 2012. The app stores who agreed, when and to which version of the form. Changes to a form create a new version, so older consents stay linked to the wording parents saw.

    A consent history the data protection officer can audit.

  • Welsh and English side by side

    Welsh-medium and bilingual schools need every screen, notification and form in Welsh, written properly, not machine translated at the last minute. We plan bilingual content from the first design so Welsh text fits layouts and parents choose their language once. Staff writing in English can request a Welsh version before sending.

    A parent app Welsh-speaking families can use in their own language.

  • Trust-wide dashboards

    Central teams see message reach, consent completion and absence reporting rates by school, without opening pupil records they have no reason to view. Access is limited by role, so a trust attendance lead sees patterns while only school staff see names. Figures refresh daily so leaders discuss current patterns.

    Leaders spot the school that needs support without breaching access rules.

  • Parents' evening and meeting booking

    Families with several children across different schools in the trust book slots for each child from one screen, choosing in-person or video appointments where the school offers both. Teachers see a running order on their phones, and the office no longer rebuilds timetables by hand from paper reply slips.

    Booking that respects siblings in different schools.

  • Closure and emergency alerts

    Snow, heating failures and building incidents close schools at short notice. Priority alerts go out by push notification, with SMS or email as a fallback, and show who has opened them, so office staff know which families still need a call. Templates for common closures are written in advance, so the office only fills in the details on the day.

    Every family reached quickly when a site closes.

  • Accessible from the first screen

    We design to WCAG 2.2 AA so parents using screen readers, larger text or switch controls can report an absence or sign a form without help. The Equality Act 2010 covers England, Scotland and Wales, while Northern Ireland has its own disability law, and both expect reasonable adjustments. We test with assistive technology on both iOS and Android.

    An app that every parent can operate without asking the office.

Who this is for

Schools and groups that outgrow a single messaging tool.

A national school app makes sense when the problem is coordination: too many systems, too many sites or too many sets of rules. It is rarely the right first step for one small primary already happy with its MIS parent module. These four situations are where we see the strongest case for building, and each needs a slightly different first release.

Before committing to a build, we compare what your current MIS parent modules and messaging contracts already do. If a configuration change solves most of the problem, we will say so in discovery rather than propose an app you do not need.

01

A multi-academy trust growing by conversion

Each school that joins brings its own MIS contract, its own messaging habits and its own parent expectations. Standardising everything at once rarely works. We build the app so a new school can join on its existing MIS and move to the trust standard later, while parents get a consistent experience from the day the school comes into the trust. Families get the same messages, absence reporting and consent screens whichever school in the trust their child attends.

The integration layer absorbs differences between schools.

02

A group with schools in more than one nation

An independent group with a school in England and another in Scotland, or a trust working along the Welsh border, faces different safeguarding guidance, inspectorates and terminology. Year 7 in one school is S1 in another. We configure each school's wording, guidance prompts and data rules separately on one shared platform. Year group labels, curriculum references and inspection terminology follow each school, so a parent in Aberdeen and a parent in Kent both recognise the language. Staff training material is adapted for each nation as well.

Terminology and guidance are settings, not separate apps.

03

A local authority supporting maintained schools

Councils that buy services for their maintained schools need an app those schools can opt into, with data held separately per school and clear controller responsibilities. We design the tenancy and data processing terms so each school remains the data controller for its own pupils. Schools keep their own branding inside the app, and the council sees only the aggregate figures the agreement allows. Council officers can manage onboarding centrally, while head teachers decide which features their own school switches on and when.

Clear controller and processor roles from the start.

04

An independent school foundation

Fee-paying schools often need boarding notices, weekend activity sign-ups, exeat requests and alumni contact alongside the usual parent features. Families may live overseas and expect the app to work across time zones and languages. We build these modules on the same core so day and boarding families share one app. House staff get their own view of who is in, who is out and who is signed off sick. Admissions staff can also send welcome packs to new families before term starts, and international parents can choose their preferred language for routine notices.

Boarding and day families in one product.

Six stages from first school to full rollout.

  1. 01Audit of systems and rulesWe list every MIS, payment service, safeguarding tool and messaging product in use across your schools, and note which nation's guidance each school follows. The audit tells us how many connectors and settings the build will need.
  2. 02Data protection impact assessmentWe prepare the information your data protection officer needs for a DPIA: data flows, retention, processors, hosting location and how children's data is minimised. Your DPO signs off the pack before build begins.
  3. 03Shared core designParents, teachers, office staff and trust leaders each get a role. We design the screens they share and the settings that change per school or per nation. Every role is checked against the principle of least access.
  4. 04Pilot school buildOne or two schools go first, chosen to cover different MIS platforms. Their feedback on absence reporting, consent and alerts shapes the release the rest receive. The pilot also proves each MIS connector under real conditions.
  5. 05Phased rolloutSchools join in planned waves, each with parent onboarding material, staff guidance and a check that MIS data matches what the app displays. No wave starts until the previous one is stable.
  6. 06Termly review and releaseUsage data, support tickets and policy changes, such as a new edition of statutory guidance, set the priorities for the next release each term. Governors receive a short report after each term.

Technology

What we build this with.

We usually build the parent and staff apps in Flutter or React Native, with a web admin panel and a cloud back end hosted in a UK region when your DPIA requires it. Sign-in can run through Microsoft or Google accounts the trust already manages, so staff use credentials IT already controls. Push notifications run through Apple and Google services, with SMS reserved for urgent fallbacks to keep messaging costs predictable.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

03Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions trusts and school groups ask.

By making nation, phase and MIS settings per school rather than building four apps.

Each school record carries its nation, its phase and its MIS. Those settings decide which year group labels appear, which safeguarding guidance staff prompts refer to, which consent forms are needed and how data is fetched. The parent experience stays the same everywhere, while the rules underneath follow the school. When guidance in one nation changes, only the schools in that nation receive the updated configuration. Schools that later move MIS, for example from SIMS to Arbor, change one setting and one connector rather than their parent app.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews