Subcommittee weighs two proposals for Talent gateway site; asks staff for follow-up on affordability, commercial viability and prevailing-wage risk

The subcommittee reviewed two developer proposals for a high-visibility Talent site and asked staff to collect more information on affordability mixes, commercial viability and construction risks before the full board considers a recommendation.

Speaker 1 opened the discussion by noting members received the RFQ materials and interview summaries, including a separate scoring from an external reviewer. "He had Hacienda about 10% higher," Speaker 1 said, but added that several evaluators treated concept design differently than team capacity. The committee spent much of its time weighing the relative merits of the two teams: one that emphasized a larger affordable-housing project (referred to here as Hacienda) and another that presented a mixed-income approach with more market-rate components (referred to here as Edlund/Elan).

Why it matters: The selection affects how many affordable units are delivered, whether the site includes a commercial frontage along Highway 99, and whether city contributions push the project into prevailing-wage territory — a change that could materially raise costs and affect feasibility.

On affordable housing and unit mix, members discussed apartment counts and AMI targets. Speaker 3 said Edlund appeared less reliant on public funding and cited differences in how each team proposed to allocate units across AMI bands. The transcript records an approximate count for Edlund at 86 units; Hacienda’s totals were discussed in ranges (participants referenced 66 rentals plus townhomes in different passages). The committee treated those numbers as approximate and asked staff to confirm exact unit counts and proposed income caps.

Live-work and commercial questions dominated part of the debate. Committee members asked how live-work units would actually function (separate cold shells, upstairs apartments with businesses below, or plug-and-play units) and whether there was realistic market demand for that form of tenancy. "I'm very curious about the live work things...is every single one of these units...a studio that runs the thing underneath," Speaker 3 said, noting concerns about empty commercial spaces if market demand is weak.

Construction technology and long-term maintainability also drew scrutiny. One proposal relied on integrated or prefabricated wall systems and other patented modular approaches. Members raised "red flags" about who would service proprietary components and whether local tradespeople would have the skills to maintain them long term. Speaker 1 summarized the risk: while the components themselves draw on established techniques, the integrated system was newer and warranted more evidence of durability and serviceability.

Prevailing-wage risk: Speaker 1 warned of a legal threshold that could change cost obligations. "There are a couple of different triggers that, 1 trigger is the total amount of of public contributions to the project, and that's $750,000," Speaker 1 said, noting BOLI guidance and a Eugene case were relevant to whether adjacent projects would be treated as related for valuation purposes. The committee emphasized the need to know how much city contribution — including land write-downs or incubator funding — would count against that threshold.

Zoning and planning commission concerns: Members discussed whether the site would require zoning changes (spot rezoning versus plan amendments) and noted the planning commission’s preference to keep long-term options open for commercial uses. Several members stressed retaining flexibility so that a future commercial frontage could be preserved if market conditions changed.

Next steps: The subcommittee agreed staff will ask both teams for clarifications on AMI mixes, reliance on public funding, evidence and examples for proprietary construction systems, maintenance/warranty arrangements, realistic commercial uses for live-work units, and secure bike storage details. The subcommittee signaled it would reconvene or provide those answers in the next packet before a full-board discussion. Speaker 3 said, in the transcript, that given the answers the committee would be in a better position to weigh a preference; at the end of the discussion members indicated they would likely ask for additional work from one or both teams rather than immediately selecting a developer.

The meeting adjourned after the staff follow-up assignment; no formal developer selection or binding vote appears in the record.