ISA Education Technologies Ltd

Built by people who
know the school day.

The reception queue at 08:45, the register chase, the fire drill count: ISA Bridge is built by a team that understands those moments firsthand. This page is about who we are, and why schools put safeguarding records, door locks and payment data in our hands.

The legal facts ISA Education Technologies Ltd

Registered in England and Wales, company number 15632053, incorporated 10 April 2024. Registered office: 124 City Road, London, EC1V 2NX. ISA Bridge is our product.

Why the company exists

Your MIS was never
going to do this part.

School management systems are built around the pupil record: admissions, marks, groups, census. They are good at it. But the operational half of the day happens somewhere else entirely, and it has been colonised one contract at a time. Dinner money here. The visitor book there. Concerns in a portal. Room bookings in a spreadsheet only one person understands. Consent replies in a mailbox.

Each of those systems keeps its own copy of your people, and each copy drifts. The result is not a technology problem that anybody notices. It is a Tuesday where a simple question takes four applications and a phone call, and a fire drill that depends on a list printed at ten to nine.

ISA Bridge is one platform for that half of the day, including the parts that involve a physical building. We think that is the useful thing to build, and we think it is unusual that nobody had built it.

Provenance

A young company on
a proven platform.

ISA Bridge is built on an engine that has been running whole school operations in production for years: registers, staff attendance, approvals, bookings, catering and parent services. It is not a prototype, and it was not written last year by people learning what a school is.

The UK product is built on top of that engine by the same people, which is why capabilities that normally take a suite years to connect - the register feeding the meals, the door feeding the roll call - worked together here from the start.

A mature engine, purpose-built for the UK Written by people who have run school operations Hosted in the UK, on your own instance
How it is built Every school gets its own instance and its own database

Not a shared table with a school identifier in it. Your own application instance, your own database and your own encryption key. That is an architectural decision made before there was any commercial reason to make it.

What you get instead of a logo wall

Four things only
a focused team delivers.

Scale buys a big supplier many things. It also costs them these four, and they are the four that decide what the second year of a contract feels like.

01

You talk to the people who build it

There is no first-line queue and no ticket that gets triaged toward someone who might understand it. When a school tells us something is wrong, the person who fixes it is usually in the conversation. When you ask for something, the answer is a yes, a no or a date, from someone entitled to give it.

02

You can move the roadmap

An early school has real influence over what is built next. That is not a courtesy; it is how a product this broad gets the operational details right. Several of the things on this website exist because somebody running a school office said the first version was wrong.

03

Changes land in days

A big suite batches your request into a quarterly release and a voting board. Here, the school that asks for something talks to the person who builds it, and improvements ship as soon as they are ready. Several features on this website exist because a school asked for them.

04

Your data is yours, and so is the exit

Exit terms, export formats and notice periods belong in a contract before you sign it, not in a support ticket years later. Ours are written down and we will send them at the first meeting, because a supplier confident in its product has no reason to lock the door.

How we work

Three commitments
we will put in writing.

We survey before we promise

Anything touching your building - readers, terminals, a fire panel interface - starts with a site survey, and we will tell you if the answer is that it cannot be done well at your site. A quotation before a survey is a guess dressed up as a price.

We would rather sell you four modules than eleven

If you already have something you like, keep it. A platform argument that requires you to rip out a system that works is a sales pitch, not advice. We will tell you which parts of ISA Bridge would genuinely improve on what you run, and which would not.

The demo runs on your scenario, not ours

Bring a real process, with the awkward parts left in. We build the demonstration around it, and you leave with a written scope your governors can read rather than a slide deck. What you see is what your school would run.

Ask us anything a big supplier would dodge.

Who at your company can see our data. Where is it held. How fast do changes actually ship. What does the exit look like. Every answer comes from the people who build the platform, in the first half hour, in writing if you want it.

Book a first conversation