Most schools ask this in the first ten minutes of a call. It is a better question than “what does it do”, so here is the answer up front.
ISA Bridge is the operational layer around your system of record: the front door, the follow-up after the register, the money, the bookings, the approvals and the roll call. It is not an MIS and we would not sell it as one.
Which column a system falls into depends on how your school uses it, and we will go through yours line by line at the first meeting. This is the general shape.
The visitor book or sign-in system. Dinner money and wallet top-ups. The uniform shop. The parent app and messaging tool. Consent and survey forms. Room, minibus and equipment booking. Staff leave requests. Paper or email approval chains. The safeguarding case record.
That is commonly six to ten separate contracts, each with its own login, its own copy of your people and its own renewal date.
Your MIS. It remains the system of record for pupils, staff, marks, groups and census, and we read from it rather than competing with it. Your finance system stays too, along with your HR and payroll.
Also staying: your assessment platform, your teaching and learning tools, and anything you already run that works well. ISA Bridge is designed to take over the operational layer around them, module by module, at whatever pace your renewals allow.
Your MIS, through the established data route your school already uses, for pupils, contacts, staff, groups, rooms, attendance codes, medical and dietary information and free-meal entitlement. Your identity provider, so staff sign in with the Microsoft or Google account they already have. Your card payment provider. And, where relevant, your door hardware and your fire panel.
This is the part that only shows up once two of them are running. Because everything sits on one platform with one set of people, the modules compound: switch on a second and the first starts doing work it never did on its own.
None of those needs configuring as an integration. They are consequences of the data already being in one place, which is why they keep working when a supplier changes an API, and why nobody has to reconcile anything overnight.
One module replaces a contract. Several of them replace the reconciliation between contracts, which is where the actual hours go. The schools that get the most out of ISA Bridge are the ones that started with a single pressure point and kept going once they saw what the second module did to the first.
Ask what happens when a member of staff leaves at Easter. It is the quickest way to see the difference between a platform that shares one architecture and a portfolio that shares an invoice.
They are removed in the MIS. They may still hold a door card, still appear in the visitor system’s host list, still be a named approver, still be on the fire roll call print-out, and still have an account in the parent messaging tool. Somebody has to remember all six.
They exist once. Removing them removes their door access in the same act, and the instruction is held until the door next answers, however long it has been offline. They stop being an approver, stop appearing on the roll call, and their outstanding equipment loans are visible from the same screen.
The access review enumerates every member of staff, every role and every right, distinguishing what came from a role from what was granted directly. When somebody asks in November who could open which door in March, that is a screen rather than an investigation.
Included means it is part of ISA Bridge and you turn it on. Add-ons are licensed separately, and anything with hardware in it is scoped and quoted after a site survey.
A form, an approval route or a set of booking rules built in one school exports as a single file and imports into the next, with a preview of exactly what came across before anything is created. The trust decides what good looks like once, and schools adopt it rather than reinventing it.
The consolidation argument multiplies across a trust. A central team negotiating one operational platform rather than eight separate renewals per school is a procurement saving a CFO can put in front of trustees, and it removes eight sets of data-processing terms to keep track of.
Fifty-two named rights, composed into roles the trust defines, with the same two-person access review everywhere. When a trust DSL, a central finance lead or an auditor asks who can see what, the answer has the same shape in every school rather than depending on how each one was set up.
The trusts getting the most from ISA Bridge picked a single priority and rolled it out everywhere before adding the second. Safeguarding, the front door and the family app are the usual first choices, and each one gives the central team a consistent picture it did not have before.
Just the list, with roughly what each one costs and when it renews. We will map it against ISA Bridge and send back what a consolidated operational layer would look like for your school, with the renewal dates that make the sequence work. That is a more useful first exchange than a demo.
Get your systems mapped ↗