Who Keeps the Lights On? Governing Supplier Concentration and Renewal Risk

Independent schools are rarely the sole authors of their own daily operations. Catering, coach transport, IT support, cleaning, grounds maintenance, payroll systems, admissions software and a range of specialist pupil services are frequently delivered by external suppliers. That arrangement can be efficient and well managed. It can also leave a board with a misleadingly simple picture: a monthly invoice, a named account manager and an assumption that someone else is watching the contract.

For governors, the question is not whether outsourcing is appropriate. It is whether the school understands the dependencies it has created, the terms on which those dependencies rest and what would happen if a critical provider failed. In the 2026–27 environment, with cost pressures, cyber exposure and recruitment constraints affecting suppliers as well as schools, that understanding belongs in the boardroom.

From invoice oversight to dependency oversight

A contract register is not a procurement filing system. It is a governance tool. Its purpose is to identify which external relationships matter most to the school’s educational offer, regulatory compliance, safeguarding arrangements and financial stability — and to ensure that those relationships are actively managed.

The first step is therefore not to list every purchase order. It is to agree a definition of criticality. A supplier may be critical because of annual value, but also because it controls pupil data, provides transport for vulnerable pupils, supplies meals to boarders, maintains the systems on which admissions depend or holds specialist expertise that cannot be replaced at short notice. A small contract can carry a large concentration risk.

A useful register will distinguish between strategic, operational and low-risk suppliers. For each strategic or operational contract, governors should expect to see the supplier’s legal entity, the service provided, the contract start and end dates, notice periods, renewal dates, annual value, payment terms, termination rights, service levels, key performance indicators and the named internal owner. Where relevant, it should also record data processing arrangements, subcontractors, insurance cover, business continuity plans, regulatory dependencies and the exit route.

The register need not be exhaustive in every field. It should be sufficiently complete to answer three board-level questions: what would hurt, how soon could it hurt and how prepared are we?

Bringing concentration into view

Boards are accustomed to financial concentration in fee income, donor support or borrowing. They should apply similar discipline to supplier concentration. If one provider delivers catering across several sites, or one IT partner supports both the school’s management information system and its network, the loss of that supplier is not a single-service inconvenience. It is a compound event.

A concise board dashboard can show the top ten suppliers by annual value, the top ten by operational criticality and any supplier where the school represents a material share of the provider’s own revenue. That last point matters: a school may be a small customer to a national firm but a dominant customer to a local coach company or specialist therapy provider. Dependence can run in both directions.

Governors should also ask how contracts interact. A catering contract that relies on school kitchen staff, a transport contract that depends on a single depot and an IT contract that includes embedded school-based technicians all create different continuity questions. The register should make those linkages visible rather than leaving them to be discovered during an incident.

The renewal calendar as a governance rhythm

Many supplier risks are foreseeable because contracts have dates. A renewal calendar, reviewed at least annually and ideally each term, allows the school to test the market, negotiate from evidence and avoid the false economy of rolling forward simply because time has run out.

For critical contracts, the board should expect a renewal paper well before the notice deadline. That paper should not be a recommendation dressed up as a review. It should set out the case for continuation, retendering, insourcing or a hybrid arrangement, with evidence on cost, quality, compliance, resilience and pupil impact. It should also identify the cost and disruption of transition, including staff implications where relevant.

The calendar is also a useful check on governance drift. A contract that was once strategically important may no longer be so; a previously low-risk supplier may have grown into a critical dependency through incremental variations. Regular review keeps the register honest.

Questions to ask before renewal

Governors do not need to negotiate contracts. They do need to test the assurance they are given. Before a critical renewal, the following questions are a reasonable starting point:

• What evidence do we have that the service is performing against its agreed standards, not simply that no one has complained recently?
• What is the total cost of the relationship, including management time, variations, ancillary charges and exit costs?
• How easily could we replace the supplier, and what would the first thirty days of transition look like?
• What dependencies has the supplier created through subcontractors, proprietary systems or embedded staff?
• What has changed in the supplier’s financial position, ownership or capacity since the contract began?
• How are safeguarding, data protection, cyber security and regulatory obligations addressed in the contract and in practice?
• What are the termination rights, notice periods and service credits, and have we ever tested them?
• Who inside the school owns the relationship, and what does that person report to the board?

These questions are not a substitute for legal or procurement advice. They are a way of ensuring that the board’s decision is informed by more than price and continuity.

When a critical supplier falters

Supplier failure rarely arrives without warning. Late deliveries, staff turnover, missed service levels, requests for early payment, unexplained changes in account management or a sudden loss of subcontractors may all be signals. The contract register should identify who is responsible for monitoring those signals and when an issue escalates from operational management to board assurance.

If a critical supplier is in difficulty, the board should expect a short, evidence-based assurance pack. It should cover the nature of the problem, the pupils and services affected, the supplier’s remediation plan, the school’s contingency options, communication arrangements for parents and staff, and the financial exposure. Where safeguarding or regulatory compliance is involved, the pack should also confirm that the appropriate external notifications have been considered.

Contingency planning should be proportionate. For some contracts, a documented fallback provider is sufficient. For others, the school may need standby arrangements, stock buffers, temporary staffing plans or a staged exit. The important point is that the plan is written down, tested in discussion and owned by a named senior leader.

A register that earns its keep

A contract register should not become a bureaucratic exercise. Its value lies in focus. If it helps governors see the school’s critical dependencies, review renewals in good time and ask better questions when a supplier falters, it is doing its job.

The board’s role is not to manage suppliers. It is to satisfy itself that the school’s most important external relationships are understood, monitored and supported by credible contingency arrangements. In an operating environment where so much of the school day depends on someone else’s systems, staff and vehicles, that is a proper governance concern — and a practical one.