K-12 Leaders Get Vendor AI Pitches in the Inbox

The vendor deck says “AI tutor.” The parent email says “FERPA.” The board meeting is in nine days. Nobody agrees what the word means yet.

That is K-12 procurement in the generative era: not a lack of enthusiasm, but a translation crisis that arrives as forwarded threads. The U.S. Department of Education’s Office of Educational Technology hub at <a href="https://tech.ed.gov/" target="_blank" rel="noopener noreferrer">tech.ed.gov</a> frames safe, evidence-minded adoption. The <a href="https://files.eric.ed.gov/fulltext/ED661924.pdf" target="_blank" rel="noopener noreferrer">Empowering education leaders AI toolkit (ERIC PDF)</a> is a practical artifact superintendents actually forward. OECD’s <a href="https://www.oecd.org/en/topics/sub-issues/ai-principles.html" target="_blank" rel="noopener noreferrer">AI Principles</a> add cross-border language on transparency and information integrity that district lawyers increasingly cite in RFP replies.

How should a K-12 leader evaluate AI pitches without a data science team?

District leaders evaluate AI pitches without a data science team by separating marketing language from contract language, mapping claims to concrete student-data flows, and documenting decisions in email threads that legal and families can follow. McKinsey’s <a href="https://www.mckinsey.com/industries/education/our-insights" target="_blank" rel="noopener noreferrer">education insights</a> repeatedly tie value to workflow redesign, which for schools means mail-bound diligence loops: curriculum forwards vendor claims, IT forwards security questionnaires, parents forward news clips. NIST’s <a href="https://www.nist.gov/itl/ai-risk-management-framework" target="_blank" rel="noopener noreferrer">AI Risk Management Framework</a> supplies governance vocabulary without requiring ML fluency.

What failure mode shows up first in vendor email threads?

The failure mode is definitional drift. One message uses “AI tutor.” The next uses “adaptive practice.” The third uses “human-in-the-loop,” but nobody can point to the human or the loop. By message twelve the thread is fighting adjectives instead of reviewing data retention.

ISTE’s <a href="https://www.iste.org/" target="_blank" rel="noopener noreferrer">AI in education resources</a> and CoSN’s <a href="https://www.cosn.org/" target="_blank" rel="noopener noreferrer">leadership technology materials</a> help teams ask better questions early. EdSurge and Chalkbeat cover how districts behave under public pressure. Common Sense Education’s <a href="https://www.commonsense.org/education/digital-citizenship" target="_blank" rel="noopener noreferrer">digital citizenship hub</a> is a parent-trust anchor when boards ask for plain language.

Harvard Graduate School of Education’s <a href="https://www.gse.harvard.edu/ideas/usable-knowledge" target="_blank" rel="noopener noreferrer">Usable Knowledge</a> is a helpful tone reference when leaders need language that is serious without sounding like they are performing expertise they do not have.

What does “FERPA-safe” mean in a district email chain?

In practice, “FERPA-safe” in a district email chain should mean the leadership team can name what student records are disclosed, to whom, for what purpose, and what rights families retain—before anyone types a vendor slogan into a board packet. If the thread cannot answer those four buckets in plain English, the phrase is decoration, not diligence.

The workflow before: twelve messages before “FERPA-safe” is defined

Before, the curriculum director forwards a PDF, the superintendent loops legal, and the thread balloons while classrooms still need a decision about pilot scope. Speed without clarity creates the worst outcome: a quiet pilot that becomes a loud scandal because nobody wrote down what “opt out” meant.

Micro-scene: a principal forwards a vendor screenshot of a cheerful chatbot next to a parent’s worried question about essay grading. The thread needs two different sentences: one for the board, one for families. If those sentences contradict, you do not have a communications problem. You have a decision problem.

Why does another LMS-style portal fail this persona?

Because the people who must say “no” or “not yet” are already maxed on logins. The superintendent is reading mail on a phone outside a gymnasium. The curriculum director is forwarding from a car line. The IT lead is answering security questions between help-desk tickets. A portal that requires training is a portal that becomes a rumor mill instead of a system of record.

Email is not perfect. It is, however, the place where urgency already shows up.

The via.email workflow after: forward, structure, human review

via.email routes specialist help through email addresses. It does not access your inbox, remember across separate threads, or send on your behalf.

Draft AI Use Policy at draft.ai.use.policy@via.email turns leadership bullet points into draft board-ready language you still edit.

Assess AI Risk Exposure at assess.ai.risk.exposure@via.email translates a vendor pitch thread into plain-language risk framing for internal debate.

Decode Security Questionnaire at decode.security.questionnaire@via.email converts dense vendor security mail into questions a principal can answer with counsel.

Write Grant Proposal at write.grant.proposal@via.email helps draft narrative sections from constraints and facts you supply—humans still own accuracy and submission.

What must remain human-only?

Final policy adoption. Legal sign-off. Anything that tells families how student data is handled. Anything that commits funds. Anything that could be read as a warranty about compliance “being handled by software.”

How should leaders run a pilot decision without pretending software audited the vendor?

Leaders should treat pilots like small procurement events: written scope, written success criteria, written stop conditions, and a single thread that contains the evidence trail. If a vendor cannot answer retention questions in mail, assume the answer will not improve after purchase.

Status detail: a small-district superintendent in Wisconsin keeps a “definitions appendix” note that gets pasted into every vendor thread: what “AI-assisted” means for teachers, what “review” means for administrators, what “student data” includes in their district’s interpretation. It saves hours because it stops the adjective tournament before it starts.

Procurement checklist in plain English

Ask vendors for data retention in one paragraph. Ask what training data means for your specific deployment. Ask for the human review path before a student-facing output ships. Ask for opt-out language you can paste into family communications without rewriting tone three times.

NCES <a href="https://nces.ed.gov/" target="_blank" rel="noopener noreferrer">data resources</a> help ground discussions in what districts actually measure, not what decks claim.

Broader implications: calm is a budget line in public institutions

Trust is not a slide transition. It is the ability to explain a decision to an angry parent without sounding like you are hiding behind a brand.

Related reads: how teachers lose mail time that is not teaching, how procurement stalls on manual coordination, and how refocus costs eat strategic work.

The thread is where your district either earns trust—or spends it.

Forward the mess. Extract the questions. Edit the language. Keep humans on the decisions that outlast any vendor logo.

Public education does not need another dashboard hero. It needs legible mail.

When the board asks what you decided, the answer should fit in a thread, not a black box.

That is procurement politics done honestly: slower sentences, safer kids, fewer surprises in the inbox.