CB26-001 · Ordinance · 2026 · City of Arvada

An Ordinance Repealing and Reenacting or Amending Various Sections of the Land Development Code of the Arvada City Code Relating to Short-Term Rentals

Official status: First Reading

Prime sponsors

Sponsor information is on the official bill page (linked below).

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

Arvada first adopted short-term rental (STR) laws in 2020. The City Council asked City team members to review the ordinance to ensure it was less burdensome to implement and administer, and that enforcement provisions were more transparent. As a result, team members are proposing changes to the existing STR ordinance. The proposed changes include: • Requiring that an STR permit be held by a real person. Legal entities, such as corporations, LLCs, or partnerships, etc., may still own an STR property -- as is the case now. The ordinance simply ensures that the actual permittee is a real person. • Requiring that a person hold only one STR license. • Creating more transparency around administrative and enforcement provisions and processes. Note: Because the City previously issued STR permits (licenses) to legal entities and previously allowed permittees to hold more than one STR permit, the proposed ordinance “grandfathers” in STR permits issued to a legal entity on or before December 1, 2025, and to those individuals and entities that held more than one STR permit on or before December 1, 2025. These “legacy” permit holders and permits will be allowed in accordance with the remaining provisions of the proposed ordinance. These provisions are intended to prevent disruptions to the STR marketplace in Arvada. A draft of the proposed STR “Program Rules” is attached to this agenda packet. The Rules are intended to provide more transparency about STR application processes, about STR permittee responsibilities, and about how administrative enforcement actions are handled. In accordance with the City Code, the Rules will be the subject of an upcoming public hearing before the city manager or his designee. After that, the proposed Program Rules will be forwarded to the City Council via a resolution to be considered by the City Council on February 17, the same evening as the second reading and public hearing on the STR ordinance. The Arvada team recommends that the City Council approve CB26-001, An Ordinance Repealing and Reenacting or Amending Various Sections of the Land Development Code of the Arvada City Code Relating to Short-Term Rentals.

Status timeline

Every recorded action on CB26-001, oldest first
DateLocationAction
02/03/2026City CouncilListed on the City Council agenda — Ordinances (First Reading)
02/17/2026City CouncilListed on the City Council agenda — Public Hearings

Full text

Official record

City of Arvada — City Council meetings, CivicClerk (arvadaco.api.civicclerk.com)

Source: City of Arvada — City Council meetings, CivicClerk (arvadaco.api.civicclerk.com) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

d169fc07297e9c1e6f83b761eb53ed8f420a1a3ecc1a4630f0fb7a2754a82998

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-10-28 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: City of Arvada — City Council meetings, CivicClerk (arvadaco.api.civicclerk.com) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.