Your area Not set — showing everywhere
How it works Support this town
Meeting report · Board of Representatives
Creating this report cost real money. Help fund coverage →

Board of Representatives — July 20, 2026

Board approves $403K safety contract despite inability to review documents

The meeting featured a single dissenting vote and a disagreement regarding the timing of the vote relative to the availability of contract documents.

Date Monday, July 20, 2026 Duration 0.5h Speakers 7 Public comments 3 Decisions 1 Lively
▶ Video

Questions about this meeting? ⁠Just ask.

Ask MeetingWatch answers from this meeting’s report, transcript, and records — with linked sources.

Summary AI-generated to surface controversy & community impact without bias — always verify against the actual meeting before relying on it.

At the July 20 Board of Representatives meeting, a significant decision was made regarding public safety on Washington Boulevard—but it was made under questionable circumstances.

The Board voted 7-1 to approve a $403,205 contract with Stantec for design services to improve pedestrian and bicycle safety in the corridor. While everyone agrees that addressing recent fatalities on Washington Blvd is an absolute priority, the process used to approve this expenditure raised serious questions about oversight.

Due to a website outage, the digital documents supporting the contract—including the RFP and the vendor's proposal—were inaccessible to the representatives during the meeting. Representative Stephen Shore was the sole dissenting vote, expressing that he was uncomfortable approving a $400,000 single-line item without the ability to review the actual paperwork.

Speed is important when lives are at stake, but it should not come at the expense of fiscal responsibility and proper due diligence. When the public expects their representatives to vet large contracts, they should have the tools necessary to do so.

Jul 20, 2026 0.5h long 7 speakers 3 public comments 1 decisions Lively
❝ Notable statements ↔ Drag to browse

“I'm just not comfortable signing off on a four hundred thousand dollar single line item to a vendor without at least looking at the paperwork.”

— Stephen Shore · Expressing opposition to the immediate vote due to the website outage preventing review of the RFP and proposal. ▶ 20:13

“Once you approve this, it's basically we're off to the races in design.”

— Luke · Explaining the immediate impact of the contract approval on the project timeline. ▶ 14:07
This meeting — choose a section

Public ⁠impact

Issues from this meeting with documented community impact.
What was discussed

A $403,205 design contract to improve safety in a high-fatality corridor.

What happened

The committee voted to approve the contract despite the lack of immediate document accessibility.

Topics ⁠discussed

Each topic expands to quotes and full context.
Speakers: Unidentified speaker, Luke, Stephen Shore, Representative Gilbride, Representative Hughes, Representative Sanford
What was discussed

The committee discussed the approval of a contract with Stantec for design services to improve safety on Washington Boulevard.

What happened

The committee voted to approve the contract despite concerns regarding document accessibility.

Controversy & ⁠dissent

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

Potentially controversial issues

01

Washington Boulevard Pedestrian and Bicycle Safety Enhancement Project Design Contract

The issue involved a large expenditure ($403,205) for safety improvements in a corridor with recent fatalities, but the vote was complicated by technical failures that prevented members from reviewing the contract documents.
Board position: The board approved the contract to avoid delays in addressing safety concerns.
Internal dissent
Representative Shore voted against the contract because a website outage prevented him from reviewing the RFP and vendor proposal prior to the vote.
medium concern

Split votes

Approval of contract with Stantec for Washington Boulevard pedestrian and bicycle safety enhancement project design (RFP 2025.0147).
7-1-0

Public ⁠comment

What residents said — verbatim, with timestamps.
2
Speakers
3
Comments
2
Addressed
1
Partial
0
Not addressed
Representative Kilbride
▶ 16:34
Addressed
The speaker requested clarification regarding the funding source for the project. They asked whether the costs were coming from the capital budget or if it was part of a state-funded portion. Key concern
Clarification on whether project funding is from the city's capital budget or state funds.
Board response
a speaker (likely a city official/department head) clarified that the project is 100% city-funded and was already approved in the capital budget.
The board official provided a direct answer regarding the source of the funding.
Representative Shore
▶ 05:36
Addressed
The speaker inquired about the specific timeline for the implementation and start of construction for the corridor project. They expressed strong support for the project due to safety concerns and recent fatalities in the area. Key concern
Request for a timeline on when construction and implementation would actually begin.
Board response
a speaker explained that while some improvements could start as early as 2027, this specific project is looking at a 2029 timeframe, noting a 'rolling wave' of improvements.
The board official provided a projected timeline and explained the phased approach.
Representative Shore
▶ 21:13
Partial
The speaker expressed discomfort with voting on a large contract without having reviewed the full supporting documentation, such as the RFP and vendor proposal. They noted that while an email was sent, the links provided were broken due to a website outage. Key concern
Inability to review essential contract documents prior to voting due to technical issues and late distribution.
Board response
a speaker (Chair) acknowledged the issue, explained the distribution process, and offered to forward the documents. Despite a motion to postpone, the board ultimately proceeded to a vote.
The Chair acknowledged the difficulty and the broken links, but the board did not grant the request to postpone the vote, choosing instead to proceed with the approval.

