How school districts actually buy edtech: procurement explained

Edtech companies spend heavily on salespeople and conferences, yet the buying decision they are chasing is spread across a district's teachers, technology directors, procurement officers, school board, and legal counsel. A single Chromebook cart purchase can touch four departments and take eight months. Understanding the actual sequence — not the version described in vendor pitch decks — explains why good products die quietly and mediocre incumbents keep their contracts.

What does the buying process look like from the inside?

Most district purchases begin informally. A teacher sees a product at a conference or a colleague's school and asks for a trial. Vendors call this the «pilot» stage; districts usually call it nothing at all, because no money has moved and no administrator has formally approved anything. The first formal gate is a needs determination: a principal or curriculum director decides whether the request aligns with an identified goal, such as a reading intervention gap or a device refresh cycle. From there, the request typically passes through five checkpoints.

The privacy gate deserves particular attention. Since around 2015, states have adopted student data privacy statutes that push districts to demand signed data privacy agreements before any tool touches student records. Many vendors first learn their standard terms of service are insufficient when a district technology director returns a redlined contract with state-specific deletion and breach-notification language.

When does a purchase have to go out for bid?

The formal bidding question is threshold-based. Every district, and in many states every education service agency or cooperative, sets a dollar threshold below which a purchase order can be issued on staff signature alone. Above that threshold, state law or district policy usually requires competitive quotes, a request for proposals, or participation in a cooperative purchasing contract. Common patterns include three written quotes in the low tens of thousands of dollars and a full RFP at higher amounts, though exact figures vary by state.

Cooperative purchasing is the escape hatch most vendors underestimate. Contracts awarded through consortia such as state-level purchasing programs or national cooperative networks let a district buy without running its own bid, because the competitive process already happened once, at the co-op level. For vendors, landing on a cooperative contract is often more valuable than any individual district win.

Why does everything slow down in spring?

District budgets run on a July-to-June fiscal year in most states. Federal grant money often carries an obligation deadline in late September, and local budget approval happens in spring. The practical consequence: purchase orders cluster between March and June, when remaining funds are being spent and next year's budget is being finalized. A vendor that starts a sales conversation in May has usually missed the buying window for the coming school year and is competing for leftover funds.

Federal funds add their own timing. Title I and other ESSA program funds typically must be obligated within set windows, and spending rules differ by program. Procurement staff must also check that federal purchases follow Uniform Guidance requirements, which impose stricter conflict-of-interest and documentation standards than local funds alone.

Who really holds veto power?

Superintendents sign, boards approve, but day-to-day vetoes are distributed. A data privacy officer can block a tool over contract language. A procurement director can reject a sole-source justification. A finance officer can flag an expense against the wrong fund code. And an instructional technology coach who says the tool duplicates something already deployed can end a request before it reaches any of them. Vendors that map only the org chart's top layer routinely misread why deals stall.

What happens inside a formal RFP?

A request for proposals is a public document, and writing it well is a skill districts often lack by omission. The specification section determines the competitive field: requirements written around one vendor's feature list produce one responsive bidder, while requirements written around outcomes — measurable gains, integration standards, data portability — invite alternatives the district has never heard of. Scoring rubrics are published in advance in many states, and vendors read them closely; a rubric weighting years of district references at forty percent tells new entrants not to bother.

After submission comes evaluation, usually by a committee of teachers, administrators, and technology staff working from the published rubric, sometimes with scored demonstrations. Reference calls with two or three current customers are standard practice and more informative than any demo. The committee's recommendation routes back through procurement for a responsibility determination — debarment checks, insurance, financial stability — before the board sees it. Districts that skip the financial-stability conversation for small software vendors are the same districts that later scramble when a tool shuts down mid-contract.

Protests are rare but real. A losing bidder can challenge the award, and even an unsuccessful protest freezes implementation for months. Clean documentation — scores kept, notes dated, conflicts of interest disclosed — is the district's only defense.

What should a school leader do with this?

For administrators, the working checklist is short: name the budget owner before the pilot starts, define what evidence would justify a purchase, get the privacy agreement reviewed early rather than after the demo has won people over, and check the bid threshold before promising a vendor anything. For vendors, the honest version is less flattering: the product is being evaluated not only on student outcomes but on contract flexibility, data handling, and whether the purchase can clear procurement before the fiscal year closes. The districts that document this sequence publicly tend to get better pricing and fewer failed deployments — and the vendors that learn it stop describing school buying as a single decision.