Custom School Administration Software and MIS for UK Schools

The UK school MIS market has been through years of upheaval. SIMS has lost much of its old dominance to Arbor and Bromcom, and ScholarPack has been sunset. Schools that picked a platform five years ago now face forced migrations, rising licence fees and the same question again: which system fits how we work?

For most single schools with standard operations, a commercial MIS like Arbor or Bromcom is probably fine. If your situation is more complicated, such as a multi-academy trust with mixed school types, an independent school with non-standard fees, or integration needs no off-the-shelf product supports, a system built around your own workflows is worth considering.

I run ByteGears as a senior-led studio. You work directly with me, the person writing the code, from scoping through to deployment, with trusted specialists brought in where a project needs them.

MIS, SIS or school administration software?

These are mostly names for the same system. UK schools and trusts call it an MIS. Colleges, universities, international schools and US vendors call it a student information system (SIS). Whatever the label, the core is pupil records, attendance, assessment and communication with parents.

The difference that matters is the market a product was built for. A UK school needs DfE census returns, statutory attendance submissions, EHCP tracking and safeguarding records an inspector will ask for. An international SIS often has none of these, while a UK MIS may not cope with rolling enrolment, multiple currencies or UKVI attendance reporting for visa students. If you sit between the two, for example a language school, an international school in the UK or an FE college with apprenticeship programmes, that gap is often why a custom build comes up.

Where off-the-shelf school MIS platforms fall short

Most commercial school management systems work reasonably well for straightforward single-school setups. Problems start when your situation doesn’t match the vendor’s assumptions.

Rigid workflows. Standard MIS platforms impose their own structure for attendance, behaviour, assessment and pastoral care. If your school uses a different approval chain, a non-standard curriculum (Montessori, IB, project-based learning) or an unusual pastoral structure, the system won’t bend, and you change your processes to fit the software.
Integration that goes one way. Finance sync with Xero or Sage often works at a basic level, but two-way, real-time integration is rare. A pupil moved between sets in the LMS still has to be updated in the MIS by hand. Connecting to specialist SEND software, niche catering platforms or bespoke HR systems usually means paid custom work from the vendor or manual workarounds.
Multi-site headaches. MATs with mixed school types (primary, secondary, special, alternative provision) find that commercial platforms impose one reporting structure. Trust-level dashboards rarely allow for the differences between how a primary school and a PRU run.
Reporting that misses the point. Standard reports rarely match what your leadership team or governors need. Custom reports are unavailable, expensive or slow, so staff export to Excel and build pivot tables by hand.
Pricing that escalates. Per-pupil licensing, per-module add-ons and annual price increases are common, with implementation, migration and training charged on top.
Vendor lock-in. Proprietary data formats, vendor-owned customisations and high switching costs leave schools feeling trapped. When The Key Group acquired Arbor, Integris and ScholarPack, then sunset ScholarPack, affected schools had no choice but to migrate again.
Safeguarding shortfalls. Some platforms lack clear DSL escalation workflows, don’t flag attendance patterns for welfare monitoring, or have incomplete audit trails. These gaps surface at the worst time: during an Ofsted inspection or a safeguarding investigation.

What I build instead

I start with your processes. I watch how your office staff, teachers and leadership team work, then build software around that, so nobody relearns their job to suit the code.

You own the system. No subscriptions, no per-pupil fees, no forced upgrades. The code is yours and you control the roadmap.

Integrations that hold up. I connect to Xero, Sage, Google Workspace, Microsoft Entra ID, Moodle, Google Classroom, Canvas, ParentPay, Stripe and DfE statutory returns. Where you need real-time, two-way sync rather than nightly exports, I build it. Where you use specialist systems commercial MIS products don’t support, I write the connectors.

Compliance from the architecture up. UK GDPR, safeguarding (Children Act 1989, Education Act 2002), the DfE school census and School Workforce Census, attendance reporting to local authorities, EHCP tracking and Ofsted evidence are part of the data model and workflows from the first release.

Modular and phased. A working core goes live first, then finance, safeguarding workflows, LMS integration and analytics follow as you need them, with no big-bang migration and no disruption mid-term.

Core features

Most schools want some combination of these.

Pupil records and data management

Central record for demographics, contacts, medical information, dietary requirements, free school meals eligibility, SEND flags and EHCP status
Photo and document storage with role-based access
Retention policies aligned to statutory guidance
GDPR tools: consent management, erasure requests and subject access request handling

