Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Pud Development Committee topic
No spam. Unsubscribe anytime.
Council keeps PUD development committee intact, directs staff to publish summary of its role
Summary
After a lengthy public and council discussion about the role, transparency and membership of the PUD development committee, council voted 5-1 to retain the committee’s current structure and asked staff to create a public-facing snapshot explaining its purpose and activities.
Lakeway city council on Feb. 18 debated the structure and attendance rules of the city’s Planned Unit Development (PUD) development committee — a subcommittee that reviews PUD agreements and provides early feedback to developers — and voted to retain the committee’s current model while improving public information about its role.
Councilmember Sherman introduced the item, noting the committee was formed in 2019 to audit existing PUDs and has evolved into a forum for early developer feedback. Several residents and developers spoke during citizens’ participation about transparency and the committee’s function. Resident Carol Free said members of the public are often unsure what a PUD permits and asked for clearer descriptions of limits and public recourse. “I think the PUD needs a better clarification for the citizens so that they understand what a PUD is and what a PUD isn't,” Free said.
Developer Rip Miller described the committee as a useful filter that lets developers hear informal feedback before formal submissions to planning commission or council. “The PUD dev process allowed you to get in front of some council members and some planning commission members and literally hear what their ideas were,” Miller said.
Council members weighed competing goals: giving developers the benefit of early informal feedback from a smaller group while avoiding any perception of back-room decision-making. Several council members emphasized that PUD development meetings are advisory, produce no binding commitments, and that members frequently vote differently on the dais than the informal feedback they gave in PUD sessions.
After discussion, a motion to leave the PUD development committee structure unchanged carried, 5-1. Council also directed staff to prepare a public-facing webpage or “snapshot” describing the committee’s purpose, membership, typical process, and a high-level notice that a project was presented (for example: project type and general location) so that the full council and residents have basic awareness of committee activity without creating a prohibited walking quorum of council members.
The council’s action keeps the committee as a smaller, advisory body but adds a transparency step intended to inform the broader council and the public about the committee’s workload and the projects it is reviewing. The committee’s meetings will remain subject to open-meeting rules when an actual quorum of council members meets; staff will produce the public summary and return with suggested language for council approval.
