Coastal lot is not a normal lot

The risk: A normal-looking Oregon coastal lot should not be treated like an ordinary residential parcel until the coastal hazard/source file is built.

Primary reader: Oregon coastal land agents advising buyers or sellers.

Secondary reader: Coastal property buyers building a due-diligence file.

Issue lane: Risk File.

What changed or surfaced: The official source stack includes the DOGAMI Tsunami Inundation Map Series, Oregon DLCD’s Goal 18: Beaches and Dunes, and the FEMA Flood Map Service Center, plus local floodplain and overlay checks, shoreline/access questions, and professional follow-up before pricing, listing, lending, designing, or advising.

Why this matters this week: Evergreen Field Guide — use it before pricing, listing, touring, financing, or designing around an Oregon coastal lot.

What this does NOT prove: No map, zoning label, tax lot, address, prior structure, or planning-desk comment by itself proves a specific coastal parcel is buildable, financeable, insurable, safe, entitled, or ordinary.

What to check first:

Forward this to: A buyer, seller, land agent, lender, title contact, builder, designer, or coastal property client who is tempted to rely on ordinary-lot language.

The common question:

“Is this coastal lot buildable?”

The better OPB question:

“What belongs in the coastal hazard source file before anyone treats this as an ordinary lot?”

A coastal parcel can look simple in a listing.

It may have a tax lot. It may have an address. It may have road frontage, a zoning label, a prior structure, utility hints, ocean proximity, or a view that makes the whole file feel more valuable.

That is exactly why Oregon coastal property needs a different first question. The issue is not whether one source looks promising. The issue is whether the whole coastal hazard file supports the next property decision.

For Oregon buyers, coastal land agents, landowners, builders, lenders, designers, surveyors, planners, and due-diligence consultants, that file matters before pricing, listing, lending, designing, advising, or making a clean-sounding client statement.

This week’s OPB is not a parcel-specific legal opinion. It is not engineering advice, insurance advice, underwriting advice, title advice, appraisal advice, brokerage advice, or a claim that any map proves a specific parcel is buildable or unbuildable.

It is a practical Oregon source-file workflow for coastal lots.

A normal-looking coastal lot can sit at the intersection of several different questions:

Those are not the same question.

A zoning label can help. A tax map can help. A DOGAMI map can help. A FEMA or local floodplain page can help. A local planning desk email can help. A geotechnical report can help.

But none of those should be treated as the whole answer by itself.

That is the coastal trap: one official-looking source can create more confidence than the file actually supports.

The practical move is to stop asking one source to do too much. Build the file by source category, then write down what each source does and does not prove.

This is no longer just a generic “coastal planning” caution. The current state links support the lane.

Oregon DLCD’s Goal 18 page says Goal 18 “prohibits development on the most sensitive and hazardous landforms along the coastal shoreline, including beaches, active foredunes, and other dune areas subject to severe erosion or flooding.” The same page says Goal 18 “limits the placement of beachfront protective structures to shoreline areas that were developed prior to 1977,” and describes those structures as shoreline armoring techniques such as riprap and seawalls.

The official Goal 18 PDF also gives the file-level reason to slow down. It says coastal areas subject to the goal include “beaches, active dune forms, recently stabilized dune forms, older stabilized dune forms and interdune forms.” It also says uses should be based on the “capabilities and limitations of beach and dune areas” and the need to protect areas of critical environmental concern, scenic/scientific/biological importance, and significant wildlife habitat.

The Oregon Coastal Management Program’s Coastal Hazard Mitigation page connects those planning goals to local files. It says coastal hazard planning is guided by Statewide Planning Goal 7, Goal 17, and Goal 18, and that “These goals require local governments to identify and plan for the dynamic and potentially hazardous nature of coastal areas, particularly along the ocean shore.” It also says all cities and counties must account for natural-hazard areas in their comprehensive plans and associated ordinances.

That does not mean every coastal lot is unbuildable. It means OPB should not treat “zoned residential,” “tax lot,” “near utilities,” “prior structure,” or “ocean view” as the end of the file.

It means state coastal planning, local implementation, DOGAMI tsunami/hazard resources, FEMA/local floodplain or overlay checks, shoreline/access questions, and professional follow-up may all belong in the file before anyone makes a clean client-facing claim.

The important distinction: The useful question is not whether a coastal map, zoning label, tax lot, address, or prior structure looks promising by itself. The useful question is whether the source file supports the next decision: pricing, listing, lending, designing, advising, or moving toward a professional review.

