The School AI Renewal Checklist for 2026

Twelve questions to test every AI contract before you renew

School leaders reviewing an AI procurement renewal checklist together

AI renewals used to be routine. A school checked usage, compared the price with last year, and signed again if staff seemed happy. In 2026, that is no longer enough. AI tools now sit inside planning, report writing, safeguarding workflows, communications and administrative systems. If a supplier changes its model, narrows geographic access, shifts terms, or cannot explain where its training data came from, the risk sits with the school.

That is why renewal season needs a tougher due-diligence standard. Schools should ask vendors for evidence they can inspect, not promises they are expected to trust. If your team has already started reviewing policy and compliance, articles such as this EU AI Act roadmap and this AI policy sprint pack can help frame the wider governance picture.

Why standards changed

Several shifts have made 2026 renewals more complex. First, geographic availability is less stable than many schools assume. A tool available in one country may not be fully supported in another, or key features may be disabled regionally. That matters if a trust, network, or international school group wants a consistent workflow across sites. It also matters if teachers build routines around features that disappear later. The issues explored in this piece on geographic restrictions are no longer edge cases; they are procurement concerns.

Second, provenance disputes have become harder to ignore. Schools are increasingly asking whether vendors can prove lawful sourcing, licensing and governance around training data. That is sensible. A supplier may offer polished assurances, yet still struggle to provide documentary evidence. If you want a deeper look at that problem, these provenance questions for schools are a useful companion.

Third, regulatory pressure has sharpened expectations. Even where a school is not directly governed by one specific framework, the EU AI Act and similar regimes are influencing contract terms, documentation, risk classification and transparency standards worldwide. Vendors that cannot describe their position clearly may be signalling a broader weakness in governance.

Renew or stop?

Before asking the 12 questions, decide whether the tool should be renewed at all. This is the step schools often skip. A subscription that is rarely used, duplicates another service, or creates more review work than time savings may not deserve a second year. A department may love a tool because it is familiar, but familiarity is not the same as value.

Start with basic evidence. How many staff actually use it? Which tasks does it improve? What risks has it introduced? Has it reduced workload in a measurable way? If your school has been tracking adoption and impact, a structured review like this departmental audit scorecard can help you decide whether to scale, pause or drop a product before contract talks begin.

The 12 questions

1. Service availability

Where is the service actually available and supported? Ask for a written list of supported countries, languages, hosting regions and feature differences by location. Do not accept “global availability” as a complete answer. A school with campuses in different countries, or staff travelling between them, needs to know whether access, support hours or compliance commitments vary.

2. Contracting entity

Which entity is the school contracting with, and under which jurisdiction? Many suppliers operate through multiple legal entities. The sales team may be in one country, invoices may come from another, and the contract may point to a third. Your school should know exactly who carries the contractual obligation, where disputes would be handled, and whether subcontractors are material to delivery.

3. Data flows

What data goes in, where does it go, and who can access it? Ask the supplier to map the full data journey. That includes prompts, uploaded files, metadata, user identifiers, generated outputs and admin logs. Schools should also ask whether support staff, engineers or subprocessors can access customer content, and under what controls. If you need a practical model for this review, this privacy audit checklist is a strong starting point.

4. Retention and deletion

What is the retention, deletion and export position at the renewal point? This is crucial when a school is deciding whether to continue. Can you export prompts, outputs, settings and user history in a usable format? How quickly is data deleted after termination? Is deletion automatic, partial or available only on request? Ask for the process in writing, including timescales.

5. Training-data provenance

What can the vendor prove about training-data provenance and licensing? This question should be direct. Ask what evidence exists, who reviewed it, whether licences were obtained where required, and how disputes are handled. If the supplier cannot produce a clear answer, that should weigh heavily in your decision. “We take IP seriously” is not evidence.

6. Training on your data

