Seattle, WA
Seattle rarely sees a catastrophe. That is exactly why a real storm loss gets called maintenance
Most of this business argues that storm damage is being written off as ordinary wear by a carrier that does not want to pay for it. In Seattle the argument runs the same direction for a different reason: this is a low-hail, low-catastrophic-event market where persistent damp and moss are the normal condition of an older roof, so a desk adjuster's default read on almost any file is maintenance. A genuine wind or impact loss still happens here, and it has to be pulled out of a decade of ordinary damp before the carrier will treat it as anything else.
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 Seattle file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule.
That confirmation matters differently on a Seattle file than on most others in this business. A market that rarely produces a catastrophic event trains the desk adjuster to expect wear, not storm damage, on almost every roof that crosses the file. Proving a real event happened at all, on its own dated evidence, is the actual fight here, not proving the event was severe enough to matter.
A quiet market where the carrier's default assumption works against the claim
Low catastrophe, high moss, and a carrier that expects wear by default
Seattle's marine climate does not produce the kind of hail or catastrophic wind event that trains a desk adjuster to expect a storm loss on sight. What it produces instead is a long, wet season that keeps roof decking damp for weeks at a stretch, and persistent moss and organic growth on shaded and north-facing slopes that colonize a roof over years rather than one event. That is a real, ordinary condition of an aging Seattle roof, and most of the time a carrier's instinct to call it maintenance is not wrong on its own terms.
The problem shows up on the roof that has both kinds of damage on it at once. In a market that mostly produces slow, cumulative wear rather than dramatic weather, a genuine wind tear or impact crease reads to an adjuster as just one more sign of an old roof unless something specifically marks it as different. That inverts the usual fight in this business. Elsewhere the argument is proving a storm was severe enough to justify a full replacement. On a Seattle file the argument is often more basic than that: proving a discrete event happened at all, against a backdrop the carrier is already primed to write off as age no matter what.
Two departments, one metro area, and a boundary that decides which one applies
The City of Seattle administers its own adopted building and residential codes, each one carrying amendments specific to the city on top of the underlying model code editions, through the Seattle Department of Construction and Inspections. King County's own permitting office describes its own scope plainly: it provides permitting and code enforcement to the unincorporated areas of King County, not to the incorporated cities inside it. That means a parcel inside Seattle's boundary and a parcel just outside it, in unincorporated King County, do not automatically answer to the same office or the same amendment record, even when both addresses would get described the same way in casual conversation.
That split is a real determination on a Seattle-area file, not a formality. A supplement built for a City of Seattle parcel does not necessarily transfer to a King County one a few blocks over, and confirming which office actually reviews the permit for a specific address is a step that belongs ahead of any citation going into the file rather than something to discover after a permit comes back questioned. The roof claim inspection checklist is the field sequence that documents storm-dated damage location before a tear off erases the pattern a wind or impact claim depends on.
Three arguments specific to a Seattle roof file
A storm event has to be proven, not just described, in a low-catastrophe market
The single most useful thing a Seattle file can do is show a specific, dated damage pattern, a wind tear, a crease, an impact mark, in a specific location, rather than a general statement about the roof's condition. In scope A carrier working from a low base rate of storm claims in this market will read an undated, general description as more evidence for the maintenance theory it already favors.
The City's own amended code, administered by its own department
Seattle's own building and residential code pages state that the City has adopted the underlying model code editions with amendments specific to the city, and that SDCI administers them. Verify with local building dept The specific amendment content and the currently effective edition, since a further update was still in development at the time of this build, get confirmed with SDCI directly rather than assumed from a prior file or a different jurisdiction.
City limits, not the metro's reputation as one area, decide the reviewing office
King County's own permitting office states it serves unincorporated area only, which means an address inside Seattle and an address just outside it are not interchangeable for permitting purposes even though both sit inside the same metro area people describe as one place. Verify with local building dept Confirm which office actually has the parcel before a citation is written, not after a permit gets returned questioned.
The carriers writing Seattle, and where the maintenance assumption shows up first
State Farm, Farmers, and Allstate all carry substantial residential volume in Seattle, mirroring their statewide presence. PEMCO is the carrier worth naming specifically here: headquartered in Seattle, it holds real concentration in this exact market, and its desk has spent decades pricing exactly the kind of damp, slow-wear roof that dominates this climate. That depth of local pattern is precisely what makes the maintenance instinct so strong on a PEMCO file in particular, not a weakness unique to a national carrier working from a generic template.
The dispute that actually recurs on a Seattle claim is not about whether damage exists. It is about what caused it. An adjuster will often agree the roof shows granule loss and organic growth and stop there, filing the whole claim under age rather than isolating the discrete wind or impact event a contractor is actually trying to get paid for. Closing that argument takes located, dated evidence pointed at one specific spot on the roof, not a general description of how tired the covering looks.
Where a carrier will not move past that causation argument on its own, the reinspection supplement puts a representative back on the roof with that dated evidence already assembled, instead of restarting the wear-versus-event argument from scratch. A separate loss of value tied to the covering's age going into the claim belongs to depreciation recovery, which runs on its own separate track.
What gets recovered on a Seattle 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.
Storm-dated damage pattern separated out from ambient moss and granule wear
In scope
In a market this quiet on catastrophic events, the carrier's starting assumption about an older roof is years of damp and moss rather than a single storm date. A supplement that documents where a wind tear or impact crease sits against the surrounding wear, rather than describing the roof's condition in general terms, is what actually separates a real event from the baseline the desk adjuster already expects to see.
Confirmation of which building department actually has the parcel
Verify with local building dept
The City of Seattle administers its own adopted building and residential codes, carrying amendments specific to the city, through its own department. King County's own permitting office states it serves unincorporated area only. A parcel a few blocks from a city limit line does not automatically answer to the office an estimate assumed, and that determination gets made before a citation goes into the file rather than after a permit gets kicked back.
Underlayment spec matched to a wet-deck timeline, not a generic national default
In scope
A deck that never fully dries out between one Puget Sound system and the next needs underlayment built for that timeline, and the entry-level felt a national price list defaults to was never rated for it. Pricing the correct product is a scope decision that a checklist estimate skips because it looks like an upgrade rather than a requirement.
Moss and organic growth work kept off the storm-caused lines entirely
Usually omitted
Biocide treatment and cleanup belong on their own line, apart from anything tied to the storm date, because folding the two together is exactly what invites a desk adjuster to read the entire file as routine upkeep. Separating them protects the lines that are genuinely storm caused.
Sheathing condition written down the moment tear off exposes it
Usually omitted
Nobody can see how far years of trapped moisture traveled through the deck until the old covering comes off, and a street-level walkthrough has no way to predict it. Whatever the crew actually finds gets documented on the spot rather than assumed sound from a photo taken before tear off started.
Flashing at wall and dormer intersections rebuilt rather than reset
Usually omitted
Seattle rooflines carry a lot of wall-to-roof transitions, and a fast estimate that puts the same flashing back down after tear off is betting the seal underneath survived years it almost certainly did not. Rebuilding the joint, not just resetting the metal, is the item that keeps that same leak from reopening the file next season.
Ridge and hip closure inspected and rebuilt, not just re-capped
Usually omitted
A ridge line spends most of the year under damp air rather than a single weather event, and growth works into the closure from underneath long before anything shows up as an interior leak. Laying a fresh cap over an unopened closure is a shortcut, not a repair, and a generic estimate rarely knows to check.
Valley capacity checked against a full wet-season load, not a single-storm assumption
Code driven
A valley detail sized for occasional heavy rain, rather than for weeks of near-continuous system after system moving through, is the point where a Seattle roof actually starts leaking. Getting the metal width and underlayment layering right for that sustained load is a sizing decision, not an optional upgrade a contractor talks the homeowner into.
Rooftop fixtures detached and reset rather than roofed around
Usually omitted
Skylights and solar mounts are common enough on this housing stock that a crew hits one on a large share of jobs, and there is no version of a proper tear off where the covering gets replaced underneath a fixture nobody removed first. That removal and reinstall labor is real cost that a squares-based estimate has no line for unless someone adds it.
Impact strike from wind-thrown debris documented on its own, apart from any hail claim
Usually omitted
A mature tree limb coming down in a windstorm marks a roof in a way that looks nothing like hail and gets missed by any inspection built around bruise counts. That kind of strike needs its own photographed record tied to the wind event, because nobody is going to find it by running a hail checklist against the slope.
Fee schedule and inspection order confirmed against the actual issuing office
Verify with local building dept
City hall and the County keep separate fee tables and separate inspection sequencing, and quoting one flat number for a metro this size guesses wrong for whichever office is not actually holding the file. That number only becomes real once the correct office has been identified.
Overhead and profit where a roof loss reaches a second trade
In scope
A wind event that opens the roof and lets water reach interior ceiling drywall on the same address puts two separate trades on the same job at once, and somebody has to keep the drywall crew out until the roof itself is closed back up. That coordination is what the markup is actually paying for, independent of what either trade bills on its own.
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
Storm evidence gets pulled apart from ordinary wear, line by line
Your photos and measurements get read against the carrier's own number with one question in front of every line: did this get priced because a real event happened, or because the roof looks the way an older Seattle roof usually looks regardless of any storm at all.
- 02
Jurisdiction gets pinned down before a single code citation is drafted
A parcel inside Seattle answers to the City's own adopted code through its own department. A parcel outside that boundary, in unincorporated King County, answers to a separate office that does not administer the City's amendments at all, and that distinction gets settled first.
- 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
Follow up with the desk adjuster does not stop on a fixed schedule, and if the file reaches a point where a carrier representative needs to see the roof again, the reinspection request gets built around the storm-dated evidence already gathered. A carrier reply generally takes around three weeks to show up, and silence on their side is never logged as a closed file on ours.
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.
Seattle questions we get from contractors
Why does a Seattle roofing carrier assume damage is maintenance rather than a storm loss?
Because the base rate points that way. Seattle rarely produces the kind of catastrophic hail or wind event that trains a desk adjuster to expect a storm loss on sight, so the default read on an aging shingle field here is years of damp and moss rather than one bad afternoon. That default is not unreasonable on its own; a lot of what shows up on an older Seattle roof genuinely is slow wear. The problem is that a real wind or impact event still happens on top of that baseline, and separating the two takes documentation a checklist built for a catastrophe market never asks for.
How do you prove a storm event happened on a roof that already shows moss and wear?
By dating the damage pattern against the event rather than describing the roof in general terms. A wind-driven tear or an impact crease has a shape and a location that a decade of moss growth does not produce, and photographing that specific pattern, tied to a specific storm date, is what separates it from the ambient damp damage sitting on the rest of the roof. A supplement that just lists the roof's overall condition invites the maintenance argument instead of closing it off.
Does the City of Seattle or King County govern a given Seattle-area re-roof permit?
That is decided by the property line, not by how the area is described in conversation. City hall administers its own adopted building and residential codes, each carrying amendments specific to Seattle, through the Seattle Department of Construction and Inspections. King County's own permitting page states plainly that its office serves unincorporated area only, so a property just past Seattle's boundary is reviewed by the County's process instead of the City's. Getting that answer right for the specific parcel matters before a code citation ever goes on paper.
Is Seattle a hail market, and how does that change what a supplement should argue?
No, and a Seattle supplement that leads with bruise counts is chasing evidence this market rarely produces. What actually drives a Seattle claim is sustained wet season moisture, wind driven rain, and persistent moss and organic growth, not hail. That low-catastrophe profile is exactly why the argument here usually runs backward from most of the country: the fight is not proving a storm was severe enough to matter, it is proving a real event happened at all against a backdrop the carrier already expects to look damp and worn.
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 Seattle 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.
Seattle and the Washington market
Seattle anchors Puget Sound and the west side of the Washington market, sitting apart from Spokane and the dry side of the state on the other side of the Cascades. Files also come in from unincorporated King County and the surrounding Puget Sound cities, each checked against its own permitting office's amendment record before a citation goes into the supplement.
Send one Seattle file and get the storm evidence separated from the wear
Forward the carrier write-up, your own field photos, and the property address. Our desk pins down the reviewing department, isolates the dated event evidence from the surrounding wear, and returns a scope built on what actually happened to that roof rather than on how old it looks.