Galveston committee details draft short‑term rental ordinance, debates hotline, inspections and STARL review board

Galveston short‑term rental stakeholders and city staff spent several hours discussing revisions to a draft ordinance that would formalize complaint intake, penalties and an administrative review board for short‑term rentals.

The working group concentrated on three linked enforcement components: how complaints should be initiated and tracked, whether and when the city may inspect STR units, and how a proposed STARL (short‑term rental review) board would adjudicate repeated violations. "We're not gonna go backwards today," Committee Chair Sheila Litstone said as the group opened discussion of the latest draft.

Why it matters: the draft would change how the city documents complaints and enforces rules for short‑term rentals, affecting owners, property managers, nearby residents and platforms such as Airbnb and VRBO. Members said clearer procedures would make enforcement faster and protect due process for property owners.

Most of the meeting revolved around complaint intake and the timeline that triggers formal enforcement. Committee members agreed the official clock for resolving a complaint should start when a city hotline or dispatch notifies a listed local contact or operator — not when a neighbor first calls an individual owner. Several participants emphasized the importance of centralizing reports so the city can generate reliable lists of repeated, validated complaints.

On inspections and penalties, members debated a draft provision allowing building officials or designees to perform on‑site inspections when violations are reported or suspected. Some attendees warned that unfettered entry into private residences raises legal risks; others said a narrowly defined inspection authority is a necessary enforcement tool if violations are documented. Participants asked staff to confirm whether the building code already authorizes certain inspections and to, if appropriate, cite that code in the ordinance.

The group discussed the proposed STARL boarda three‑member panel of senior city staff in the draft that would review showings of repeated violations and recommend suspension or revocation. Questions included whether to include industry or neighbor representatives, whether the board's determinations should be strictly quantitative (documented violations) or allow more discretionary review, and what appeal route an aggrieved permit holder would have. Members debated messaging and process: staff would provide written notice of contemplated revocation, identify the violations relied upon, and the draft includes language allowing a written appeal within 20 calendar days to the city manager or designee.

On reporting and tax reconciliation, the committee discussed whether owner/operator reporting should be monthly or quarterly. Several operators and staff described practical constraints: hoteliers typically report monthly, some software workflows make monthly submission straightforward for larger operators, and smaller owners may find monthly uploads burdensome. Staff noted the city's hotel occupancy‑tax code (Chapter 33) currently requires filing with the director; software used by many operators (referred to in the meeting as Deckard/rental platform software) can produce spreadsheets operators may upload to the city system for reconciliation.

Platform responsibilities also surfaced. The draft would require short‑term rental platforms to remove listings for units that lack a valid registration; the draft references existing Chapter 19 language on platform obligations and fines (up to $500 per day cited in discussion). Several attendees said that, in practice, responses from platforms vary: some cities report prompt delisting after notice; others said Airbnb and similar platforms can be slow to act.

Members reviewed advertising and signage rules: the draft would require display of the STR registration (GVR) number in online listings and would treat different on‑site signage options (for example, a small, fixed plaque similar to existing bed‑and‑breakfast rules) differently from outward advertising or yard signs that promote rentals. Participants asked staff to return model B&B signage language and to coordinate with land‑use code (LDR) sign restrictions.

On in‑unit postings, the group favored a concise, standardized handout for guests with items such as the registration number, the local contact name and phone, trash pickup day and placement rules, emergency numbers (911 and nonemergency dispatch), quiet hours, occupancy limits, and a reminder that city codes apply and may be enforced. Staff agreed to prepare a short, printable template the city could host online.

Finally, the committee discussed implementation costs and fee design. Staff said the fiscal impact and recommended permit fee schedule depend on the final scope of services (hours of operation, enforcement staffing, software capabilities) and that the city would return a cost estimate after the ordinance language is finalized. Several members urged tying annual permit fees to the program's administrative needs so the program is self‑funding rather than requiring general‑fund support.

What’s next: staff will prepare a STARL process flowchart, refine language on hotline start times and validated complaint definitions, research inspection authority in the building code, and return suggested signage and in‑unit posting language for the committee to review at a future meeting.

Ending: committee members agreed to reconvene and to prioritize a STARL flowchart and parking/density issues at the next session; the group also approved the previous meeting's minutes by voice vote earlier in the session.