The evidence behind “approved”: a Portland decision set

The risk: A land agent turns one favorable document into a broad representation—“approved,” “final,” or “ready to build”—before the decision type, local appeal posture, LUBA record, conditions, and remaining permits are clear.

For land agents: Use this when reviewing a seller’s approval claim before writing listing remarks, a buyer brief, or a price recommendation.

What surfaced: Oregon’s official sources describe several different checkpoints. Portland says the appeal process depends on the procedure type. LUBA says available local appeals must be completed before LUBA review. And even LUBA’s “final opinions and orders” can face judicial review in the Oregon Court of Appeals.

What this does not prove: It does not determine the status of a particular property, decision, appeal, or deadline.

What to check first:

Forward this to: The broker, buyer, seller, attorney, planner, or lender who is about to rely on the word “approved.”

A favorable decision can be real and valuable without supporting every conclusion someone wants to draw from it. The land agent’s job is not to decide a legal question. It is to keep the representation no broader than the evidence.

Suppose a seller hands you a land-use decision and says, “The hard part is done.” That sentence invites at least four leaps:

The document may support one or more of those points. It may support none. What matters is the chain between the client’s claim and the official record.

This is especially important because the word final changes meaning as a file moves. A local written decision may be final for purposes of a local procedure. Completion of available local appeals may open the path to LUBA. A LUBA final order may then be subject to judicial review. Separate practical questions—building permits, infrastructure, access, expiration provisions, financing, and title—can remain after the land-use question moves forward.

The solution is not to add a paragraph of warnings to every listing. It is to build a small evidence set and choose language that matches it.

This example is explicitly hypothetical. It is not a reported transaction, parcel, case, outcome, or deadline calculation. It uses a verified City of Portland procedure to show how an Oregon land agent can turn local evidence into a bounded representation.

Hypothetical client claim: “The Portland property has final land-use approval, so we can market it as ready for development.”

Assumed document set: The seller provides what appears to be a City of Portland Type II land-use decision. No property address, project facts, decision date, outcome, or appeal event is asserted here. The agent must obtain those items from the actual file.

The City of Portland’s Land Use Review Appeals page says, “The appeal process, appeal fee and hearing body depend on the procedure type of the land use review decision being appealed.” For Type II and Type IIx decisions, the same page says a local appeal “must be submitted to the Director of Portland Permitting & Development within 14 days of the day the notice of decision is mailed.” Portland’s Land Use Decisions page adds that decisions may be appealed within 14–21 days “as outlined at the end of each individual decision document.”

Those official pages establish a procedure to check. They do not tell us whether our hypothetical document is authentic, whether it is Type II, when it was mailed, whether an appeal was filed, what the decision authorized, or what remains.

Evidence: Obtain the signed decision and notice from the City record. Match the file number, site identifier, decision type, decision-maker, scope, conditions, and mailing information to the seller’s document and proposed marketing statement.

What it supports: A match supports saying the file contains that specific City decision concerning that specific scope.

Still unresolved: Current review posture, satisfaction of conditions, later permits, and development feasibility.

Your next move:

Representation consequence: “The file contains a City of Portland Type II decision concerning [exact scope], subject to its conditions” is supportable only after those facts match. “Ready for development” still reaches beyond that evidence.

Evidence: Read the appeal instructions in the individual notice first. Then verify the current City record for a timely local appeal, a resulting hearing or decision, or written confirmation that the local record contains no appeal.

What it supports: The City’s general page tells you the Type II procedure; the individual notice and current record tie that procedure to the actual file.

Still unresolved: Whether a later LUBA proceeding exists and whether any professional interpretation is needed.

Your next move:

Timing consequence: Portland’s verified Type II local procedure uses 14 days from mailing of the notice. That is a local appeal checkpoint for that procedure—not the 21-day judicial-review provision in ORS 197.850.

Evidence: Search for a specific LUBA case or order and, if there is a LUBA order, verify any relevant Oregon appellate record. LUBA’s FAQ states that available local appeals must be completed before LUBA review.

What it supports: A named case number and actual order support a dated statement about what LUBA did. A current appellate record can support a statement about a petition or disposition.

Still unresolved: The legal effect on the property, remand work, later local action, and practical feasibility.

Your next move:

