Plan, Purchase, and Deploy at District Scale
District purchases introduce considerations beyond an individual classroom purchase: number of schools, number of students, device allocation, procurement procedures, budget cycles, IT requirements, training, support, replacement planning, and standardization.
From Pilot to District Deployment
A district does not necessarily need to begin with a system-wide rollout. A practical approach can be to identify schools, programs, or student populations where the technology may address a defined need; pilot a limited number of devices; evaluate feedback from educators, students, and support teams; refine device allocation and implementation practices; then scale to additional schools where the pilot demonstrates a useful fit.
District Procurement Considerations
District teams may need product specifications, pricing, quantity estimates, quote documentation, vendor information, purchase-order information, IT requirements, implementation documentation, and product comparison materials.
Need a District Proposal?
An internal proposal covering need, proposed solution, student population, implementation, budget, procurement, and evaluation can help move a district request through internal approval. See the district proposal template in the resource center for a structure to adapt.
Bulk Purchasing
For larger deployments, districts should contact the school sales team with the number of schools, estimated quantity, preferred model, delivery requirements, and purchasing timeline.