Your area Not set — showing everywhere
Meeting report · Town Council
Creating this report cost real money. Help fund coverage →

Town Council — June 1, 2026

The meeting was characterized by technical inquiries from the public and a collaborative approach by the board to address concerns.

Date Monday, June 1, 2026 Duration 0.8h Speakers 9 Public comments 4 Decisions 1 Routine
▶ Video 📄 Minutes
Town Council Meeting title slide, Londonderry NH Video still
Town Council Meeting title slide, Londonderry NH Frame from meeting video ▶ 02:43

Public ⁠impact

Issues from this meeting with documented community impact.
01

FY2028 Budget Guidance

Capped at a 1% increase over the default budget, including all passed warrant articles. Affected: All town taxpayers
See more
What was discussed

The council debated how to frame the FY2028 budget to prevent significant spikes in the tax rate, specifically discussing the inclusion of passed warrant articles in the total calculation.

What happened

The council reached a consensus to direct the Town Manager to propose a budget that equals the default budget plus 1%, which must encompass all passed warrant articles.

tax increase
02

Traffic Enforcement and Safety Infrastructure

Purchase and installation of approximately 10 permanent traffic counting devices. Affected: All motorists and residents in high-traffic corridors
See more
What was discussed

The Police Department proposed moving to a proactive enforcement model using 'Black Cat 2' devices and solar-powered signs to collect volume and speed data.

What happened

The council expressed support for the strategy and requested the Town Manager return in July to seek authorization for funding from the transportation capital reserve fund.

What's next

Town Manager to present request for funds on July 6th.

safety change

Decisions ⁠logged

Every recorded vote, with timestamps and dissents.
Direction for FY2028 Proposed Budget
The proposed budget should be the default budget plus 1%, and this figure must encompass all passed warrant articles to prevent tax rate spikes.
Consensus reached

Topics ⁠discussed

Click a topic to expand quotes and full context.
▶ 00:00 Traffic Safety and Data-Driven Enforcement Strategy

The Police Department presented a comprehensive strategy to improve roadway safety using real-time traffic data, automated counting devices, and targeted enforcement.

Speakers: Unidentified speaker
See more
What was discussed

Officials discussed transitioning from reactive, complaint-based enforcement to a proactive, data-driven model. Key points included using 'Black Cat 2' devices and solar-powered speed signs to collect speed, volume, and vehicle type data, which will be made available to the public via a GIS web map. There was discussion regarding the reliability of current equipment and the necessity of using objective data (crash history, speed, and traffic volume) rather than just citizen complaints.

What happened

The council expressed support for the strategy, noting the importance of having hard data to advocate for state-level improvements on major routes.

What's next

The Town Manager will return to the council on July 6th to request authorization to expend funds from the transportation capital reserve fund for the purchase and installation of approximately 10 permanent traffic counting devices.

▶ 42:38 FY2028 Budget Guidance

The Council discussed the framework for providing guidance to the Town Manager regarding the proposed FY2028 budget.

Speakers: Unidentified speaker
See more
What was discussed

The discussion centered on how to set the proposed budget to avoid significant tax rate spikes. The council debated different percentage increases above the 'default budget' and whether to include passed warrant articles in that calculation.

What happened

The council reached a consensus to provide direction for a proposed budget that equals the default budget plus 1%, with all passed warrant articles also needing to fit within that total number.

Controversy & ⁠dissent

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

Potentially controversial issues

01

Traffic Safety and Data-Driven Enforcement Strategy

The shift from complaint-based to proactive, data-driven enforcement raises questions about the intent of increased police presence and the validity of the metrics used to target specific roads.
Board position: The board supports a proactive model using automated counting devices and real-time data to identify high-risk areas.
medium concern
02

Developer Accountability and Infrastructure Funding

Residents and council members are debating whether the town should rely more on impact fees and extraction fees from developers to cover the costs of traffic and infrastructure impacts.
Board position: The board is exploring stronger verbiage in development agreements to ensure developers pay their fair share.
medium concern

Community vs. board tension

Action ⁠items

Who owes what, by when.
Present request for authorization to expend funds from the transportation capital reserve fund for approximately 10 permanent traffic counting devices.
Assigned: Town Manager · Due: 2026-07-06
Integrate traffic data and qualitative crash data into a GIS web map for public viewing.
Assigned: Mike (Staff)

Notable ⁠statements

This isn't a revenue generating program for anybody. We're looking to make this community safer for everybody on the roadways. — Unidentified speaker · Addressing public concerns regarding the motivation behind increased traffic enforcement. ▶ 08:54
I do think it's important that... we really should be looking at impact fees, extraction fees, and stronger verbiage in our development agreements to make sure that developers pay their fair share. — Unidentified speaker · Discussing the long-term funding and responsibility for traffic impacts caused by new developments. ▶ 33:01

Public ⁠comment

What residents said — verbatim, with timestamps.
4
Total speakers
4
Addressed
0
Partial
0
Not addressed
Unidentified speaker
▶ 00:48
Addressed
The speaker asks for clarification on the methodology used to determine traffic safety priority areas. They specifically inquire if the metrics are based primarily on accident reports. Key concern
Understanding the methodology for determining traffic priority areas.
Board response
The board (represented by a speaker and a speaker) clarified that while accident reports are a core component, the methodology also includes device data, citizen complaints, crash data with injuries/fatalities, and roadway characteristics.
The board provided a detailed explanation of the multi-factor data approach used to identify high-risk areas.
Unidentified speaker
▶ 01:33
Addressed
The speaker suggests that reduced speed limits might be appropriate for heavily settled residential neighborhoods. They advocate for using data collection and corridor studies to inform these changes. Key concern
Request for reduced speed limits in residential neighborhoods based on data.
Board response
The board responded by explaining their strategy of using speed signs and data collection devices to identify specific areas for enforcement and potential engineering solutions.
The board addressed the suggestion by outlining their data-driven approach to identifying where speed limits or enforcement are most needed.
Unidentified speaker
▶ 16:13
Addressed
The speaker asks for the specific location of the data collection device mentioned in the presentation. They inquire if it is located near Murray's Junkyard. Key concern
Identification of the device location.
Board response
The speaker (a speaker) confirmed the general vicinity.
The speaker confirmed the location of the device.
Unidentified speaker
▶ 18:09
Addressed
The speaker questions the validity of the data due to varying sample sizes and time periods used for different roads. They also suggest that the town should prioritize roads with the highest accident rates and look into impact fees for developers. Key concern
Data consistency, prioritization of roads, and developer accountability (impact fees).
Board response
The board explained that different sample sizes were used due to the temporary nature of the devices and that they have not assigned a specific 'rank' to roads but are focusing on the most critical areas. They also addressed the impact fees by explaining how they are currently working with developers to fund studies.
The board answered the technical concerns regarding data and addressed the policy suggestion regarding developers and road prioritization.

Accountability ⁠flags

Documented procedural gaps. Each item links to its source.

Transcript vs. official minutes

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 Londonderry.

Report composed by gemma-4-26b, grok-4-fast, grok-4.20-0309-reasoning · analyzed 2026-06-11.