Spokane, WA
Spokane runs its own wildfire code. Most reroof estimates never check it
Washington's statewide wildfire construction chapter is on hold, waiting on statewide hazard maps that are not finished. The City of Spokane did not wait. It adopted its own International Wildland-Urban Interface Code by city ordinance, which changes what roof assembly is even allowed on a City of Spokane parcel, separate from the freeze-thaw winters and dry summer wind that already make this side of the Cascades a different roof than a Puget Sound one.
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 Spokane file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule.
That last part matters more on a Spokane file than most, because the state and the city do not have the same answer on wildfire construction requirements right now. Washington's own statewide chapter is reserved, pending hazard maps the state has not finished. The City of Spokane adopted its own version anyway, under authority state law gives any city to do exactly that, and a supplement that only checks the state rule will miss the one actually governing the parcel.
What actually damages a Spokane roof, and why the code question is not settled
The state's wildfire chapter is reserved. The City's is not
Washington's building code statute lays out a statewide wildfire construction standard, but that standard only enters the state building code once a statewide wildfire hazard map and a base-level risk map for every county are finished, and those maps are still in draft. Until they are complete, the statewide chapter sits reserved rather than enforced. The same statute separately authorizes any county, city, or town to adopt the wildfire code locally, in whole or in part, on its own timeline, without waiting on the state maps at all.
The City of Spokane used that authority. It adopted the International Wildland-Urban Interface Code by its own municipal ordinance, tying the adopted edition to whatever building code edition the state has in effect, and folded it into the City's own construction standards title. That means a re-roof inside Spokane city limits is reviewed against a wildfire-construction standard today, while a comparable roof a few miles away, outside the city's jurisdiction and without its own local adoption, may not be. That split runs along a jurisdiction line, not a peril line, and it is the kind of fact a supplement written from a generic Washington code reference has no way to catch. Confirming which office actually issues the permit for a given Spokane-area parcel, city, county, or a neighboring incorporated jurisdiction, is a real step that changes which code citation belongs in the supplement.
A dry continental climate that ages a roof on its own separate clock
Spokane sits east of the Cascades in a dry continental climate: hot, dry summers with sustained wind, and cold winters that put a roof through real freeze-thaw cycling rather than the sustained wet-season moisture that drives claims on Puget Sound. That cycling works flashing loose at wall and chimney intersections and strains shingle seals through the winter months, while dry summer heat and UV exposure age the shingle mat on its own separate schedule, without the humidity that would otherwise slow it down.
None of that is a hail-belt damage pattern in any consistent sense, and a supplement built around bruise counts is solving a problem this market mostly does not have. The wind and freeze-thaw wear that actually shows up on a Spokane roof needs its own documentation, not a checklist built for a different peril. The roof claim inspection checklist is the field sequence that gets ridge, hip, and flashing condition documented before a tear off erases the evidence a wind or freeze-thaw claim depends on.
Three code arguments specific to a City of Spokane roof
The City's own Wildland-Urban Interface ordinance, not a borrowed state rule
Spokane Municipal Code adopts the International Wildland-Urban Interface Code directly, by ordinance, with its own enforcement section naming the City's building and fire code officials as the authority. The adopted edition tracks whatever building code edition the state currently has in effect, but the adoption itself is the City's own act, not a pass-through of a statewide requirement. Verify with local building dept Confirm the currently enforced edition and any local amendment with the City of Spokane before the citation goes into the file.
Class A roof assembly rating is the line that changes the covering choice
The wildfire code standard requires a Class A rated roof assembly, tested to a recognized standard, and where a covering profile leaves a gap over the decking at the eave, that gap has to be fire-stopped or backed with a specified cap sheet. A supplement that specs a covering purely on price without confirming it clears that rating for a City of Spokane parcel is pricing an assembly the permit reviewer can reject outright.
A replacement threshold that a hail or wind claim can cross without anyone intending it
The underlying wildfire construction standard reaches a roof covering that is replaced, or that has half or more of it replaced inside a twelve month period, treating that scope like new construction for assembly purposes. A large hail or wind loss that ends up covering most of a roof can cross that threshold on its own, which means the wildfire-code roof assembly question belongs in the file even when the claim started as an ordinary storm loss with nothing to do with fire.
The carriers writing Spokane, and where the first estimate defaults wrong
State Farm, Farmers, and Allstate write a meaningful piece of the residential book across eastern Washington the same way they do statewide, alongside regional and mutual carriers active in the Spokane market including Mutual of Enumclaw and Grange Insurance. PEMCO, the Seattle-headquartered regional carrier the state page discusses at length for its Puget Sound moisture habits, is a different animal on a Spokane file: the freeze-thaw and wind pattern here is not the loss type that carrier's settled habits were built around on the wet side of the state, and a desk adjuster more familiar with coastal moisture claims tends to underestimate what a real eastern Washington winter and a dry summer actually do to an older roof.
A separate and more specific dispute shows up on Spokane files: whether the wildfire construction standard even applies to the parcel. A carrier estimate written before anyone confirmed the City of Spokane's own Wildland-Urban Interface ordinance, or written for a parcel just outside city limits where no equivalent local adoption has been confirmed, can either miss a real code requirement or assume one that does not actually reach that address. Getting the jurisdiction question right before the code argument is written is what keeps that line defensible when a desk adjuster pushes back on it.
A carrier holding out on the wildfire-code line specifically will often ask to put a representative back on the roof before signing off, and the reinspection supplement answers that visit with the ordinance citation and the photos already in hand instead of relitigating the code question cold. Where age or condition knocked value off the covering itself, depreciation recovery is the separate fight.
What gets recovered on a Spokane 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.
Class A rated roof assembly confirmation under the City's Wildland-Urban Interface code
Code driven
The City of Spokane adopted the International Wildland-Urban Interface Code by its own ordinance, and that code sets a Class A rating requirement for the roof assembly, tested to a recognized standard, on the covering types it reaches. An estimate that specs a covering by price alone, without confirming it clears that rating for a City of Spokane parcel, is pricing an assembly the permit reviewer can reject.
Eave gap fire-stopping where the covering profile allows a space over the decking
Code driven
Certain roof covering profiles leave a gap between the covering and the deck at the eave, and the wildfire code standard requires that gap fire-stopped, or a mineral-surfaced cap sheet installed underneath, so embers cannot work their way in from below. A supplement written to a generic eave detail skips this because it is not a defect the eye catches from the ground.
Fifty-percent-replaced trigger review for the covering across the whole roof
Verify with local building dept
The wildfire code standard reaches an existing roof covering that gets replaced, or that has half or more of it replaced within a twelve month window, treating that like new construction for assembly purposes. A hail or wind claim that ends up covering most of the roof can cross that threshold without anyone intending a full wildfire-code upgrade, so the percentage actually being replaced needs to be checked against the threshold before the covering gets specified.
Confirmation of which building department actually has the parcel
Verify with local building dept
The City of Spokane, Spokane Valley, and unincorporated Spokane County run separate permitting and separate code adoption records, and the wildfire code question does not resolve the same way in all three. A code argument built for a City of Spokane address does not automatically transfer to a parcel a few blocks over in a different jurisdiction, so the enforcing office gets confirmed before the citation goes into the file.
Underlayment upgraded for winter freeze-thaw exposure rather than a wet-coastal spec
In scope
A Spokane roof spends real weeks each winter cycling through freeze and thaw rather than sitting under sustained coastal rain, and an underlayment spec pulled from a Puget Sound job file assumes the wrong exposure. The material needs to be rated for repeated freeze-thaw cycling at this elevation, not for a mild, wet, low-freeze coastal winter.
Ice barrier at eaves, confirmed against the currently adopted amendment for the parcel
Verify with local building dept
Jurisdictions on this side of the mountains sometimes carry an eave ice barrier requirement that a west-side estimate never has occasion to write, and it exists because of the freeze-thaw pattern a Spokane winter actually runs. Confirm the current requirement and coverage extent for the specific parcel rather than defaulting to a Puget Sound assumption.
Ridge cap and hip shingle reset after sustained dry-season wind loading
Usually omitted
Sustained wind on the dry side of the state works at ridge and hip lines over the course of a season, lifting and creasing tabs without leaving a bruise a hail-focused inspection would look for. A carrier estimate written to a hail checklist treats the ridge as a finishing detail rather than the plane most exposed to that wind, and prices the cap without the venting and closure work the exposure actually requires.
Granule loss and mat embrittlement from sustained summer heat and UV
Usually omitted
Spokane's dry continental summers put asphalt shingles through sustained heat and UV exposure without the humidity that would otherwise slow the mat's aging, and that accelerated brittleness reads as ordinary wear unless it is tied to the specific claim event rather than treated as pre-existing weathering.
Flashing and step flashing rebuilt at wall and chimney intersections after freeze-thaw movement
Usually omitted
Repeated freeze and thaw cycling works flashing loose at wall and chimney intersections over a Spokane winter in a way a single wet-season storm never does, and putting that same flashing back down on tear off is a shortcut a rushed estimate takes even after the seal underneath it has already given out.
Decking replacement for sections found compromised during tear off
Usually omitted
Freeze-thaw cycling and wind-driven moisture intrusion work on sheathing from the underside over more than one season, and nobody can see how far that damage traveled until the crew has the old covering stripped off, so the sound-deck assumption a ground-level estimate makes rarely survives tear off.
Defensible-space and vegetation clearance documentation where the parcel sits near wildland fuel
Verify with local building dept
The Wildland-Urban Interface code framework this City has adopted is paired with defensible-space expectations around the structure itself, and a property backing to open land or dry vegetation may have site conditions that affect what the code review expects, separate from the roof assembly question. Confirm the site condition with the enforcing department rather than assuming it does not apply because the damage itself is roof-only.
Permit fees and inspection sequence specific to the enforcing jurisdiction
Verify with local building dept
The City of Spokane, Spokane Valley, and Spokane County each run their own fee schedule and inspection sequence, so the correct number is only knowable once someone has pinned down which of the three offices actually holds the parcel, not by assuming one flat countywide figure.
Overhead and profit on multi-trade freeze-thaw and wind files
In scope
A winter loss that touches the roof covering, the flashing run, and interior ceiling drywall from a single freeze-thaw leak lands on three separate trade schedules at once, and keeping the drywall crew off the roof until the flashing is sealed is a sequencing job somebody gets paid to run. That is what the markup compensates, not the invoice total.
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 carrier's number gets checked against the roof, side by side
Every line of the Spokane estimate gets set beside your own measurements and photos, and we mark each spot where the price list defaulted to a coastal wet-season assembly or a hail-belt damage checklist instead of pricing what a dry-side winter and a dry-side summer actually did to this roof.
- 02
Spokane's own ordinance record gets checked before anything is cited
For a parcel inside Spokane city limits, that means the City's current building code edition alongside the City's own Wildland-Urban Interface Code ordinance, confirmed against that specific address rather than assumed from the county or the state. A parcel in Spokane Valley or unincorporated Spokane County gets checked against that jurisdiction's own record instead.
- 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
We stay on the file until the carrier answers
We keep calling the desk adjuster for as long as your file sits open, and once there is enough documented to justify bringing a carrier rep back to the roof, we build the reinspection request around it. Three weeks is the general expectation for a response, and a quiet carrier does not mean a closed file on our end.
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.
Spokane questions we get from contractors
Does Spokane have its own wildfire building code, or does it follow the state?
The City of Spokane adopted the International Wildland-Urban Interface Code on its own, by city ordinance, ahead of the state. Washington's statewide wildfire code chapter is currently reserved, on hold until statewide wildfire hazard maps are finished, but state law lets a county, city, or town adopt the wildfire code locally regardless, and Spokane did exactly that. A roof inside Spokane city limits answers to a wildfire-construction code today that a property just outside those limits may not, which is a real difference for a re-roof, not a theoretical one.
What does the Wildland-Urban Interface code actually require on a roof?
The core roofing requirement is a Class A rated roof assembly, tested to a recognized standard, plus attention to any gap between the roof covering and the decking at the eave so embers cannot get underneath it. The code also reaches exterior walls, decks, and other projections, but the roof assembly rating is the piece that shows up first on a supplement, because it changes what covering and underlayment combination is even allowed on that address, not just how thick the shingle is.
Does a Spokane wildfire code requirement apply to a normal re-roof, or only after a fire?
It is not limited to rebuilding after a total loss. The underlying state provision, and the version the City of Spokane adopted, reach an existing roof covering that gets replaced, or that has half or more of it replaced within a twelve month period, and any roof addition. A hail or wind claim that ends up putting a new covering across most of the roof can trigger the same ignition-resistant assembly requirement as a rebuild, which is easy to miss if the file gets written like an ordinary reroof supplement instead of checking the City's adopted wildfire chapter first.
Why does the parcel's exact jurisdiction matter so much on a Spokane-area file?
Spokane is not one building department. The City of Spokane, Spokane Valley, and unincorporated Spokane County each run their own permitting and their own code adoption record, and the wildfire code question in particular does not have the same answer in all three. A city ordinance can be in effect on one side of a boundary line and simply not exist on the other side of it, so confirming which office actually issues the permit for that specific parcel is a real determination on a Spokane-area file, not paperwork.
Is Spokane a hail market, and how does that compare to the wet side of the state?
Spokane sits east of the Cascades in a dry continental climate that runs hot summers, cold winters, and real wind, which is a different damage profile than the sustained wet-season moisture and moss that drives claims on Puget Sound. Freeze-thaw cycling works on shingle seals and flashing through a Spokane winter far more aggressively than anything a Seattle roof goes through, and dry summer heat with sustained wind ages asphalt shingle on its own separate clock. Neither market is a hail-belt state in the way the Front Range or the Southern Plains are, and a supplement built around bruise counts is not the right tool east of the mountains or west of them.
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.
Spokane and the Washington market
Spokane anchors the Inland Northwest, the eastern Washington market inside the wider Washington market, sitting apart from Seattle and Tacoma on the wet side of the Cascades. Files also come in from Spokane Valley and unincorporated Spokane County, each checked against its own building department's adopted code and its own answer on the wildfire construction question before a citation goes into the supplement.
Send one Spokane file and see what the jurisdiction check turns up
Send the carrier's write-up, your measurements, and the parcel address. We confirm which building department actually governs that roof, check it against the City of Spokane's own Wildland-Urban Interface ordinance where it applies, and write the supplement against the assembly and the freeze-thaw or wind damage actually on that roof, back to you next day.