Decisions ⁠logged

Every recorded vote, with timestamps and dissents.
Approval of contract with Stantec for Washington Boulevard pedestrian and bicycle safety enhancement project design (RFP 2025.0147).
The contract is for $403,205 for design services. Representative Shore was the sole dissenting vote.
7-1-0

Share ⁠this report

Drafts ready to post — click a block to copy, or use Share to post it.

X / Twitter — by angle

Decision made without full access to supporting documentation
On July 20, the Board approved a $403,205 contract for Washington Blvd safety designs. However, a website outage meant representatives couldn't actually access the RFP or proposal before voting. Is speed more important than... https://meetingwatch.org/ct/stamford/board-of-representatives/2026-07-20/ #MeetingWatch #StamfordCT
326/280 chars
Prioritizing speed over procedural review
The Washington Blvd safety project is urgent due to recent fatalities, but the Board of Representatives voted 7-1 on a $403,205 contract despite technical issues preventing a full review of the paperwork. Accountability... https://meetingwatch.org/ct/stamford/board-of-representatives/2026-07-20/ #MeetingWatch #StamfordCT
322/280 chars
Internal dissent and the importance of oversight
Rep. Shore was the lone dissenter at the July 20 meeting, refusing to sign off on a $403,205 contract because the digital documents weren't accessible due to a website outage. A vote without the facts is a vote without oversight. https://meetingwatch.org/ct/stamford/board-of-representatives/2026-07-20/ #MeetingWatch #StamfordCT
329/280 chars

X thread

1
The Board of Representatives just approved $403,205 for Washington Blvd safety improvements, but there's a catch: they did it without being able to read the contract. 🧵 #MeetingWatch #StamfordCT
194/280
2
During the July 20 meeting, a website outage prevented members from accessing the RFP and vendor proposal for the Stantec design contract. Despite this, the Board moved to a vote.
179/280
3
Rep. Stephen Shore cast the only dissenting vote, stating he was 'not comfortable' signing off on a $400k+ single line item without reviewing the paperwork first. The Board cited the urgency of recent fatalities to justify the vote.
232/280
4
While safety on Washington Blvd is a critical priority, voting on massive expenditures without accessible documentation sets a concerning precedent for fiscal oversight. We need safety AND transparency. https://meetingwatch.org/ct/stamford/board-of-representatives/2026-07-20/
226/280

Facebook — long form

At the July 20 Board of Representatives meeting, a significant decision was made regarding public safety on Washington Boulevard—but it was made under questionable circumstances.

The Board voted 7-1 to approve a $403,205 contract with Stantec for design services to improve pedestrian and bicycle safety in the corridor. While everyone agrees that addressing recent fatalities on Washington Blvd is an absolute priority, the process used to approve this expenditure raised serious questions about oversight.

Due to a website outage, the digital documents supporting the contract—including the RFP and the vendor's proposal—were inaccessible to the representatives during the meeting. Representative Stephen Shore was the sole dissenting vote, expressing that he was uncomfortable approving a $400,000 single-line item without the ability to review the actual paperwork.

Speed is important when lives are at stake, but it should not come at the expense of fiscal responsibility and proper due diligence. When the public expects their representatives to vet large contracts, they should have the tools necessary to do so. https://meetingwatch.org/ct/stamford/board-of-representatives/2026-07-20/ #MeetingWatch #StamfordCT

Action ⁠items

Who owes what, by when.
Forward the email containing the four project documents to Representative Shore.
Assigned: a speaker · Due: Immediate

Member ⁠positions

0 issues · 0 explicit · 0 inferred

Positions marked ~ are inferred from context and may not reflect the member's explicitly stated position. UNCLEAR means the vote was split but the record did not name how this member voted — it is not a “yes.”

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 xai.grok-4.3, gemma-4-26b, grok-4.20-0309-reasoning, grok-4.20-0309-non-reasoning · analyzed 2026-07-21.