Town of Lancaster — Planning Board
A 29-home subdivision was classified on October 21 at a meeting whose posted agenda never mentioned it. A neighbour said she was told at 2 p.m. that day. The board did not dispute her account — it explained that the applicant had met the filing deadline, and that it felt obliged to hear him.
The Town of Lancaster's posted agenda for October 21, 2026 is a single page. It is dated 10/15/26. Under the 7:00 p.m. pledge it lists four things: review the October 7 minutes, review the communications list, conduct a SEQR review of Project #0812 — Culver's Restaurant at 4937 William Street — and take public input. There is no fifth item.[2]
The board nevertheless took up, discussed and voted on a second project: the subdivision classification of Cozy Meadows, a proposed 29-home development at 5759 Broadway. A resident came to the microphone to say so.[1]
“My name is Lindsay Gruss. I live at 40 Parkdale Drive.”[*] Her account was precise and dated. “On Monday, October 19th, I checked the planning board agenda posted on the town board's website and noted only one agenda item relating to Culver's Restaurant. On Tuesday, October 20th, my next-door neighbor checked the website and still only one agenda item existed, again relating to Culver's Restaurant.” Then: “You can imagine my surprise and concern when I was notified today at 2 p.m. that a new item was placed on the planning board's agenda for this evening.”[1]
This publication can corroborate the documentary half of her account. The agenda in our archive — retrieved from the town's own document centre — carries only the Culver's item, and the date on its face is October 15, six days before the meeting. No amended agenda was posted to the document centre for October 21.[2]
She also named the timing problem beyond the notice itself: “It is ironic and unfortunate that this last-minute addition would coincide with the athletic events taking place this week… most likely the turnout here would be small.” Her conclusion was carefully framed as appearance rather than accusation: “It creates the appearance that the public is being denied a reasonable opportunity to become aware of the matter, to review it, and to participate in the discussion. Whether intentional or not, this kind of last-minute action can undermine public trust and gives the perception of a lack of transparency.”[1]
PLANNING BOARD AGENDA — Carlo DiRienzo, Chair — October 21, 2026, Town Hall
Date on the face of the document: 10/15/26. Cozy Meadows appears nowhere on it.[2]
The board's answer was not a denial. The member chairing in the chair's absence took the question directly: “I am the stand-in chair. I received some photos of what the actual chair received in his packet… So Cindy and I were exchanging a few emails today, and it was decided that because it was submitted at the right time — even though you guys may not have been given enough notice — we were kind of obligated to keep it on the agenda because it met the deadline.”[1]
And then, plainly: “So we're not trying to hide anything. We're just doing what we thought we had to do because they met their deadline… We can't erase how it happened, but we're being honest is how it happened and why it's on the agenda.”[1]
The board secretary described a distribution failure rather than a late filing: a letter had gone out stating the matter was scheduled for that night which she had not received, the applicant had submitted the three sets of plans the code directs him to submit, and those had gone “to the rightful places.” The chair, she indicated, had his packet by Monday. The board members in the room did not.[1]
That distinction matters, and it is the one the board itself drew: the applicant appears to have done what the code asks. The gap sits between a filing that met a deadline and a public agenda that never reflected it — and between the chair's packet and the rest of the board's. One member said aloud, before the presentation began, “you have to forgive us, we didn't — I don't think a lot of the members saw this before we got here today.”[1]
Cozy Meadows is not new to the Town of Lancaster. The same consultant presented it to the Town Board on September 8, 2026 — six weeks before this meeting — using nearly identical language. Two figures changed in between.[3]
| Sept 8 Town Board | Oct 21 Planning Board | |
| Homes | 31 | 29 |
| Density (du/acre) | 2.2 | 2.1 |
| Acreage | ~14 | ~14 |
| Value per unit | $520,000 | $520,000 |
| Max permitted density | 3 | 3 |
The two unit counts are arithmetically consistent with the stated densities on ~14 acres. The project appears to have genuinely shrunk by two homes; neither presentation mentioned the change.
The board spent several minutes explaining the vote to the room, and the explanation is worth preserving because it is the honest answer to “why was this rushed?” The classification decides which of two review tracks a subdivision follows. It is a threshold test, not an approval.[1][4]
In the board's own words: “There's a minor subdivision and there's a major subdivision. This would be classified as a major subdivision because of the number of units… It doesn't mean that we don't have to go through SEQR. It doesn't mean that we don't have to go look at the plans anymore. It doesn't mean that this will be your only chance to speak for or against the project.”[1]
The threshold itself was stated by the town's professional staff: “It really is a ministerial step for something like this. It's the threshold is essentially less than five or more… for the code.” A major classification is the more demanding path — more review, not less. As the engineering consultant put it, a “more intense review process… for a major, or less intense for the minor.”[1]
So the vote the public was given hours' notice of was the vote that subjected the project to the heavier scrutiny, and the board said repeatedly that further public hearings would follow. That is a real answer, and the brief records it as such. It does not dispose of the notice question, because the public's opportunity to be heard on a classification is not restored by later hearings on a different question — and because a resident who learns of an item at 2 p.m. cannot know in advance that it is procedural.
One member was careful about this on the record: “So, just don't want to give the appearance that decisions have been made before the vote is made.” Staff added the practical remedy, twice: residents can register on the town website for automatic email notification of Planning Board, Town Board and Zoning Board agendas, which staff called “probably for residents the best avenue.”[1]
The classification carried unanimously among the six members present. Post-classification, staff noted, “the applicant has six months to submit their either sketch plan or preliminary plan.”[1]
The agenda's one scheduled item was a SEQR review of Project #0812, a Culver's restaurant with outdoor dining and a drive-through at 4937 William Street. The existing building is to be removed and replaced at the southeast corner of William and Transit.[2]
This was the board's third look. The applicant's engineer reported back on items the board had raised previously, and the recording is a useful record of a board getting what it asked for:
The unresolved item is cross-access — a connection from the Culver's site to the property to the east, so traffic can move between parcels without re-entering Transit Road. The applicant's team reported the grade objection they had raised earlier was wrong on a second look (“up here, it's nice and flat… It's a home run for a spot to get out there”), but that the easement requires agreement from two separate neighbouring owners, because the driveway in question has no access out to William Street.[1]
One of those owners was named on the recording as Benderson[*]; the second was not identified, and the applicant's representative said so: “I don't recall who that owner is.” The audio renders a party to the arrangement as “S and K,” but no document before this board names it, and this brief does not guess. The applicant's position was that it is pursuing the easement in good faith but cannot compel it: “we can't force the adjacent landowner to play ball with us,” and so asked the board to proceed on the worst-case premise that cross-access will not be granted.[1]
The board's engineering consultant disagreed with that framing, after the applicant had left. “Just regarding Culver's on that cross-access… this board has the right to demand it, not if they get an agreement.” Asked to repeat himself — “Has the right to what?” — he said: “Require it. Require it, demand it.” A member agreed: “with our management and access plan on Transit and blah, blah, blah, we should mandate it. That's what's right.” No motion followed, and the point now sits on the record for the November meeting.[1]
Rather than defer the environmental review, the board asked its legal advisor whether to begin it knowing it could not finish. “So we know we can't get through SEQR, but Brad, I'm looking for some advice here. Should we start the SEQR process, even though we might not get through some of them because of the DOT issues?” Told it could, the chairing member opted to work through what was answerable: “let's see what we can get through, and if we have to say pause on some of them until we get more information, that's what we'll do.”[1]
The board then read the Part 2 questions aloud and answered them in sequence. Two were held open — question 5 and question 7b. The rest were answered “no” or “no or small impact.” This brief does not give a precise tally of the answered questions: two of them were read out back to back and disposed of with a single “no,” so the recording does not establish beyond doubt whether that answer covered one question or both.
“I think that's where we need to pause. We don't know.” The traffic impact study the DOT asked for had only just become possible to start, because it depended on the DOT's own driveway determination. Discussion acknowledged the change of use is retail-to-restaurant: “retail to Culver's might have some more trips… it's going to increase the traffic because the Rite Aid wasn't.”
Held because the utility work was still in progress: the first set of plans had gone to the sewer authority, with water coordination starting that week. “It's all new stuff here.”
Reasoning given on the record for several: the land-use question was answered “commercial to commercial”; question 4 was a no “because we don't have a CEA” (critical environmental area); the natural-resources question was answered on the basis that the site is already impervious — “it's concrete, concrete, there's really no change.”
The final two questions — whether a disadvantaged community is identified as bearing comparatively higher burdens under the state's assessment tool, and whether the action would increase a pollution burden within one — were both answered no. These are the newer environmental-justice questions on the state form.
“All of them are okay except for 5 and 7B, which should get answered by the traffic study and other items that the DOT are asking for.” Moved, seconded and carried by voice vote with no audible opposition.
The public input slot on the Culver's item drew no speakers. The board was explicit that tabling leaves the matter open: “We're not closing it. We tabled. We're leaving everything open.” The applicant's team indicated it anticipated returning in November with traffic-study results, while cautioning that the timeline “might be cutting it close.”
After the agenda items concluded, the chairing member distributed a document to every board member and asked them to read it before the next meeting: “I left everybody a copy of the… Carlo emailed this and would like everybody to read this draft of the overlay district for Bowmansville and be prepared to make any comments or changes that you'd like.” Paper copies were provided “compliments of my company in case you didn't have email.”[1]
No discussion of the draft's contents took place — “we don't [do] anything now, but please take some time to look at it so we can discuss” — and no vote was taken. The draft itself is not among the documents this board has posted publicly, so this brief reports only that it exists, that the chair circulated it by email, and that the Planning Board has been asked to comment on it. The substance is a matter for a future meeting, and for whatever record the town publishes of it.[1]
Six of seven members were present. The October 7 minutes, OCR'd for this brief, establish the roster; the roll call on the recording is audible but the clerk's reading is partly unintelligible, so this brief does not state which single member was absent and does not name the member who chaired. The chair, Carlo DiRienzo, was referred to in the third person throughout and did not run the meeting.
Moved, seconded, carried on a voice vote. No additions, changes or questions were raised.
Members were asked for questions or comments on the communications list and answered “No.” The list itself is not published with the agenda.
A proposed 29-home patio-home ranch subdivision on approximately 14 acres, density ~2.1 dwelling units per acre against a permitted maximum of 3, anticipated value about $520,000 per unit. The proposal includes a publicly dedicated road, public water and sanitary sewer, street lighting, a homeowners association, a PUD overlay to preserve common open space, and a 70-foot conservation easement and buffer along the neighbouring western properties.
Presented by a consultant from Studio T3[*] on behalf of a development team named on the recording but not in any document before this board. The Town Board heard the same project on September 8, 2026 as 31 homes at 2.2 units per acre; the site was described then as on the southern side of Broadway between Parkdale and Bowen, adjacent to the Logan subdivision to the east.
This item did not appear on the posted agenda. Moved to classify as major, seconded, carried on a voice vote with none against.
Eleven Part 2 questions answered “no or small impact”; questions 5 (traffic) and 7b (wastewater utilities) held open pending the DOT-driven traffic impact study. No action was requested by the applicant, who described the appearance as an update. Tabled by voice vote; the matter remains open and no public hearing was closed.
Distributed in hard copy to all members after the agenda items, having been emailed by the chair. Members asked to read it and prepare comments or changes for discussion at a future meeting. No discussion of contents and no vote.
On the notice question. This brief reports a documented discrepancy: an item was decided that the posted agenda does not contain. It does not allege a violation of law. Whether a classification vote on an item absent from the posted agenda complies with the Open Meetings Law and the town's own subdivision code is a legal question this publication is not positioned to answer, and the board's explanation — that the application met its filing deadline and the board felt obliged to hear it — is reported in full and in the board's own words. The board did not dispute the resident's account of what the website showed, and neither does our archive.
What we checked. The agenda is the town's own posted PDF, retrieved from its document centre and OCR'd for this brief because the file is a scan with no text layer. We also re-ran the fetch after the meeting: no amended October 21 agenda had been posted. The comparison with September 8 comes from this pipeline's own recording of that Town Board meeting.
Roster. The October 7 minutes were OCR'd for this brief and establish the board as Carlo DiRienzo (Chair), Rebecca Anderson, John Copas, Anthony Gorski, Joseph Keefe, Lawrence Korzeniewski and Michael Reinhold, with staff Ed Schiller (Wm. Schutt & Associates), Brad Davidzik (Deputy Town Attorney), Matt Fischione (Code Enforcement Officer) and Cynthia Maciejewski (Secretary). Whisper mangled five of the seven surnames on the October 21 recording — rendering them Colfess, Keith, Morrison, Ryan and DiRenzo — which is why no vote or statement in this brief is attributed to an individual member by name except where the minutes or the agenda supply the identification. The roll call is audible but the clerk's reading is too garbled to establish reliably who was absent, so we say six of seven and stop.
Names we did not print. The resident's name and address are given as she stated them at the microphone and are marked for verification. The Cozy Meadows consultant and his clients, and the Culver's applicant's engineers, were named only on audio; the project entity “Culver's” and the addresses are confirmed by the agenda, but the people speaking for them are not, per this pipeline's standing asymmetry between entities and individuals. One party to the cross-access discussion is rendered by the recording as “S and K” and appears in no document; we have not guessed at it.
Capture. 42.4 minutes, faster-whisper “large-v3,” 509 segments of which 487 are distinct, most frequent segment 1.96% (“Okay.”), longest identical consecutive run 2, language confidence p=0.963 — all within this pipeline's degeneracy thresholds. Coverage is 83.8%, lower than this pipeline's typical 99%: this is a room-microphone capture and roughly seven minutes of the file is silence, including a long pause while members read the minutes and another while the resident approached the microphone. The recording begins about three minutes before the gavel and captures pre-meeting conversation among members on unrelated local political matters, which this brief does not report.
Street validation against the town's street inventory returned Parkdale Drive and William Street as exact matches. A reference in post-adjournment conversation to “Bond Road” is almost certainly Bowen Road (confidence 0.842), consistent with the September 8 description of the site as lying between Parkdale and Bowen; it is not reported as fact because it falls after the meeting was closed.