DC policy and DCPS AI rules

In the August snapshot, these four were in the no-statewide-rule category. Yet New York City requires AI tools to pass review before use with student data, Philadelphia names district-approved products, Houston conditions older students' access on written parent consent and task-specific teacher permission, and DCPS prescribes approved-tool and staff-use safeguards. Students and families must identify their own district, rather than borrow a neighboring district's permission. Educators and leaders should make the local tool list and use conditions accessible. Washington and Massachusetts, by contrast, sit in the tracker guidance category, demonstrating why 'state guidance' and 'local rule' need separate fields. ^{[7][8][42][34][14]}

Fairfax says it does not provide or approve student access to general-purpose GenAI on district-issued devices; its separate guide for personally owned devices says the teacher's assignment rules come first and advises asking a caregiver before creating an account. Boston's TECH-06 policy and spring 2026 policy call for privacy-impact assessment, approved tools and family information. DCPS's AUP addresses approved student-learning tools and staff expectations; its annual enrollment acknowledgement is receipt of a policy, not a standalone consent to AI use. Together these cases show why device control, product approval and parental permission must be separate database fields. ^{[26][13][23][14]}