From the K–12 edition of October 23, 2026
Chalkbeat obtains NYC's list of 38 ed tech products flagged under its student AI restrictions; several vendors say they don't use the prohibited AI
New York City Public Schools (reported by Chalkbeat New York) · K-12 student-facing generative AI restrictions and ed tech vetting · New York City, New York, United States
- Publisher
- Chalkbeat New York
- Original publication
- October 23, 2026, 5:35pm UTC (Chalkbeat)
- Source retrieved
- 2026-10-24
What happened
After more than a month of requests, Chalkbeat obtained the Education Department's list of 38 previously allowed products whose AI components the city said it would discontinue or disable under its new student-facing AI restrictions. The list includes widely used reading and math curriculums, student assessment tools and the department's own chatbot teaching assistant built with Microsoft and used in six schools last year. Amira, an AI reading tutor used in more than 200 city schools, was banned outright because officials said it cannot function without AI. Several companies, including HMH (Read180) and the translation tool Wordly, said their products do not use student-facing generative AI and did not know why they were flagged. The department said restrictions apply to student-facing generative AI features, not necessarily whole products, and that it is working case by case on whether features can be disabled, but did not explain how it decided which tools met the definition. Some vendors disabled features quickly: All In Learning turned off AI-assisted grading, and Magma Math disabled AI hints on September 4 and was cleared on October 5. Coursemojo and Gemini are also banned but not on the list.
Why it matters
The largest U.S. district's restriction is being implemented product by product, and the list shows how hard it is to define and verify 'student-facing generative AI' across a large ed tech portfolio, a problem every district with an AI policy will face.
Evidence and measured results
Investigative reporting based on an obtained district list and company responses; no district documentation of the vetting method was released.
Limitations and uncertainty
Reporting covers the list and company statements; the list is not exhaustive per officials; the department's criteria and testing process are undisclosed. Earlier NYC moratorium coverage is archived; this source adds the obtained product list and vendor disputes.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A district restricting student-facing generative AI cannot consistently tell which products and features fall under the rule, and vendors dispute its calls.
- Stakeholders
- Chief information officer
- Student privacy officer
- Chief academic officer
- Ed tech vendors
- Community education councils
- Discovery questions
- How is student-facing generative AI defined in your review?
- Which products were flagged and on what evidence?
- How are vendor disputes resolved?
- Can AI features be disabled per tenant?
- Value hypothesis
- A documented feature inventory and dispute process could make restriction decisions more consistent and defensible; not measured in this source.
- Potential engagement
- A short engagement to inventory AI features across the ed tech catalog and design a review and reinstatement workflow.
- Unsupported claims
- No evidence the restrictions improved outcomes.
- No vendor is shown to be compliant or non-compliant on independent testing.
- No cost of disruption reported.
Pre-sales engineering
Role takeaway
- Fit
- Fits ed tech products with configurable AI features that can be disabled by the district.
- Architecture and integration
- Provide tenant-level controls to disable student-facing generative AI and export the configuration for district records.
- Prerequisites
- District definition of student-facing generative AI
- Vendor admin controls
- Test accounts
- Constraints
- NYC student-facing generative AI restrictions
- New York Education Law 2-d
- Mid-year curriculum dependence
- Security
- Supply verifiable evidence of which models process student data and when features are off.
- Proof of value
- Feature map reviewed by the district
- Disabled-feature test reproduced
- Decision record per product
Delivery
Role takeaway
- Work
- Inventory, classify and decide on AI features across a district's ed tech catalog, with a dispute path.
- Dependencies
- Vendor cooperation
- Central ed tech staff time
- Clear written definition
- Ownership
- Central ed tech or student privacy office.
- Skills and adoption
- Train reviewers to test AI features rather than rely on vendor descriptions.
- Governance checkpoints
- Definition approved
- Flag list published to schools
- Dispute review
- Reinstatement decision logged
- Acceptance criteria
- Proposed: every product has a recorded decision and rationale
- Proposed: disputes resolved within 30 days
- Proposed: schools receive the current list
- Risks
- Core curriculum disruption
- Inconsistent definitions
- Unverified vendor claims
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?
Restrictions target features inside products, so compliance depends on vendors' ability to disable AI components by tenant or customer. Interpretation: districts need feature-level configuration evidence, not product-level labels.
Governance
Who approves, reviews and stays accountable for outcomes?
Central department flags products and negotiates reinstatement case by case; the definition used and the review method are not public; parents are directed to schools or community education councils for information.
Security and privacy
What data, permissions and controls need testing?
A critic quoted in the article says neither vendor claims nor the department's own review can be trusted without more transparent vetting. Interpretation: districts need verifiable vendor attestations and testing.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Some tools allowed only for English learners; teachers lose AI grading features; the policy carves out tools serving English learners.
Procurement
What should contracts, pricing and exit terms secure?
Previously approved products are being re-reviewed for AI features; reinstatement depends on disabling them.
Operating model
Which teams own the service once it runs?
Central review and case-by-case negotiation with vendors after a mayoral announcement.
Publication history
- 2026-10-23K–12 · Issue 475 resources
Stable resource ID: chalkbeat-nyc-38-flagged-edtech-products-student-facing-ai-vetting-disputes-20261023