Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Edtech Registry topic
No spam. Unsubscribe anytime.
Committee weighs adding EdTech registry to data-broker bill, flags enforcement gaps
Summary
Members considered importing H.650 registry language into H.211 to track educational-technology providers used in Vermont schools; discussion focused on definitions, whether free tools are captured, who enforces registry requirements (AG vs. auditor) and concerns about chatbots and product quality control in schools.
The Senate Economic Development, Housing & General Affairs Committee discussed integrating an educational-technology registry into its data-broker vehicle as a way to preserve registration language if an independent EdTech bill stalls.
A committee member (speaker 2) urged adding a registry modeled on H.650 to H.211 so the registry would survive possible delay in Senate Finance: "This is something Rick also has drafted... I would suggest we might add the language to this bill in case it doesn't move out of finance," the member said. Counsel later confirmed parts of a registry are already public in earlier reports and that a registry subchapter would require providers who operate under paid contract in Vermont schools to register products, supply names, privacy-policy links and attest that the products comply with student-privacy standards.
Why it matters: Members emphasized the registry is a first step to identify which products operate in schools but said it does not by itself ensure product quality or stop problematic tools. Several speakers pointed to examples where third-party lists included low-quality or inappropriate offerings and said districts and the Agency of Education must also strengthen procurement and oversight.
Enforcement gap: Committee members repeatedly noted registries typically lack enforcement. Speaker 2 and others asked whether the attorney general would be tasked with enforcement; counsel said the AG's office has resisted taking broad enforcement responsibility. The auditor’s office can audit related consortia (for example, the nonprofit Vitalert), the committee noted, but the auditor does not have rulemaking or enforcement authority.
Technical scope: Counsel described registration mechanics: providers would list each product used under a paid contract at named schools, provide a link to privacy policies and terms of use, and attest compliance with student-privacy standards in law. Committee members and counsel acknowledged free tools used in classrooms without contracts may escape registry coverage and said the registry should be step one in a broader approach.
Next steps: Members asked staff to circulate registry language and to consult the auditor and other stakeholders; the committee planned to return to the registry language after finishing H.211 and to reconvene the next morning for a possible vote.
