By Brett Roer, Founder & CEO of Amplify & Elevate Innovation
In February I sat in a room in Montgomery County, Ohio, with 72 educators and leaders from 11 organizations, on the first day of an AI Community Playbook Lab that Dr. Shannon Cox had convened. Before we did anything with a tool, I asked every table one question. What is already happening with AI in your district, formally or informally?
The answers took most of the morning. A curriculum director had three teachers running quiet pilots she had never been told about. A superintendent had a privacy review that started the previous spring and stalled. One district had run a PD session that landed well and then never followed it up. Another had a board member who had been reading about governance for a year and had nobody to talk to about it.
That morning is the reason I keep coming back to sequencing. Every district I partner with has more AI work in motion than it realizes. Building an AI roadmap for schools rarely means starting from zero. Most of the work is putting what is already underway into an order the community can trust.
Why an AI roadmap for schools starts with listening
The districts I get to be part of move deliberately. They listen before they launch. They align leadership before they ask educators to integrate. They build community trust before they scale.
That sequence is what holds. It gives teachers something to walk into. It gives families something to recognize. It gives boards something to support publicly. It gives superintendents a way to talk about AI that is grounded in their own community rather than in a slide someone else made.
The pace of adoption makes the order matter more, not less. RAND’s survey panels found that in 2025, 54 percent of students and 53 percent of English language arts, math, and science teachers said they used AI for school, up more than 15 percentage points in one to two years. At the same time, only 35 percent of district leaders said they provided students with training on AI. The RAND report is worth reading in full, because the gap it describes is the gap a roadmap closes. Use is already here. Guidance is what is missing.
The timeline below is a guide, not a prescription. Some districts compress these phases. Some take longer on year one because they are starting from a quieter place. What I care about is the sequence.
A three-year AI implementation roadmap for K-12 districts
Year one: listen and align
The first year is foundation work. From the outside, not much looks like it is happening. That is by design.
Inside the district, four things take shape.
A clear-eyed picture of where people are. Educators, students, and families, including the tools that arrived informally and the questions nobody has asked out loud yet. In Montgomery County we ran that listening through a protocol I built called Pass the Mic™: anonymous, structured, and synthesized the same day so the room hears itself before anyone leaves.
Leadership alignment. The superintendent, cabinet, and building leaders develop a shared language and a shared understanding of AI’s role in the system. I have watched cabinets discover in one ninety-minute conversation that they were using the same words to mean four different things.
Community listening. Structured conversations with students, families, educators, and staff that surface the real questions, tensions, and aspirations. This is where the roadmap stops being an IT project and becomes a community one.
A community-built framework for responsible AI use. Written in plain language, this becomes the district’s foundation document. If your district is in Ohio, this is also the document that satisfies the law: House Bill 96 requires every school board to adopt an AI policy covering student and staff use by July 1, 2026, and the Ohio School Boards Association’s summary sets out what it has to address. A framework the community built will pass that test and be worth more than the model policy alone.
The board is in the conversation too. A focused presentation and a short asynchronous resource give board members the governance literacy they need to ask informed questions and support the strategy publicly.
Year two: pilot and learn
With alignment and guidance in place, the district moves into purposeful experimentation.
A small number of vetted tools, chosen for specific use cases. Clear success criteria for each pilot, defined before it launches. Sustained, differentiated professional development for educators, grounded in the framework and language built the year before. An AI advisory committee with diverse representation that provides ongoing oversight. Transparent decision-making that keeps earning community trust.
Two pieces of the year-two work have their own guides on this site. If you are choosing tools, start with how to vet AI tools for schools. If the privacy review is the thing that stalled, the student data privacy guide walks through what a K-12 leader needs to have in place.
The most important habit in year two is documentation. What is working? What is surfacing as people try things? What new questions are coming up that the framework needs to grow into? The roadmap is a living document, and the evidence year two produces is what shapes year three.
Year three: scale and sustain
Scaling means expanding what has earned its place. Pilot results, educator feedback, and student experience determine what gets adopted district-wide. Some of what was piloted will not scale, and that is a sign the process is working.
By year three, AI expectations are part of new teacher onboarding, annual professional development cycles, and the district’s strategic plan. By then it has stopped being a special initiative and become how the district operates. Annual review cycles and community feedback loops keep the guidance current as the technology changes.
The work your district has done by this point has value beyond your borders. Sharing your process through regional networks, conferences, and peer connections strengthens the field and reflects well on the people who led it.
A readiness check before you build a district AI rollout plan
Before sequencing anything, leaders need a clear picture of where things stand. The readiness work I do with districts answers four questions.
Awareness. Are educators, students, and families working from shared language about AI, or are people operating from different definitions?
Infrastructure. Does the district have a process for vetting and approving AI tools? Are data processing agreements in place? Is there a clear privacy framework? If you are not sure what data the tools already in your building are collecting, this piece on the data conversation is the place to start.
Capacity. Has leadership been through AI learning themselves? Do educators have access to sustained professional development?
Governance. Is there a structure for ongoing AI decision-making? Who is responsible for monitoring tools after adoption? Is community voice built into the process?
The answers are a starting point. They tell leaders where the roadmap should begin and which conversations need to happen first. In Montgomery County, the readiness check on day one is what told us which districts needed policy language first and which needed a listening process first. Same lab, different starting points.
How the roadmap lines up with federal guidance
Districts sometimes ask me whether a community-built roadmap will hold up against what the state or the federal government expects. In my experience it holds up better than a compliance document does, because it was built by the people who have to live with it.
The U.S. Department of Education’s Dear Colleague letter of July 22, 2025 sets out five principles for AI in education: educator-led, ethical, accessible, transparent and explainable, and data-protective. It also says stakeholders, and parents in particular, should participate meaningfully in decisions about adopting new technologies. Read the three-year sequence above against those five principles and you will find every one of them in year one. That is not a coincidence. A roadmap that begins with listening produces guidance that is transparent and educator-led by construction.
Communicating the roadmap
One of the most important parts of the work is the communication around it. Three principles keep the message landing.
Be the first to say it. If your district is exploring AI policy, running pilots, or working through hard questions, share that proactively. Transparency creates space for trust.
Speak to values, not just logistics. Families want to know three things. Is my child safe? Is this being used thoughtfully? Does the school care about what I think?
Invite dialogue. Community forums that begin with “what do you want to know?” and “what would make you feel confident?” generate partnership.
When the story is consistent across the superintendent’s office, the building principal, and the classroom teacher, trust follows the message.
A first move you can make this month
If your district is at the beginning of this work, the first move is leadership alignment. Pick one ninety-minute conversation with your cabinet. Two questions to anchor it. What are we already doing with AI in this district, formally and informally? And what is the values commitment we want our AI work to live by?
You leave that meeting with a starting point your leadership team owns together. In Montgomery County, by the end of the three-day lab, 94.3 percent of the 115 survey responses said they were more confident about the work ahead, and the series earned a Net Promoter Score of +83. I share those numbers with the sample size on purpose. They came from 72 people who started the way I am suggesting you start: by naming what was already moving.
What is already moving in your district? And who has not been asked yet?
Frequently asked questions
What is an AI roadmap for schools?
An AI roadmap for schools is a sequenced plan that takes a district from where it is today with AI to where its community wants it to be, usually over two to three years. The strongest roadmaps start with a readiness check and a listening process, align leadership on values and guardrails, produce a community-built framework for responsible use, then pilot a small number of vetted tools before scaling what earns its place.
How do you assess AI readiness in a school district?
A practical readiness check answers four questions. Awareness: are people working from shared language about AI? Infrastructure: are vetting and privacy processes in place? Capacity: has leadership done the learning themselves, and have educators received meaningful professional development? Governance: is there a structure for ongoing decisions that includes community voice? The answers tell leaders where the roadmap should begin.
What should a district AI rollout plan include?
A strong district AI rollout plan includes a readiness check, a community listening process, leadership alignment on values and guardrails, a community-built framework for responsible AI use, a phased professional development plan, a governance structure with diverse representation, a sequence for piloting and scaling tools, board preparation, a community communication strategy, and an annual review cycle.
How long does an AI implementation roadmap for K-12 take?
Most districts I work with plan across three years: year one for listening and alignment, year two for piloting and learning, year three for scaling and sustaining. Districts with a state deadline, such as Ohio’s July 1, 2026 policy requirement, often compress year one so the framework is adopted first and the listening continues alongside it.
A thought partner for your roadmap
Building an AI roadmap that earns community trust takes time, and a thought partner who knows both the technology and the realities of leading a school district. I provide AI Strategic Advisory at the superintendent level for leaders shaping the next phase of their district’s AI work, and the Community AI Playbook is the year-one process in full.
If you want a confidential sounding board as you sequence your district’s AI work, I would welcome the conversation: brett@aeieducation.org, or book a conversation.
