Fulshear council approves Belmont Estates plat after hours of resident objections over on-lot ponds

The Fulshear City Council on Tuesday approved the Belmont Estates Section 1 amending final plat after a more than two-hour discussion in which residents warned that on‑lot detention and retention ponds would make large portions of 2‑acre estate lots unusable and expose future homeowners to maintenance and safety liabilities.

Supporters of delaying or denying the plat argued the developer's plan places wet‑bottom ponds and drainage easements directly across many individual lots, potentially shrinking usable yard area and creating long‑term inspection and liability questions. "Large detention ponds and drainage easements on individual lots is a completely different development plat model… It will make large portions of these lots unusable for the homeowner," said Bill Clifford, a local resident who spoke during the public‑comment period.

Why it matters: Several speakers — including licensed engineers and long‑time residents — urged the council to hold the plat so staff could add clearer plat notes and deed restrictions spelling out maintenance responsibility and access for inspections. They warned that counting water bodies or detention easements toward the 2‑acre minimum set in the city's Comprehensive Development Ordinance (CDO) would undermine the intent of estate zoning and could expose homeowners to insurance and safety problems.

City staff told council members the original Belmont plat listed larger regional reserves maintained by the MUD, but the current amendment shows additional retention features and easements that encumber back portions of many lots. Staff said Fort Bend County's drainage review focuses on effects to county tributaries and does not by itself approve local plat details; the city still performs inspections for grading and infrastructure.

Legal limit on denial: City legal counsel told the council that Texas law constrains a municipality's ability to deny a plat on the basis of "spirit and intent" alone. "A municipal authority that disapproves a plat shall provide the applicant a written statement of the conditions for the disapproval that clearly articulates each specific condition for the disapproval," counsel read during the meeting. In practice, counsel said, denials or conditional approvals must cite an applicable ordinance or statute.

Developer response: Srini Gogineni, representing Heightened Capital Development, told the council the project team has modified grading, lowered house pads and invested roughly $2 million to address neighbor concerns and create wet‑bottom amenity ponds they characterize as enhancements. He said maintenance responsibilities for the easements will be documented with the MUD, HOA and in deed/plat notes.

Council options discussed included conditional approval tying plat recording to a maintenance agreement or specific plat notes and returning the matter to Planning & Zoning. Staff warned that state statute creates a 15‑calendar‑day "shot clock" for applicants to cure deficiencies after a conditional denial; if the city lacks a meeting during that period, the plat may be automatically approved unless properly conditionalized.

Outcome and vote: Councilmember Johnson moved to approve the plat; Councilmember Connor seconded. The motion passed; one councilmember recorded an abstention. The council did not adopt a separate ordinance change at the meeting, but several councilmembers asked staff and legal to draft amendments to the CDO to consider excluding detention/retention easements from net usable acreage for estate lots in future code updates.

What's next: The plat was approved for recording; several councilmembers directed staff to return with proposed CDO language at a later meeting and suggested a work session with Planning & Zoning to prevent similar disputes. Residents who opposed the plat said they will continue to press for stricter CDO language and clearer plat/deed notes about maintenance and access.