Spend consequence: A favorable local decision may justify the next scoped investigation. A pending or unknown review posture may justify delaying spend that cannot be recovered. This issue does not estimate a dollar amount or recommend a transaction outcome.

There are three checkpoints in this example: Portland Type II local appeal, an appeal to LUBA, and judicial review of a LUBA order. The numbers are easy to collapse, so keep the source and triggering event attached to each one.

Portland’s page also describes some decision types that go directly to LUBA, with a 21-day submission period from the date of decision. That is a description of the local-decision-to-LUBA transition—not a separate fourth appeal lane, and not the Type II local appeal used in our hypothetical.

For that LUBA-filing transition, LUBA’s current 2026 Rules of Procedure state in OAR 661-010-0015 that a notice of intent to appeal generally must be filed “on or before the 21st day after the date the decision sought to be reviewed becomes final,” subject to the rule and statutory exceptions. That is the lane for starting review at LUBA.

For the later judicial-review transition, ORS 197.850 governs judicial review after a LUBA order. Subsection (3)(a) says a petition in the Court of Appeals “must be filed within 21 days following the date the board delivered or mailed the order.” Subsection (3)(b) says filing and service on identified adverse parties of record are jurisdictional and “may not be waived or extended.”

None of those provisions supplies the deadline for a Portland Type II local appeal. None should be used here as a do-it-yourself deadline calculator. The operative notice, current rule, actual delivery or mailing facts, case record, and qualified advice control the real file.

The most defensible representation is often a short chain of nouns: decision type, date, scope, conditions, and verified review posture. “Approved” is useful only when those nouns sit behind it.

If this decision were on the table, OPB would read the individual local notice before any general webpage, then build forward through the local record, LUBA case number, and appellate record. The more irreversible the next move, the fresher and more specific the evidence should be.

Save a one-page Claim → Evidence → Branch note before publishing approval language:

Claim received: “Final land-use approval; ready for development.”

Evidence in hand: A seller-provided document described as a Portland Type II decision. Authenticity, property match, scope, conditions, mailing information, and current appeal records have not been verified.

Result: UNKNOWN. The broad claim is not established by this document set. This does not mean the approval is invalid or that an appeal exists.

Sentence to use now: “The seller has supplied a document described as a Portland Type II decision. Its scope, conditions, and current review status have not been independently verified; this description does not establish development readiness.”

Next scoped action: Obtain the official decision and notice through the City's land-use decision source, match the identifiers and scope, and check the current local record. Then follow any relevant LUBA/court record. Discuss reliance-dependent commitments with the client and qualified advisor; do not substitute this note for their decision.

What changes the note: A verified matching decision improves the document finding; a verified appeal changes the review-status finding; missing records keep that finding unknown. Neither a match nor silence in an index resolves every feasibility question.

The visual below is a phone-friendly reminder. The written steps and filled note carry the detail.

When the decision is located but review posture is incomplete:

When the documented search is favorable but you are not giving a legal conclusion:

When an appeal or remand is shown:

A builder or small developer can tie design authorization to the same evidence set: operative decision, conditions, current review posture, expiration language, infrastructure, and next permit. A lender or title/escrow team can turn finality into a document condition—identify the exact official source supporting the status used in underwriting or closing.

Those are different transaction decisions, but they should not require different facts from the agent. A clean agent file travels.

Trigger to monitor: A new document changes the hypothetical file’s review posture—a local appeal filing or decision, a LUBA notice/order, a Court of Appeals filing/disposition, or a remand decision.

Exact source trail: The individual Portland decision/notice and City record first; the LUBA final-opinions index and specific order second; the Oregon Court of Appeals record when relevant.

Decision change: Update the representation, the commitment allowed, and the person who must review the file. A favorable update can support a more precise statement and the next scoped spend. An adverse update can pause reliance. An unknown result keeps the statement narrow.

Where does a real Oregon approval file still leave you stuck: finding the operative decision, proving the local appeal result, locating a LUBA record, or explaining the status to a client?

Reply with the jurisdiction and the missing record—not a confidential client file. OPB may use the pattern to improve a future source-file guide.

If this would help an Oregon land agent, builder, lender, or landowner avoid overstating an approval, forward it their way.

If you found this useful, subscribe to Oregon Property Brief so you don’t miss the next Oregon property signal.