Lenox Planning Board Continues Cross-Town-Line Form A, Seeks Counsel on Frontage

Planning Board · Meeting of July 21, 2026

Lenox Planning Board continues a cross-town-line lot-split application after frontage questions and application errors surface. The board voted unanimously to defer action on a Form A submitted by surveyor Mike Parsons of Kelly Granger and Parsons Surveyors on behalf of property owners Michael Lynch and Susan Baker, who seek to carve out a one-acre lot on Hawthorne Street that sits 0.65 acres in Lenox and 0.35 acres in Stockbridge. The application listed a wrong street name and an outdated assessor's map reference — map 6, parcel 24 instead of the correct map 203, lot 79 — requiring the applicant's in-person initials before the board can act.

The deeper obstacle is that all 174 feet of road frontage lie in Stockbridge, where the R4 district requires 300 feet; Lenox requires only 150 feet but has none within its own boundary. Chair Tom Delasco said the board will consult town counsel on whether Lenox's split-town zoning bylaw paragraph allows Stockbridge frontage to satisfy Lenox's requirement. The matter is continued to the August 4 Planning Board meeting.

In the full story:

  • Background and stakes
  • The question before the board
  • Application errors requiring correction
  • Substantive content
  • The deliberation
  • Procedural steps and outcome
  • The complete report — 1,761 words

Source: the Planning Board meeting of July 21, 2026, reported from the official video recording and transcript.

Keep reading with a 14-day free trial

Subscribe to Berkshire County News to keep reading this post and get 14 days of free access to the full post archives.

Already have an account? Sign in. Ask about this instead

A subscription gets you:

  • Subscriber-only posts and full archive
  • Post comments and join the community
  • 24x7 access to local news

Subscribe to Berkshire County News

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe