Westbrook Currents TL;DW! meeting summary · westbrookcurrents.com/tldw/2026-09-01-planning-board
‹ TL;DW! Planning Board

Westbrook Planning Board — September 1, 2026

Westbrook High School (Room 114), 125 Stroudwater St. (Hybrid via Zoom) · 7:00 PM

Attendance: Present: Chair Larry McWilliams, Jason Frazier, Kevin Price, Oriana Farnham (alternate), Lucas Schrage (alternate). Absent: Vice Chair John Turcotte, Karen Axelson, Nancy Litrocapes, Robin Tannenbaum.

Watch the full video on Vimeo ↗ Meeting packet ↗

Each item shows a timestamp like 57:13 (minutes:seconds) or 1:52:13 (hours:minutes:seconds). Tap it to jump to that moment in the video.

Quick read: Planning Board weighs staff plan to drop data centers from Rock Row's zoning. The board also approved a three-lot subdivision on Longfellow Street and looked at a new "social engagement" design ordinance.

Five of nine seated board members were present (McWilliams, Frazier, Price, Farnham, Schrage); Turcotte, Axelson, Litrocapes, and Tannenbaum were absent.

New Business

1:58
26-000636 — Subdivision, Final Vote — 108 Longfellow Street, Longfellow 108 LLC Dustin Roma (DM Roma Consulting Engineers) returned with the final plan for the three-lot subdivision workshopped August 4.

Dustin Roma (DM Roma Consulting Engineers) returned with the final plan for the three-lot subdivision workshopped August 4. The plan adds a confirmed sight-distance measurement at the proposed Lot 1 driveway (shown adequate in both directions).

It also adds conditions. These restrict Lots 2 and 3 to shared access over the existing easement (a right to use part of someone else's land). They rule out new curb cuts onto Longfellow Street.

City Planner Rebecca Spitella flagged one correction to the conditions of approval: the application date needed to read August 6, 2026. She also confirmed the open-space fee is due before the final plans can be released for recording.

Member Jason Frazier questioned why a small land subdivision like this one is subject to an open-space fee-in-lieu at all, given the resulting lots have ample private yard space. (A fee-in-lieu is a fee paid instead of providing the open space.) Staff explained the fee formula (a percentage of average lot size times an assessor-set cost per developable acre).

Staff pointed to the workshop item later on the agenda that would amend the ordinance (a city law). That item covers the fuller policy rationale and planned revisions. No public comment.

✓ Approved 5–0 by roll call, moved by Kevin Price (with the amended application date), seconded by Oriana Farnham. The board separately voted 5–0 to move into workshop session for the remaining agenda items, moved by Oriana Farnham, seconded by Lucas Schrage.

Point / Counterpoint

“It just seems in this case ... why are we charging fees for these little subdivisions that people have freestanding ... single-family homes with plenty of outdoor space ... Multifamily, that makes sense ... but for this I don't know why we're doing that, but I guess that's just what we do.”— Jason Frazier, Board Member · 11:05

Workshop

13:47
25-001050 — Land Use Ordinance Amendment — Subdivision Review Additional Requirements (§335-13.3.H) City Planner Rebecca Spitella reintroduced this “social engagement” ordinance amendment.

City Planner Rebecca Spitella reintroduced this “social engagement” ordinance amendment. An ordinance amendment is a change to a city law. It was workshopped last fall. A public hearing is planned for October.

The amendment began as a City Council referral (a matter sent to a board or committee to study). It would fold the subdivision ordinance's existing, partly duplicative “appearance assessment” findings into clearer community site-design standards.

The standards are modeled on the Village Review Overlay district's. They cover building orientation toward public streets, parking located behind/beside structures where feasible, native-species landscaping, and lower-scale pedestrian lighting. The lighting would copy the spacing of public street lights, though not necessarily their fixture style.

It also rewrites the open-space standard. When amenities are provided on site, the new standard is 300 sq. ft. per studio/one-bedroom unit and 500 sq. ft. per two-plus-bedroom unit. Before, it was a flat 300 sq. ft. no matter the unit size.

When conservation is used instead, a higher land-reservation requirement applies. This is to discourage reserving land that was unbuildable anyway. Projects that can do neither would pay a recalculated fee-in-lieu, based on an assessor-set cost per developable acre.

Several members pressed for clarity.

  • Kevin Price asked how the amendment applies to projects already in process. That prompted a board discussion, led by Chair McWilliams. The discussion was about whether site plan extensions (more time on an approved site plan) should have a hard cap rather than the current informal practice.
  • Jason Frazier argued the lighting standard was too rigid. He said it should state safety/anti-glare goals rather than dictate fixture spacing. He also asked for clearer language on what counts as a “corner” lot.
  • Oriana Farnham agreed that clearer lighting language would help the board judge designs consistently. She backed keeping native plantings mandatory (“shall”), leaving the board's waiver provision as the route for any exception.
  • Lucas Schrage agreed, citing the city's stewardship of the Presumpscot River.

Staff welcomed the lighting feedback and will revise that language. Staff will also compare a new state dark-sky law with the city's own ordinance. The law takes effect October 1, for publicly funded projects. No public comment.

✓ No vote — workshop item; a public hearing is targeted for the October 2026 meeting.

Point / Counterpoint

“I think we can and should regulate that as a city ... it doesn't just affect the people who live on that property ... I support ‘shall use native plants’ and let them, if they feel really passionate, use the waiver provision.”— Oriana Farnham, Board Member (on native-species landscaping) · 44:28

49:53
26-000777 — Land Use Ordinance Amendment — Data Centers Ordinance City Planner Rebecca Spitella gave an extensive briefing prompted by a City Council referral.

City Planner Rebecca Spitella gave an extensive briefing prompted by a City Council referral. The briefing followed the state legislature's passage of Legislative Document 307. That bill would have created a Maine Data Center Coordination Council and an 18-month moratorium (a temporary ban). Governor Mills vetoed it.

The briefing also followed the Westbrook City Council's own precautionary June 1, 2026 180-day local moratorium, passed even though no data center project was then pending. Today, “data center” is a defined use with no standards beyond ordinary site plan review. It is permitted only within the Rock Row contract zone (a special zoning deal for one property).

Spitella covered data center types. They range from small on-site “enterprise” server rooms to large “hyperscale” centers driven by artificial intelligence. None of the latter exist in Maine. Total New England data center capacity is smaller than Northern Virginia's alone.

She also covered four impact areas.

  • Water use/discharge: evaporative cooling is most common and most water-intensive. Closed-loop “dry” cooling uses far less water, but more energy. Immersion cooling raises unresolved questions about per- and polyfluoroalkyl substances. These are long-lasting man-made chemicals.
  • Power demand: it could stress or support the grid, depending on existing capacity. The state's Public Utilities Commission is doing its own ongoing regulatory review.
  • Noise: continuous ambient equipment noise. Locally, it is regulated only by a police-department reasonableness standard.
  • Economic development: a tax base that does not lose value over time, but relatively few permanent jobs. There is also a public-trust risk around community benefit agreements.

Staff recommendation: remove data centers as a permitted use from the Rock Row contract zone. This would effectively prohibit new standalone development citywide for now.

Staff gave these reasons. Industry change is moving faster than regulation. Also, Westbrook's dense population pattern makes it more likely to stress than support the grid.

Staff would continue to allow small on-site “enterprise” information technology rooms as an accessory use (a secondary use on the same property).

✓ No formal vote. This was an informational/advisory workshop discussion to shape a forthcoming ordinance amendment. Views were mixed. Oriana Farnham fully supported the staff recommendation. Chair Larry McWilliams and Jason Frazier floated keeping the use with limits (such as a wattage cap, closed-loop cooling or self-generated power). Staff will reach out to Rock Row's owners about the board's direction.

Point / Counterpoint

“If it doesn't impact the community, it doesn't do any harm, then there's no harm in having one, right?”— Jason Frazier, Board Member (data scientist by profession) · 1:16:43

“I don't think Westbrook should be the test case for that.”— Oriana Farnham, Board Member · 1:26:40

“We will be at public hearings until midnight every single time we have a planning board meeting if somebody brings a data center to town ... community benefits agreements are consolation prizes. They are not benefits to the community.”— Oriana Farnham, Board Member · 1:28:46

Not a replacement for watching — and not an official record. This summary highlights the meeting's key discussions and decisions; it's not a substitute for watching the full meeting, and summarization necessarily condenses and selects. It's also an unofficial product of Westbrook Currents, an independent site — not the City of Westbrook — and may contain mistakes. For complete context or the official record, watch the full video or see the City's approved minutes.

How this was made: Produced from the meeting video (linked above, hosted on the City's Vimeo showcase). The audio was transcribed with AI-assisted speech-to-text and speaker identification. This process cross-checked names against the official Planning Board roster, attributed speakers from context (introductions, roll-call order, direct address by the Chair) rather than the raw diarization labels alone, and drafted this summary and the quoted excerpts. Quotes are lightly cleaned of filler words/false starts but not reworded. Reviewed by Gerald Doyon. A separate AI accuracy check then compared this summary against the transcript and agenda packet. Errors it found were corrected, and Gerald Doyon verified against the meeting video the points only the video could settle.