Are customer prompts, files or outputs used for model training or tuning? Schools should ask this in plain terms and request a contract clause, not just a help-centre link. Clarify whether data is used for foundation model training, product improvement, safety tuning, human review or evaluation. Also ask whether defaults differ between free, education and enterprise tiers.

7. Safety controls

What safeguards, refusal rules and escalation pathways exist for school use? A supplier should be able to explain moderation controls, age-appropriate boundaries, abuse detection, incident response and routes for urgent review. In practice, a school needs to know what happens when a pupil generates harmful content, a teacher receives a false claim, or a safeguarding-related prompt raises concern.

8. Regulatory classification

How does the supplier classify the tool under the EU AI Act and similar regimes? Even if your school sits outside the EU, this answer reveals how mature the vendor’s governance is. Ask whether the supplier has completed a formal classification exercise, what obligations it believes apply, and what documentation it can share. Vague answers here often predict weak answers elsewhere.

Ready to Revolutionise Your Teaching Experience?

Discover the power of Automated Education by joining out community of educators who are reclaiming their time whilst enriching their classrooms. With our intuitive platform, you can automate administrative tasks, personalise student learning, and engage with your class like never before.

Don’t let administrative tasks overshadow your passion for teaching. Sign up today and transform your educational environment with Automated Education.

🎓 Register for FREE!

9. Audit evidence

What audit evidence, logs and documentation will the school receive? A reliable supplier should offer more than a dashboard screenshot. Ask what logs are available to administrators, what policy documents can be shared, how incidents are recorded, and whether independent assurance reports exist. For schools using AI in report writing or other high-volume workflows, auditability matters as much as convenience, as discussed in this comparison of AI assistants and audit trails.

10. Mid-contract change

What happens if the model, pricing or terms change mid-contract? AI products are changing quickly. A school may buy one thing and receive another six months later. Ask whether the vendor can swap the underlying model, reduce limits, add adverts, retire features or alter pricing during the term. If that sounds unlikely, remember how quickly free and paid offers can shift, as noted in this briefing on AI dependency risk.

11. Exit and continuity

What are the exit rights, migration routes and continuity plans? A good renewal review asks not only how to stay, but how to leave. Can the school migrate data cleanly to another vendor? Is there a transition window after termination? What happens if the product is discontinued, access is suspended, or the supplier exits your region? Continuity planning is part of responsible procurement, not a sign of mistrust.

12. Walk-away threshold

What would make the school walk away from renewal? This final question is for your internal team. Set a threshold before negotiations begin. For example, your school may decide not to renew if the supplier cannot provide written training-data provenance, refuses deletion commitments, will not confirm non-training on customer content, or cannot explain its regulatory classification. A clear walk-away line keeps the process disciplined.

The evidence pack

By the end of the review, your school should be able to assemble a one-page renewal evidence pack for senior leaders, governors and procurement colleagues. Keep it concise and factual. Include the product name, supplier entity, jurisdiction, supported geographies, key data flows, retention terms, provenance evidence, training position, compliance classification, audit materials, change clauses, exit rights and your renewal recommendation.

This one-page summary is especially useful when several products are up for renewal at once. It allows decision-makers to compare tools on evidence quality, not sales confidence. In many schools, that simple shift will lead to better outcomes than any lengthy vendor presentation.

A stronger renewal culture

The real goal is not to make procurement slower. It is to make renewal decisions more defensible. A school that asks better questions is more likely to spot weak contracts, hidden dependencies and unsupported assumptions before they become expensive problems.

In 2026, the strongest AI buyers in education will not be the schools with the biggest budgets. They will be the schools with the clearest standards. If a vendor is trustworthy, these questions should not alarm them. They should be ready with documents, explanations and contractual clarity. If they are not, that tells you something important.

To calmer renewal meetings and stronger evidence on every contract, The Automated Education Team

Table of Contents

Categories

School Operations

Tags

Procurement Safety Ethics

Latest

Alternative Languages