Galveston staff propose citywide short‑term rental parking standard; committee tables decision

City staff presented a proposal to the Galveston Short‑Term Rental Committee to expand an existing parking rule for short‑term rentals that now applies only in historic R‑3 districts to other residential zoning districts, require new STR registrations to document on‑site parking, and to grandfather existing registered STRs until renewal.

The proposal, outlined by staff presenters Tim and Teresa, would apply the city’s current limited‑use standard—one required parking space per guest bedroom, with up to two on‑street spaces counted toward that total—across single‑family zoning where STR use is allowed. Staff said new registrations would be denied if applicants cannot document required on‑site parking, while preexisting registered STRs would keep grandfathered status at renewal. “We are not gonna please everyone,” Tim told the committee during the presentation.

Why it matters: committee members said the issue mixes private property expectations with neighborhood livability. Residents and some elected members raised concerns about enforcement and fairness, especially on narrow streets and in parts of the city where on‑site parking is uncommon. The committee did not vote on the staff draft; members agreed to table the proposal and asked staff to return with clearer language and enforcement options.

Details of the proposal and staff explanations

Staff told the committee the limited‑use standard already in the Land Development Regulations (LDR) requires one parking space per guest bedroom, with up to two on‑street spaces counted. That standard currently applies only to R‑3 historic districts. Staff recommended changing zoning tables so that short‑term residential dwellings would carry an “L” (limited use) in additional residential zones, which would trigger the existing parking requirement there as well.

On enforcement and registration, staff said the registration portal (Deckard software) would be updated so applicants must declare the number of bedrooms and the number of on‑site parking spaces and check an attestation that they meet the requirement. Teresa said the italicized text in staff packets was “copied and pasted directly from our code of ordinances.” She explained that existing STRs would be grandfathered as preexisting nonconforming uses and that only new registrations or new construction would be subject to the amended registration requirement.

Staff also described existing tools already in the code: (1) restricted parking areas that are established by traffic studies and ordinance and provide resident passes and guest passes; (2) traffic‑engineer authority to restrict parking on narrow streets (20‑ to 30‑foot thresholds) with council approval; and (3) driveway and driveway‑material standards (on‑site parking spaces must meet 9 by 20‑foot dimensions and use approved materials except where beachfront rules apply). The fire marshal, Chris Harrison, told staff he and battalion chiefs drove neighborhoods and did not identify widespread fire‑access issues due to parked vehicles.

Public comment and committee concerns

A public commenter, Priscilla Smith, told the committee she sees STR‑related party and traffic impacts on her block and disputed the idea that residents can’t distinguish guests from neighbors. “I know my neighbors and who parks on the street regularly and who does not,” Smith said. She also noted commercial hotels have staffed check‑in and security, which private STRs do not.

Committee members debated multiple enforcement and policy questions: whether to tie required parking to the number of bedrooms, whether a simpler rule—allowing only two on‑street vehicles per STR regardless of bedroom count—would be easier to enforce, how grandfathering should operate, and whether applicants could satisfy requirements by securing off‑site parking or building on‑site spaces. Several members argued for keeping the registration‑attestation approach to collect data and to prevent bad actors from avoiding rules; others warned that enforcement will be complaint‑driven and could prove difficult in practice.

Staff directions and next steps

Staff outlined immediate steps the committee requested: update the registration portal to add bedroom and on‑site parking fields and an attestation; have the city engineer finalize objective criteria for conducting restricted‑parking studies; and return to the committee with revised ordinance language and clearer enforcement options. The committee did not adopt the staff draft. Instead, members voted to table the item and asked staff to bring refined language and enforcement scenarios at the next meeting.

Votes and formal actions

The meeting recorded two formal, short actions: approval of minutes at the start of the meeting (motion by Sheila Lindstone; second by David Bloom; outcome approved) and a later procedural action to table the staff STR parking proposal until the next meeting (motion to table by Ted Shook; second not specified on the record; outcome tabled).

What remains unresolved

Committee members asked staff for clearer, enforceable language on: (1) whether required parking should be tied strictly to the number of bedrooms; (2) how grandfathering will be treated when ownership or registration lapses; (3) practical enforcement pathways for complaints about excess vehicles; and (4) objective criteria and thresholds for council‑directed restricted‑parking studies. Staff indicated they will return with revised ordinance text and implementation details.

A forward look

Members expressed a shared goal of reducing impacts from problematic STR operations while preserving lawful STR use by compliant operators. The committee directed staff to return with clarified language and enforcement options; a formal vote on any ordinance change was not held and will await the next meeting.