If this decision were on the table: OPB would start by separating the coastal file into source lanes — state coastal planning, DOGAMI tsunami/hazard resources, FEMA/local overlays, shoreline/access questions, and professional transaction follow-up — before relying on ordinary residential-lot language.

Save this before your next coastal property conversation:

A coastal lot is not “ordinary” until the source file shows which hazard, access, local-review, professional, lending, insurance, and title questions still remain.

The Oregon Department of Geology and Mineral Industries’ Tsunami Inundation Map Series is one of the core source lanes for a coastal file.

DOGAMI says it has “been identifying and mapping the tsunami inundation hazard along the Oregon coast since 1994.” Its TIM overview also says that, “[u]sing federal funding awarded by NOAA,” DOGAMI developed “a new generation of tsunami inundation maps to help residents and visitors along the entire Oregon coast prepare for the next Cascadia Subduction Zone (CSZ) earthquake and tsunami.”

That matters because it tells a reader this is not a random map layer. It is an official hazard-planning source with a long Oregon Coast program history.

DOGAMI also says its TIM series maps “incorporate all the best tsunami science that is available today,” including updated computer simulation models using high-resolution lidar topographic data and lessons from the 2004 Sumatra, 2010 Chile, and 2011 Tōhoku earthquakes and tsunamis. DOGAMI says each publication includes two plates: “one showing local-source (Cascadia Subduction Zone) and one showing distant-source (Alaska-Aleutian Subduction Zone) tsunami inundation scenarios.” For Cascadia, DOGAMI says TIM Plate 1 displays five “T-shirt sizes” — S, M, L, XL, and XXL — intended to bracket a range of impacts.

For a coastal buyer, agent, builder, or advisor, that is useful source-file context.

It can help answer:

But here is the client-safe boundary:

A DOGAMI tsunami map is not a yes/no buildability letter. It is not a lender approval. It is not an insurance quote. It is not a geotechnical design. It is not a local land-use decision. It is not a promise that a site is safe, unsafe, permitted, unpermitted, financeable, or unfinanceable.

It is one source in a coastal hazard file.

That distinction is the point of this issue.

For a first-pass Oregon coastal lot file, separate the sources into five lanes.

Start with state coastal-planning context, including beaches and dunes, coastal hazards, and the local jurisdiction’s implementation path.

The reader move is simple: identify the current state coastal-planning source, then confirm how the city or county implements it. Do not stop at “zoned residential.” Coastal planning context may live outside the easiest zoning-label summary.

Ask:

Which state coastal planning or beaches/dunes source should be reviewed for this property, and which local code or checklist implements it?

Pull the relevant DOGAMI tsunami resource into the file.

At minimum, note the source name, map series or viewer, publication date if available, community or map sheet, scenario language, and what the map is being used for.

The right file note sounds like:

DOGAMI tsunami source reviewed for hazard-planning context. This note does not determine buildability, structural design, insurance, lending, title, or local approval.

That kind of sentence is boring. Boring is useful. It keeps the file from turning a map screenshot into a conclusion.

A coastal file should usually include a federal and local hazard/overlay check.

FEMA describes its Flood Map Service Center as “the official public source for flood hazard information produced in support of the National Flood Insurance Program (NFIP).” FEMA also says to use the MSC to find an official flood map and access other flood-hazard products, while warning that effective information downloaded or printed from the site “may change or become superseded by new maps over time.”

That may mean FEMA flood map review, city or county floodplain development pages, local coastal overlay districts, erosion or landslide references, and any local mapping or permit checklist that the planning desk points to.

Use this lane carefully. A federal flood map or local overlay page can show that another source needs to be checked. It does not automatically answer the full transaction, design, or entitlement question.

Ask:

Is there a local floodplain, erosion, coastal overlay, geologic hazard, or natural-resource layer that changes the planning, building, survey, engineering, insurance, or transaction file?

Then document the answer source by source.

Oregon coastal property can raise questions that do not fit neatly into a normal residential-lot checklist.

Examples include beach access, public-right issues, riparian or shoreline context, bluff or dune conditions, and whether shoreline protective structures, repairs, or stabilization concepts are even in the conversation.

Do not make a casual legal statement here. Do not tell a client a structure is allowed, grandfathered, prohibited, repairable, or transferable unless the proper legal, local, or professional source supports that exact claim.

The safe file note is narrower:

Shoreline/access/protective-structure questions may require local planning, legal, survey, engineering, and state-source review before client-facing conclusions.

