From the K–12 edition of September 21, 2026
NYCPS publishes 2026–27 AI and screen-time floor: GenAI moratorium in 2K–8, five dosage-capped HS pilots, staff AI barred from grading and placement
New York City Public Schools (NYCPS) · K-12 large urban district policy / operating guidance · New York City, United States
- Publisher
- Guidance on Artificial Intelligence (AI) and Screen Time (NYCPS)
- Original publication
- School-year 2026–27 guidance page concurrent with September 2026 rollout
- Source retrieved
- 2026-09-22
- Event date
- 2026-09-02
What happened
NYCPS’s official guidance for 2026–27 imposes a moratorium on student-facing generative AI in grades 2K–8, recommends grade-banded 1:1 screen-time limits, requires two 45-minute high-school AI literacy modules, and confines HS GenAI to five centrally approved pilots (Quill, Edia, Brisk Teaching, Playlab, Intel AI-Ready Schools) with weekly dosage caps and one-pilot-per-student exposure. Staff may use AI for planning/operations under ERMA privacy review but must not use AI for grading, behavior monitoring, or placement/promotion/graduation decisions. IEP/504 assistive technology remains excepted.
Why it matters
Largest-U.S.-district operating model other LEAs will be asked to match or explain against: grade-banded GenAI floors, named pilot allowlists, staff high-stakes AI prohibitions, and privacy review gates.
Evidence and measured results
Opened the NYCPS guidance page end-to-end via WebFetch: Chancellor note, grade/AI/screen table, 2K–8 moratorium language, HS literacy and five-pilot tables with dosage examples, staff-use limits, ERMA explanation, accessibility exceptions, and afterschool/CBO alignment commitments.
Limitations and uncertainty
Guidance without outcome evaluation yet; enforcement and the full list of disabled AI features in the ~38 tools are incomplete on-page; publicationDate aligned to Sept 2026 announcement/rollout rather than an on-page timestamp.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-22; 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 need a defensible GenAI floor that protects younger learners while offering narrow, supervised HS pilots without high-stakes automation.
- Stakeholders
- Chancellor/superintendent
- CTO
- academic leadership
- UFT/teacher unions
- families/CECs
- procurement/privacy counsel
- Discovery questions
- Can GenAI features be disabled by grade band on district devices?
- Which student decisions (grading, placement, discipline) are hard-blocked from AI?
- Do you have a privacy review gate equivalent to ERMA before classroom enablement?
- How will you cap pilot dosage and prevent multi-pilot student exposure?
- Value hypothesis
- Vendors that ship kill-switches, privacy packets, and dosage-limited HS pilot configurations will clear large-district bars faster than open GenAI suites.
- Potential engagement
- 4-week NYC-floor gap assessment: map current tools to 2K–8 off / HS allowlist / staff high-stakes blocks and produce a remediation backlog.
- Unsupported claims
- That the moratorium improves achievement
- Guaranteed enforcement without device-management capacity
- That five pilots generalize as effective for all HS students
Pre-sales engineering
Role takeaway
- Fit
- Fit for districts with MDM/IdP control over student devices and edtech entitlements; poor fit for BYOD-unmanaged GenAI.
- Architecture and integration
- Grade-band policy engine → vendor GenAI feature flags; pilot entitlement service; staff AI scopes excluding gradebook/discipline/placement APIs; ERMA artifact store.
- Prerequisites
- Authoritative edtech inventory
- MDM/SSO
- privacy review workflow
- SPED 504/IEP process owners
- Constraints
- Assistive-tech exceptions
- CBO/afterschool alignment
- Vendor update lag when AI features appear silently
- Security
- NYS 2-d / FERPA-aligned DPAs, encryption, breach notice, and minimization for pilot telemetry.
- Proof of value
- Demonstrate GenAI disabled on a 2K–8 student profile
- Show AI cannot post grades or placement recommendations
- Pilot user limited to one approved tool with dosage telemetry
Delivery
Role takeaway
- Work
- Configure kill-switches, publish staff/family guidance, enroll HS literacy modules, run pilot application process, and monitor vendor AI feature updates.
- Dependencies
- Legal/privacy
- academic PD
- device management
- union communication
- Ownership
- District academic and technology leadership jointly; principals enforce school practice.
- Skills and adoption
- Mandatory HS AI literacy modules; staff training on permitted planning uses vs prohibited high-stakes uses.
- Governance checkpoints
- Allowlist published
- Quarterly pilot dosage review
- Coalition/policy refresh path
- Exception audit for IEP/504
- Acceptance criteria
- Documented GenAI-off for student-facing tools in 2K–8
- Only named HS pilots enabled with family notice
- No AI used for grading or placement decisions in sampled workflows
- Risks
- Shadow AI via personal devices
- Vendor silent GenAI feature adds
- Overburdening teachers for enforcement without central controls
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?
District stacks need vendor kill-switches for GenAI features in existing edtech, ERMA-equivalent privacy review before classroom enablement, pilot entitlement controls limiting students to one approved AI program, and staff-tool configurations that block AI grading/placement paths.
Governance
Who approves, reviews and stays accountable for outcomes?
Boards should publish grade-banded GenAI rules, named allowlists, literacy requirements, and explicit bans on AI for high-stakes student decisions; create a parent/educator coalition path for 2027 policy refresh as NYCPS describes.
Security and privacy
What data, permissions and controls need testing?
ERMA plus NYS Ed Law 2-d vendor agreements are the gate; families need plain notice when students enter pilots; assistive-tech exceptions must not become a GenAI loophole without IEP/504 team determination.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
IEP/504 assistive exceptions must stay available; HS literacy modules and staff PD are workforce prerequisites; SPED teams need clear exception documentation.
Procurement
What should contracts, pricing and exit terms secure?
RFPs should require GenAI feature disablement, ERMA/2-d packets, pilot dosage controls, and contractual notice before AI features are added to existing products.
Operating model
Which teams own the service once it runs?
Shift from open experimentation to grade-banded floors, named pilots, and human-decision integrity for grades and placements.
Publication history
- 2026-09-21K–12 · Issue 164 resources
Stable resource ID: nyc-doe-ai-screen-time-guidance-202627