Oregon Property Brief — Issue 008

A housing site can look real before it is real.

The zoning may allow homes. The city may want the units. The site may sit inside a growth area. A seller may call it “prime housing land.” A public meeting may mention housing supply. A policy headline may make it sound like Oregon is clearing the path.

But housing does not get built on policy headlines.

It gets built after water, sewer or wastewater, stormwater, transportation, power coordination, frontage improvements, system capacity, funding, design, permitting, and timing all line up enough for a project to move.

That is the hidden gate in a lot of Oregon housing land conversations:

Zoned for housing is not the same as served for housing.

This matters because infrastructure risk is easy to underwrite too late. It often sits outside the sexy part of the deal: not the concept plan, not the zoning map, not the “units possible” count, not the legislative press release. But it can decide whether a site is feasible, when it can move, who has to pay, and whether the value being discussed is near-term value or someday value.

Oregon’s new Housing Infrastructure Financing Program makes that distinction more visible. It does not solve every site. It does not mean a private buyer can assume state money will appear. But it does show how the state is now naming the problem: housing production can be gated by specific infrastructure for specific proposed housing development.

For OPB readers, that is the useful signal.

The question is not just whether Oregon wants housing.

The question is whether a specific site has a credible infrastructure path.

When you hear “housing opportunity,” do not stop at:

Can housing be allowed here?

Ask the next question:

What infrastructure has to exist, who controls it, who pays for it, and when will it actually be usable?

That one question changes how different readers should behave:

That is why this issue is not just about HIFP. HIFP is the entry point. The reader value is the due-diligence workflow.

House Bill 3031 created a program through which the Oregon Infrastructure Finance Authority may provide financial assistance for infrastructure to support housing development. Business Oregon’s Housing Infrastructure Financing Program page says the program is administered by the Oregon Infrastructure Finance Authority, which sits within Business Oregon.

The program categories are the same categories that often decide whether housing land can move:

Business Oregon describes HIFP assistance as grants, loans, and forgivable loans for infrastructure for a specified proposed housing development. The Oregon administrative rules for the program add more useful details for readers: a project can include development or improvement of transportation, water, wastewater, or stormwater infrastructure, including improvements to system capacity, and it must primarily support a specified proposed housing development.

That language is important because it is not vague “housing support.”

It is site-and-infrastructure specific.

It tells you the diligence lens to use even if your site is not part of HIFP:

That is a much better question set than “Is housing allowed?”

Oregon property conversations often blur several different ideas into one word: “feasible.”

But feasibility has layers.

A site can be:

The mistake is treating one layer as proof of the next.

A zoning map does not prove sewer capacity. A UGB discussion does not prove annexation timing. A concept plan does not prove stormwater feasibility. A public funding program does not prove a specific site will receive money. A capital improvement list does not always mean the improvement is funded this year.

For readers, the practical move is to separate the layers before the deal language gets too confident.

The state program tells you what Oregon is trying to solve. The local public-works trail tells you where the problem shows up.

For a real site, ask for the local documents that translate ambition into infrastructure reality:

Redmond’s Capital Improvement Program page is a useful example of the kind of source trail to look for. Redmond describes its CIP as a planning tool for infrastructure priorities, asset maintenance, and growth management. The page points readers to a five-year forecast and project hub, and its listed examples include wastewater capacity, water capacity and redundancy, transportation improvements, stormwater work, and utility extensions connected to affordable housing.

The point is not that Redmond answers your site’s question.

The point is that every serious “housing opportunity” claim should eventually be traceable to local infrastructure evidence like that.

If the claim is “this land could support housing,” the follow-up is:

Show me the document that says how it gets served.

Use this as a script before buying, listing, financing, filing, or relying on an Oregon housing site.

Ask whether water is available at the site boundary with enough pressure, capacity, and fire-flow support for the proposed units. If not, ask what is required: line extension, upsizing, pump station, reservoir, pressure-zone work, easement, or offsite improvement.

The expensive word is not always “no.” Sometimes it is “yes, after…”

Ask whether sewer service exists with capacity for the proposed density. A site may need a main extension, lift station, pump station decommissioning, treatment-capacity solution, or phased connection strategy. If the site is outside city limits or a service district, ask whether annexation or district consent is part of the path.

For rural or edge sites, do not casually substitute “septic maybe” for a sewer answer. That is a different due-diligence lane.

Stormwater can change layout, cost, and buildable area. Ask what standards apply, whether detention or treatment is required, whether downstream capacity is a problem, and whether the site has drainage, wetlands, slope, or natural-resource constraints that change the design.

A site plan with units is not the same as a site plan that has solved stormwater.

