What Should Schools Ask an AI Vendor to Put in Writing?

A demonstration can show a school how quickly an AI tool produces a quiz, translates a message, or drafts a comment. The most important parts of adopting the tool are often the ones the demonstration cannot show. What information moves where? Who can change the service? What happens when a family needs an alternative or the school decides to leave?
Ask for written answers early enough for someone to examine them. A school can start with five questions, identify which answers belong in an agreement or supporting documentation, and decide which gaps need resolution before students and teachers rely on the service.
Why the question is timely
UNESCO's 2026 work on education in the age of AI includes a commissioned paper on procurement, along with work on learner safety and the full cost of ownership. The terms a school agrees to can shape what it can control after a tool enters classrooms. The European Commission's November 5 Education and Skills Package also describes new cooperation on trusted digital infrastructure and education services. These are policy developments and discussion papers. A school still needs to look closely at the product, all relevant agreements, and the proposed use.
1. What information does the tool need, and who can use it?
Ask the vendor for a plain description of the information collected in the school version of the product. Include prompts, uploaded work, voice recordings if applicable, account metadata, and usage logs. Ask what is optional, who receives the data, and which service providers help process it. Clarify what the vendor means by using information to improve its service and what control the school has over any use beyond delivering the product.
An illustrative example is a feedback app that operates with sample text during a trial but invites students to upload named assignments after launch. The school should examine the actual classroom configuration. A written data map can expose differences between what staff expected and what students would be asked to provide.
2. How can the school verify and change the settings?
Ask for documentation of school administrator controls and a chance to inspect an account configured the way the vendor proposes. Establish who can turn features on, see account activity, or create integrations. Decide how the school will be notified if features, processing arrangements, or defaults change.
Use a fictional student account and example work to try ordinary tasks. Compare what a student, teacher, and administrator can see. If a protection depends on a setting, document who enables it and when it will be checked again. This kind of review supports technical and privacy specialists by giving them a clear picture of the proposed workflow.
3. What happens when a learner needs another way to participate?
Ask the vendor to describe which functions work with assistive technology and where there are known gaps. A school can test a few essential tasks using keyboard navigation, a screen reader, or another relevant accommodation. Invite the accessibility team to help decide what adequate participation would look like.
A trial might show that a student can open an assignment but cannot reach the feedback controls with a keyboard. Record the barrier and ask how it will be addressed. Explain what alternative students will have while the issue is unresolved, including how they will receive the same instruction and support.
4. What support will the school receive when something goes wrong?
Find out how school staff can report a safety concern, confusing output, or a suspected data incident. Ask who responds, in what time frame, and what information the school can expect. Agree on a contact who can take ownership when the issue involves the vendor, another provider, and a school employee.
Evaluate the response process during a trial using a harmless example. Staff should be able to explain how they would pause an activity and help a learner while a question is being investigated. Make sure that teachers and families have a clear school contact, even if the vendor supplies a reporting tool.
5. What happens to the work, records, and accounts when we leave?
Ask what can be exported, in what format, and who can request it. Clarify what happens to student and teacher accounts and what retention applies after the school stops using the service, including backups and copies held by service providers where relevant. Ask how the school will receive confirmation that agreed steps were completed.
A school should be able to describe how teaching continues if it changes tools partway through a year. For example, a teacher may need to return drafts and feedback to students without requiring them to maintain a discontinued account. Knowing the exit route also makes a short trial a more meaningful option.
Record the vendor’s response beside the staff member who checked it. Store decisions with ordinary purchasing records so a new teacher or administrator can see how the tool was approved and which uses the approval covered.
Make the decision usable after the meeting
Put the answers beside the learning purpose, who will review the trial, and how the school will decide whether to proceed. Include teacher preparation, accessibility, administrative time, and exit work when estimating the cost. Have the appropriate school staff review the agreement and supporting materials before approval.
The AI in Schools guide offers questions about classroom use and evidence. The vendor conversation should give the school specific answers it can test, explain to families, and revisit if the service changes.
Illustrative image generated with AI.




