Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Ai In Education topic
No spam. Unsubscribe anytime.
District unveils draft AI guidebook for classrooms; staff, tech to jointly vet tools
Summary
District staff presented an AI guidebook that would require teacher and tech review of tools, human oversight, and attention to FERPA/COPPA compliance; the board asked that the EdTech committee and staff continue reviews before a formal adoption step.
District staff presented a draft AI guidebook designed to guide faculty use of artificial-intelligence tools in instruction and administrative work. The presentation emphasized human oversight, district review and a multi-step vetting process for tool adoption.
"The number 1 thing that we want to maintain in all of this is human oversight," said the presenter from the Department of Student Achievement (speaker 9). The guidebook (distributed in the board book) includes: a checklist for teachers and staff to fill out when proposing a tool; a technology-department review for technical and data-security concerns; an instructional review for curricular alignment; and a requirement that, if either tech or instruction staff deny a tool, the request is not approved.
Staff said the guidebook will also address legal compliance (FERPA and COPPA), citation of AI-produced content, concerns about bias and inaccuracy in AI outputs, and training and pilot opportunities through the district's EdTech committee. The guidebook contains a draft review workflow: teacher submits tool for consideration -> tech + instruction review -> professional development and pilot if both approve.
Board members asked about next steps and whether the guidebook should return for board action. Staff described a near-term plan of staff and committee review and broader training for the fall; the board did not take an immediate vote.
Next steps: EdTech committee and tech/instruction staff will continue reviews and prepare training and pilot proposals; staff will bring a recommended implementation path and any policy language back to the board.