That sentence does not sell the property. It protects the file.

The final lane is where many coastal files become real.

The source stack may point toward geotechnical review, coastal engineering, surveying, local planning interpretation, title review, insurance availability, lender requirements, appraisal questions, or construction-design constraints.

This is where the OPB rule is simple:

If the source file points to a professional question, do not convert that into a casual conclusion.

Write down the follow-up.

Use this as the main artifact for the issue. The goal is not to “clear” a property in one sitting. The goal is to build the file before anyone relies on ordinary-lot language.

Planning-desk question:

Which state coastal planning or beaches/dunes source should be reviewed for this property, and which local code or checklist implements it?

Planning-desk/professional question:

What DOGAMI tsunami source or evacuation-resource page should be included in the file, and who should interpret it for design, emergency planning, or transaction use?

Question:

Does floodplain status create a local permit, elevation, insurance, survey, or lender documentation question?

Question:

Besides base zoning, what overlay or hazard chapters should be reviewed before this property is described as ordinary residential land?

Question:

Are shoreline, access, beach, dune, bluff, or protective-structure questions present, and who can answer them in writing?

Check each item as “not needed,” “possibly needed,” “needed,” or “unknown”:

End the file with a plain-language note:

This coastal lot source file identifies planning and hazard sources that should be reviewed before relying on ordinary-lot assumptions. It does not determine buildability, legal rights, engineering feasibility, insurance availability, financing approval, title status, appraisal value, or local entitlement outcome. Those questions require the appropriate agency, professional, or transaction-party review.

That one paragraph may be the most important part of the checklist.

Avoid these shortcuts:

Safer language:

“This appears to be a coastal lot where the source file should include state coastal planning context, DOGAMI tsunami resources, FEMA/local overlay checks, shoreline/access questions, and professional follow-up before anyone relies on ordinary-lot assumptions.”

That is not as punchy as a listing headline. It is more useful.

For builders and designers: Do not begin with ordinary-lot assumptions. Ask which coastal hazard, floodplain, geologic, shoreline, access, and local review sources must be checked before design scoping or schedule claims.

For land agents and brokers: Keep listing and client language source-safe. A zoning label, view, road frontage, tax lot, or prior structure should not become a buildability promise without the supporting file.

For lenders, title, and escrow: Ask whether the file separates hazard-map context, floodplain/local overlay questions, title/access issues, insurance follow-up, and professional reports instead of treating one screenshot as proof.

For landowners, buyers, and investors: Before pricing or making an offer, build the source index and write down what each source does and does not prove.

For planners, consultants, surveyors, and advisors: Help the client identify the correct official source lane and the professional follow-up question; do not let source references become parcel-specific conclusions without the right review.

Pick one Oregon coastal property — a listing, client question, old lead, family parcel, or hypothetical file.

Build a one-page source index:

If you cannot fill in those seven lines, the lot is not ready to be treated like an ordinary lot.

There is no single statewide date that resolves a coastal lot’s source file. The meaningful trigger is a change in an official source or in how a state or local agency applies it.

OPB is watching DOGAMI, Oregon DLCD and the Oregon Coastal Management Program, FEMA, and Oregon coastal cities and counties for:

What would change the decision: a new or revised source that adds a mapped constraint, changes the review lane, requires additional documentation or professional analysis, or makes prior client-facing language unsafe to repeat.

When one of those triggers appears, OPB will trace it to the controlling source and explain what changed, what it does not prove, and what readers should verify next.

If this would help someone who is looking at, listing, financing, designing, or advising on an Oregon coastal property, forward it their way.

Reply with the Oregon coastal city, county, or hazard source you wish more buyers checked before making an offer, listing a property, quoting a build path, or advising a client.

The most useful replies are specific:

Those replies help OPB build better coastal source monitoring without turning local anecdotes into unsupported claims.

If a coastal property looks simple on a listing page, build the hazard/source file before you price, lend, design, or advise.

OPB’s Oregon Coastal Lot Hazard File Checklist walks through the state coastal planning, DOGAMI tsunami/hazard, FEMA/local overlay, shoreline/access, and professional follow-up questions to document first.

Reply “coastal checklist” and I’ll send the one-page version.

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

Use these as source orientation, not parcel-specific approval proof:

OPB note: this issue intentionally does not make parcel-specific buildability, legal, engineering, geotechnical, insurance, lender, appraisal, title, brokerage, or entitlement conclusions. It is a coastal source-file workflow for first-pass due diligence and professional follow-up.