Ask what frontage, access, intersection, signal, sidewalk, bike/pedestrian, transit, or offsite road improvements are triggered. A small-looking access issue can become a material cost or timing gate if it requires coordination with a city, county, ODOT, railroad, neighboring owner, or utility.

Also ask whether the transportation improvement is required before occupancy, before plat approval, before building permits, or later.

Find the public facility plan, CIP, utility master plan, transportation system plan, or capital budget. Then ask three simple questions:

A project listed in a plan is not the same as a project funded for construction. The difference matters.

Ask whether the improvement is publicly funded, developer-funded, grant-supported, loan-supported, partially funded, or unfunded. If public funding is involved, ask whether it comes with affordability, covenant, procurement, wage, timing, reporting, or partnership conditions.

If the answer is “we’re pursuing funding,” treat that as a watch item, not a solved condition.

Ask for system development charges, connection fees, meter fees, frontage obligations, latecomer fees, reimbursement district exposure, and any offsite improvement estimates. A site can be technically serviceable but financially different once these costs are modeled.

For agents and landowners, this is where “housing potential” can become a pricing conversation rather than a slogan.

If the site is in an unannexed UGB area, expansion area, urbanizable land, or edge condition, ask what has to happen before urban services are available. DLCD’s UGB Expansion Area Planning Grants are a reminder that planning for unannexed land can include public facilities, transportation, hazards, resources, land-use designations, and annexation provisions.

That is not the same as immediate service.

Wetlands, riparian areas, slopes, floodplain, geologic hazards, easements, railroad crossings, and natural-resource protections can affect whether infrastructure can be extended where the concept plan assumes it will go. DLCD’s wetland technical assistance materials are a reminder that housing readiness can depend on site-specific inventories, delineations, avoidance, and mitigation planning.

Again: separate the layers.

Ask for the actual sequence: planning, design, funding, right-of-way, permitting, bidding, construction, inspection, acceptance, connection, and occupancy. Then compare that sequence with the deal’s assumptions.

If the housing schedule says 18 months but the infrastructure schedule says 36, the infrastructure schedule is probably the real schedule.

A site may depend on several decision-makers: city public works, county roads, a sanitary district, a water district, ODOT, DSL, DEQ, a council, an infrastructure finance board, a developer, a neighboring owner, or a lender. Name the party that controls the next step.

If nobody owns the next step, the risk is not technical. It is organizational.

Do not rely only on verbal confidence. Ask which official source proves the answer:

The goal is not to become an engineer. The goal is to know which claim is documented and which claim is still an assumption.

After the 12 questions, put the site into one of four buckets.

The site has service availability, capacity, access, and no major unfunded offsite infrastructure gate identified. This does not mean the project is easy, but infrastructure is not the first unknown.

The site can be served, but only after defined improvements with a known owner, cost range, funding path, and timeline. This can still be workable, but the deal should price the improvement path honestly.

The needed infrastructure appears in a plan, CIP, grant discussion, or public process, but funding/timing is not firm. This may be a long-term opportunity, not a near-term housing site.

The pitch depends on housing demand, zoning, or policy direction, but nobody has documented the service path. This is the danger bucket. It may still be worth investigating, but it should not be marketed or financed as if the infrastructure answer is known.

Infrastructure diligence does not make a reader negative on housing.

It makes the reader more precise.

Oregon needs housing, and many communities need better infrastructure to support it. But a property-specific decision still has to answer property-specific questions.

That precision can protect a buyer from overpaying for “future potential.” It can help an agent write safer listing language. It can help a landowner understand what a buyer is really underwriting. It can help a lender spot timeline and cost exposure. It can help a builder know whether to spend money on design now or wait for a public improvement to move. It can help a local official explain why the bottleneck is not just zoning.

The best version of this issue is not “infrastructure matters.” Everyone already knows that in the abstract.

The useful version is:

Here is the source trail. Here are the documents. Here are the questions. Here is how to tell a real service path from a housing story.

For OPB, the useful watchlist is not broad “housing funding.” It is specific pairings of sites, public entities, infrastructure improvements, and timelines.

Watch for:

That is where OPB can keep adding value: turning scattered public documents into practical Oregon property intelligence.

Pick one site, listing, planning area, or project you care about.

Then answer these three questions before trusting the housing story:

If those answers are clear, you understand the site better than most people reading the zoning line.

If those answers are not clear, the next call is not to the marketing brochure. It is to planning and public works.

What Oregon site, city, or infrastructure bottleneck should OPB track next?

Reply with a city, project, listing, planning area, public-works document, or local infrastructure question. I’ll add it to the OPB source watchlist.

If you find value in these issues consider subscribing to stay informed.