Changing Supplier Does Not Have to Rest on One Handover Day. Here Is the Benchmark We Would Set.

The institution has decided, at last, to consider another supplier. A paper sets out what a change would look like.

On the last day of the old contract the present supplier’s system is switched off. On the first day of the new one, the new supplier’s system must be running, with every admission, fee record and certificate in it. The paper calls this the transition. It has one date.

The head of the institution asks what happens if the new system is not ready. The answer is that the old contract would have to be extended, at short notice, on whatever terms were offered.

What We Found

For this article we went through the public record on what a change of supplier involves: a trade press report in mid-2026 on one schools authority’s IT contract in the UK, one vendor’s survey of about 500 IT professionals in the US (2025, not about education), and the UK government’s own review of its digital services, published in January 2025.

First, what we did not find: no public case of a college or university moving off the supplier of an application built for it, no figure for what a change of supplier costs an institution, and nothing from India or the Middle East on this issue.

A change of supplier can be started and not finished. By the trade press report, one UK schools authority signed an earlier contract, worth several hundred million pounds, to replace the long-standing arrangement for its schools’ IT. That contract ended within its first year, which the report describes as agreed by both sides and without fault. We did not examine why the replacement ended, and draw no cause from it. It is a contract to run schools’ networks and IT service, which is not our kind of work, and we pass no judgement on the authority or either supplier.

Fear of disruption is a common reason to wait. In one vendor’s survey of about 500 IT professionals in the US, nearly four in ten named fear of disrupting operations among their reasons for not modernising. The survey is cross-sector, and about two thirds of those who answered work in technology or software.

Arrangements last a decade. The UK government’s own review found that councils buy their children’s social care systems from 3 main providers, and use each system “for a median 10-year period”. These are packaged products bought by local councils, not education, and no method is given for the figure.

Our reading: when leaving is planned as one step on one date, it is a step an institution can rarely afford to get wrong, so it is put off and the contract is extended. The records above do not tie any delay to one-step planning, and the schools record is not an account of one. Our point is narrower: a plan with no single handover day removes one reason to wait.

What a Staged Exit Opens Up

The usual view is that a change of supplier is one transition, on one date, set by the old contract. Our reading is that an institution which leaves one module at a time opens up three things the single handover cannot.

No single day carries the institution. The old system keeps running under its present supplier while each module moves, so a module that is not ready waits, and admissions, fees and results do not all meet a new system on the same morning.

Proof before acceptance. Each module is checked, function by function, against what the old system did, before anyone accepts it.

A decision after each module. After each accepted module the institution can continue, or pause. At no point does the whole system rest on a firm that has just arrived.

This is our reading of the evidence. It is not a measured market figure.

Four Ways to Leave, Weighed

There are four real options. Each one is right for somebody.

Option	When it fits	What it risks
One switch-over on the day the old contract ends	The system is small, well described, and a short stop would not hold up admissions, fees or results	Everything rides on one date, and the old supplier’s knowledge leaves just as it is needed
Build a complete new system beside the old one, then switch everything at once	The institution can fund both systems for the whole build, and has a full description	Two systems paid for throughout, and the switch-over risk only postponed
Extend the old contract for a short term while a new firm builds everything	The institution needs time and the present supplier agrees to a short extension	The new system is still switched over on one day, and the short term may need extending again
Leave one module at a time, with the old system still running under the present supplier until the last module has moved	The institution cannot stop admissions, fees or results, and wants proof at each step	The first step is an assessment that costs money before anything moves; it relies on the present supplier keeping the old system running while modules move, under the institution’s contract with it; for a time the institution pays two firms; each stage must still be approved

Where You Are Now, and Where You Should Be

Before any work begins we set a benchmark: a few measures taken from your own systems, each with a target. For this issue it would look like this.

