School districts in the United States spend billions of dollars each year on education technology, yet the path from "we need a new platform" to a signed purchase order remains obscure to many teachers and even some administrators. The process typically runs through a needs assessment, a formal procurement, a pilot, and a contract review, and it can take anywhere from three months to more than a year. Exact rules vary by state and by district size, but the broad sequence is remarkably consistent across the country's roughly 13,000 public districts.
Who decides what a district buys?
Buying decisions are rarely made by one person. In most districts, a request starts with a classroom need identified by teachers or instructional coaches, then moves to a technology director who checks security and integration, and finally reaches a business office that controls the money. Large districts often maintain a formal review committee that includes curriculum leaders, IT staff, data privacy officers, and sometimes teachers and principals. Smaller districts may rely on a superintendent and a part-time technology coordinator. State law frequently adds another layer: purchases above a threshold set by the state, often a few thousand dollars, usually require competitive bidding or documented quotes.
What triggers the search for a new platform?
The most common trigger is an instructional gap that staff notice during the school year: a math intervention tool that does not fit the intervention block, or a reading platform students will not use. Districts also replace tools when contracts expire, when federal or state funding streams open or close, or when a legacy product is sunset by its vendor. After the pandemic-era Elementary and Secondary School Emergency Relief funds expired in September 2024, many districts conducted full audits of their software subscriptions and cut tools they could no longer justify, a discipline that has largely persisted.
What does the procurement process look like step by step?
While every district writes its own procedures, the standard arc looks like this:
- Define the problem in writing, with the instructional outcome the district wants, not the product name.
- Check existing licenses, because many districts already own tools that go unused.
- Issue a request for proposals or requests for quotes, depending on the dollar threshold set by state law.
- Score vendor responses against a rubric that covers pedagogy, accessibility, data privacy, and total cost.
- Run a pilot in a sample of schools with a defined success measure agreed in advance.
- Negotiate the contract, including data terms and renewal clauses.
- Plan rollout, training, and evaluation before the first invoice is paid.
Why do districts run pilots first?
A pilot limits the financial and instructional risk of a bad purchase. Districts typically pilot a platform in three to ten schools for one semester, with a comparison group where feasible, and judge it on usage data, teacher feedback, and whatever outcome the purchase was meant to move, such as attendance or course completion. Vendors generally support pilots because a successful trial is their strongest sales argument. The risk districts guard against is the pilot that quietly becomes a full purchase without a formal decision, which auditors in several states have flagged as a common procurement failure.
How do funding streams shape the decision?
The money source often determines what can be bought and when. Title I funds for high-poverty schools must align with the schoolwide plan; IDEA special education funds must serve students with disabilities; and state instructional materials adoption cycles dictate replacement timelines in adoption states such as Texas and California. Federal programs administered by the U.S. Department of Education come with rules on supplementing rather supplanting local funds, and district finance officers routinely reject otherwise attractive purchases because the funding stream does not fit. Smart technology directors involve finance early rather than at the end.
What do districts evaluate beyond the product itself?
A modern evaluation rubric weighs factors the sales demo never shows. Reviewers ask whether the platform meets accessibility standards under Section 508 of the Rehabilitation Act and the Web Content Accessibility Guidelines, whether it integrates with the student information system using standards such as OneRoster, and whether the vendor signs the district's data privacy agreement. They also probe the total cost of ownership: per-student licensing, implementation fees, training, storage, and the staff time needed to keep the tool running.
| Cost element | What to ask |
|---|---|
| License model | Per student, per school, or flat district fee? What happens when enrollment drops? |
| Implementation | Are data migration and rostering setup included or billed separately? |
| Training | Is professional development bundled, and for how many sessions? |
| Renewal | Does the contract auto-renew, and what is the notice window to cancel? |
| Exit | Can the district export its data in a usable format at the end of the term? |
Where do districts actually find vendors?
Beyond formal bid postings, discovery happens at state and national conference exhibit halls, through regional service agency vendor fairs, and — increasingly — through peer networks where a neighboring district's technology director describes what worked. Several states publish approved-vendor lists from prior statewide bids, which shortens both discovery and procurement. Districts also field substantial inbound marketing, and a practical rule many procurement offices apply is to route every unsolicited demonstration request through the same intake form, so that sales relationships do not form around the formal process.
Where do state purchasing consortia fit in?
Most states operate cooperative purchasing programs that let districts buy from pre-negotiated contracts, skipping the bid process for commonly used goods and services. Regional education service agencies and multi-state consortia perform a similar function, negotiating once on behalf of many districts and using the combined volume for better pricing. For small districts without procurement staff, these contracts are often the only realistic way to buy enterprise-grade platforms. The tradeoff is that the consortium's rubric, not the district's own priorities, drove the original evaluation.
What commonly goes wrong?
Practitioners and auditors point to a short list of recurring failures: buying a tool with no owner responsible for implementation, skipping the privacy review because a deadline loomed, paying for licenses counted by projected rather than actual enrollment, and letting pilot access quietly continue into an unpriced year. Another frequent problem is shelfware — products that are purchased, deployed, and then used by a fraction of teachers because training and instructional integration were never funded. Usage analytics built into modern platforms have made this harder to hide, and many districts now review license utilization annually before renewing.
How long does all of this take?
A disciplined mid-sized district should budget four to nine months from problem definition to first classroom use, and longer for a learning management system replacement. Districts that try to compress the timeline usually pay for it later in training gaps or contract terms they did not have time to negotiate. The purchasing calendar matters too: decisions made in spring align with summer setup time and fall launches, while decisions made in October often wait until the following budget year. Understanding that rhythm is one of the most practical things a vendor, a teacher, or a newly elected board member can learn.
For more context, read EdTech Contract Red Flags Districts Should Catch Before Signing.
For more context, read edtech professional development.
For more context, read How Districts Should Evaluate AI Tutors Before Buying.