Admissions and enrolment

Application intake, interview or assessment notes, offers and acceptances
Waiting lists with automatic enrolment when a place is accepted
Rolling enrolment for colleges, language schools and online providers that don’t run on a September intake

Attendance and registration

Digital registers with your own absence codes and automated alerts to parents
Attendance pattern detection for safeguarding (persistent absence, unexplained absence, children missing education)
Statutory attendance submissions to the local authority and DfE
Support for the attendance guidance that became statutory in August 2024
Attendance reporting for visa sponsors where you teach international students

Assessment and progress tracking

Grade entry with your own grading scales (percentage, letter, descriptor), weighted calculations and predicted versus actual grades
Support for Progress 8, EBacc and non-standard curricula
Moderation and marking workflows
Progress flags: on track, at risk, accelerated
Exam entry management, results recording and transcript generation

Behaviour and safeguarding

Incident logging with severity grading and sanction tracking
Exclusion records, suspensions and permanent exclusions, with appeal tracking
Safeguarding concern recording with DSL-only access controls
Escalation workflows to MASH and multi-agency partners
Staff DBS status tracking and clearance monitoring
Full audit trail for Ofsted and police investigations

SEND

EHCP assessment and plan tracking with annual review scheduling
Support plans with progress monitoring
Support staff allocation and caseload management for the SENCO

Parent portal

Real-time access to attendance, grades, behaviour records and reports
Event and trip management with permission slips
Fee statements, payment history and online payment
Direct messaging to staff with read receipts
Parents’ evening booking

Timetabling and scheduling

Class scheduling with teacher allocation and room management
Conflict detection, cover management and substitution tracking
Complex timetables: split-site, shared staff, cross-phase groups, rotating weeks

Finance and billing

Fee invoicing with VAT calculation, recurring charges, and scholarship and bursary adjustments
Payment reconciliation linked to Xero, Sage or your existing accounting system
Arrears tracking and automated payment reminders
Trip and activity billing
Inter-school billing for MATs with shared services

Reporting and dashboards

Leadership dashboards with drill-down from trust to school, year group, class and pupil
Custom report builder with export to CSV, PDF and Excel
DfE census and School Workforce Census submission support
Cohort analysis and attainment gap tracking
Scheduled reports distributed by email

Integrations

Single sign-on via Google Workspace or Microsoft Entra ID
Finance: Xero, Sage, AccountsIQ
Learning platforms: Moodle, Google Classroom, Canvas
Assessment and analytics: CAT4, Power BI
Parent payments: ParentPay, Stripe, PayPal
Communication: SMS providers, email platforms, Microsoft Teams, Slack
Document storage: Google Drive, OneDrive
REST API and webhooks for third-party systems

How a project works

First Gear. I document your current processes, map your data, identify integration points and agree priorities with your school business manager, IT lead, SENCO and headteacher. If you’re migrating from an existing MIS, I assess data quality and plan the extraction. You get a working prototype of one core workflow and a fixed-price build plan.

Core build. I build the core first, usually pupil records and attendance, and you test working software as it grows. Assessment, the parent portal, SSO and further modules follow in phases.

Data migration. I extract data from your existing system (SIMS, Arbor, Bromcom or spreadsheets), cleanse it, resolve duplicates and inconsistent field mappings, and run a pilot migration on a small subset before the full load. For multi-site trusts with years of history, this is the most time-consuming part.

Testing and parallel running. The new system runs alongside your existing one so you can verify data accuracy while staff test real workflows. Go-live is timed for a half-term or summer break.

Training and handover. Office staff, teachers and leaders each get training on the parts they use. I also train a few super-users who can support colleagues, and provide written guides and video walkthroughs for the parent portal.

After launch. Bug fixes, security patches and new features come from the person who built it.

Cost and ownership

Custom development costs more up front than a SaaS subscription.

A SaaS MIS charges a yearly licence that grows with your roll, plus implementation, data migration and training at the start, and module add-ons, integration fees and annual price rises after that. Over five years those add up, and you still don’t own anything.

Most builds cost £2k–£10k and go live within a month, with the price fixed at the end of First Gear. A multi-academy trust project with cross-school consolidation, finance integration and safeguarding workflows, or a large independent school with complex fee billing, is split into phases, each fixed-price.

Once it’s built, you stop paying licence fees. You own the code, and you’re not exposed to vendor price increases, forced migrations or product discontinuations. For schools and trusts spending heavily on SaaS plus workarounds, that changes the economics.

