AIContractsVendor Risk

What should your district require before signing an AI vendor contract?

The DueDilly Team · November 16, 2026

What should your district require before signing an AI vendor contract?

Anthropic and Microsoft have signed binding AI privacy terms for schools. Here are five terms to require in writing before your district signs any AI vendor contract.

On November 10, the American Federation of Teachers and its New York City affiliate, the United Federation of Teachers, announced that Anthropic has signed a binding AI Safety and Privacy Standard for Schools, effective that day for its existing agreements with districts using Claude for Teachers. Microsoft signed the same standard in September, effective November 1.

That makes two major AI companies that have agreed to contract terms districts can point to. The word that matters is binding: these are contract terms, not a privacy policy, and a privacy policy can change with a website update.

But the standard only covers the companies that signed it: Claude for Teachers, not every tool built on Claude, and not the next AI vendor that arrives with a pilot offer and a signup link. For every other vendor, the protections are terms your district has to ask for in writing before signing. The unions say they are still negotiating with OpenAI, and they have no agreement yet with other developers, so for most vendors the asking still falls to the district.

Why FERPA alone does not cover this

FERPA is still the law most districts reach for first. It governs education records, who can see them, and when a school may share them. But it was written before generative AI, and it does not spell out what a district must ask before an AI tool touches student work.

FERPA does not say whether a vendor may use student prompts to train its next model, set a deadline for deleting student data when a contract ends, say how quickly a vendor must tell you about a breach, or say who reviews a decision the AI helped make about a grade, a discipline referral, or a class placement. Those are contract questions now. Without the term in the contract, the district relies on the vendor's goodwill and its privacy policy, and both can change without a board vote. The vendor's promises need to sit in the agreement itself, with dates and duties attached, so the district can hold the vendor to them after the sale.

Five terms to require before signing

The Anthropic and Microsoft agreements give districts a ready-made checklist: five terms to require, in writing, before signing any AI vendor contract.

1. Student data never trains the model

The contract should say plainly that the vendor will not use student or educator data to train or improve its AI models. Anthropic agreed to this, with only a narrow exception for limited safety work. If a vendor says its model "learns from usage," get what that means in the contract, in writing.

2. Deletion on a deadline, backups included

Your district should control how long student data is kept and when it is deleted. Under the new standard, Anthropic must delete data from active systems and from backups within 180 days of a school's request. Ask for a number, not a promise to delete data "when reasonable." The deadline should cover backups too, because a backup is still a copy of student data.

3. Breach notice within 72 hours

The standard requires Anthropic to report a breach within 72 hours, and to contain it and limit the damage, even after the contract ends. Ask for the same timing, and ask who gets the notice. A notice that arrives weeks later, or goes to an inbox nobody monitors, is not a notice. Seventy-two hours is the bar two major companies have accepted. Hold the rest of your vendors to it.

4. A human reviews consequential decisions

AI can inform a decision about a grade, a discipline referral, or a class placement, but it should not make that decision on its own. The standard calls for districts to have policies and training so a person reviews any consequential decision the AI informs. Put the duty in the contract: the product must support human review, and the district keeps the final call. A tool that grades a student without a human in the loop has taken over a decision the district is accountable for.

5. Plain-language answers, and no selling student data

The vendor should explain in plain language what data it collects, what it uses it for, where the product falls short, and what safeguards apply. Student data should be used only for authorized educational purposes, never sold, and never used for targeted advertising. If a vendor cannot explain its data practices in plain language, that tells you how it will communicate when something goes wrong.

What to do when a vendor will not agree

Some vendors will push back, especially smaller ones that use another company's model and say the terms are out of their hands. That is the start of the conversation, not the end of it.

First, ask for the term in writing and ask what the vendor will agree to instead. A vendor that will not agree to "no training on student data" may agree to no training on data from your district specifically. Get that version in writing, with a date attached.

Second, bring the gap to purchasing and leadership, risk stated plainly. "This vendor will not agree to delete our student data on a deadline" is a decision leadership can weigh. "We signed a standard contract" is not.

Third, document the decision: what was asked, what was refused, who accepted the risk. That record protects the people who raised the concern.

Fourth, limit the exposure. Run a small pilot instead of a districtwide rollout. Keep student names and identifiers out of the tool until the terms are settled. Set a date to revisit it before the renewal comes around. A no from a vendor is useful information about how it will treat your data after the sale, not just before it.

How to check a vendor before you sign

Before you sign anything, check what is already public. The free scan at duedilly.io/compliance-check checks a vendor's FERPA and COPPA evidence, its certifications, and whether its source links are live and real. It takes minutes and gives you something concrete to bring to the vendor: what is missing, and what we need in the contract.

The free 90-day trial goes further, running a vendor through the full review, breach-indemnity analysis included. Its contract scan surfaces renewal increases buried in the original contract, so you know the projected cost before renewal, and whether to find a cheaper option or go in ready to negotiate.

The point is not to find a perfect vendor. It is to sign with your eyes open, the terms that matter already in the contract.

Two major AI companies have now agreed, in binding contracts, to protect student data, give districts control over deletion, require fast breach notice, and keep a human in charge of consequential decisions. Those terms appeared because districts, through their unions, asked for them in writing and would not take no. Your district can ask for the same from every AI vendor before the next contract is signed.

This article is not legal advice. Contract language should be reviewed by your district's solicitor before signing.