From the K–12 edition of September 29, 2026
Quaker Valley AI policy: FERPA-gated tools, assignment AI-use scale, and human-final grading/HR decisions
Quaker Valley School District · Local education agency board policy · United States — Pennsylvania (Quaker Valley School District)
- Publisher
- Quaker Valley School District
- Original publication
- Proposed/approved AI policy text (board action reported Sept. 22, 2026)
- Source retrieved
- 2026-09-30
- Event date
- 2026-09-22
What happened
Quaker Valley’s Artificial Intelligence policy PDF requires age-appropriate AI instruction emphasizing human supervision and skepticism; CIPA filtering of AI tools capable of generating obscene/pornographic material; strict FERPA adherence; and a ban on student PII in AI tools not pre-approved by the Director of Technology after privacy/data-handling/FERPA review. Teachers must state permitted AI use per assignment on a 0–4 scale (No AI through Full AI Use with Human Oversight) with disclosure rules; AI may assist grading but teachers make final grade decisions; final HR evaluation/hiring/promotion decisions remain human; and regular PD on ethical AI, privacy, and compliance is required.
Why it matters
Primary LEA policy artifact operationalizing FERPA procurement gates and assignment-level AI-use scales—useful template alongside same-week Petaluma draft debates.
Evidence and measured results
District policy PDF retrieved in full; local press reports 8–0 board approval Sept. 22; not outcome evidence.
Limitations and uncertainty
Single Pennsylvania district; PDF shows template numbering ('No. XXX'); effectiveness depends on classroom enforcement not examined here; why-now is fresh board adoption plus parallel Petaluma grade-band drafting.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-29; 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 enforceable AI rules that cover privacy vetting, academic honesty, and human decision authority—not only aspirational principles.
- Stakeholders
- board
- superintendent
- Director of Technology
- teachers
- HR
- counsel
- Discovery questions
- Is there a living approved-AI list with FERPA/privacy review?
- Do teachers publish assignment-level AI-use levels with disclosure rules?
- Are final grades and HR decisions prohibited from being AI-only?
- What PD covers ethical AI and data privacy annually?
- Value hypothesis
- If LEAs adopt FERPA-gated catalogs plus assignment AI-use scales with human-final decisions, they reduce both privacy and integrity failure modes.
- Potential engagement
- Policy-to-operations package: approved-tool rubric, 0–4 syllabus language, and PD agenda mapped to board policy.
- Unsupported claims
- Uniform compliance across classrooms without audit
- That CIPA filters alone stop all harmful generative AI
- Guaranteed workload reduction from the policy
Pre-sales engineering
Role takeaway
- Fit
- Strong template for mid-size U.S. districts formalizing generative AI controls.
- Architecture and integration
- Identity-aware approved-app list; DLP/PII warnings for consumer AI; LMS fields for AI-use level; human confirmation step before grade posting.
- Prerequisites
- Board policy adoption
- Director of Technology authority
- Existing AUP/CIPA filters
- Academic honesty code
- Constraints
- Personal-device bypass
- Teacher notice burden
- Vendor model changes after approval
- Security
- No student PII in non-approved AI; FERPA-aligned DPAs; secure handling if AI assists grading.
- Proof of value
- Approved-AI list published
- Sample assignments show 0–4 levels
- Grading workflow requires teacher finalization
Delivery
Role takeaway
- Work
- Publish approved tools, train staff on use scale and FERPA rules, sample-audit assignment notices, calendar policy review.
- Dependencies
- board minutes
- filter configuration
- vendor contracts
- PD calendar
- Ownership
- Director of Technology owns approvals; teachers own assignment notices; superintendent owns procedures.
- Skills and adoption
- Practice writing clear AI-use levels and teaching skepticism about accuracy.
- Governance checkpoints
- Tool approval reviews
- Semester syllabus audit
- Discipline consistency check
- Annual PD
- Acceptance criteria
- Zero known classroom use of non-approved AI with student PII
- Majority of sampled secondary courses state AI-use level
- HR/grading human-final rules reflected in procedures
- Risks
- Paper policy without approved-list maintenance
- AI-assisted grading drifts to AI-final grades
- Students ignore disclosure rules on personal devices
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?
Maintain approved-AI inventory, assignment metadata for use levels, and grading workflows that keep humans as final decision-makers.
Governance
Who approves, reviews and stays accountable for outcomes?
Board-level AI policy with tech-director vetting authority and academic-honesty discipline path.
Security and privacy
What data, permissions and controls need testing?
FERPA-aligned vetting before any student PII touches an AI tool; CIPA filter obligations for generative AI sites.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Age-appropriate AI instruction and PD obligations create workforce training demand across roles.
Procurement
What should contracts, pricing and exit terms secure?
New AI resources require tech-director approval including privacy policy and FERPA compliance review before classroom use.
Operating model
Which teams own the service once it runs?
Moves AI from ad hoc teacher choice to cataloged, noticed, and auditable practice with human decision floors.
Publication history
- 2026-09-29K–12 · Issue 245 resources
Stable resource ID: quaker-valley-ai-board-policy-20260922