Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Shared Access Easement topic

No spam. Unsubscribe anytime.

Hudson council postpones shared-access easement for 30 Acres Drive after residents raise safety, process concerns

Hudson City Council · December 16, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

After a series of public comments from longtime residents, Hudson City Council voted unanimously to postpone consideration of a proposed shared-access easement for 30 Acres Drive (consent item 25-185) to April 7, 2026, to allow time for additional review and negotiation.

Hudson City Council on Tuesday delayed action on a resolution that would authorize the city to accept beneficiary rights under a shared-access easement along 30 Acres Drive, agreeing to revisit the measure at its April 7, 2026 meeting.

The move followed lengthy public comment from several residents who said the draft easement had been circulated too late for meaningful review and that its maintenance and liability provisions appeared to impose long-term costs on property owners while granting official access rights to the city and other entities.

"Residents should not be asked to react to a moving target," said Kristen Kelling, a fourth-generation resident of 30 Acres, urging council to table the resolution until the final version with exhibits and maps is circulated and reviewed with legal counsel. Kathleen Itel and Greg Janick likewise asked for more time to consult attorneys and to see a redlined, final easement.

Council members described the concerns as serious and procedurally important. Councilor Getz moved to postpone the item to the first regular meeting in April; Councilor Weinstein seconded the motion. City Solicitor Pitchford and City Manager Thomas Sheridan told council the city would not accept the easement unless the underlying property owners had finalized and signed the document, and that the legislative language had been drafted broadly to allow the parties latitude while negotiations continued.

"We were not a party to the negotiations," Pitchford said, adding that the administration had no objection to postponement. Sheridan said the legislation was written so the city would accept the easement only after all required signatures were in place and that delay would not, by itself, bind the city to any agreement.

A roll-call vote to postpone passed 7–0. The postponement is effectively a date-certain continuance to April 7, 2026; councilors said the extra time should allow residents and the administration to reconcile outstanding issues, particularly maintenance and cost-sharing provisions.

What happens next: Council’s postponement leaves the easement unresolved. If parties rework the draft and all required signatories execute a revised easement, the city manager would be authorized to sign for the city under the terms of the pending resolution. If residents and the developer do not reach agreement, there is no legal effect from passing the resolution earlier, city staff said.

Votes at a glance: the motion to postpone 25-185 to April 7, 2026 passed 7–0.