Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Bias Reporting Systems topic
No spam. Unsubscribe anytime.
Concord work group outlines town-level bias reporting plan after focus groups show distrust of school-based reporting
Summary
Work group members heard focus-group findings that many residents distrust school-based reporting and favor a town-level incident reporting system with multiple access modes, confidentiality, and visible follow-up; the town CIO described a Microsoft 365-based, low-cost option and staff training needs. Draft report outline due late April.
Deborah Dorfman, a member of the Bias and Hate Incident Reporting Work Group, said the group’s focus groups revealed widespread distrust of school-based reporting and a preference among many participants for a separate town-level reporting option.
“In several cases parents reported that some high school students felt unsafe wearing Stars of David,” Dorfman said, summarizing participants’ concerns. She described accounts of community exclusion—people being told “You don’t belong here”—and said the groups heard that many incidents go unreported to police or schools.
The work group heard that participants faced several barriers to reporting, including concerns about privacy and confidentiality, uncertainty about anonymous reporting, and fear of retaliation that could include economic consequences for business owners. Dorfman said participants feared reports would “fall down the rabbit hole” without clear follow-up and emphasized that collected data must not be “just data” but should lead to training, interventions and resources.
The group discussed features participants want in a reporting system: multiple reporting modes (online, phone, paper and in-person), multilingual access, optional contact fields to preserve anonymity, a simple user experience, visible confirmation and follow-up to reporters, and using aggregated data to identify patterns. Members also discussed how to distinguish protected speech from reportable incidents and how the town might verify reports’ accuracy.
Jeff Weiner, the town’s chief information officer, presented a technical overview of how a town-level system could operate. He described storing submissions securely in Microsoft 365, using Microsoft Power BI to analyze trends, and starting with manual intake and routing handled by trained staff, with the option for automated routing later. Weiner told the group that “AI is not necessary” for processing because existing Microsoft tools provide adequate automation, and he emphasized the need for staff training on intake and routing and for legal review and Town Council approval of final procedures.
At the start of the meeting, the group approved the minutes of its Feb. 24, 2026 meeting; Deborah Dorfman moved to approve, Sandeep Pisharody seconded, and the motion passed with all in favor (Dorfman, Dan Hart, Pisharody and Paul Boehm). Paul Boehm said the Select Board has extended the group’s deadline to May 15. The work group plans to focus the next two meetings on defining system components and preparing a draft report outline by late April, followed by revision and coordination with the Select Board.
The work group also reviewed a proposed taxonomy of incident types (including race, sexual orientation, gender identity, religion/antisemitism, disability, age, class, bullying, vandalism, harassment and assault) and location categories (public/town spaces, institutional/service locations and an "Other" catch-all) to keep reporting simple but comprehensive.
The meeting adjourned at 7:33 p.m. The work group is scheduled to reconvene March 24 to continue drafting system components and report structure.
