Artificial intelligence may feel like an entirely new governance challenge for school districts.
It introduces important questions about accuracy, bias, transparency, student data, intellectual property, human oversight, and the appropriate use of automated recommendations. These risks deserve focused attention—but they do not require districts to build an entirely separate governance system.
AI tools are part of the district’s larger EdTech ecosystem. They are requested by employees, evaluated by multiple departments, purchased through district budgets, used with students and staff, supported by technology teams, and eventually renewed or retired.
When AI governance is managed as a separate initiative, districts risk creating another isolated committee, spreadsheet, policy document, and approval process. Instead of improving oversight, this can produce the same fragmentation districts are already trying to solve.
The better approach is to integrate AI into the district’s existing EdTech governance strategy—applying additional review where the risks warrant it while maintaining one connected system for products, people, policies, contracts, decisions, and accountability.
AI Is Already Embedded Throughout the EdTech Ecosystem
AI governance is not limited to stand-alone generative AI platforms.
Vendors are adding AI features to products districts already use for:
- Learning management
- Assessment and feedback
- Student information
- Productivity and collaboration
- Cybersecurity and monitoring
- Translation and transcription
- Special education
- Communications
- Human resources
- Data analytics
- Tutoring and intervention
- Content creation
A district may approve a product for one purpose and later discover that the vendor has added an AI assistant, automated recommendation engine, content generator, or data-analysis feature.
This makes it difficult—and increasingly unrealistic—to maintain a clean division between “AI tools” and “other EdTech.”
The more useful question is not simply, “Does this product use AI?”
Districts also need to ask:
- What does the AI feature do?
- Who will use it?
- What data does it access?
- What decisions could it influence?
- Can the feature be disabled?
- Does it change the product’s original approved use?
- What level of human review is required?
- Does the product now need to be evaluated again?
These questions belong within the district’s complete EdTech lifecycle.
A Separate AI Initiative Creates More Fragmentation
Many districts begin their AI governance efforts by creating a new committee, drafting a separate policy, or maintaining an independent list of approved AI tools.
These can be valuable starting points. The problem occurs when they remain disconnected from the district’s broader technology-management processes.
A separate AI initiative may create:
- A second product inventory
- A different request form
- An overlapping review committee
- Separate approval records
- Conflicting employee guidance
- Additional spreadsheets
- Disconnected policies
- Limited visibility into contracts and costs
- Unclear ownership after approval
For example, an AI committee might approve a tool based on its instructional value and acceptable-use expectations. However, the product may still need a privacy agreement, accessibility review, security assessment, procurement approval, contract, budget code, implementation owner, training plan, and renewal decision.
If these activities happen in disconnected systems, the district still lacks a complete view of the product.
AI governance should strengthen the district’s existing governance structure—not create another layer employees must navigate.
AI Requires Additional Scrutiny, Not an Entirely Separate Lifecycle
AI products can introduce risks that require specialized questions and expertise. But the stages through which those products move remain familiar.
Like every other EdTech product, an AI-enabled tool must be:
- Discovered or requested
- Evaluated
- Approved, denied, or conditionally approved
- Purchased or provisioned
- Communicated to employees
- Implemented and supported
- Monitored
- Renewed, restricted, or retired
The difference is the depth and type of review required.
A basic productivity tool that generates generic brainstorming ideas without accessing protected information may require a relatively light review. An AI system that analyzes student performance, recommends interventions, evaluates writing, or influences high-impact decisions should receive much greater scrutiny.
Districts can account for these differences through risk-based workflows within the same governance system.
| AI use | Potential review level | Additional considerations |
| Brainstorming without protected data | Lower | Accuracy, approved use and employee verification |
| Creating instructional materials | Moderate | Bias, accessibility, age appropriateness and curriculum alignment |
| Processing student work | Elevated | Privacy, data retention, model training and parental consent |
| Recommending interventions or placements | High | Transparency, validity, human oversight and potential disparate impact |
| Influencing grades, discipline or eligibility | Highest or restricted | Legal review, executive approval, documented oversight and appeal procedures |
This allows districts to apply appropriate controls without forcing every AI use through the same exhaustive process.
Build AI Questions Into Existing Review Workflows
The district’s standard EdTech request and evaluation process should include questions that reveal when an additional AI review is necessary.
Requesters might be asked:
- Does the product use artificial intelligence or machine learning?
- Has an existing product recently added AI functionality?
- What task will the AI perform?
- Who will interact with it?
- Will students use it directly?
- What information will users enter or upload?
- Does the system create profiles, predictions, scores, or recommendations?
- Could its output influence a decision about a student or employee?
- Is human review required before its output is used?
- Does the vendor retain prompts or use district data to train its models?
- Can the AI functionality be disabled?
- How will the district measure accuracy and effectiveness?
The answers can determine which departments need to participate.
A teacher-facing content generator may require technology, curriculum, privacy, and accessibility review. A system that supports employee screening or student placement may also require legal, human resources, executive, and policy review.
One coordinated workflow ensures the appropriate stakeholders are involved without creating an entirely different system for every category of technology.
Use the Same Cross-Department Governance Team
AI governance cannot belong exclusively to the technology department, curriculum team, or a temporary AI task force.
The same cross-functional collaboration required for effective EdTech governance becomes even more important when AI is involved.
Each department brings a different perspective:
- Technology evaluates infrastructure, integrations, access, support, security, and technical feasibility.
- Curriculum and instruction evaluates instructional purpose, academic alignment, age appropriateness, and classroom impact.
- Privacy and security examine data collection, retention, sharing, model training, authentication, and vendor risk.
- Legal and policy leaders assess regulatory obligations, contracts, intellectual property, transparency, and high-impact uses.
- Accessibility and special education teams evaluate equitable access and the effect on students with disabilities.
- Finance and procurement assess cost, purchasing requirements, contract terms, vendor sustainability, and overlapping solutions.
- Administration provides strategic direction, establishes acceptable risk, and ensures alignment with district priorities.
- Educators and school leaders contribute practical insight into how the product will be used in real classrooms and operations.
An AI advisory group may still provide valuable expertise. However, its work should connect directly to the district’s established decision-making structure, product records, approval workflows, and executive accountability.
Maintain One Complete Product Inventory
Districts cannot govern AI effectively if AI-enabled products are stored in a separate list from the rest of the technology portfolio.
One centralized inventory should identify:
- Stand-alone AI products
- Existing products with embedded AI
- Enabled and disabled AI features
- Approved users and grade levels
- Approved use cases
- Data restrictions
- Required training
- Review history
- Product and contract owners
- Costs and budget codes
- Privacy, security, and accessibility documentation
- Contracts and renewal dates
- Incidents or concerns
- The next scheduled review
This helps leaders see AI in context.
They can determine whether multiple departments are purchasing similar tools, whether vendors are adding unreviewed features, whether approved products are being used as intended, and whether the district already owns an alternative to a newly requested product.
Without this connection, AI oversight becomes another incomplete snapshot rather than part of the district’s full technology strategy.
Communicate AI Guidance Through the Approved-Tools Catalog
A policy alone cannot answer every practical question employees will have.
Teachers and staff need to know:
- Which tools are approved
- Who may use them
- What the approved uses are
- Whether students may access them directly
- What information may be entered
- What restrictions apply
- Whether parental consent is required
- How AI-generated content should be reviewed
- What training is required
- Which alternatives are available
- Who to contact with questions
- How to request a new tool or use case
This guidance should appear alongside the other information employees already use to evaluate and access district technology.
A searchable staff catalog gives employees one trusted location for both AI and non-AI products. It also prevents employees from having to compare an approved-tools list, an AI spreadsheet, a privacy database, a policy document, and several departmental websites before making a decision.
The easier the district makes it to find accurate guidance, the more likely employees are to follow it.
Connect AI Approval to Contracts and Renewals
AI review should not end when a tool is approved.
Vendor capabilities, terms, data practices, and underlying models can change rapidly. A product that met the district’s requirements when purchased may operate differently by the time its contract renews.
Connecting AI governance to contract and renewal management creates natural opportunities to ask:
- Have new AI features been added?
- Have the terms of service changed?
- Is district data used for model training?
- Have subprocessors or underlying models changed?
- Have any incidents or complaints occurred?
- Is the product still being used for its approved purpose?
- Are employees following the documented restrictions?
- Has the tool delivered its expected instructional or operational value?
- Does the district still need it?
- Has another approved product introduced overlapping functionality?
- Should the product be renewed, restricted, renegotiated, or retired?
A separate AI committee may not know when a contract is approaching renewal. A connected governance system makes ongoing review part of the product’s normal lifecycle.
Include AI in Training, Support, and Incident Response
AI governance is not only about approving products. It also governs how those products are used.
District training should connect AI expectations to existing procedures for:
- Student-data privacy
- Cybersecurity
- Acceptable use
- Academic integrity
- Accessibility
- Instructional-material selection
- Copyright and attribution
- Records management
- Employee conduct
- Incident reporting
Employees should know how to report situations involving protected information entered into an unapproved tool, inaccurate or harmful output, inappropriate student use, biased recommendations, synthetic media, impersonation, unexpected feature changes, or undisclosed AI-generated content.
These incidents may require participation from technology, privacy, curriculum, legal, communications, human resources, or administration. They should be documented with the associated product so the district can identify patterns and determine whether access, training, approval, or policy needs to change.
Govern the Use Case, Not Just the Product
A simple list of “approved AI tools” can create a false sense of security.
The same product may present very different levels of risk depending on how it is used.
For example, a tool may be approved for an educator to brainstorm lesson ideas without entering student information. That approval does not necessarily mean students may create accounts, upload their work, or rely on the system for personalized academic recommendations.
District governance should document:
- The approved purpose
- Eligible users
- Permitted data
- Prohibited data
- Approved features
- Required human oversight
- Training requirements
- Limitations and conditions
- The process for requesting a new use
This is true for AI and for EdTech more broadly. Products should not be approved in the abstract; they should be approved for specific users, purposes, and conditions.
Apply Continuous Governance
AI policies, inventories, and approval decisions cannot remain static.
Districts need an ongoing process for monitoring:
- New AI-enabled products
- AI features added to existing products
- Changes to vendor terms and privacy practices
- Emerging risks
- Employee and student use
- Incidents and complaints
- Product effectiveness
- Training needs
- New laws, regulations, and board policies
- Renewal and retirement decisions
This does not mean starting a new initiative each time the technology changes. It means building AI considerations into the district’s regular product reviews, policy updates, training cycles, contract renewals, and leadership reporting.
Continuous governance is more sustainable than a one-time AI task force because it assigns lasting ownership and connects review to the district’s daily operations.
One Governance Strategy, with Risk-Based Controls
AI creates new questions, but it does not erase the governance responsibilities districts already have.
Every digital product still needs a defined purpose, accountable owner, appropriate review, clear approval status, supporting documentation, contract oversight, employee guidance, ongoing monitoring, and an eventual renewal or retirement decision.
Creating a separate AI governance structure may initially feel more responsive. Over time, however, it can make the district’s technology environment even more fragmented.
A stronger strategy is to maintain one EdTech governance framework with risk-based controls for AI and other emerging technologies.
That means:
- One product inventory
- One coordinated request process
- One cross-department governance structure
- One source of truth for employees
- Connected contracts and documentation
- Clear ownership
- Risk-based evaluation
- Continuous review throughout the product lifecycle
Bring AI Into the Complete EdTech Lifecycle
AI governance should not become another spreadsheet, committee, or policy operating on the edge of the district’s technology strategy.
It should strengthen the system the district uses to discover, evaluate, adopt, communicate, monitor, renew, and retire every digital resource.
Veracity helps K–12 districts bring AI and EdTech governance together by centralizing product information, coordinating cross-department evaluations, documenting approved uses and restrictions, connecting contracts and renewals, publishing searchable catalogs, and maintaining visibility across the complete EdTech lifecycle.
AI may require additional scrutiny—but it should never require districts to sacrifice coordination, consistency, or a complete view of their EdTech ecosystem.
Ready to build AI governance into your district’s larger EdTech strategy? Contact info@veracityvs.com.