Galveston STR committee reviews registration portal, verification and enforcement steps ahead of city takeover

The Galveston Short-Term Rental Committee spent its meeting reviewing the Park Board registration portal and discussing how the city should manage STR registration, verification and enforcement after the program transitions to municipal control.

Committee members said the current online application provides a useful baseline but contains gaps and data-quality problems that could hinder enforcement. Key issues raised included reliance on the Galveston Central Appraisal District (GCAD) property identifier, the accuracy of owner information following sales, how to verify registrations for new construction, how to handle property managers and co-hosts, and whether the city should require sworn affidavits and site plans for some listings.

Why it matters: the committee is preparing recommendations for City Council and staff as control of STR registration moves from the Park Board to the city’s systems. Committee members want clear, enforceable registration requirements so that complaints (noise, parking, occupancy) can be investigated against a reliable record of what the owner or operator declared when they registered.

Most of the meeting focused on the registration form currently hosted by the Park Board. Committee members walked through the portal page‑by‑page and flagged fields that should be required or clarified. Several raised the GCAD property ID as the best unique identifier but noted that it can be hard for some applicants to find. “The GCAD number is the 1 unique identifier to every piece of property,” Tim (staff member) said, and committee members recommended linking the GCAD lookup directly from the form and making the GCAD/property ID a required field rather than letting applicants type free‑form addresses.

Committee members also discussed ownership verification. New builds and recent sales sometimes do not show updated owner names in GCAD, which slows verification; an affidavit or submission of closing documents was suggested as an option where ownership records lag. Members asked staff to design a verification workflow so development services could flag mismatches and request supporting documents before a registration is finalized.

On responsibilities and local response, the committee recommended requiring a local 24‑hour contact who can respond to incidents within one hour and suggested requiring that contact to be at least 18 years old. Speakers said the portal already enforces a one‑hour proximity rule in one instance: when a test entry named a contact outside the jurisdiction, the system blocked the submission. The committee discussed whether local contacts should be required to provide a date of birth or other proof; members favored including an attestation in the registration and handling further verification through enforcement rather than complex online ID capture.

A recurring theme was the role of property managers versus owner‑operators. Members urged that the owner remain legally responsible for the property even when a manager files the registration; if a management company registers on an owner’s behalf, the meeting recommended the management agreement or a notarized owner authorization accompany the registration. Several members warned against making the portal so onerous that managers and owners drop off the registry and collections of the hotel occupancy tax (HOT) and other reporting suffer.

The committee discussed affidavits and sworn self‑certifications used in other Texas coastal cities (committee members referenced Corpus Christi as a model). Attested statements could require applicants to confirm they have read noise, trash and HOA rules and to certify the accuracy of the floor plan and contact information. Members noted practical limits on requiring notarized affidavits for thousands of registrants and suggested a hybrid approach: an online attestation for renewals and a notarized affidavit in flagged or high‑risk cases.

Regarding floor plans and occupancy, members debated whether the registration should require a sketch floor plan and whether to record maximum occupancy. Several committee members argued for a simple, plain‑paper sketch (no scale required) so the city has a baseline record for enforcement when complaints arise. Others warned that occupancy limits are legally fraught in Texas without local data tying occupancy to safety or nuisance harms; the committee asked staff and legal to advise on which occupancy or bedroom definitions are defensible and enforceable.

Parking enforcement was described as a separate but related workstream that staff (Tim and others) will further develop. The committee agreed parking questions should remain on the registration form (number of off‑street spaces) because parking rules often tie to declared bedrooms/occupancy, but members emphasized that street‑parking enforcement is a police/traffic function and may require different remedies.

Technology and data: members commented on the Park Board’s vendor (Deckard/Deckard‑style portal) and the need to know what changes the vendor can implement and at what cost. The meeting noted the registration portal currently lists a planned portal open date of Dec. 1, 2024; members asked city IT, finance and planning to coordinate on which fields must be made required and which changes the vendor can implement quickly.

Next steps and direction to staff: the committee asked staff to incorporate the committee’s registration recommendations into the draft ordinance and software configuration notes; staff were asked to report back with (1) a proposed list of required fields, (2) a verification workflow for GCAD mismatches and recent sales, (3) a recommended affidavit/attestation approach, and (4) a proposal for triggering site‑plan submission (for example, when declared occupancy greatly exceeds typical bedroom counts). Committee members also reviewed a tentative timeline: a draft ordinance incorporating committee comments could be prepared by August, with additional materials ready for City Council review in October; the committee’s charter currently sunsets in early December.

A brief formal action: committee members moved to approve the meeting minutes from the packet. The motion was made by Sheila Lipscomb, seconded by David Bloom, and approved by voice vote.

The committee scheduled follow‑up meetings to continue review (members picked dates to reconvene and to begin ordinance redlines) and asked legal, development services and finance to attend upcoming sessions to address enforceability, code language and data/collection questions.

Ending note: members emphasized balancing enforceability and ease of compliance so owners and managers register rather than circumvent the system. Several members said the city should aim for clear owner responsibility statements at the front of any registration packet and a pragmatic verification and enforcement process that protects neighbors while remaining feasible for the city to administer.