How to Get Your Tool on a District's Approved AI Tools List (Step-by-Step)

For a growing share of districts, the approved-tools list is the gate a purchase passes through. If your category is not on it, teachers may stop using your product, school leaders may question renewals, and your champion may not know how to move the conversation forward.
That makes the list more than an IT detail. It is part of how to sell to school districts.
The practical goal is not to persuade one teacher that your product is useful. It is to help the district decide that your product is understood, controlled, appropriate, and allowed.
1. Understand what the approved-tools list actually is
An approved-tools list is an internal governance document. It is not a vendor directory or a marketing asset.
The list tells staff which software they may use, under what conditions, and sometimes with which data or user groups. It may vary by:
- Grade band
- Student age
- Feature set
- Type of user
- Data collected
- Whether a teacher must supervise use
- Whether family notification or consent is required
Approval may not be a simple yes or no. A district might approve a tool for teachers but not students. It might allow the product for older grades, but restrict it for younger students. It might permit a specific feature while requiring other features to remain disabled.
Most important, getting on the list is the permission layer. It is not the contract.
A product can be approved for use and still require a separate procurement, privacy agreement, purchase order, or board approval. This is where the distinction between budget authority and veto power matters. As we covered in K12 District Decision Makers Explained: How to Map the 6 People Who Actually Approve Your Contract, the person who wants the product may not be the person who can approve it or stop it.
Find the policy owner
The list is rarely owned by one person.
The review may involve:
- Technology or IT leadership
- Curriculum and instruction
- A privacy or data lead
- Legal
- Finance and procurement
- The sponsor of an AI working group
The policy owner is the person you need to identify first. Depending on the district, that may be a chief technology or information officer, chief academic officer, privacy or data lead, procurement owner, or central-office leader responsible for AI governance.
The person who maintains the list day to day may be a director-level technology or instructional-technology lead rather than the superintendent.
Your school-level champion can help you find this person. Ask:
“Who owns the approved-tools process, and who signs off when a new tool is added?”
2. Understand why the list became the gate
When AI rules are unsettled, districts often default to review.
Purchases and renewals can stall while IT, curriculum, privacy, legal, and procurement teams decide:
- What uses are allowed
- Which ages or grades are in scope
- What student data can enter the product
- Whether the district needs a contract or addendum
- Which features need to be disabled
- Who is responsible for monitoring changes
This is the operating reality described in A District AI Policy Freeze Is a Buying Window, Not a Dead Quarter. A freeze changes the buying process before it changes the district’s underlying need.
Non-AI products can also be pulled into AI review. That may happen because:
- The product handles student data
- A new AI feature was added
- A teacher uses a general-purpose AI tool alongside your product
- The district is reviewing all classroom software under one policy
Your product can be allowed, restricted, or absent.
Absent is the worst of the three because it is ambiguous. A teacher may think the product is acceptable. IT may think it has not been reviewed. Procurement may assume the product cannot be purchased. Your champion is left trying to explain a status that does not exist.
3. Follow the review process step by step
Step 1: Find out whether a list exists
Start with public research.
Check the district’s:
- Technology or AI policy page
- Approved-tools or software page
- Board agendas and minutes
- Staff or family handbook
- Acceptable use policy
- Technology department resources
Then ask your school-level champion which tools are approved in your category.
Do not assume the public website contains the complete list. Some districts publish only a summary. Others maintain an internal inventory that staff can access after signing in.
Your first goal is to learn whether a list exists, what it is called, and how a new entry gets considered.
Step 2: Identify the owner and sign-off path
Ask who maintains the list and who approves additions.
Find out whether the district has:
- A standing technology review
- An AI working group
- A privacy or data governance committee
- A recurring software review cycle
- A standard vendor intake form
- A chair or sponsor who coordinates the process
Do not stop at the superintendent or the person who showed interest. You need the person with policy ownership and the people with veto power.
A useful question is:
“If the district wanted to add this tool for a defined grade range, which offices would review it before approval?”
That question helps you map the path without asking your contact to sell internally on your behalf.
Step 3: Get onto the review calendar
Do not work from your sales calendar. Work from the district’s review calendar.
Ask to be considered in the next review cycle. Then ask:
- When is the next review?
- What materials are required?
- Who receives the submission?
- What is the deadline?
- Will the review cover the whole product or selected features?
- Can the district approve a limited pilot first?
This is a better motion than repeatedly asking whether the district is ready to buy. Your goal is to become a complete submission before the committee meets.
Step 4: Prepare the review packet before you are asked
Make the packet easy to forward internally. It should answer practical questions in plain English.
Cover:
Data and security
- What student and staff data you collect
- Where the data is stored
- Who can access it
- How long it is retained
- How deletion works
- Which subprocessors are involved
District requirements
- How your product addresses the district’s FERPA and COPPA review
- A data processing agreement
- Terms that permit school use
- Access controls and administrator settings
- Incident response and escalation procedures
FERPA and COPPA should be treated as part of the district’s vetting lens, not as broad claims a vendor can use to bypass review. IT, legal, and privacy teams determine what the district requires.
AI-specific questions
- Does the product use AI?
- Is student data used for model training?
- Are AI features off by default?
- Can administrators disable or limit those features?
- What does the teacher see?
- What does the student see?
- How are outputs reviewed?
- What happens when the product changes?
Age and use restrictions
- Which grades or ages the tool is designed for
- Which features are appropriate for each group
- Whether student access should be limited
- Whether teacher-only use is the recommended starting point
- Which restrictions you recommend yourself
Family communication
- What families need to be told
- What information is collected
- How the district can explain the product
- Whether the tool supports an opt-out path
Support
- Who the district contacts
- Expected support process
- How incidents are escalated
- How the district is notified about material product changes
Do not make the reviewer assemble this information from a public privacy policy, sales deck, and help center. That creates unnecessary work and makes your company look less prepared than it may be.

