<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/" >

<channel>
	<title>Comprehensive Plan &#8211; Mount Vernon Civic Integrity Project</title>
	<atom:link href="https://mvcip.org/tag/comprehensive-plan/feed/" rel="self" type="application/rss+xml" />
	<link>https://mvcip.org</link>
	<description>Welcome to the Mount Vernon Civic Integrity Project</description>
	<lastBuildDate>Mon, 09 Mar 2026 17:57:33 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>Planning Didn’t Prevent the 214 Gramatan Project — It Enabled It</title>
		<link>https://mvcip.org/blog/planning-didnt-prevent-the-214-gramatan-project-it-enabled-it/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 11 Jan 2026 20:25:43 +0000</pubDate>
				<category><![CDATA[Planning]]></category>
		<category><![CDATA[Building Department]]></category>
		<category><![CDATA[Comprehensive Plan]]></category>
		<guid isPermaLink="false">https://mvcip.org/?post_type=blog&#038;p=1070</guid>

					<description><![CDATA[The 214 Gramatan project shows how planning failed to stop harm and instead enabled it. A Comprehensive Plan that relies on broken review and record keeping cannot deliver meaningful protection to residents.]]></description>
										<content:encoded><![CDATA[<p>Mount Vernon recently adopted a <a href="https://www.mountvernonny.gov/605/Comprehensive-Plan" target="_blank" rel="noopener">Comprehensive Plan</a> intended to guide growth, density, infrastructure, and neighborhood impacts across the City. That plan necessarily presumes two things: basic competence by the City departments and boards charged with administering land-use laws, and the integrity of the zoning and planning records on which future decisions are supposed to rely.</p>
<p>But what happens when those assumptions fail—when the officials responsible for zoning and planning do not do their jobs, and the “official” records instead appear sloppy, incomplete, or altered after the fact?</p>
<p>214 Gramatan happens.</p>
<p><a href="https://mvcip.org/blog/the-house-next-door" target="_blank" rel="noopener">The 214 Gramatan project is a large apartment building constructed practically on top of the private residence owned by Dina Periello</a>. What was reviewed and approved on paper bears little resemblance to what was ultimately built. And when the project was later scrutinized through FOIL requests, the City’s zoning file revealed discrepancies that raise serious questions about whether the record was retrofitted to justify an unlawful structure rather than to reflect what was actually approved.</p>
<p>When 214 Gramatan happens, the problem is no longer confined to one property or one neighbor. The integrity of not just a single project, but the planning framework the City now claims to follow, is called into question.</p>
<h4>The Records Appear Altered</h4>
<p>Please review the attached documents, particularly the “<a href="http://mvcip.org/downloads/214%20Gramatan%20ZBA%20Application.pdf" target="_blank" rel="noopener">214 Gramatan ZBA Application</a>,” signed by Sal Saleh as owner and Tom Abillama as architect. This document was produced in response to FOIL requests and appears to be the only zoning application on file for this project.</p>
<p>Several key fields in this application show clear signs of alteration. On page 1, the entry for “Existing Site Area,” and on page 4, the entries for “Size of principal building,” “Number of dwelling units on site,” and the number of parking spaces before and after approval are all missing the standard printed line beneath the entry. In each instance, the figures are handwritten in a style that is arguably different from surrounding entries. One parking entry also appears to show that a prior figure was removed and replaced, with remnants of the original number still visible beneath the handwritten “26” and above the printed line. These anomalies do not appear elsewhere in the application.</p>
<p>These are not minor details. Site area, building size, and number of dwelling units are core facts the Zoning Board relies on to evaluate density, scale, and the extent of zoning relief being requested. They are foundational to the Board’s authority and decision-making.</p>
<p>The importance of these altered figures is underscored by the Zoning Board’s September 19, 2017, Findings of Fact. Those Findings repeatedly describe and analyze a project consisting of 36 dwelling units. They do not mention a 53-unit building, nor do they discuss the site-area figures that now appear on the application.</p>
<p>The first time the record reflects consideration of a substantially larger project is in the March 2019 Amended Findings of Fact. Yet the City’s files contain no amended zoning application, no dated revision, and no explanation of when the application data was changed or how those changes were presented to the Board. The file contains only the seemingly altered application, with signatures dated nearly three years earlier.</p>
<p>In other words, the only zoning application currently on file does not correspond to the project the Zoning Board actually reviewed and approved in 2017.</p>
<p>The presence of handwritten changes to the most consequential parts of the application—combined with the absence of any contemporaneous findings addressing those figures—raises serious questions about the integrity of the administrative record. At a minimum, the application and the Board’s findings do not match.</p>
<p>Residents are entitled to know when these changes were made, who made them, and why the official application now reflects numbers that were never the subject of the Board’s original review. Without that information, there is no basis to conclude that the zoning approvals were grounded in a complete, accurate, and transparent record—and no credible basis to offer assurances about the “integrity” of this project.</p>
<h4>The Project Fundamentally Changed &#8211; But the Application and Review Process Did Not</h4>
<p>The contrast between the September 2017 Findings of Fact and the March 2019 Amended Findings exposes a basic contradiction in the City’s own record. The project was treated as if it posed no environmental issues, even as City agencies were raising concerns about traffic, parking, sewer capacity, and shadow impacts—and, in some cases, calling for further investigation. Despite those unresolved issues, the Zoning Board closed out environmental review in 2017 by issuing what’s called a “Negative Declaration,” and never revisited it.</p>
<p>That decision is troubling on its own, but it becomes far more problematic in light of what followed. The Amended Findings were adopted after a substantial change in the project’s scale, intensity, and density. Even assuming—purely for argument’s sake—that the expanded project could be justified on zoning grounds, SEQRA does not permit environmental review to be frozen in time.</p>
<p>A Negative Declaration issued for an earlier version of a project cannot simply be carried forward after a material increase in size and density without revisiting environmental impacts. Yet there is no indication that the ZBA revisited <a href="https://dos.ny.gov/state-environmental-quality-review-act-seqra-basics" target="_blank" rel="noopener">SEQRA</a> at all in connection with the amended approval. There is no supplemental environmental review, no discussion of whether the changes constituted a substantive change under SEQRA regulations, and no explanation for why the earlier Negative Declaration remained valid. The Amended Findings acknowledge a materially different project but are silent as to its environmental consequences.</p>
<p>You don’t need expert reports to see the problem.</p>
<p>The private home next door has been severely impacted—physically, functionally, and in terms of light, air, and livability. That reality makes the conclusion that this project posed “no significant adverse environmental impacts” ring hollow. If a neighboring home can be so profoundly affected, the claim that no deeper review was required was not just wrong—it was reckless.</p>
<p>At best, this reflects a City that failed to take a hard look. At worst, it suggests a willingness to preserve a paper finding long after reality made it indefensible.</p>
<p>Taken together:</p>
<ul>
<li>Altered application entries</li>
<li>Escalating project scope</li>
<li>No amended application matching the final build</li>
<li>No additional substantive review</li>
<li>No change to the SEQRA determination</li>
</ul>
<p>…the question is unavoidable: how far did the City and/or the developers go to paper over zoning and environmental violations after the fact?</p>
<p>District Attorney Cacace should answer that question.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><em>Supporting Documents:</em></p>
<p><em><a href="http://mvcip.org/downloads/214%20Gramatan%20ZBA%20Application.pdf" target="_blank" rel="noopener">214 Gramatan ZBA Application</a></em></p>
<p><em><a href="http://mvcip.org/downloads/Findings%20of%20Fact%20-%20September%2019%2C%202017%201.pdf" target="_blank" rel="noopener">Findings of Fact &#8211; September 19, 2017 1</a></em></p>
<p><em><a href="http://mvcip.org/downloads/Amended%20Finding%20of%20Facts%20-%20March%2028%2C%202019%201.pdf" target="_blank" rel="noopener">Amended Finding of Facts &#8211; March 28, 2019</a></em></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>You Can’t Build Forward on Broken Systems</title>
		<link>https://mvcip.org/blog/you-cant-build-forward-on-broken-systems-mount-vernons-comprehensive-plan-is-a-failure-of-planning-law-and-basic-competence/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 11 Jan 2026 19:12:40 +0000</pubDate>
				<category><![CDATA[Governance]]></category>
		<category><![CDATA[Comprehensive Plan]]></category>
		<category><![CDATA[Planning]]></category>
		<guid isPermaLink="false">https://mvcip.org/?post_type=blog&#038;p=1057</guid>

					<description><![CDATA[Mount Vernon’s Comprehensive Plan ignores failing infrastructure, sidesteps environmental review, and removes public safeguards, all while placing greater strain on neighborhoods already at their limits.]]></description>
										<content:encoded><![CDATA[<p>Across the city, residents brace for heavy rain not with confidence, but with pumps, quick dams, and towels at the ready—hoping their basements won’t flood with stormwater or raw sewage. Roads are crumbling and, in some places, unpaved. Parking shortages are constant. Buildings sit neglected for years—just look at Mount Vernon City Hall. Streetlights don’t work. Infrastructure fails under routine stress. Meanwhile, City expenses continue to rise, and the only reliable revenue source remains property taxes.</p>
<p>Against this backdrop, City Hall has produced a so-called Comprehensive Plan that addresses none of these realities.</p>
<p>After years of work and more than $600,000 in public funds, the plan does not fix flooding, drainage, roads, parking, or failing utilities. Instead, it functionally abolishes single-family zoning without any assessment whatsoever of whether Mount Vernon’s infrastructure can withstand the resulting impacts, and without any analysis of how the City would pay for those impacts without further burdening the homeowners whose neighborhoods the plan would fundamentally dismantle.</p>
<p>This is not comprehensive planning. It is a dangerous abstraction untethered from reality.</p>
<h4 style="margin-top: 2em;">Density Is Not Our Goal — It Is Our Crisis</h4>
<p style="margin-top: 1em;">The plan repeatedly invokes “density” and “diversity” as virtues to be pursued. That framing is fundamentally flawed.</p>
<p>Mount Vernon is already one of the most densely populated and demographically diverse cities in New York State. Diversity here is not a future aspiration—it is our lived condition. Density is not an opportunity—it is a strain on infrastructure that is already failing.</p>
<p>The only things Mount Vernon truly needs more of are competence, infrastructure investment, and accountability.</p>
<p>Repackaging density as progress, without first fixing basic systems, is not visionary. It is irresponsible.</p>
<h4 style="margin-top: 2em;">“As-of-Right” Means No Public Safeguards</h4>
<p style="margin-top: 1em;">Under existing law, building multi-family housing in a single-family zone requires a variance or special permit. That process is not a technicality—it is the public’s only line of defense. It requires:</p>
<ul>
<li>Notice to neighboring property owners</li>
<li>A public hearing</li>
<li>Review by the Zoning Board of Appeals</li>
<li>The ability to impose conditions to mitigate harm (parking, drainage, traffic, design)</li>
</ul>
<p>Making these uses as-of-right eliminates every one of those safeguards. No hearing. No community review. No enforceable mitigation.</p>
<p>In a city already suffering from flooding, traffic congestion, parking shortages, and failing infrastructure, removing public oversight is not reform. It is deregulation with foreseeable consequences.</p>
<p>You cannot preserve “neighborhood character” while abolishing the zoning rules that define it. Neighborhoods are not just façades; they are systems—of ownership, traffic flow, runoff, and stability. A triplex may resemble a single-family home from the street, but it brings more cars, more waste, more stormwater, and more pressure on systems that already fail every time it rains.</p>
<h4 style="margin-top: 2em;">Environmental Review Should Not Have Been Optional</h4>
<p style="margin-top: 1em;">A Generic Environmental Impact Statement (GEIS) is not red tape. It is the tool New York law requires when a city proposes policies that will reshape how land is used across entire neighborhoods. Its purpose is simple: to force the city to look honestly at cumulative impacts—on flooding, drainage, sewer capacity, traffic, parking, schools, and neighborhood stability—before those impacts are locked in.</p>
<p>That obligation is triggered by what a decision actually does, not by how it is labeled. When a government action increases density, changes permitted uses, or intensifies demands on already-strained infrastructure, the law requires a hard look up front—not after damage is done and residents are left to deal with the consequences.</p>
<p>Skipping that step is not a judgment call. It is a failure to follow the law.</p>
<p>And this matters because, under General City Law, zoning must be in accordance with the comprehensive plan. The plan is not a harmless policy document or a wish list; it is the foundation for every land-use decision that follows. Claiming that a plan with citywide zoning consequences has “no environmental impact” is not just implausible—it defies both logic and law.</p>
<h4 style="margin-top: 2em;">Real-World Consequences Expose the Fiction</h4>
<p style="margin-top: 1em;">These concerns are not theoretical. Homes adjacent to City-approved developments have already suffered severe damage due to poor oversight and inadequate planning. One such case is that of Dina Perriello, whose home has been destabilized as a result of nearby construction approved and overseen by the City (check out our story about the impacts of the 214 Gramatan project here:<br />
<a href="https://mvcip.org/blog/the-house-next-door/" target="_blank" rel="noopener"></p>
<blockquote class="wp-embedded-content" data-secret="gZ5GpH8z8G"><p><a href="https://mvcip.org/blog/the-house-next-door/">The House Next Door</a></p></blockquote>
<p><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;The House Next Door&#8221; &#8212; Mount Vernon Civic Integrity Project" src="https://mvcip.org/blog/the-house-next-door/embed/#?secret=cegd6T1yAS#?secret=gZ5GpH8z8G" data-secret="gZ5GpH8z8G" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe><br />
</a></p>
<p>The occurrence of such damage from a single project directly contradicts the conclusion that similar development on a citywide scale would result in no significant adverse environmental impacts.</p>
<p>When residents raise concerns and are met with indifference or hostility rather than remediation, it underscores the deeper problem: a government that cannot manage even small-scale development safely has no business orchestrating citywide land-use change.</p>
<h4 style="margin-top: 2em;">A Pattern of Disregard for Law and Process</h4>
<p style="margin-top: 1em;">This failure is not confined to planning and zoning. It is consistent with a broader pattern: delayed budgets, reliance on short-term debt to pay basic bills, slow or stalled permitting, and an inability to perform routine municipal functions competently or on time.</p>
<p>A city that struggles to manage its finances, oversee construction, or maintain infrastructure cannot credibly claim the capacity to manage a generational redevelopment strategy—especially one that intensifies density without first repairing what is broken.</p>
<p>Mount Vernon deserves better than slogans, buzzwords, and paper plans.</p>
<p>Any serious planning effort must begin with reality, comply with the law, and put residents—not developers—first. That means honest environmental review, meaningful public participation, and infrastructure investment before zoning changes that permanently alter neighborhoods.</p>
<p>Without those fundamentals, a comprehensive plan is not a roadmap. It is a liability.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><em>If you want to read the Comprehensive Plan, you can download it <a href="https://www.mountvernonny.gov/DocumentCenter/View/11851/Envision-Mount-Vernon---FINAL?bidId=" target="_blank" rel="noopener">here</a></em><br />
<em>(Fair warning, it is 473MB and 413 pages long)</em></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
