Grand Junction Housing Affordability Task Force Meeting Summary - October 30, 2025

The Grand Junction Housing Affordability Task Force met on October 30, 2025, at 15:30 UTC to continue developing code and policy recommendations aimed at lowering housing costs. Members reviewed pending proposals, assigned new work on transportation engineering design standards (TEDs), approval expirations, and staff review practices, and discussed how to handle commercial code issues without losing focus on residential affordability.

Discussion Items

Task force scope and commercial code

• Mayor Kennedy asked the group to keep its primary focus on residential housing affordability, while allowing adjacent commercial items to be referred to another avenue when they overlap with multifamily or other housing work.
• Several members supported forwarding a recommendation that City Council create a separate avenue or subcommittee for commercial code improvements, rather than letting those issues disappear.
• Some members noted commercial code crosses over into multifamily, so relevant commercial items should still be considered where they affect housing costs.

TEDs consultant scope

• Ivan said TEDs are a major cost driver and proposed hiring a consultant, perhaps around $100,000 rather than $200,000, to review street-section standards and multimodal requirements.
• Mark and Ivan agreed to draft a narrow scope or RFP for a TEDs consultant by the Monday before the next meeting so the committee could decide whether to request funding.
• Staff noted the city faces a 14% operational budget cut, so any consultant funding would likely require a one-time fund-balance decision by Council.
• Keith cautioned that TEDs are tied to other adopted policies and codes; Ivan responded that the TEDs standards themselves set unnecessarily high costs, citing the FNFO Parkway at $33 million per half mile.
• A member also suggested creating an administrative committee when a project receives a certain number of review comments, at the applicant's choice, to avoid endless review cycles.

Certified irrigation design requirement

• Ivan and Mark presented a proposal to remove the certified irrigation designer requirement from the landscape code, saying the certification does not exist in practice and landscape architects should be able to stamp irrigation designs within their licensure.
• Members agreed the recommendation was directionally sound, but asked Ivan to verify the correct code section because his draft cited an unrelated section (21.06.040) from an AI search.

Bicycle parking/storage

• Mark and Mike presented a previously submitted recommendation to remove long-term bicycle parking/storage requirements from the code, including for multifamily projects.
• The group confirmed this recommendation was already forwarded to staff.

Landscaping and irrigation for properties without water access

• Ivan and Mark discussed a proposal to reduce or waive landscaping/irrigation requirements where irrigation water is not available or a tract has historically not been irrigated, noting costs of $15,000-$25,000 or more on affected projects.
• Speakers stressed that the solution should be a clear code flexibility, not a variance, and that no-irrigation landscaping standards should be developed.
• The item was sent back to Ivan and Mark for further work, with input from Kevin and others.

Local agency referrals and staff review authority

• Mark described repeated instances of city staff adding requirements outside the code, such as directing developers to pipe irrigation ditches and collect signatures from all downstream users, and said staff should cite code sections and refer outside agencies without enforcing risks that belong to the developer.
• Members agreed to send a recommendation to staff asking them to outline and define planning staff's review role, including code-citation requirements and how referral-agency comments are handled.
• The group also identified survey department demands, such as perfect title requirements, as a related problem needing urgent intervention; Ron, Mike, and Ivan agreed to work on it.

Approval expirations

• Mike and Keith discussed a proposal to lengthen approval expirations to a five-year minimum, allow multi-year extensions, and prevent approvals from expiring while a project is under construction.
• They agreed to draft a recommendation for the committee, including a requirement for city action or notice before an approval expires.

Other items discussed

• Detention-pond aesthetics: members questioned a mandate to make detention ponds amenities, asked for a status update from city staff, and noted concerns about final acceptance and drainage issues.
• Cottage courts: a member said the current code is well-intentioned but does not work in practice; if he proceeds with a potential cottage-court project, he will share the case study.
• Inclusionary zoning: one member noted the housing strategy still lists inclusionary zoning even though only one of 100 stakeholders surveyed supported it; others responded that the housing strategy is already being reviewed by the housing division and may be better addressed separately.

Key Outcomes

• The task force confirmed its focus on residential housing costs and will refer commercial-code items through a separate avenue.
• Mark and Ivan will prepare a narrow TEDs consultant scope/RFP for review before the next meeting.
• The certified irrigation design repeal will be finalized with a corrected code section and then forwarded as a recommendation.
• The bicycle parking/storage recommendation remains forwarded to staff.
• Ivan and Mark will continue developing landscaping/irrigation flexibility language, including no-irrigation planting standards.
• A request will be sent to staff to define planning staff's review procedure and code-citation expectations.
• Ron, Mike, and Ivan will work on survey-related intervention, and the group will seek a city status update on detention-pond requirements.
• Mike and Keith will draft approval-expiration recommendations for the next meeting.