One is land and improvements. The other depends on guest capacity, parking, approvals, timing, operating costs, and income that the property may or may not support.
That distinction matters whenever a rural property is pitched around venue potential. One pending Clackamas County application makes the diligence problem visible: up to 48 events a year, as many as 200 guests, and three different descriptions of the parking. For a buyer evaluating a similar opportunity, that gap belongs in the offer file before the venue story belongs in the price.
A proposed rural venue is a diligence file, not an operating fact. Z0148-26 was pending when checked September 10, 2026.
90-Second Oregon Property Decision Brief
The proposal: Clackamas County file Z0148-26 describes a home-occupation event venue at 16570 S Springwater Road with up to 48 events per year and a maximum of 200 guests.
The land: The property is zoned EFU—Exclusive Farm Use. In plain English, that is Oregon farm zoning. A wedding or event use on EFU land is not simply a matter of owning a suitable barn; the proposed business has to fit the land-use path and the site.
The discrepancy: The county notice describes parking for 100 vehicles plus grass overflow. In the public application record, the applicant says 100 designated spaces plus 100+ overflow spaces, while a June 29 site plan labels 52 general spaces and 1 ADA space, plus an overflow area with no vehicle count shown.
The deal consequence: Those records do not prove that the property has only 53 spaces, and they do not prove a violation. They do show that a buyer cannot yet tie the 200-guest business assumption to one clear parking plan.
The next move: Ask for the current county staff report or decision, the exact dated plan under review, the county’s written parking calculation, and any site-specific building/occupancy, septic, and fire records that apply.
Watch next: Recheck the official case page on September 17. The hearing is scheduled for September 24, and the county says the staff report will be available at least seven days before the hearing.
The proposal is the easy part to understand
The official hearing notice is specific: the applicant proposes “up to 48 events per year with a maximum of 200 guests” on EFU-zoned property.
That gives a buyer a proposed business scale. Forty-eight event dates and 200 guests are not abstract planning details; they are the numbers someone might use to imagine bookings, staffing, parking flow, vendor access, or income.
The county’s public Accela record displayed the case as “Pending” when checked September 10. The public attachment list then showed a May 13 county letter and the applicant’s August 20 submission. That verifies a real proposal moving through a public process. It does not verify approved guest capacity, operating timing, site-specific approvals, or the income assumptions a buyer might use in a valuation.
This is the commercial distinction: the application describes what the applicant wants to run; the buyer needs evidence of what the property can actually support.
The parking discrepancy
Three descriptions in the public Z0148-26 file: the county notice, applicant statement, and June 29 plan. Checked September 10, 2026. The comparison does not establish a final count or a violation.
Parking is where the business story and the property file stop lining up neatly.
Here is what the checked public documents say:
County notice: a dedicated gravel parking area for 100 vehicles, with grass overflow.
Applicant submission: 100 designated spaces plus 100+ overflow grass spaces.
June 29 plan: 52 general spaces + 1 ADA space, with a separate 150-by-200-foot overflow area but no vehicle count assigned to it.
Those may ultimately be reconcilable. The plan may show only one portion of the parking concept. Another dated plan may control. The overflow area may be counted elsewhere. County staff may request a revision or explain the numbers in its report.
But the checked file does not answer those questions yet.
The important conclusion is narrow: the records describe parking differently. The 52 general and 1 ADA labels do not establish that only 53 vehicles can park on the property. The notice and applicant statements do not establish that 100 dedicated spaces or 100+ overflow spaces have been accepted. No parking-compliance conclusion follows from the discrepancy alone.
For a buyer, however, the discrepancy is already useful. It identifies the assumption that needs proof before the business concept is allowed to influence price.
What the discrepancy can do to an offer
Guest capacity is not purchased in the abstract. The site has to support the operating model.
Consider three explicit hypotheticals:
If the offer assumes 200-person events: A later county record could support that scale, support a smaller scale, or require a different layout. If the supported capacity changes, the buyer’s booking and revenue model changes with it. No financial result is known here; the point is that capacity should remain a condition in the model, not a fact in the price.
If the business plan assumes the current parking layout works: A later record could require a revised layout, different circulation, or a different treatment of overflow. That could change how much of the site is available for guests, vendors, landscaping, or other improvements. The public file does not establish any particular redesign or cost.
If the opening timeline assumes land-use review is the last step: The checked planning file does not establish site-specific building/occupancy, septic, or fire approvals. If one or more separate records are required and still pending, the operating timeline may differ from the buyer’s assumption. Which records apply must be confirmed with the responsible offices.
None of these scenarios predicts the county’s decision. Each shows why venue value should be separated from bare property value until the supporting record is assembled.
A buyer can still like the property. A buyer can still pursue the concept. The disciplined move is to write the offer around what remains unknown.
Put the venue story in the right part of the deal
Before making an offer, separate the transaction into two columns. The pending application is evidence for diligence; it is not itself a property right to put in the price.
What exists today
the land and existing improvements;
the physical barn and site as they exist;
any issued, transferable rights and documents the seller can actually provide.
What still needs proof
the event scale the county ultimately supports;
the dated parking plan the county relies on;
the number and treatment of guest, employee, ADA, and overflow spaces;
the conditions attached to any future decision;
the site-specific records needed before the business can open.
That split improves several deal conversations at once. It gives the buyer a cleaner diligence list. It keeps a lender’s income assumptions tied to evidence. It helps a broker describe the opportunity without representing an unfinished process as an existing business right.
Broker language that earns trust
Avoid this:
“The property is permitted for a 200-person wedding venue with parking for 100 cars.”
Use this instead:
“A pending Clackamas County application proposes up to 48 events per year with a maximum of 200 guests. The public documents checked September 10 describe parking differently, so buyers should verify the current county report, the dated plan under review, final capacity and conditions, and any separate site-specific approvals needed to operate.”
For a shorter listing or buyer note:
“Event-venue application pending. Proposed scale: up to 48 events annually and 200 guests. Buyer to verify county status, parking plan, conditions, and operating approvals.”
That language does not undersell the opportunity. It tells a serious buyer exactly where the opportunity ends and the diligence begins.
A records request you can send today
Instead of asking, “Is the venue permitted?” send this:
Please send the current county staff report or decision for Z0148-26, the exact dated site plan the county is reviewing, and the county’s written parking calculation. The calculation should show how the 200-guest proposal, employee parking, ADA spaces, designated spaces, and overflow area fit together. Please also send any site-specific building/occupancy, septic, and fire records that apply. If a document is pending or a review does not apply, please identify the county office and date that confirmed the status.
A broker can send that to the listing side. A buyer can add it to the diligence request. A lender or advisor can use the same list to identify which assumptions belong in underwriting and which belong in a conditions column.
Then let the answer change the decision:
If the official records support the proposed scale and reconcile the site plan: keep diligence moving, but tie the business assumption to the documented conditions and applicable issued records.
If they support a smaller scale, a redesign, or another material constraint: rerun the revenue and improvement assumptions, then condition, reprice, or leave the transaction as the facts warrant.
If the count, plan, or operating records remain unknown: keep venue income out of represented property value and preserve the diligence contingency.
Save this decision rule: while the official file remains unresolved, keep venue capacity and income conditional and request the records that can move the decision.
Watch Next: September 17
The official September 24 hearing page says the staff report “will be available for inspection at no cost at least seven days prior to the hearing.” That makes September 17 the next useful source check.
When the report appears, look for four things:
Which dated site plan the county analyzes.
How the report explains the 100-vehicle notice, the applicant’s 100 designated plus 100+ overflow claim, and the June 29 plan’s 52 general + 1 ADA labels.
What guest and employee assumptions the parking analysis uses.
Whether the report identifies changes or conditions that would alter the proposed business scale.
The September 24 hearing is a scheduled event, not a promised outcome. The report is valuable because it may turn today’s parking question into a documented deal input before the hearing occurs.
Source note
For readers who want to test the version question, the deeper file includes the county’s ZDO-293 project page, an official proposed-amendments redline, and current county pages for Section 806, Section 1015, Section 1203, and Section 1307. The redline is not a signed ordinance, and the checked record does not settle which code text the county will apply to every issue in this case. Use the staff report or written case record for that answer.
One question: Have you seen parking, occupancy, septic, or another operating record change a rural-property deal? Hit reply with the record and what changed.
Know a buyer, broker, lender, or rural property owner considering a venue use? Forward this issue to them before the business story enters the price.
If you found this useful, subscribe to Oregon Property Brief so you do not miss the next Oregon property signal.