I want to paint you a picture. Not a theoretical one — a specific one.
It's a Tuesday night in October. A school board meeting. Agenda item seven is AI policy. A board member — the skeptical one, the one who asks the hard questions — leans forward and says: "Can you walk us through exactly what your school is doing with AI and how students are protected?"
There are two versions of what happens next.
In the first version, the principal shifts in her chair. She mentions that teachers are being thoughtful about it. She says "we're monitoring the situation." She references something she read about FERPA. The board member follows up. The principal doesn't have a clean answer. The meeting goes sideways.
In the second version, the principal opens a one-page summary. She walks through it in four minutes. Why they started the AI launch. What policies are in place. Which tools are approved and how they were reviewed. What training staff completed. What families were told. What the pilot showed. What comes next. The board member nods. The item closes. The meeting moves on.
That second version isn't luck. It's what 90 days of doing this carefully produces.
"AI-ready doesn't mean AI everywhere. It means being able to answer the next question — whatever it is, whoever asks it — with something specific."
What "Ready" Actually Means
I hear "AI-ready" used a lot right now. Usually it means something vague — staff who've attended a workshop, a policy document someone drafted, a pilot that's "in progress." That's not what I mean.
An AI-ready K-8 school can answer five questions clearly. In any room. To any audience. Not with a prepared speech — with actual documentation behind it.
- What problem are we using AI to solve? One sentence. Approved by leadership. Not "we're exploring AI" — a specific, operational answer.
- Who is responsible for AI decisions? A named team with specific roles. Not "IT." Not "the principal." A cross-functional group with documented ownership.
- Which tools are allowed? A published approved-tool list. Staff don't have to guess. Every tool on the list has been reviewed against a standard set of privacy questions.
- How are students protected? A prohibited-data rule. A vendor vetting checklist. A signed DPA for each approved tool. Grade-band expectations. Written down. Communicated.
- How will we know whether to expand? A pilot scorecard with criteria. Not "teachers liked it." Specific thresholds for privacy, instructional value, workload, student thinking, equity, and trust.
When a school can answer all five — not hypothetically, but with actual documents — that's what ready looks like.
What It Looks Like in Each Room
Here's the thing about readiness: it doesn't show up in one place. It shows up everywhere, all at once, whenever someone asks.
The principal arrives with a one-page summary.
Nine bullets. What was done, what was learned, what is changing, what is approved for Month 4, what is not approved yet, and when the next review is. The board doesn't need the full document set in the room. They need to know someone is in charge and the work is real. That one page proves it.
Teachers know exactly what's allowed without having to ask.
There's an approved-tool list. There are assignment labels — "No AI," "AI for ideas only," "AI for feedback," "AI allowed with disclosure." There's a one-rule everyone can remember: when in doubt, don't enter student information. No guessing. No experimenting with something that wasn't vetted.
The parent gets a real answer in under 24 hours.
Not "we're looking into it." Not a three-paragraph disclaimer. A specific response: here are the tools approved for student use, here is our privacy rule, here is the family FAQ on our website, here is who to call if you have further questions. That email takes five minutes to write when the documents already exist.
Students know what AI is, what it isn't, and what they're allowed to do with it.
Grade-band expectations are clear. K-2 students aren't using generative AI chatbots independently. 6th graders who use an approved tool for feedback know they need to disclose it. The teacher didn't have to invent the rules — they were given to them, and they make sense.
What It Doesn't Look Like
I want to be clear about this, because the version of "AI-ready" that gets talked about most is not the version I'm describing.
It's not AI everywhere. A school where every teacher is using five different tools, students are chatting with AI assistants unsupervised, and no one has a DPA on file is not ready — it's exposed.
It's not a ban either. A school where the answer to every AI question is "we don't allow it" is not protected — it's behind. The tools are already in the building whether the policy acknowledges them or not.
Ready is the middle. Controlled. Deliberate. A school where the people who need to know what's happening actually do, where the people who need rules have them, and where the people who are going to ask hard questions get real answers.
"The tools are already in the building whether the policy acknowledges them or not. Ready is the middle — controlled, deliberate, documented."
What 90 Days Actually Produces
The 90-Day AI Launch Plan isn't about getting AI everywhere. The outcome at day 90 isn't "we use AI." It's "we can account for what we're doing."
Here's what exists at the end of a responsible 90-day launch:
A purpose statement that explains why AI is being used at this school — one sentence, approved by leadership. A launch team with named roles, meeting weekly, moving through a defined sequence of decisions. A staff AUP that tells teachers what they can do, what they can't, and what to do when they're not sure. A student AUP with grade-band expectations that make sense for a 7-year-old and for a 13-year-old — separately. A family communication that was sent before questions became complaints. An approved-tool list, even if it has two items on it, with vendor review documentation on file. A pilot scorecard that shows what the evidence said and what was decided. A board update that closes the loop with governance.
That's it. That's what ready looks like. Not a binder full of procedures. A set of documents that together answer every question that's coming — and most of them are already coming.
"We started with a clear purpose. We built the team. We wrote the rules before something went wrong. We told families what we were doing. We ran a small pilot, looked at the evidence, and made a deliberate decision about what comes next. We can show you every step."
That principal in the board meeting — the one in version two — didn't get lucky. She just started earlier than most.
The gap between version one and version two is smaller than it looks. It's a team, a sequence, and about 90 days of deliberate work. The picture on the other side of it is worth it.
The complete sequence that produces this picture.
The 90-Day AI Launch Plan is a week-by-week guide that takes a K-8 school from wherever it is right now to a place where it can answer every question above — with documents to back it up. All editable. All ready for your school's name. Every room in the building covered.
- AI purpose statement — 3 editable options
- AI launch team charter with named roles
- Staff and student AUP — editable by grade band
- Approved-tool list template with DPA tracking
- Family communication — plain English, no legal jargon
- Pilot scorecard — 6 criteria, Green/Yellow/Red
- Board update outline — 9 bullets, ready to present