Portland, OR
One statewide code, and three counties still fighting over who reviews the permit
Oregon's building code statute makes the state's adopted edition the same requirement everywhere in the state and blocks a city or county from writing its own competing version. Greater Portland spans Multnomah, Washington, and Clackamas counties, a ring of separately incorporated cities, and a regional urban growth boundary a state-chartered government administers, none of which the code question resolves. The code is uniform. The office that reviews the permit is not, and that is what a supplement has to get right before it gets to the roof itself.
By Kyle Hamrick, Founder
The Estimate Company is run by a licensed independent insurance adjuster, with claims experience across many states, writing for contractors nationwide. What we bring to a Portland file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule.
That last part carries extra weight on a Portland-area file specifically, because the statewide rule and the address are further apart here than in most of the country. The code is settled the moment the state adopts an edition. Which office enforces it on a given roof, inside a metro built out of three counties and a ring of incorporated cities, is a separate determination every time.
A uniform code, a metro that is not uniform underneath it
The state preempts the code question. It does not preempt the map
Oregon's building code statute states plainly that the state building code is applicable and uniform throughout the state and in every municipality, and bars a city or county from enforcing a different requirement on the same subject without the state's own authorization. That is a genuinely unusual posture. Most of the states in this corpus run the opposite arrangement, where each city adopts its own edition and a supplement has to prove which one applies. In Oregon, the edition is not in dispute. The City of Portland's own current code record shows exactly that in practice: when the state adopted its 2023 edition, the City adopted it on the state's own effective date and phase-in schedule, administrative provisions first, construction provisions on a six month runway, rather than writing a Portland-specific alternative.
What that preemption does not touch is which office actually reviews a given permit. Greater Portland is not one building department behind one uniform code. It is the City of Portland's own Bureau of Development Services, a ring of separately incorporated cities each running their own permitting office, and three counties, Multnomah, Washington, and Clackamas, each administering their own unincorporated land. Multnomah County's own permit records confirm it issues permits only for unincorporated area, and separately maintains intergovernmental agreements with the cities of Portland, Gresham, and Troutdale to handle enforcement inside those cities instead. The code citation is identical no matter which of those offices holds the file. The office itself is not, and confirming it is the actual determination a Portland-area supplement has to make that a single-jurisdiction file never does.
A regional government that decides where the metro can grow, not how a roof is built
Layered above all three counties sits Metro, a regional government the Oregon Legislature created by statute in 1978 for one specific purpose: managing the Portland area's urban growth boundary, the line separating land planned for city services from land that is not. The Land Conservation and Development Commission approved the region's original boundary as consistent with the state's own planning goals in 1980, built from growth plans Clackamas, Multnomah, and Washington counties had already been assembling since the prior decade. State law has required Metro to keep a twenty year supply of land inside that boundary since 1997, reviewed on a set legislative cycle, with the boundary itself expanded many times since it was first drawn.
Metro does not review a roofing permit and does not sit inside the code question at all. What it does is make boundary and annexation status a real fact on a Portland-area parcel in a way it rarely is anywhere else in this corpus: whether an address sits inside a specific incorporated city, inside the boundary but still unincorporated, or newly annexed following one of Metro's periodic expansions, changes which building department's own amendment record actually reaches that roof. None of that shows up as a difference in the covering, the underlayment, or the flashing detail the state's uniform code requires. It shows up entirely in which office's letterhead the permit carries, which is exactly the kind of fact a supplement written from a generic Oregon reference has no way to catch.
Three code arguments specific to a Portland-metro roof
The edition is not local. The enforcement is
Every jurisdiction across this metro answers to the same statewide code edition on the same statewide timeline, and no city or county here has the authority to substitute its own version of a roofing requirement without the state's own sign-off. Code driven That means the citation itself travels cleanly from one Portland-area file to the next. Verify with local building dept The building department reviewing it does not, and gets confirmed for the specific parcel before the citation is written up.
A wildfire provision that is opt-in, not automatic
The Building Codes Division's own current amendment record lists a specific wildfire hazard mitigation provision alongside a separate document covering its local adoption, which confirms that provision is not folded into the statewide code uniformly the way the ordinary roof assembly requirements are. Whether it reaches a given Portland-area roof is a real question, not a copy-paste from a Medford or Bend file. Verify with local building dept Confirm local adoption status for the specific parcel before assuming either way.
A replacement threshold that still has to be confirmed, not assumed
The residential code's existing-building provisions carry a threshold where enough of a roof gets replaced or repaired that the remainder is brought up to the current standard alongside it, the same mechanism the Oregon state page identifies statewide. Verify with local building dept The specific percentage and its current wording get confirmed against the enforcing department for that parcel, not carried over from memory or from a different jurisdiction's file.
The carriers writing Portland, and where the jurisdiction question trips them up
State Farm, Farmers, and PEMCO carry a meaningful share of the residential book across the Willamette Valley, PEMCO among them as a Pacific Northwest regional carrier with real concentration in this specific metro. None of that carrier behavior is unique to Portland as a city; it is a Willamette Valley pattern the Oregon state page already covers. What is specific to this metro is a desk adjuster defaulting to whichever jurisdiction's amendment record they pulled last, because three counties and a ring of incorporated cities inside one carrier territory means the same adjuster is routinely working files out of Portland proper, Beaverton, Gresham, and unincorporated Washington County in the same week, each potentially carrying a different local amendment layered on the same statewide code.
That produces a specific failure mode: a code citation that was accurate on last week's Hillsboro file gets pasted into this week's Portland file without anyone checking whether the enforcing office, or its amendment record, actually matches. Confirming jurisdiction before the citation is written is what keeps that line from being the reason a carrier pushes back. Where a carrier holds out on a jurisdiction or code dispute specifically, the reinspection supplement answers that with the correct department and citation already confirmed, rather than starting the jurisdiction argument over from a blank page. A separate dispute over how much value an aging covering lost before the claim even started belongs to depreciation recovery, which runs on its own track entirely.
What gets recovered on a Portland roof file
Ordered by how often the item is missing when a file reaches our desk.
Status key: In scope. Usually omitted. Code driven. Verify with the authority having jurisdiction. Every status is spelled out in words beside the item, so nothing depends on color.
Confirmation of which building department actually issues the permit
Verify with local building dept
A Portland-area parcel can sit inside the City of Portland's own Bureau of Development Services jurisdiction, inside Gresham, Beaverton, Hillsboro, Lake Oswego, or another separately incorporated city, or in unincorporated Multnomah, Washington, or Clackamas County. Multnomah County itself only issues permits for unincorporated land and hands enforcement inside Portland, Gresham, and Troutdale to those cities under its own agreements. The code the reviewer applies does not change. The office that applies it does, and citing the wrong one produces a supplement that looks correct for an address it does not actually cover.
Statewide code edition and phase-in window confirmed against the permit date
Code driven
Oregon's building code statute makes the state's adopted edition applicable and uniform everywhere in the state, and the City of Portland's own current code record shows it adopting the state's ORSC edition on the state's own effective date and phase-in schedule rather than authoring a separate local edition. A supplement dated during a phase-in window has to confirm which edition actually governed the permit application date, not just the date of loss.
Local amendment or wildfire mitigation opt-in checked against the specific parcel
Verify with local building dept
The state's own code administration record shows wildfire hazard mitigation provisions handled as a named local-adoption option layered onto the statewide code rather than a single uniform requirement everywhere, which means whether that provision reaches a given Portland-area roof is a real question to confirm rather than an assumption to carry over from a different Oregon file.
Repair-versus-full-replacement threshold under the existing building provisions
Verify with local building dept
The residential code carries a threshold where enough of a roof's covering being replaced or repaired pulls the remainder up to current requirements, the same mechanism the Oregon state page identifies for the rest of the state. This page does not print an unverified percentage for it. Whoever holds the permit for that specific parcel is the one who states the number that actually applies, and that answer is pulled fresh rather than copied forward from an older file.
Annexation and boundary status checked before a city-specific code citation is written
Verify with local building dept
The urban growth boundary that Metro administers determines which land carries city services and which does not, and a parcel just inside or just outside a specific city's limits, or inside the boundary but still unincorporated, is not a cosmetic distinction. It determines which building department's own record and any local amendment actually apply, and that status is confirmed for the specific parcel before a jurisdiction gets named in the file.
Waste factor on hip, valley, and dormer-heavy rooflines across newer subdivision stock
In scope
Suburban growth inside the urban growth boundary in Hillsboro, Beaverton, and outer Clackamas County has produced subdivision rooflines with more hips, valleys, and dormer breaks than a simple gable, and a default 10 to 12 percent waste factor undercounts the real cut waste on that kind of roof. The percentage gets calculated from the roofline in front of us, not assumed.
Starter course at eaves and rakes
Usually omitted
A starter row has to be bought as its own product and installed as its own pass, and it is not something a crew improvises by flipping a leftover shingle upside down at the eave. Leave it off the invoice and the manufacturer's wind warranty for the entire slope above it stops applying, which is a real cost every time a Portland-area carrier estimate rolls it silently into the field shingle count.
Ridge system priced as three separate operations: the cut, the vent, and the cap
Usually omitted
The saw work to open the ridge slot, the labor to set the vent baffle into it, and the pass that lays purchased cap shingle over the assembly are three distinct operations on three different days more often than not, and an estimate that pays for the cap shingle alone is treating the other two as if they cost nothing to perform.
Decking condition documented as tearoff exposes it
Usually omitted
Older housing stock inside the original city limits and in some of the closer-in unincorporated pockets was decked before current fastening standards existed, and what a ground-level photo shows before tearoff rarely matches what the crew actually finds once the covering comes off. The condition gets documented as tearoff finds it, not assumed from the outside.
Detach and reset on solar arrays and rain-collection hardware
Usually omitted
Rooftop solar panels and rain-catchment tanks turn up often enough on this metro's newer construction that a crew has no way to work underneath either one, and the labor to pull that hardware clear of the deck and reinstall it once the new covering is on belongs on the invoice whether or not the carrier's original write-up ever priced it.
Overhead and profit on files spanning multiple permitting jurisdictions in one contract
In scope
A contractor running several roofs across this metro in the same stretch of work can be pulling permits from the City of Portland, a suburban city, and a county office inside the same crew schedule, and somebody has to track which submittal went where and under which office's fee schedule before the crews ever show up. That coordination cost is real and it does not scale down just because any one job on the schedule happens to be small.
Permit fee schedule confirmed for the specific issuing office
Verify with local building dept
Each incorporated city in this metro, along with Multnomah, Washington, and Clackamas counties for their own unincorporated land, runs its own fee schedule, and assuming one flat metro-wide number produces a figure that is wrong for most of the addresses it gets applied to.
Each becomes a written line with a reason attached, inside a real Xactimate file. Depending on the claim it ships as a roofing supplement, an Xactimate supplement package, a supplemental estimate, or a full claim estimate written from scratch.
What happens to your file after you send it
- 01
The line items get pulled apart against the parcel, not just the roof
Your measurements and photos go up against every line of the carrier's Portland-area number, and the review starts by asking whether the write-up was even built for the right office's rules, since a generic Pacific Northwest template misses a jurisdiction detail before it ever gets to the shingle.
- 02
Multnomah, Washington, or Clackamas gets identified before a single citation is drafted
The statewide code does not shift depending on which of the three counties or which incorporated city holds the parcel, but the enforcing office and its own amendment record absolutely do. That determination gets made and documented first, ahead of any code language going into the file.
- 03
The supplement is written in Xactimate and delivered as a PDF
Real file, real price list, real sketch. You get the PDF as the deliverable, and the ESX free any time you ask for it. Retail estimate work with no supplement attached delivers the ESX. Written same day or next day, submitted next day. One to three extra days on large commercial and multi structure work.
- 04
Nothing gets marked closed just because the carrier went quiet
Desk adjuster follow-up continues without a fixed cutoff, and if the file reaches the point where a carrier representative needs to walk the roof again, that reinspection gets built around the jurisdiction and code work already on record rather than starting over. A response typically lands within about three weeks, and silence on the carrier's side is not treated as a resolved claim here.
Two promises, stated separately
Promise one: the fee
The standard fee is 15 percent of supplemental recovery. If a file produces no additional approved recovery, you pay nothing on that claim. That is the whole fee structure, and it applies claim by claim.
Promise two: the guarantee
Send us an average of 2 claims per week for 12 months. If that volume does not produce a minimum of six figures in additional margin for your company, we write you a $5,000 check at the end of the 12 months. The volume, the 12 month term, the six figure threshold, and the $5,000 figure are one set of terms and they always travel together.
Two different promises, no overlap. The fee describes what a single claim costs you. The guarantee describes what a year of steady volume is worth. Nothing in the fee structure is a guarantee, and the guarantee does not change the fee.
Portland questions we get from contractors
Does a Portland-area re-roof answer to a different code than the rest of Oregon?
No. Oregon's building code statute makes the state code applicable and uniform statewide, and bars a city or county from enforcing a different requirement on the same subject without the state's own authorization. The Bureau of Development Services administers that same statewide code inside Portland city limits, on the same edition and the same adoption timeline the state set, rather than writing its own competing version the way a city in a municipal-adoption state might. The code answer for a Portland re-roof is not a local invention.
If the code is the same everywhere in Oregon, why does jurisdiction still matter on a Portland file?
Because a uniform code answer does not mean a uniform permitting office. Greater Portland spans Multnomah, Washington, and Clackamas counties, plus a ring of separately incorporated cities inside those counties, and a county government here does not administer its own building code countywide the way that phrase implies. Multnomah County issues permits and keeps permit records only for unincorporated land, and it has separate agreements with the cities of Portland, Gresham, and Troutdale to handle enforcement within their own boundaries. The code citation does not change from one side of a city limit to the other. Which office actually reviews the permit does.
What is Metro, and does it have any say over a roofing permit?
Metro is a regional government the Oregon Legislature created in 1978 specifically to manage the Portland area's urban growth boundary, the line that separates land with city services from land that does not have them. It is not a building department and it does not review a roofing permit. It matters here because it is a second, genuinely regional layer of authority above the county level that most of this corpus's metros do not have at all, and it is part of why a Portland-area jurisdiction question can turn on annexation and boundary status in a way a single-county metro's never does.
Does Portland's climate change what gets missed on a supplement?
The wind-driven rain and moss pattern that drives a Willamette Valley claim is real on a Portland roof specifically because Portland sits inside that valley, and that mechanism is argued in full on the Oregon state page rather than repeated here. What this page adds is the layer above the roof itself: confirming which of several possible building departments and code amendment records actually governs a specific Portland-area parcel before a citation goes into the file, since that confirmation step is a real determination on this metro in a way it is not on a single-jurisdiction one.
How fast is turnaround, and what does it cost?
Estimates are written same day or next day and submitted next day. Larger commercial and multi structure files take one to three extra days, said up front. Carrier response runs about three weeks as a general expectation. The standard fee is 15 percent of supplemental recovery, and a file with no additional approved recovery owes nothing on that claim.
What does a Portland supplement typically recover?
On claims where the roof is already approved for full replacement, our own closed files show a median recovery of about $4,000, with half landing between roughly $1,800 and $9,500. Claims that start denied or repair-only run far higher.
Portland and the Oregon market
Portland anchors the north Willamette Valley inside the wider Oregon market, distinct from Salem and Eugene further south in the same valley and from Bend and Medford on the other side of the state. Gresham, Hillsboro, and Beaverton send files from this same metro too, each one run past its own building department's amendment record and its own jurisdiction answer before any citation reaches the supplement.
Send one file from this metro and find out which office actually holds it
Forward the carrier write-up along with the parcel's street address and your own measurements. The county and city question gets settled first, the statewide code gets applied against whatever tearoff actually shows, and a rewritten scope lands back in your inbox the next business day.