Behind every classroom app is a layer of district software that few teachers think about and no district can run without: the student information system (SIS) that holds enrolment, attendance, schedules and grades; the learning management system (LMS) where assignments live; the rostering and single-sign-on services that connect hundreds of apps to the right students; the device-management, filtering and monitoring tools that satisfy federal law and parents; and the finance, HR, special-education and transportation systems that run the district as an organization. This layer is less exciting than classroom software but much more durable. Contracts renew at very high rates, switching takes years, and private equity has spent two decades rolling it up. The same concentration means a single breach can expose tens of millions of children, as the December 2024 PowerSchool incident showed. This section explains the systems, the interoperability standards that connect them, the economics that attract PE, and the security and safety issues that now dominate district technology agendas.
What the study covers
- 1Overview: the district systems stack
- 2Mechanics
- 3Why private equity loves this layer
- 4Key numbers
- 5Landmark cases
- 6Pitfalls
- 7How an expert thinks about it
- 8Glossary
Technical exhibits
Worked examples, checklists and case studies included with this study.
Interoperability Standards Primer
OneRoster, LTI 1.3, Ed-Fi, SIF, CASE, QTI, Caliper, Clever/ClassLink and SSO, explained for product managers and investors
PE Rollup Worked Example
Stylized buy-and-build of a K-12 district-software platform: entry, add-ons, organic growth, exit and value decomposition, computed by script
Powerschool Case Study
From Apple to Pearson to PE, IPO, Bain take-private and the 2024 breach: what the PowerSchool story teaches about the infrastructure layer