Six documents — drafted by a cross-functional team of teachers, district leaders, and policy hands — to take a district from "we should probably write something" to a board-adopted policy students, families, and staff can actually live with.
These are sequenced to be used together. Start with the roadmap, end with family communications — but every document also stands alone if you only need one piece.
A week-by-week playbook for moving from "we should do something about AI" to a board-adopted policy with rollout. Names the working group, the listening sessions, and the gates.
Open the roadmap → Download .docxA drop-in policy template, structured by section and annotated. Three posture variants (Permit with Disclosure, Structured Use Only, Restricted) so the board can see real options instead of a single take-it-or-leave-it draft.
Open the AUP template → Download .docxWhat it's reasonable to ask of a 7-year-old vs. an 11th-grader. Skills, exposures, and disclosures by grade band — the framework your AUP and curriculum decisions should sit on.
Open the grade-band framework → Download .docxOne page. Eleven questions. A scoring rubric your procurement team can run in 30 minutes on a vendor pitch — with a clear pass/needs-work/reject signal.
Open the vendor rubric → Download .docxFor state agencies and districts large enough to set their own floor: model regulatory language for student data protection, vendor obligations, and incident response.
Open the state guidance → Download .docxA family-facing letter, a six-question FAQ, and talking points for principals at back-to-school night. The bridge between the policy you adopted and the families who need to understand it.
Open the family kit → Download .docx"Districts that wrote AI policy with teachers and students adopted three months faster and rescinded half as often as districts that wrote it for them."
Every district is different. Use these documents as a credible starting draft you can argue with — not as boilerplate to ratify. Three suggestions before you do anything else.
The single biggest predictor of whether a policy lasts is whether teachers, students, and families saw it before adoption. Convene first; redline second.
Don't argue word-by-word. Ask the board to pick one of three postures (Permit / Structured / Restricted), then let staff draft language to match.
Write a 12-month review into the policy itself. Models and student usage are moving fast; a policy without a review date will calcify or get ignored.
Every document in this toolkit, as a styled .docx file. Open in Word, Google Docs, or Pages — rebrand for your district, adapt the language, ship it. Same content as the web versions, formatted for printing and board packets.
| No. | Document | Best for | Word file |
|---|---|---|---|
| 00 | Toolkit overview | Briefing the cabinet or board on what's coming | Download .docx → |
| 01 | District Implementation Roadmap | Project plans, RACI charts, board calendars | Download .docx → |
| 02 | AI Acceptable Use Policy — district template | Drop into your policy manual, adapt sections, redline | Download .docx → |
| 03 | AI Literacy by Grade Band | Curriculum review, PD planning, scoping documents | Download .docx → |
| 04 | Ed-Tech AI Vendor Evaluation Rubric | Procurement files, vendor scorecards (printable) | Download .docx → |
| 05 | Model State Guidance — student data & AI | State agency drafting, legislator briefings | Download .docx → |
| 06 | Family Communication Kit | Letter, FAQ, principal talking points (mail-merge ready) | Download .docx → |
Font note. The .docx files request Cambria for headings, Calibri for body, and Consolas for monospace — fonts that ship with Microsoft Office on Windows and Mac. If your environment substitutes them, the document will still render cleanly.
These documents are released under Creative Commons Attribution-NonCommercial 4.0. Strip our logo, rebrand for your district, ship it. We just ask three things.