Starbucks Proposal Faces Traffic Management Scrutiny at Bridgewater Zoning Board Meeting

The Bridgewater Zoning Board meeting on March 11, 2025, focused on the ongoing discussions regarding the proposed Starbucks development on Route 22, delving into site plan modifications and traffic management strategies. Key elements of the meeting included changes to the site’s ingress and egress, traffic flow impacts, and the effectiveness of signage and enforcement to mitigate potential traffic disruptions.

0:00The Starbucks application, in its fifth hearing, took center stage as the applicant’s representative detailed significant modifications made to the site plans to address traffic flow concerns on Route 22. A notable change was the removal of the Route 22 ingress driveway, a previous point of contention despite its approval by the Department of Transportation. Instead, the site plan now proposes an entrance on Morgan Lane, allowing right-in access only, with no exit from this point. This adjustment aims to improve traffic management by directing incoming traffic through Morgan Lane, minimizing congestion on Route 22.

Modifications also included narrowing the drive-thru lane from two to one, accommodating a stacking capacity of 15 to 16 cars, with additional internal stacking available for the same number. The plan reduces the number of outdoor seating areas and redistributes parking spaces closer to the building. These adjustments slightly reduced overall lot coverage, moved the building back an additional ten feet from Route 22, and maintained unchanged stormwater management systems.

Board members raised concerns about ensuring effective traffic direction, particularly regarding the potential for illegal right turns from the site. To address this, the plan proposes raising curb heights to deter such maneuvers, though complete prevention may not be feasible. Additionally, discussions included the potential incorporation of local statutes into signage to reinforce compliance and deter violations. Suggestions for a temporary police presence to ticket offenders during the initial opening weeks were received favorably.

Further testimony from site planners and engineers shed light on the implications of these revised plans for traffic and site design. The board scrutinized the adequacy of signage, questioning whether the proposed traffic management strategies would be sufficient to prevent confusion and ensure smooth flow, especially for first-time visitors.

30:08Her findings suggested that the proposed development would not degrade existing traffic conditions, maintaining typical levels of service for highway corridors.

47:06The board continued to express concerns about potential traffic increases stemming from the nearby restaurant and hotel, with particular attention to the weaving movements at driveways. They discussed the impact of closing a driveway on the former Goddard School site, which the NJDOT had granted permission to remove, though further analyses were requested by the department.

1:46:21In addition to the Starbucks application, the meeting touched on proposed developments by the Jewish Community Center (JCC) and a townhouse project. Peter St, an applicant planner, presented the case for use variances sought by the JCC. The discussion focused on the public benefits of the JCC’s services and the implications of its expansion, with members questioning the adequacy of traffic data presented in prior testimonies. The board debated the scope of an Open Public Records Act request, arguing for a broader area of study to fully understand traffic patterns.

2:49:30The townhouse project, with a proposed density of 5.03 units per acre, also sparked debate. Concerns were raised about environmental impacts, including tree removal, and the demand for age-restricted housing. Questions about the relevance of historical data on population changes were discussed, highlighting the need for current data to assess the demand for senior housing. The board agreed to reconvene for further discussions in subsequent meetings, recognizing the need for more detailed data and clarity in future presentations.

Note: This meeting summary was generated by AI, which can occasionally misspell names, misattribute actions, and state inaccuracies. This summary is intended to be a starting point and you should review the meeting record linked above before acting on anything you read. If we got something wrong, let us know. We’re working every day to improve our process in pursuit of universal local government transparency.

Receive debriefs about local meetings in your inbox weekly:

is discussed during:
in these locations: