Georgetown council approves annexation, zoning changes and development agreement for Shell Spur project amid neighborhood concern

Georgetown, Texas — The Georgetown City Council on April 14 approved annexation and zoning changes for a roughly 43‑acre proposal at Shell Road and Shell Spur and adopted a development agreement that requires the developer to build intersection improvements before vertical construction.

Staff planning manager Ryan Clark told the council the application (item 6a for 28.93 acres and item 6b for 14.2 acres) partially met approval criteria: the proposal would bring commercial services and connect the site to city wastewater infrastructure but raised compatibility, tree‑preservation and transportation concerns for nearby low‑density neighborhoods. Clark said the current PUD iteration did not include the buffering and transition standards the council previously requested.

Amanda Brown of HD Brown Consulting, presenting for the applicant, said annexation would allow the developer to withdraw a pending Texas Commission on Environmental Quality on‑site wastewater permit and tie the site into Georgetown’s wastewater system. She described a development agreement that requires construction of a traffic signal, a left‑turn lane and a right‑turn lane at Shell Road and Shell Spur with the project’s first phase, and estimated the developer’s impact‑fee and improvement contribution at roughly $2.3 million in impact fees and about $1.5 million in improvements.

Neighbors including Heath Culp and Carol Tharpe urged caution. Culp, who has repeatedly participated in the application process, said the reduced densities and the guarantee that intersection improvements will be built up front were important neighborhood benefits. Tharpe said she preferred annexation and council oversight to an alternative that could allow an on‑site wastewater facility near large single‑family lots, but said multifamily next to her property would be undesirable.

Councilmember Kevin moved to approve the annexation and PUD ordinances with detailed modifications: limit MF‑1 density to 10 dwelling units per acre, change certain commercial zoning to C‑1, require 50‑foot setbacks from existing residential, set a minimum building separation of 10 feet in tracks 1 and 2, require an 8‑foot opaque screening wall along the southern property line, restore base impervious‑cover rules rather than the applicant’s proposed reallocation, remove certain tree‑preservation language from the PUD, and strike PUD utility regulations that conflict with separate utility policies. The council approved item 6a and item 6b with parallel modifications; each motion passed with one member opposed.

The development agreement (item 6c) was approved with added building‑material standards — including minimum masonry coverage and facade requirements — a commitment to construct the traffic signal and turn lanes described by staff, and fee waivers noted in the motion. The council approved the development agreement on a simple majority; one council member voted against the motion. Council scheduled a second reading of the ordinances at a subsequent meeting.

Ryan Clark and Wesley Wright (transportation staff) told council staff’s concerns centered on the absence of a site plan to confirm impervious‑cover allocations and that, without tradeoffs or additional amenities, increased impervious cover and reduced building separation could be problematic. The applicant said the PUD recalibrates MF‑1 standards to reflect a horizontal, lower‑density product rather than vertically stacked multifamily and that the project includes provisions intended to preserve many existing trees.

What’s next: The annexation and PUD ordinances will return for second reading at a future Council meeting; the development agreement takes effect after the formal ordinance process completes and any conditions read into the record are incorporated between first and second reading.

Quotes

“We will be able to withdraw that application, if we’re able to annex into the city tonight,” Amanda Brown said, referring to the pending TCEQ on‑site wastewater permit.

“The requirement to put these traffic improvements in before they get any vertical builds is tremendous,” neighborhood speaker Heath Culp said, describing the intersection improvements as a major neighborhood benefit.

Actions and votes

• Item 6a (annexation and PUD, ~28.93 acres): Motion by Kevin; seconded; approved with one opposed (motion carried). • Item 6b (annexation and PUD, ~14.2 acres): Motion by Kevin; seconded; approved with one opposed. • Item 6c (development agreement with infrastructure and building‑material conditions): Motion by Kevin; seconded; approved (simple majority) with one opposed.

Context

The proposal moves 43 acres currently in Georgetown’s extraterritorial jurisdiction into the city and would allow the developer to connect to city wastewater service instead of pursuing a TCEQ on‑site wastewater plant. Council and staff emphasized transportation and stormwater implications of the PUD standards, and neighbors pressed for protections on tree preservation, setbacks and building materials.

Reporting note: Article draws from council presentations, applicant testimony and public comments at the April 14 City Council meeting.