The main MIS suppliers don’t publish licence prices, so the number to compare against is your own: last year’s MIS invoice, the add-ons and integrations billed on top, and the staff hours spent on workarounds. Send me those and I’ll set them against a fixed-price build.

Who this works for

Custom school administration software isn’t for everyone. A single primary school with 300 pupils and standard operations is probably fine with Arbor. Here is where a custom build makes sense:

Multi-academy trusts with mixed school types (primary, secondary, special, alternative provision) needing consolidated reporting that respects how each school runs, rather than forcing a single template
Independent schools with non-standard fees, such as scholarships, bursaries, multi-currency boarding fees and VAT on extras, that commercial billing modules can’t handle without extensive configuration
Schools locked into legacy SIMS with years of custom fields, bespoke reports and integrations that make moving to another commercial platform prohibitively complex
Special schools and alternative provision tracking EHCP outcomes, individual curricula and multi-agency safeguarding workflows that standard products don’t support well
FE colleges and training providers managing vocational timetables, employer engagement and off-the-job training hours for apprenticeships
Language and international schools handling rolling enrolment, several curricula or currencies, and attendance reporting for UKVI
Nursery and early years chains managing Ofsted-compliant records, EYFS tracking, dietary and allergy management and parent communication across settings
Schools with unusual integration needs, such as specialist SEND software, niche catering platforms, bespoke HR systems or legacy finance tools no commercial MIS connects to
Tutoring centres and supplementary schools needing session booking, tutor allocation, progress tracking and payments in one system instead of three or four separate tools
Any school or trust that has been through a forced migration and doesn’t want to go through it again

Common Questions About Custom School Administration Software and MIS for UK Schools

Is a student information system the same as a school MIS? ›

Mostly, yes. UK schools say MIS (management information system); colleges, international schools and US vendors say SIS (student information system). Both hold pupil records, attendance, assessment and parent contact. A UK MIS also has to produce the DfE census returns, attendance submissions and safeguarding records that an international SIS usually leaves out, so check that before you buy one built for another market.

How does custom development cost compare to SaaS school MIS platforms? ›

A SaaS MIS charges a yearly licence, usually per pupil or per school, with implementation, migration, training and extra modules on top, and the fee rises as your roll grows. A custom build costs more up front but carries no licence fee afterwards and you own the code. Most of my builds cost £2k–£10k, fixed at the end of First Gear; a trust-wide system is split into phases, each priced the same way. The economics favour building when you're already paying for workarounds, extra modules and manual processes on top of the licence.

What is the typical development timeline? ›

The first release, covering pupil records, attendance and one more core workflow, goes live within a month. Assessment, the parent portal, SSO and finance follow as further phases, each about a month long with its own fixed price. A multi-academy trust usually rolls out school by school, with go-live timed for a half-term or the summer break.

Can you integrate with our existing systems? ›

Yes. Common integrations include finance platforms (Xero, Sage), identity providers (Google Workspace, Microsoft Entra ID), learning platforms (Moodle, Google Classroom, Canvas), parent payments (ParentPay, Stripe), assessment data such as CAT4, BI tools such as Power BI, and DfE statutory returns. I build two-way sync where it matters, so a class change in your LMS updates the MIS too. Where a system has no API, I use CSV, SFTP or a custom adapter.

What about GDPR and safeguarding compliance? ›

Every system includes encryption at rest and in transit, role-based access, full audit trails and retention schedules aligned to statutory guidance, plus subject access request tooling. Safeguarding modules support concern logging with DSL-only access, escalation workflows, MASH referrals and attendance pattern alerts for welfare monitoring. Data can be hosted in UK data centres.

How do you handle data migration from our current MIS? ›

I extract, cleanse and map your existing data, whether it's in SIMS, Arbor, Bromcom or spreadsheets. I start with a data audit for duplicates, missing fields and inconsistent codes, run a pilot migration on a small subset, then run old and new systems in parallel before cutover so nothing is lost. Multi-site trusts with years of history and custom fields take longest.

When does a custom build make more sense than Arbor or SIMS? ›

Off-the-shelf MIS platforms work well for single schools with standard operations. Custom makes sense when you have multi-site complexity across different school types, unusual fee structures, non-standard curricula, integration needs commercial platforms don't support, or a legacy system carrying years of costly customisations. If your staff spend more time working around the software than with it, that's usually the signal.