Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Language Access topic
No spam. Unsubscribe anytime.
Hopkins board reviews draft language access plan; staff to add ASL, AI guidance and clearer family outreach
Summary
District staff presented a draft language access plan required by Minnesota law, highlighting interpreter contracts, bilingual seals and liaison supports. Board members asked for added guidance on ASL, augmented communication, and rules for AI‑assisted translation, plus clearer communications and twice‑yearly reviews.
Get email alerts on the Language Access topic
No spam. Unsubscribe anytime.
Hopkins Public School District presented a draft language access plan at its Nov. 18 board meeting, saying state law requires districts to adopt such plans by the 2025‑26 school year. Dr. Mary Pirie Reid told the board that Minnesota statute 123B.032 requires districts to set out how they will deliver interpreter and translation services for students and families who use heritage languages other than English.
The district’s draft, led by Assistant Superintendent Anne Urtle and Director Jolene Goldotti, packages existing systems (language identification and EL programming, family supports, bilingual seals, student success cultural liaisons and translation/interpreting contracts) into a single document for board adoption. Goldotti said the district currently contracts with an organization called Weaving Cultures for in‑person, phone and video remote interpreting, and that staff plan to finalize the draft in the coming weeks.
Board members and staff discussed monitoring and reporting: Attorney Greason and others asked whether the plan will include outcomes reporting. Goldotti said the district already monitors components such as ACCESS assessment results and liaison contact volumes and will surface those outcome slides to the board.
Members pressed for more explicit coverage of accessibility needs. Questions included whether American Sign Language and augmentative and alternative communication are included; presenters said ASL contracts exist but ASL and augmentative communication are not yet fully reflected in the draft and will be added. Directors also asked for guidance on whether and how AI tools may be used for translation. Staff recommended language allowing AI‑assisted drafts when a high‑proficiency human reviewer vets content before distribution.
Several board members asked for clearer, multi‑channel communications so families know how to access services. Staff described current enrollment flags, Blackboard automatic translations (Somali, Hmong, Spanish), and website translation tools; they said some families prefer English or have limited literacy in the heritage language, so communications need multiple modes (phone calls, liaison outreach, translated forms). The team proposed publishing the finalized plan on the district website and adding instructions and contact steps.
Board members also urged an explicit policy discouraging use of students as ad‑hoc interpreters in conferences and asked for a codified timeline for updates; staff reiterated the plan will be reviewed and updated at least every two years and that some components will be monitored more frequently.
Next steps: staff will add ASL and augmentative communication elements, draft AI‑use guidance that requires human review, add clearer communications instructions and publish the plan on the district website for public feedback before returning to the board for final approval.

