From the K–12 edition of September 30, 2026
RAND (IES-sponsored): Accountability and alignment more than doubled Zearn Math usage goals, with teacher trade-offs
RAND Corporation · K-12 education research · United States (large urban district case)
- Publisher
- RAND research report RRA5192-1
- Original publication
- September 30, 2026
- Source retrieved
- 2026-10-01
- Event date
- 2026-09-30
What happened
Same-day RAND report (Todd & Huguet; IES-sponsored) examines how one large urban district raised Zearn Math usage over two years inside a 32-school RCT context. In year one, fewer than one in five students met the platform's annual lesson goal; in year two about half did. Six case-study schools (126 interviews over two years) credit a package of accountability strategies (clearer expectations, centralized monitoring, incentives) and alignment strategies (curriculum fit with Eureka, dedicated schedule time, fewer competing tools, expanded professional learning). Authors stress trade-offs: some teachers found clearer structure helpful, while others reported stress, worry about consequences for missing targets, or concern that platform time displaced other valued activities. This report analyzes implementation/usage, not student achievement (achievement covered in a separate Pane et al. paper).
Why it matters
Preferred-domain, same-day evidence that edtech (and by transfer, AI tools) scale through accountability-plus-alignment packages, and that usage gains can carry workload and opportunity-cost trade-offs without proving durable learning by themselves.
Evidence and measured results
Qualitative case studies nested in a larger RCT (32 schools); 126 interviews; platform usage metrics; not a generative-AI causal study.
Limitations and uncertainty
Single large urban district; six case-study schools not statistically generalizable; self-reported interviews; Zearn Math is adaptive math software, not generative AI; usage gains are not achievement claims in this paper.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Districts buy edtech/AI tools that stay optional and underused, then lack honest language about the teacher costs of forcing usage up.
- Stakeholders
- superintendent
- curriculum
- principals
- teachers
- evaluation
- board
- Discovery questions
- Is the tool scheduled, or only encouraged?
- How does it align to the core curriculum, not as an extra?
- What monitoring and incentives are planned, and what are the teacher stress risks?
- Which competing tools will be retired?
- Value hypothesis
- If districts combine clear expectations, schedule time, curriculum alignment, and PD, usage can rise enough to make outcome evaluation possible, provided trade-offs are managed.
- Potential engagement
- Implementation design sprint mapping accountability/alignment package and trade-off metrics before renewal.
- Unsupported claims
- That usage doubling equals achievement gains in this report
- That findings automatically transfer to generative AI chatbots
- Guaranteed teacher workload reduction
Pre-sales engineering
Role takeaway
- Fit
- Useful for districts implementing supplemental platforms or AI tutors that need sustained, curriculum-aligned use.
- Architecture and integration
- Embed in LMS/schedule; sync with core curriculum units; centralize usage dashboards with school-level nuance.
- Prerequisites
- core curriculum mapping
- bell-schedule authority
- PD capacity
- tool consolidation plan
- Constraints
- single-district evidence
- incentive funding sources
- risk of punitive monitoring
- Security
- Limit monitoring data to educational purposes; control vendor access to classroom usage traces.
- Proof of value
- Usage goals tied to scheduled blocks
- Documented curriculum alignment
- Teacher feedback loop on displacement/stress
Delivery
Role takeaway
- Work
- Clarify expectations, schedule dedicated time, align to core curriculum, reduce competing tools, expand PD, monitor usage and trade-offs.
- Dependencies
- principal schedule control
- curriculum specialists
- PD providers
- possible incentive budget
- Ownership
- Curriculum/instruction owns alignment; principals own schedule fidelity; district analytics owns monitoring ethics.
- Skills and adoption
- Coach teachers on integrating platform/AI practice into core lessons, not as spare-moment filler.
- Governance checkpoints
- expectation memo
- schedule audit
- midyear teacher stress/displacement survey
- renewal review
- Acceptance criteria
- Usage targets defined with scheduled time
- Competing-tool list reduced
- Trade-off metrics collected alongside usage
- Risks
- Punitive target culture
- Usage theater without learning measures
- Displacement of higher-value instruction
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Schedule-integrated usage windows, curriculum alignment, and reduced tool sprawl matter more than optional add-on access for sustained platform use.
Governance
Who approves, reviews and stays accountable for outcomes?
Central expectations and monitoring raise usage but need guardrails against punitive target culture; preserve school-level judgment within district guidance.
Security and privacy
What data, permissions and controls need testing?
Centralized usage monitoring creates student/teacher activity data that needs privacy-aware retention and purpose limits, even for non-generative platforms.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Expanded PD and clearer expectations can help uneven teacher capacity, but rigid targets may stress staff and compress time for other supports.
Procurement
What should contracts, pricing and exit terms secure?
Budget for PD, coaching, and possible incentive costs alongside licenses; require implementation plans, not seat counts alone.
Operating model
Which teams own the service once it runs?
Treat edtech/AI as scheduled instructional infrastructure with accountability and alignment, not optional apps.
Publication history
- 2026-09-30K–12 · Issue 254 resources
Stable resource ID: rand-edtech-accountability-alignment-20260930