Step 5: Make the tool easy to describe
Give the district one plain sentence it can paste into its own list.
The sentence should explain:
- What the tool does
- What it does not do
- Which grades or users it is for
For example:
“This teacher-led planning tool helps educators organize intervention activities for middle school students; it does not make placement or discipline decisions and does not require students to create independent accounts.”
Your wording will depend on the product. Keep it factual. Avoid claims such as “safe for all students” or “fully compliant.”
If the district can describe your tool accurately, it becomes easier for staff, families, IT, and procurement to understand what approval covers.
Step 6: Use pilot framing while the rules are still open
A small, compliant pilot gives a reviewer a low-risk way to say yes.
Define:
- The schools or classrooms involved
- The grade range
- The approved users
- The features included
- The data required
- The pilot duration
- The support process
- The success measures
- The review point at the end
A pilot should help the district answer a specific question. It should not be a vague promise that broader adoption will happen later.
Save adoption language for after the entry exists. First help the district approve a controlled use case. Then use the pilot evidence to support the next decision.
Step 7: Close the loop and keep the entry current
Ask for written confirmation of:
- Approval status
- Approved grades or users
- Approved features
- Data restrictions
- Required family communication
- Review or expiration date
- Conditions for renewal
Keep the district pointed to current documentation. The list may be reviewed periodically. New features, new subprocessors, new hosting arrangements, or new AI functionality can trigger a re-review.
Approval is not a one-time victory. It is an ongoing documentation and communication responsibility.
4. What to do when the answer is no, or not yet
A “not yet” often means the district is missing documentation, not that your product is missing a feature.
Ask:
“What would need to be true for the district to reconsider this?”
You may learn that the district needs:
- A completed privacy questionnaire
- A signed data processing agreement
- More detail on model training
- A teacher-only configuration
- A narrower grade range
- A family notice
- A defined incident process
- A review by a different office
Restrictions can be workable. If student access is limited, start with teacher-only use. If one grade band is approved, compete inside that scope. If certain features are restricted, explain how the product works without them.
Do not argue with a district policy you are trying to operate inside. Find the allowed scope and build evidence there.
5. Put the review in the district fiscal year
Policy reviews and budget planning do not always move on the same schedule.
Many districts operate on a July 1 through June 30 fiscal year. The four useful planning windows are:
- July–September: New-year implementation and early priorities
- October–December: Evaluation, evidence, and budget conversations
- January–April: Planning, budget requests, and next-year decisions
- April–June: Final approvals, procurement, renewals, and adoption
A review that closes in the fall or winter can land just as the district shapes next-year priorities during the January–April planning window.
That is why the timing matters. Being on the approved list before the budget line is written is the whole game. Once the district has defined its allowed use cases, your champion can discuss scope, funding, and implementation instead of first arguing that the product should be reviewed.
The K12 District Sales Calendar guide maps these windows in more detail. The free guide is available through a form that asks for your name and email. It is designed to help EdTech teams plan research, outreach, evaluation, and procurement around the district buying year.

The practical takeaway
The approved-tools list is not the contract. It is the permission layer that makes the contract, pilot, and renewal easier to discuss.
Find the list. Identify the policy owner. Get onto the review calendar. Prepare the packet before the district asks for it. Make the product easy to describe. Start with a controlled pilot when appropriate. Then keep the entry current.
That is how to sell EdTech to schools when approval has become part of the buying process.
If your company has district traction but needs more qualified conversations with K12 district decision makers, DistrictPipeline is a fractional K12 outbound and pipeline team for lean EdTech companies. We help growing EdTech companies create qualified K12 pipeline without hiring another SDR.