Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the School Safety topic

No spam. Unsubscribe anytime.

School resource officer update draws board requests for clearer student‑impact data

Independent School District 535 (Rochester Public Schools) School Board · April 21, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Rochester Public Schools and Rochester Police Department gave a monitoring update on SRO activities and data; board members pressed for clearer tracking of distinct students affected, demographic breakdowns, and aligned reporting periods.

City police and district staff presented the board with an update on school resource officer (SRO) activity and an overview of a two‑year SRO contract during the April 21 meeting, prompting board members to ask for clearer, student‑level reporting and demographic breakdowns.

Superintendent Kent Pel introduced Chris Ling, the district’s director of school safety, and Sergeant (name variously reported in the transcript as Valair/Blair) from the Rochester Police Department to summarize SRO duties under Minnesota statute and the year‑to‑date activities. Jackie Peterson, chief of schools, noted that SROs participated in violence‑reduction efforts, safety drills, classroom presentations on vaping and social media, community events (for example, a back‑to‑school block party and cultural celebrations), and more than 100 conflict‑resolution meetings with students and families through March 1 of the school year.

Presenters displayed a chart contrasting district incident counts and RPD outcome categories; they cautioned the board that the visualization mixes incident‑level counts (an incident can involve multiple students) with individual‑level outcomes and acknowledged that some items labeled on the chart were consolidated for presentation. Chris Ling said the district’s discipline tracking (Skyward) shows 64 level‑two referrals to police this school year. Speakers stated that arrests in the presented window were zero, though the transcript contains partially garbled numerical phrasing and the presenters pledged to clarify the counts in a subsequent report.

Board members pressed on several fronts: training and selection of SROs (Sergeant described a state‑mandated 40‑hour basic SRO course plus ongoing police training such as de‑escalation and crisis intervention), recruitment and turnover, examples of restorative practices (one SRO convened parents and families to mediate a middle‑school conflict), and whether the district could report how many distinct students had SRO contact rather than event totals. Director Whitehorn and others asked for demographic breakdowns to identify any disproportionality; presenters said RPD tracks demographic factors but compiling cross‑system student‑level reports would require case‑by‑case data matching and additional work.

Several board members requested that future SRO reporting align time windows, distinguish incidents from individuals, and provide counts of distinct students who had contact with law enforcement through SROs (including whether a student had repeated contacts across years). The superintendent and staff said they will work with RPD to refine dashboards and align reporting windows for future board monitoring.

No change to the SRO contract was proposed; the item was presented as monitoring information during the second year of the two‑year agreement.