Measure	Typical starting point	Where it should be	How it is checked
Share of the system described in a document the institution holds	Little or none; the original tender document describes the system as planned	The whole system, in a current specification the institution owns, confirmed by its own staff	The specification
The cost of leaving	Unknown until after the end date, if ever	Known before the end date, set beside the cost of staying	The cost comparison
Modules traced	None; the change is pictured as one handover	Every old function in each module linked to its replacement	The traceability matrix
Stages accepted	A completion certificate signed on a switch-over date	Each module accepted by a named person at the institution before the next begins	The staged plan, updated after each module
The old system	Switched off on one date	Kept running by the present supplier until the last module has moved	The staged plan

The starting points above are what we expect to find; in an engagement they are replaced by your own figures, taken in the first review. The targets are what we would work towards with you. They are not results we have already achieved for an education body.

How We Work With You

1. We listen: a free Reliability Review. A first conversation about the system, the contract’s end date and any transition plan already drafted. You leave with a short written note of what we found. You can start with a conversation about the system; we ask for read-only code access only when the assessment begins.
2. We research. We research your sector, the regulator’s position and what the public record says about firms in your situation. This article is an example of that work.
3. We read the system and propose: the Legacy System Specification Assessment. Here the system is the application the institution wants to move off its present supplier. The institution arranges read-only access to the code with its supplier, as its contract allows. It produces a map of the system as it stands, a written specification of what it does, a risk register, a cost comparison between keeping and replacing the system, and a staged plan with a fixed quote. AI does a first pass, our senior engineers review it and trace it to the code, and your own experts confirm it. Code access is read-only and logged, never used for training, and deleted within 30 days of the evaluation ending unless we engage. You get the options and our recommendation.
4. If you approve, we build. We replace a system one module at a time while the old one keeps running. We never do a single cutover. Each module has a traceability matrix. The work is billed by milestone, each milestone tied to a module you accept, and you can pause after any accepted module.
5. We review against the benchmark. Before work starts we set the benchmark. After each module we show you where each measure stands, and the filled-in benchmark is yours at the end.

The Review is free. Every paid step is fixed price, agreed at scoping. Stop after any step. The findings are yours. The assessment fee is credited in full against the first build stage if it starts within 90 days of the report.

What we do not do: we do not take over the running of the supplier’s system or keep it running while modules move; the present supplier does, under the institution’s contract with it. We do not negotiate with a supplier, give legal advice, or obtain code or data from a supplier. We do not move, clean or vouch for student records; moving records is done by the institution’s own people or a firm they choose. We do not run a school’s or a campus’s network or IT service, and we do not implement or move packaged products. We do not work in COBOL, RPG or FoxPro or on mainframes. We do not say a staged exit is quicker or cheaper overall; it may take longer on the calendar. We do not say we are empanelled with any government, university or board, we give no advice on budget or purchasing rules, and we do not say an institution’s budget year, governing-body approval or tender will fit any of our terms. We have no published case of this work for an education body.

What changes for the business:

Role	What they gain
Head of institution	A change of supplier no longer means staking admissions, fees or results on one handover day.
Head of purchasing	The work can be bought one part at a time, without committing to a single supplier for another long term.
Head of IT	Each part that moves sits on technology the institution controls, while the supplier’s system runs until the last part has gone.
Head of finance	Money for the exit is asked for one stage at a time, each stage with its own evidence.
Registrar	Admissions, records and certificates move one at a time, each checked and accepted, and nothing rests on a single handover day.

The cases in this article, and what IOanyT does about that kind of problem:

The case	What IOanyT does
This article names no organisation as a case. Its figures are one unnamed schools authority’s IT contract, one cross-sector survey and one review of councils’ packaged systems.	We make no comment on the authority or its suppliers, and our part is far narrower: we do not run networks or IT services. For an application a supplier built for an institution, we replace one module at a time while the present supplier keeps the old system running, and check each module against a traceability matrix before it is accepted.

IOanyT is a consultancy with its own engineering team: we study the problem, recommend, and prove it by building only what you approve. We turn one handover day into modules, each checked and accepted before the next, while your present supplier runs the old system.

Book a free Reliability Review →

Get a fixed quote →

See the Legacy System Specification Assessment →