Skip to content

A procurement checklist for AI learning tools

A sound review of an AI learning tool checks instructional fit, content accuracy, how the tool handles answers and integrity, student safety, privacy and contract terms, accessibility, rostering and integration, and total cost. Ask for evidence on each point rather than marketing claims, and run a short, measured pilot before committing to a district-wide purchase.

How to use this checklist

AI tools touch curriculum, privacy, IT, special education and classroom practice all at once, so a review led by one department tends to miss something. Bring in a curriculum lead, someone from IT or data privacy, a special education representative and at least two teachers who will actually use the tool. Give each person the sections closest to their work.

The single most useful step is to test the tool yourself with your own problems, not the vendor's demo script. Try a problem from your adopted curriculum, a problem with a common student mistake built in, and a request for the answer outright. You'll learn more in 20 minutes than from a slide deck.

This page is general information, not legal advice. Check specific questions with your district's counsel.

Instruction and accuracy

Student safety and academic integrity

Privacy, security and contract terms

Accessibility and access

Integration, support and cost

Running a pilot that tells you something

Ask vendors for any evidence of effectiveness they have, and read it closely: who were the students, what was measured, and was there a comparison group? Then gather your own evidence. Write down what success looks like before the pilot starts, so the decision isn't shaped by whoever is most enthusiastic at the end.

A useful pilot runs six to eight weeks in a few classrooms, with a clear unit or skill focus. Collect usage data, a pre- and post-unit measure you already trust, teacher observations and short student surveys. Compare against similar classes that didn't use the tool if you can.

If Helio is on your list, we'll answer each item here in writing. Helio rosters from Clever or ClassLink, checks every math claim before it's spoken, guides rather than giving answers, doesn't store voice audio, and is priced per student per year with an invoice due in 30 days.

Questions

How long should a pilot of an AI learning tool run?

Six to eight weeks is usually enough for novelty to wear off and for a full unit to finish. Decide what you will measure before it starts.

Should we ask AI vendors for a VPAT?

Yes. Ask for an Accessibility Conformance Report against WCAG 2.1 AA and Section 508, and test the most important tasks yourself with a keyboard and screen reader.

What evidence of effectiveness should we expect from a vendor?

Ask who the students were, what was measured, and whether there was a comparison group. Newer tools may have little outside evidence yet, which makes a well-designed local pilot more important.

Who should be on an AI tool review team?

A curriculum lead, an IT or data privacy lead, a special education representative and teachers who will use the tool. Families can be included through a notice and a chance to ask questions.

What is the most important privacy question to ask an AI vendor?

Ask whether student data, including conversations and voice, is used to train AI models, and make sure the answer is written into the contract.