MeetingWatch
Your area Not set — showing everywhere
Meeting report · Board of Representatives
Creating this report cost real money. Help fund coverage →

Board of Representatives — May 28, 2026

The meeting was characterized by persistent questioning from representatives and frustration regarding a multi-year lack of public access to vital safety data.

Date Thursday, May 28, 2026 Duration 0.8h Speakers 9 Public comments 5 Mildly contentious
▶ Video

Public ⁠impact

Issues from this meeting with documented community impact.
01

Public Food Safety Transparency

Inability to verify restaurant hygiene standards in real-time affects public health awareness and consumer choice. Affected: All Stamford residents and dining consumers
safety change

Controversy & ⁠dissent

Where the board, the community, or the agenda diverged.

Potentially controversial issues

01

Lack of Public Access to Restaurant Inspection Data

Residents cannot easily verify the safety of local food establishments due to software incompatibility and regulatory shifts, creating a transparency gap regarding public health.
Board position: The administration cited technical and regulatory barriers (FDA code/vendor issues), while representatives pushed for immediate interim transparency measures.
Internal dissent
While no formal split vote occurred on the topic, there was significant tension between the administration's explanation of 'technical limitations' and the representatives' demand for better constituent service and transparency.
high concern

Community vs. board tension

Public ⁠comment

What residents said — verbatim, with timestamps.
5
Total speakers
1
Addressed
4
Partial
0
Not addressed
David Blank
▶ 10:44
Addressed
Representative Blank questioned whether the issue with restaurant inspections was related to the actual inspections or just the record-keeping process. He sought clarification on whether the public currently has to contact the department directly due to software incompatibility. Key concern
Clarification on whether inspection services are still being performed despite the lack of public digital access.
Board response
The Board (via Director Bishop Pullen and Supervisor Early) explained that inspections are being performed and records exist, but a software incompatibility with the current vendor (Viewpoint Cloud) prevents automatic public posting.
The administration provided a detailed technical explanation regarding the software transition and confirmed that the work is being done, just not easily accessible online.
Kendaria Wilson
▶ 16:53
Partial
Representative Wilson expressed concern over the long duration (since 2020) that inspection results have been unavailable to the public. She also inquired about the current process for requesting information and raised concerns regarding the cleanliness and oversight of food trucks during the summer months. Key concern
The lack of transparency since 2020 and the potential safety risks associated with insufficient food truck inspections.
Board response
The administration explained the Freedom of Information process and the timeline for the new platform (expected mid-summer). Regarding food trucks, they confirmed they are inspected but noted that staffing and certification requirements create challenges.
The board addressed the procedural questions and the timeline for the software fix, but the concern regarding the long-term delay (-6) and the specific safety risks of food trucks was acknowledged more as a shared concern rather than a solved issue.
Terry Adams
▶ 21:00
Partial
Representative Adams asked if there is a physical rating certificate (like A, B, or C) posted at restaurants. He suggested that the city should look into implementing a rating system to make it easier for consumers to choose safe dining options. Key concern
The absence of a visible, easy-to-understand rating system for consumers.
Board response
The administration explained that the new FDA food code uses a pass-fail model rather than a letter rating system, making a traditional rating difficult to implement under current state guidelines.
The board explained why the current system doesn't allow for ratings, but the speaker's suggestion to explore a new way to implement such a system was noted as something for the committee to look into further.
Michael Field
▶ 24:53
Partial
Representative Field argued that the lack of a visible letter rating system (like in Los Angeles) makes the process non-constituent friendly. He suggested that the current method of looking up reports online is not practical for most people and asked if a simpler system could be adopted. Key concern
The lack of transparency and ease of use for the general public regarding restaurant safety.
Board response
The Director stated she lacks the authority to decide on a rating system as it is governed by the state's FDA food code, though the Chair suggested the committee might research overlays or state-level changes.
The board explained the legal/regulatory barriers preventing a rating system, but the speaker's request for a more transparent/engaging method was referred to future committee research.
Representative Stone
▶ 27:59
Partial
Representative Stone proposed an interim solution where restaurants with 'priority' violations are manually flagged and posted on the website as PDFs. He argued that while a full system integration is pending, the public should at least be alerted to high-risk violations. Key concern
Providing timely, high-priority safety information to the public as an interim measure.
Board response
The administration noted that current systems require manual work to flag these items and that they are working toward an automated solution to minimize the need for manual manpower.
The administration acknowledged the feasibility of the idea but explained the current manpower and software limitations preventing immediate implementation, though they agreed to 'think about it.'
Support coverage

Creating this report cost ⁠real money.

MeetingWatch attended, transcribed, and analyzed this meeting on its own dime. If this work is valuable to you, chip in to keep covering Stamford.

Report composed by grok-4.3, gemma-4-26b, grok-4.20-0309-reasoning · analyzed 2026-05-30.