From the K–12 edition of September 18, 2026
OSSE/REL Mathematica LEA survey: only 45% of DC LEAs had staff AI policies; model guidance ranked top need
OSSE with Regional Education Laboratory at Mathematica · K-12 state education agency survey research · Washington, D.C., United States
- Publisher
- The State of AI in District of Columbia LEAs (survey results brief)
- Original publication
- May 2026 (survey brief); fielded February 2026
- Source retrieved
- 2026-09-19
- Event date
- 2026-02-01
What happened
In February 2026, OSSE and REL Mathematica surveyed DC’s 69 LEAs (59 responses collapsed to 39 unique LEAs). Only 45% reported written staff AI guidance and 34% reported student-use guidance. Procurement maturity was uneven (formal review 41%, informal/ad hoc 26%, not procuring 28%, unsure 5%). LEAs ranked model instructional AI policy as the most useful OSSE support, ahead of privacy guidance and educator training. Top adoption challenges included data privacy/security, tool quality, lack of federal/state guidance, bias, staff readiness, and uncertain instructional value. Why now: OSSE’s Sept 1, 2026 staff model policy was built explicitly in response to this gap and was not yet in the SLED k12 archive.
Why it matters
Quantifies the policy-readiness gap that SEAs and large districts must close before scaling staff AI—and explains demand for model policies over procurement templates alone.
Evidence and measured results
Opened the May 2026 PDF brief: policy prevalence (45%/34%), procurement pie chart categories, ranked desired supports, use-case interest bars, and challenge severity distributions. Cross-checked with OSSE press release citing the same 45% staff-policy figure as the impetus for the September model policy.
Limitations and uncertainty
Self-report LEA-leader survey (39 LEAs), not classroom outcome measurement; published May 2026 (pre-policy) so pair with the September model policy for current operational meaning. Interest bars are not evidence of effective use.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Most LEAs still lack written staff/student AI policies and formal AI procurement review while facing privacy and quality concerns.
- Stakeholders
- SEA program leads
- LEA executives
- CTOs
- Procurement
- Board members
- Discovery questions
- Do you have written staff and student AI policies today?
- Is AI procurement formal, ad hoc, or not happening?
- Which challenge is prohibitive: privacy, quality, bias, or guidance gaps?
- What SEA supports would unblock you first?
- Value hypothesis
- A bounded policy-and-procurement readiness engagement converts survey-identified gaps into adoptible local controls before instructional scale-up.
- Potential engagement
- 3-week LEA AI readiness baseline and staff-policy draft aligned to OSSE survey constructs.
- Unsupported claims
- That policy adoption raises achievement
- That 45%/34% figures generalize outside DC
- Guaranteed reduction in privacy incidents after templates
Pre-sales engineering
Role takeaway
- Fit
- Fit as a governance instrumentation and template layer; not a student tutoring product.
- Architecture and integration
- Policy status fields in ITSM/inventory; procurement workflow states; training completion linked to IdP entitlements.
- Prerequisites
- LEA inventory of AI-touched tools
- Executive sponsor for policy
- Privacy officer involvement
- Constraints
- Survey is DC-specific
- Self-report bias
- No student outcome measures
- Security
- Prioritize privacy/security review gates because leaders already flag them as major challenges.
- Proof of value
- Baseline report matching OSSE metrics
- Draft staff policy approved by counsel
- Procurement checklist used on one live purchase
Delivery
Role takeaway
- Work
- Run readiness survey, draft staff policy, stand up formal review steps, and plan educator PD against top challenges.
- Dependencies
- OSSE/SEA templates
- Legal
- PD providers
- Ownership
- LEA chief of staff or CIO owns readiness metrics; academics own instructional examples later.
- Skills and adoption
- Train leaders to interpret readiness metrics and staff to follow new review steps.
- Governance checkpoints
- Baseline published
- Staff policy adopted
- Procurement SOP live
- Acceptance criteria
- Written staff AI guidance adopted
- Formal AI review path documented
- Top two challenges have named owners
- Risks
- Policy theater without enforcement
- Skipping student-use policy after staff-only win
- Overclaiming instructional value the survey does not support
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?
Many LEAs still lack formal AI procurement review—expect ad hoc tool sprawl until SEA templates and allowlists land; privacy and bias concerns should drive security review gates before instructional rollout.
Governance
Who approves, reviews and stays accountable for outcomes?
Staff policy and student policy are separate adoption problems; SEAs should sequence model staff guidance first where LEAs request it most, then student-use and procurement templates.
Security and privacy
What data, permissions and controls need testing?
Data privacy/security was among the most cited significant challenges—supports prioritizing DPAs and enterprise controls before expanding student-facing GenAI.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Staff readiness and training ranked as needed supports; interest in disability and EL use cases exists but is not evidence those uses are effective yet.
Procurement
What should contracts, pricing and exit terms secure?
With only ~41% reporting formal AI review, vendors should expect uneven diligence and help buyers stand up review—not exploit ad hoc paths.
Operating model
Which teams own the service once it runs?
SEA support sequencing (model policy → privacy → PD) mirrors how LEAs ranked needs; operating plans should follow that order.
Publication history
- 2026-09-18K–12 · Issue 134 resources
Stable resource ID: osse-dc-lea-ai-survey-brief-may2026