Skip to content
Colorado Local Ordinance Affordable Housing

Build-to-Rent Meets the Zoning Code: What Commerce City’s Hogan PUD Fight Reveals

Obedio research
Obedio research

Build-to-rent (BTR) has become one of the fastest-growing segments in American residential development, and a single land-use case in Commerce City, Colorado shows exactly why it is also one of the trickiest to entitle. On July 6, 2026, the Commerce City Council takes up Ordinance PUDA25-0003, a request to amend the Hogan Property Planned Unit Development to allow a roughly 227-unit build-to-rent community of detached homes and duplexes called Yardhomes at Fronterra Village. The Planning Commission has already recommended denial on a 3-2 vote. City staff recommends approval. For anyone tracking the BTR pipeline, the split is instructive.

The project

The applicant, Urban Moment, is asking the City to reshape about 16.82 acres inside a PUD that was originally adopted back in 2003. The land sits on the east side of Chambers Road, north of the 102nd Avenue alignment, at 10230 Chambers Road and 15955 East 101st Way. The proposal consolidates several planning areas that today allow a mix of commercial and single-family residential, and it converts them to what the code calls “household living” — a hybrid of smaller detached single-family homes and two-unit buildings, all held under common ownership and offered for rent rather than for sale.

The amendment also folds in a leftover 1.10-acre parcel owned by School District 27J, a remnant created in 2009 when the Stuart Middle School subdivision redrew Joplin Street. Adding it lets the applicant improve circulation, add units, and carve out an outdoor gathering space. The conceptual site plan submitted with the application is explicitly illustrative; unit count and layout are expected to change as the project moves into subdivision and a development agreement.

Why the code is the real obstacle

The most telling detail for development professionals is buried in the staff report: neither Commerce City’s 2009 Land Development Code (under which this application is being processed) nor its newer 2025 code actually contemplates this product type. Build-to-rent detached housing falls into a gap between the categories that most zoning ordinances were written to handle — it looks like single-family from the street but operates like multifamily on the balance sheet.

That gap is precisely why the applicant pursued a PUD amendment with customized development standards rather than a standard rezoning. The proposed deviations cover unit size, setbacks, building separation, and architectural design, tailored to the scale, ownership model, and on-site amenities of a BTR community. Staff supports those modifications, noting most standards otherwise track the existing code. It is a clean illustration of a broader reality: the BTR sector is frequently forced to innovate through flexible zoning tools because base codes have not caught up to the product.

The case for approval

Staff’s recommendation leans heavily on housing policy. Commerce City’s 2018 Housing Needs Assessment found that 76 percent of the city’s homes are single-family detached — 86 percent in the Northern Range — and the Comprehensive Plan repeatedly calls for a broader mix, including “missing middle” housing and higher-density product near commercial corridors. The subject site is classified for greenfield development and sits as a natural transition between commercial uses and Xcel power lines to the north and existing homes to the south.

Staff also points out that the commercial land south of the power lines has struggled to develop since 2003. Rather than leave it vacant and underused, the applicant proposes a housing type rarely found in the Northern Range, backed by design standards governing site layout, landscaping, fencing, and architecture. The submitted traffic impact study concluded the development’s effect on surrounding intersections would be minor.

The case for denial

The Planning Commission was not persuaded. Its 3-2 recommendation found the proposal failed two approval criteria under Section 21-3251(3): consistency with the Comprehensive Plan’s goals, and the requirement that a PUD address a unique situation, confer a substantial benefit, or deliver creative design that improves on standard development. Commissioners in opposition cited the loss of commercially zoned land, impacts on adjacent residents, and questions about the market-rate rents the community would command. A neighbor’s letter raised privacy, character, and home-value concerns.

Notably, the commissioners who voted in favor cited many of the same facts staff did — the uniqueness of the product, the housing diversity it adds, and the practical judgment that commercial development simply was not going to materialize on this parcel. The two sides looked at identical information and reached opposite conclusions about whether a rental product clears the “substantial benefit” bar. That is the entitlement risk BTR developers live with.

Why it matters beyond Commerce City

Public engagement was thin — one resident attended the first neighborhood meeting, none attended the virtual second one, and one opposition letter reached the Planning Commission — yet the application still drew a split recommendation. That underscores how much BTR outcomes hinge on code interpretation and discretionary criteria rather than organized opposition.

For developers, planners, and land-use attorneys, the Hogan case is a compact study in three recurring BTR themes: base zoning codes rarely have a home for the product, the PUD (or its equivalent) becomes the workaround of choice, and approval often turns on whether a body accepts that rental detached housing delivers a public benefit worthy of custom standards. Commerce City’s council reading is a second reading, following a first on May 18, 2026, so the final decision rests with elected officials weighing staff’s housing-policy rationale against the commission’s skepticism.

However it lands, the case is a useful marker of where the build-to-rent conversation is heading — from whether these communities get built to how the codes should classify them in the first place.

Share this post