The Contract Behind the Classroom: A Procurement Checklist for District Leaders Evaluating EdTech
Procurement Has Become a Leadership Competency
A decade ago, most district technology decisions were modest: a reading intervention here, a gradebook upgrade there, each reviewed by a small committee. Today's agreements are more consequential. A single platform may define how teachers plan lessons, where student records live, which vendor sees assessment data, and how much of the discretionary budget is committed before the school year begins.
Yet procurement review in many districts remains a compliance exercise conducted after the instructional decision is already made. That sequence is backwards. The contract is where instructional intent either survives or quietly erodes.
Begin With the Instructional Problem, Not the Demonstration
Vendors are skilled at demonstrating what their product does. Leaders should arrive with a different question: what specific, documented problem are we trying to solve, and what would improvement look like six months from now?
A useful discipline is to write that question down before any vendor conversation and circulate it to the evaluation committee. If a product demonstration cannot be mapped directly to the stated problem, it belongs in a future consideration file rather than the current decision cycle. This single practice reduces the common pattern in which districts purchase a platform because its capabilities were impressive, then retrofit a rationale afterward.
The Clauses That Decide Whether a Tool Serves You
Most contract problems cluster in a handful of predictable places. Leaders reviewing a proposed agreement should confirm the following before signature:
Data ownership and use. Student data generated by the platform should remain district property, and the vendor should be contractually barred from using it for model training, product development, or resale without explicit written authorization. This point deserves particular attention in 2026, as more platforms embed generative features that learn from user inputs.
Retrievability and export. The district should be able to extract its data, in a usable format, at any time and at no additional charge. Exit rights that exist only on paper are not exit rights.
Termination provisions. Ask what happens if the district ends the agreement mid-year. Penalties, data deletion timelines, and transition assistance should all be specified.
Price protection. Multi-year agreements should cap annual increases and disclose the cost of required add-ons that will not appear in the first-year quote.
Performance commitments. Uptime guarantees, support response times, and remedy provisions matter operationally, particularly for tools used in daily instruction.
Privacy Review Is Not a Formality
Federal and state student privacy obligations have grown more specific, and district counsel should review any agreement that touches student records, biometric data, or classroom audiovisual capture. The practical test for leaders without legal training is straightforward: can we explain to a parent, in plain language, what data the platform collects, why, how long it is retained, and with whom it is shared?
If that explanation requires extensive qualification, the agreement is not ready. Transparency obligations also extend to families, and a district that cannot answer those questions confidently invites avoidable disputes.
Design Pilots That Produce Evidence, Not Anecdotes
Pilots frequently fail as decision tools because they lack a comparison condition, a defined duration, and pre-agreed success criteria. A stronger design specifies which classrooms will participate, what outcome measures will be examined, who will review the results, and what decision will follow from each plausible finding.
Equally important is deciding in advance what result would lead the district to decline a purchase. Without that condition, pilots tend toward confirmation rather than evaluation, and the sunk effort of a trial becomes its own argument for adoption.
Total Cost Beyond the License
Administrators should account for the costs that survive the quote: staff professional learning, integration with existing systems, device requirements, dedicated support time, and replacement of tools displaced by the new platform. These figures frequently exceed the license fee itself, and they belong in the board presentation alongside it.
Signing With Your Eyes Open
The most reliable safeguard is procedural rather than technical. Assign one person to own the contract rather than the relationship, separate the instructional evaluation from the commercial negotiation, and schedule a formal review before each renewal rather than allowing agreements to roll forward automatically.
Districts that treat procurement as an instructional decision tend to end up with fewer tools, deeper adoption, and contracts that can be ended without disruption. That outcome is not the product of better vendors. It is the product of better preparation.
