Commerce City staff push form-based Land Development Code draft; council presses on setbacks, mapping and data centers

Commerce City planning staff presented a public draft of a rewritten Land Development Code that removes an R-3 maximum-density cap and shifts emphasis from numeric density limits toward building forms, design standards and context-based zoning.

The draft, staff said, is intended to implement the city's recently adopted comprehensive plan and to make zoning outcomes more predictable across contexts such as 'mixed use regional,' 'mixed use neighborhood' and central neighborhoods. "The public initial draft has gone live and is available on the city's website," Community Development Director Jeff Bridal said during the presentation, noting outreach to the development community and the public.

Why it matters: The rewrite would change how the city regulates the size and form of housing and commercial development. Instead of a single multifamily density cap (the existing R-3 maximum of 24 dwelling units per acre), staff proposes a mix of development options, zoning districts and building-form standards that set lot size, setbacks, coverage, height and parking rules for specific building types. Council members said those details will affect neighborhood character, infrastructure needs and the city's ability to attract the types of housing required by the comprehensive plan.

Key points from the presentation and council discussion

- Structure of the draft: staff described three organizing tools in the draft LDC. Development options (broader contexts such as central neighborhoods or neighborhood village) would determine open-space expectations and the set of zoning districts appropriate for an area. Zoning districts would control allowable uses. Building forms would set the lot-level bulk and form standards (setbacks, lot coverage, permitted height and how parking is placed).

- Form-based approach, not a single density metric: Staff described removing the R-3 24-dwelling-units-per-acre maximum and instead writing standards for specific building types (single-family, duplex, townhome, multiplex, apartment). Staff argued the approach lets the city encourage 'missing-middle' housing types that can coexist on a block while avoiding the unpredictability that a single density number can produce.

- Heights and context: Staff said the draft ties recommended heights to context: example recommendations shown were about 45 feet (roughly three to four stories) in lower-intensity contexts and about 75 feet (roughly five to six stories) in regional mixed-use contexts such as transit-oriented or express-corridor areas.

- Setbacks and the visual corridor: Council members repeatedly raised setbacks and tree lawn widths. Staff said a 15-foot front setback for some multiplex building forms is in the draft but noted that, combined with arterial right-of-way widths and a wider tree lawn (typically 8 feet), the effective visual setback from the curb would often be roughly 30 feet. Several council members voiced a preference to retain a 20-foot setback on arterials; staff agreed they could model that as a context-sensitive change. "If we're not comfortable with 15 feet along our major roads, we can look at resetting that back a little bit further," a staff member said.

- Mixed-use and preserving commercial frontage: Staff proposed a requirement to preserve commercial frontages along arterials: developments within 600 feet of an arterial or collector would have to provide active commercial space at the frontage or use vertically mixed-use buildings. Council members saw the 600-foot depth as a way to protect a minimum depth of commercial land while still allowing residential transition behind or vertically above commercial.

- PUDs and mapping: Staff said the code change itself is separate from the mapping exercise. There will be a second phase to address how existing planned-unit developments (PUDs) are treated on the zoning map. Staff proposed allowing existing built-out PUDs to convert to base zones while offering in-process PUDs the option to continue under their PUD approvals; staff said they will return with implementation options in August and aim to finish the LDC adoption process with hearings in September (Planning Commission) and October (City Council), and adoption by November.

- Design standards and materials: The draft includes more prescriptive material and massing rules for building facades and roofs, stronger street-facing articulation and foundation plantings. Staff said some materials would be restricted as primary facades (for example, the draft calls out EIFS and plain concrete block as prohibited materials for primary facades and allows certain materials only as secondary accents up to a percentage of the facade).

- Sustainability index: The draft includes a points-based sustainability index; projects that adopt features such as cool roofs, solar, or low-impact stormwater designs would earn points toward a sustainability threshold. Staff said certified green buildings (for example, LEED) could be exempt from the index.

- Uses: The draft reorganizes use tables into uses-by-right, limited uses (allowed with explicit additional standards) and conditional uses (subject to public hearing). Staff explained how limited/conditional uses would be treated administratively and would expire if unused for 12 months.

Council directions and nonbinding decisions captured in the meeting

- Setbacks: Council expressed a preference to retain a 20-foot arterial setback as a baseline (rather than lowering to 15 feet) for certain building forms; staff agreed to model that option. This was discussed as council direction rather than a formal vote.

- Mapping and PUDs: Staff will return in August with implementation options for mapping existing PUDs into the new zoning structure and for outreach to affected property owners.

- Data centers: Council members asked how data centers should be regulated. Staff proposed treating "data centers" under current code definitions of warehousing; multiple council members asked that data centers be treated as a conditional use that would require public hearing and added scrutiny. Council members expressed interest in an additional, deeper review of data centers (energy use, cooling water needs, visual impacts, co-locators) beyond the LDC rewrite. The council signaled consensus to initially require a conditional-use public hearing for data centers with a commitment to study the use further.

Quotes (from meeting participants)

- "We've been busy since the last time we brought both bodies together in April... the public initial draft has gone live and is available on the city's website," Jeff Bridal, Community Development Director, said as staff opened the presentation.

- "If we're not comfortable with 15 feet along our major roads, we can look at resetting that back a little bit further," a staff planner said during the setback discussion.

- "We might choose to look at PUDs in two ways... if the PUD is done and it's built out, let's apply the basic standard zone districts that are anticipated in LDC," staff said when explaining mapping options for existing PUDs.

Sources and next steps

Staff asked for public comments on the draft through the posted comment period (June). They said they will review comments, return to the development community with a summary in July, present implementation and mapping options in August and proceed to public hearings in September (Planning Commission) and October (City Council) with the goal of adopting the code in November.

What the article leaves open

Staff and council discussed many policy trade-offs without taking formal votes: the final setback rules, mapping of R-3 or other zones across the northern growth areas, and detailed standards for materials and sustainability credits remain subject to change as staff refines the draft with consultant input and public comments. The council also asked for additional legal and policy analysis about several state-level items mentioned in the meeting (governor's executive order and related House bills) before taking final action.

Ending note

Staff described the LDC revision as a multi-step process: rewrite the code, then perform the mapping and implementation work. Council members said they want more granular cost and construction analyses (for example, how different setbacks affect construction type and cost) before finalizing the rules that will shape new housing and commercial projects in Commerce City.