Beachwood committee reviews SiteStream speed‑camera proposal after study finds high speeds on I‑271 and school corridors

The Beachwood City Council committee on public safety on Monday heard a presentation of a city speed study and a vendor proposal to deploy photo‑enforcement cameras and handheld speed units after data showed substantial speeding on I‑271, Shaker Boulevard and near several school zones.

The study presenter said the two‑day sample recorded thousands of vehicles traveling 76–100 mph and that 246 vehicles exceeded 100 mph during that period. Sales Director Hassan Davaja of SiteStream, the vendor that supplied the study and would operate a civil-photo enforcement program, described the technical workflow: radar triggers a capture, the system saves a rear‑license‑plate image and a ten‑second evidence clip, former law‑enforcement reviewers vet potential violations, and the city — which owns the data — makes final enforcement decisions.

Council members pressed the vendor and staff on data accuracy, privacy and legal access. A council member asked whether cameras record continuously or only when a threshold is exceeded; SiteStream said the system is ‘‘live’’ but stores clips only when the city’s threshold is met and that the vendor does not retain, monetize or share the data. The company also said captured evidence would be stored on a CJIS‑compliant server and that retention rules are set by the city; the vendor estimated that data tied to violations could be retained up to one year under state practice.

Council members also questioned calibration and independence: SiteStream said sensing equipment used in the study was a Custom Signals sensor commonly used by law enforcement and was calibrated and tested. Staff emphasized that the city selected locations for monitoring and that officers performed installations for independence.

The committee discussed program design and safeguards. Staff recommended focusing initial deployment on three priorities: 1) high‑speed stretches of I‑271 during times officers cannot safely patrol, 2) the Chagrin/Richmond intersection (a high‑crash site), and 3) school zones. SiteStream told the committee the program is intended to be civil enforcement (not criminal), with proposed fine ranges presented in the study materials: for general speeding, examples given were $155 for 10–19 mph over the limit, $200 for 20–29 mph and $300 for 30+ mph; school‑zone thresholds and fines were described separately.

Council members raised concerns about revenue and state offsets: staff warned that increases in locally generated fines can interact with state offsets to local government funding and asked whether fines would be earmarked for law enforcement, general fund needs, or safety programs. SiteStream said the program would run at no start‑up cost to the city, with an example revenue split of roughly 65% to the city and 35% to the vendor; the company also proposed returning a small portion of proceeds to driver‑education efforts.

Legal and public‑records questions were prominent. One presenter cited a recent Public Records Act provision that treats automated license‑plate recognition data held in a law‑enforcement database differently from other public records; the vendor and council discussed subpoena procedures and the city’s authority over what is disclosed. The vendor repeatedly emphasized that any agency requests would follow legal process and that the city, not the vendor, would control disclosure.

On contract terms, SiteStream said the proposed agreement is five years with termination clauses (examples given of 40–90 day notices and settlement language). Council members asked whether a pilot or phased deployment was possible; the vendor said the contract permits cancellations and that deployments can be scaled or removed after evaluation. Staff proposed evaluating outcomes after about six months of live enforcement and monitoring crash counts as the principal success metric; SiteStream suggested a target of about a 20–25% reduction in speeds based on other deployments, while staff emphasized crash and fatality reductions as the primary measure.

Communications staff recommended a robust outreach plan including mailers, a public information session prior to voting, a 30‑day public awareness campaign and a 30‑day warning period when cameras are installed but citations are not issued. The committee asked staff to provide a four‑year crash dataset to accompany contract terms before a council vote.

Next steps: committee members asked staff to place the item on the May 18 council agenda and to circulate the proposed contract and specific early‑exit terms to council prior to that meeting. No formal vote was taken at the committee session. The committee adjourned after agreeing to return with the requested materials and a communications plan.