ISBE released its statewide AI guidance in July, and when I talked to other educators they felt it was a mandate. It isn’t, and that changes what your fall should look like. Inside this issue : what the 409 pages are, what they ask of your district, and a 20-minute path through them.
What the 409 Pages Really Say
ISBE delivered its statewide AI guidance to the Governor and General Assembly, 409 pages, required by Public Act 104-0399, released publicly in July. There is no deadline, no penalty, and no required artifact anywhere in the document. ISBE goes out of its way to say districts should not copy and paste model language, and it promises more guidance, free professional development, and policy templates in the 2026-27 school year. The only hard date in all 409 pages belongs to a different law: the internet safety statute sunsets July 1, 2027, and its successor adds AI and synthetic media.
So what is it? A requirements spec. It tells you what good looks like and expects you to build it locally: roughly 45 require, establish, prohibit, and define expectations for your policies, an implementation checklist, a stakeholder listening expectation that comes with question stems instead of finished surveys, and a goodness-of-fit process for reviewing tools. My favorite line in the document is on page 104: it is often more effective for people to respond to a model than create one. ISBE is handing you the model. Districts that read this as a mandate will freeze and wait. Districts that read it as a spec get a year head start.
2.5 Hours to 11 Minutes, 60,000 Transcripts at 98%, 17 Models Under One Roof: Inside UC San Diego's Build-It-Yourself AI Strategy by Dr. Aviva Legatt. The best build-over-buy story I have read this year, because it comes with outcomes: contract review went from two and a half hours to 11 minutes, and 60,000 transcripts a term now match at 98 percent, with a human still in the loop. The line worth stealing for your next cabinet meeting: why do it if you can't measure it. They measured the manual baseline before building, so they could name the savings after.
Nobody Checked Deloitte's Report. One Academic Did. It Cost Them A$97,587. by Nate, Nate's Newsletter. A consulting firm shipped a government report with AI-fabricated citations, one academic checked the footnotes, and the refund was real money. The failure was not the tool, it was the missing human review. If your district guidance says a human reviews everything before it goes out, this is the story that explains why that sentence earns its place.
State K-12 AI Policy in 2026: Milestones, Momentum and Missing Links by Ji Soo Song, ExcelinEd. The national context for what Illinois just did. Nearly 100 state bills touch AI in education this year, and this piece maps where states are moving on data protection, tool safety, and teacher training, and where the gaps still sit. Read it to see that a guidance-first, templates-later approach like Illinois' is the mainstream path, not an outlier. Useful when your board asks how the state compares.
Read the ISBE guidance yourself, in 20 minutes.
The guidance lives on ISBE's AI guidance page, and the full PDF is here. Nobody is going to read 409 pages. You do not need to. The page numbers below are the printed ones at the bottom of each page, and 20 focused minutes gets you the load-bearing parts.
First, pages 27 to 30, about ten minutes. This is the frame everything hangs on: the four tenets, the context of one document serving 860 very different districts, and the disclosure that ISBE used AI to help draft it. Read this first and every later section snaps into place.
Second, pages 289 to 291, about five minutes. The implementation checklist. It is the closest thing to an instrument in the whole document, and it is the fastest way to see what ISBE expects a district to stand up: governance, policy, tool review, stakeholder listening, professional learning.
Third, page 107, about three minutes. The six bright-line conditions. These are the closest the document comes to hard rules, and they are the sentences to quote when someone asks what we can and cannot do.
That is the 20 minutes. If you have 25 more in you, add pages 321 to 326, the district next steps: roughly 45 expectations written as require, establish, prohibit, and define bullets. That list plus the checklist is the skeleton of every AI policy conversation you will have this year. Bring the page numbers to your next leadership meeting. Being the person who has read the source changes the conversation.
Did this issue land?
One more thing, two things coming. Episode 6 of the podcast drops Wednesday, August 19: the story of how a toy cash register I built for my daughter turned into a real curriculum tool. And since the guidance asks districts to benchmark what their stakeholders think about AI while handing you question stems instead of surveys, I went ahead and built the surveys: a complete stakeholder listening kit, seven instruments covering everyone from central office to families. More on that one soon. Next Friday: what the guidance says, and mostly leaves unsaid, about students with disabilities and multilingual learners.
That's it for this one. If something here landed, share it with someone who'd get something out of it. If it didn't, that's part of the deal too. You can find more of what I'm working on at evalveconsulting.com, or book a call if you want to talk through what you're dealing with.
Talk soon,
Chris