Oklahoma City, Oklahoma
Two mechanisms hit the roof. The file has to prove which is which
An Oklahoma City claim routinely opens with impact damage and uplift damage sitting on the same covering under a single date of loss. That is not a weather observation, it is an evidence problem: until the documentation says which marks came from which mechanism, the estimate cannot price either one honestly, and the quieter of the two tends to vanish inside the louder one.
By Kyle Hamrick, Founder
An Oklahoma City file gets built around what the photographs can actually establish, section by section against the ordinance the permit office enforces. We hold no adjuster appointment in this state. What the carrier owes the homeowner is settled between those two, and neither of them is who we work for. The contractor sending us the file is.
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 an Oklahoma City file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule. More about Kyle.
The statewide code floor, the peril split as a statewide pattern, and carrier detail across Oklahoma are covered on the Oklahoma roofing supplements page. What is on this page is the evidence and ordinance work specific to an address inside this city.
What makes an Oklahoma City combo file hard, and it is not identifying the damage
Identification is easy. Attribution is the job
Anybody who has spent a season on roofs can look at a covering and say it took damage. The harder question, and the one an Oklahoma City file lives or dies on, is which of the two things that arrived that afternoon produced any given mark. Impact leaves a point event: a bruise you can feel through the mat, granule displacement centered on the strike, a dent in soft metal with a direction to it. Uplift leaves a sequence: adhesive released along a course, a crease where the tab folded over and came back, fasteners backed partway out or torn through the mat. Both can sit within a few feet of each other on the same elevation.
Once you accept that, the photography changes. A caption reading north slope, third course, documents where you stood. A caption naming the mechanism the image is offered to prove, and what in the frame supports it, documents an argument. The second kind survives a reinspection with a different person on the roof. The first kind gets re-interpreted by whoever shows up.
The usual defect is a merge, not a denial
A first estimate on a two mechanism loss rarely says outright that one of them did not happen. What it does instead is write a single quantity that reads as generous until somebody asks it to account for both. The covering gets a number, the number looks like a roof, and the scope that the second mechanism actually required never appears as anything you could point at and dispute. Nothing was refused, so there is nothing obvious to appeal.
Unwinding that is arithmetic before it is advocacy. Quantities get assigned by elevation with the reasoning attached to each one, so the total stops being a lump that can absorb whatever it needs to. A merged total is only defensible while it remains a single figure. Broken into surfaces with a stated basis under each, it either accounts for both mechanisms or visibly does not, and that is the entire move.
Why the split is worth the effort rather than a technicality: the terms attaching to each mechanism on the same policy are frequently not the same terms, so an allocation that never happened is a settlement calculated on assumptions nobody stated out loud. That is why the declarations page travels with the file, and depreciation recovery is its own engagement wherever the covering got written down for age.
An Oklahoma City address is not automatically an Oklahoma City permit
The city limits reach well past a single county line. Oklahoma City property sits in Canadian and Cleveland counties as well as Oklahoma County, and the city's own guidance to residents warns that its ZIP codes overlap neighboring municipalities closely enough that people routinely get charged as though they lived somewhere else. If a mailing address can be wrong about which city you are in, an estimate written off that address can be wrong about which ordinance it is answering.
For a supplement that matters at exactly one point: the citation. Amendments are municipal, and a section number that is correct for a house on one side of a boundary road can be the wrong document a quarter mile away. Verify with local building dept Establish which authority will issue the permit for that specific parcel before any section number goes into writing, because a citation to the wrong jurisdiction costs more credibility than making no citation at all.
Three code arguments that do not care which peril wins
Here is the practical reason to know the ordinance on a combo file. A code requirement attaches to the work being performed, not to the mechanism that made the work necessary. Once replacement is on the table, these three hold no matter how the causation argument lands, which makes them the steadiest ground on the file.
The adopted shelf carries more than one vintage, so cite the section and not the year
Oklahoma City's Development Center publishes the list of codes currently adopted, and reading it in full is worth the two minutes. Building, residential, plumbing, mechanical, fuel gas, existing building, and fire all sit at their 2018 editions. The electrical code sits at 2017. The energy code sits at 2009. The city also publishes an amendment document for each discipline, with the state amendments marked inside the same file. A supplement that says the 2018 code as though one year covered the whole shelf invites a correction that costs the rest of the argument its footing. Verify with local building dept Pull the current amendment document for the discipline you are citing before the section number is quoted.
The ice barrier amendment says something the climate table does not
This one gets missed constantly, and honestly the layout invites it. The city amended Table R301.2(1) to record that ice barrier underlayment is not required in the eave condition that table describes. Read only that line and you conclude there is no ice barrier anywhere on an Oklahoma City roof. The amended text of Section R905.1.2 then adds two independent requirements underneath: a 36 inch wide ice barrier in all valleys, run the length of the valley and centered on it, and a 36 inch wide ice barrier at every change in roof pitch where the lower roof has a lower pitch than the upper roof. Those are written as their own sentences and they do not depend on the eave condition at all. Code driven On a cut up roof form this is scope the first estimate almost never carries.
The re-cover door is closed on asphalt, and the deck definition is written down
Two amendments work together here. The city's Section R908.3.1.1 lists conditions under which a roof re-cover is not permitted, and an existing roof already carrying one or more application of asphalt shingles is on that list, which removes the overlay option rather than merely discouraging it. Then the amended sheathing requirement defines what a solidly sheathed deck is not, naming gaps wider than the covering manufacturer allows along with warped, split, cracked, deteriorated, and rotten boards. A decking dispute usually turns on whose judgment counts, and a written definition is what turns it back into a question of fact. Verify with local building dept Confirm the section text in force with the Development Center, since these documents are reissued.
What gets recovered on an Oklahoma City 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.
Impact evidence and uplift evidence captured as two separate photo sets
In scope
One folder of roof photographs proves a storm happened. Two folders, one built around strike marks and one built around released tabs and backed out fasteners, prove that two mechanisms were at work on the same covering. The second version is what an allocation argument runs on, and it can only be assembled before the covering leaves the property.
Slope by slope allocation of the loss rather than one blended roof total
In scope
A single roof total lets whichever mechanism was written first absorb everything the second one did. Assigning quantities elevation by elevation, with the reasoning attached to each, forces the conversation onto the actual surfaces instead of onto a lump sum that nobody can take apart afterward.
Ice barrier in every valley and at every change in pitch where the lower roof is flatter
Code driven
Oklahoma City's amended Section R905.1.2 carries this as its own requirement, worded independently of the eave condition the climate table addresses, and it specifies a 36 inch width run the length of the valley and centered on it. First estimates on complex roof forms here regularly show none of it, because the estimator checked the table and stopped there.
Drip edge at eaves and at rake edges, with the rake run set over the underlayment
Code driven
The city's amended Section R905.2.8.5 requires it on both edges and then goes further than most readers expect by dictating the sequence at the rake, where the drip edge goes over the underlayment rather than under it. A carrier line that funds edge metal without addressing which edges or in what order has not answered the section it is supposed to be satisfying.
Decking replaced where boards meet the amended definition of a deficit condition
Code driven
Oklahoma City amended its sheathing requirement to define what a solidly sheathed deck is not, naming gaps wider than the covering manufacturer allows along with warped, split, cracked, deteriorated, and rotten boards. That converts a judgment call into a checklist an inspector can be walked through, and none of it is visible until the old covering is off.
Full tear off rather than a re-cover over an existing asphalt application
Code driven
The amended re-cover section names an existing roof already carrying one or more application of asphalt shingles as a condition under which a re-cover is not permitted. Where the carrier scope assumes an overlay is available, the ordinance has already removed that option, and the removal and disposal quantities follow from it rather than from an argument about preference.
Fastening and uplift resistance priced to the amended design wind speed for this city
Verify with local building dept
Oklahoma City filled its amended Table R301.2(1) with a specific design wind speed rather than leaving it to a regional map, which means the fastening answer for an address inside the city limits comes out of the city's own table. Confirm the current figure with the office issuing the permit, because the amendment documents are reissued and the table travels with them.
Starter course at eaves and rakes
Usually omitted
On a claim where uplift is half the argument, the course that anchors the first row is not a detail to fold into a field price. It carries its own material, its own labor, and its own bearing on whether the covering manufacturer stands behind the wind rating that the rest of the file is leaning on.
Ridge exhaust vent, hip and ridge cap, and end plugs
Usually omitted
Three separate operations happen along that line and a fast first estimate usually funds whichever one the software suggested first. On a roof where wind is one of the two perils in play, the ridge is also the line most likely to show the damage that gets attributed to the other one.
Impact damage to soft metals and appurtenances recorded before the tear off
Usually omitted
Gutter aprons, flashing legs, vent hoods, and equipment housings hold a strike mark far more legibly than a weathered shingle does, and they are the corroboration a hail allocation rests on when the field reads ambiguously. They also leave the property with the debris, which makes this a one chance record.
Removal and reinstallation of mounted rooftop equipment
Usually omitted
Anything fastened through the covering has to come off before the deck is exposed and go back on once the new assembly is finished. That is scheduled labor with a real cost attached, and it shows up on the contractor's invoice whether or not anybody wrote a line for it during the first pass.
Overhead and profit where the trade count is the trigger
In scope
A storm that put both perils on the house rarely stopped at the roof, and once fence, gutter, siding, and opening repairs are on the same claim number somebody has to sequence those crews and carry the risk if the sequence fails. What decides the question is how many trades need coordinating, not how large the roof line happens to be.
Not one of those is submitted as a request. Each lands as a priced line carrying its own basis, inside a real Xactimate file. The wrapper follows whatever the claim needs, whether that is a roofing supplement, an Xactimate supplement package, a supplemental estimate, or a full claim estimate written from scratch.
Why the split gets lost between the roof and the desk
A two mechanism loss still travels as one claim number with one date of loss attached, and every downstream system treats that as one event. The inspector who went up may well have seen both. Whether both survive the trip into the estimate depends on whether the notes distinguished them in a way the next reader can act on, and the next reader is frequently working from the file rather than from memory of the roof.
That is a records problem more than an attitude problem, and it is why the burden lands on the contractor's side of the table. A submission that arrives already separated gives the desk something it can process without going back up. A submission that asks the desk to do the separating is asking for a judgment call from someone who was never on the property, which is a slower and worse outcome even when everyone involved is acting in good faith.
After a metro wide event the same dynamic gets sharper, because inspection volume climbs and the time available per file does not. When a file stops moving, reinspection supplement work gets somebody from the carrier side back up there with the evidence already sorted by mechanism, so the second visit answers a narrow question rather than reopening the whole loss. Carrier by carrier detail for Oklahoma is on the Oklahoma roofing supplements page.
What happens to your file after you send it
- 01
The carrier estimate is read for what it merged, not just for what it missed
On a two peril file the common defect is not an outright omission. It is a merge, where one mechanism's scope quietly settles inside another mechanism's total. We take your measurements and photos and mark every line where a quantity is doing work for damage it was never written to cover.
- 02
Each damage type gets tied to the evidence that proves it
Strike marks, mat fracture, and dented soft metals go on one side. Creased tabs, released adhesive, and withdrawn fasteners go on the other. Captions name the mechanism rather than only the location, so the allocation argument arrives already built instead of getting assembled during a phone call.
- 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, desk adjuster calls, and reinspection support when the carrier sends someone back out. Response runs about three weeks as a general expectation, and the file does not close on our side because it went quiet on theirs.
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.
Oklahoma City questions we get from contractors
One storm brought hail and wind to the same roof. Why does that complicate the supplement?
Because two damage mechanisms landed on one assembly under one date of loss, and the file now has to prove which marks came from which. Impact and uplift leave different signatures, they sit on different parts of the roof, and they are argued with different evidence. When the estimate treats the loss as one undifferentiated storm event, the weaker of the two arguments usually disappears into the stronger one and never gets priced at all. Splitting the evidence is the work, and it happens before any line item is written.
Which building codes has Oklahoma City actually adopted?
The Development Center publishes the current list, and the important thing about it is that the shelf is not one vintage. Building, residential, plumbing, mechanical, fuel gas, existing building, and fire all sit at the 2018 editions, the electrical code sits at 2017, and the energy code sits at 2009. The city also publishes its own amendment document for each of those, with state amendments marked inside it. Citing a blanket edition year across the whole shelf is the fastest way to hand an adjuster a reason to dismiss the citation, so the section and the amendment get named individually.
Does an Oklahoma City roof need ice barrier when the city's own climate table says it is not required?
Those are two different questions and the answer to the second one does not settle the first. The amended Table R301.2(1) for Oklahoma City does record that ice barrier underlayment is not required in the eave condition the table addresses. The city's amended Section R905.1.2 then separately requires a 36 inch wide ice barrier in every valley, run the length of the valley and centered on it, and again at every change in roof pitch where the lower roof is flatter than the upper roof. An estimator who reads only the table concludes there is none anywhere on the roof, which is exactly the misread this amendment produces.
Can a carrier write a re-cover instead of a tear off on an Oklahoma City asphalt roof?
Not where an application of asphalt shingles is already on the deck. The city's amended Section R908.3.1.1 lists the conditions under which a roof re-cover is not permitted, and one of them is an existing roof that already carries one or more application of asphalt shingles. That is a written prohibition rather than a preference, so a scope built around laying new shingles over the old ones is not answering the ordinance. Confirm the section text currently in force with the Development Center before it goes into a supplement, since amendment documents get reissued.
How much does an Oklahoma City 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. Two mechanism files where one of the two never got scoped tend to open in that harder category rather than the easier 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.
Around the corridor
Files also come in from Edmond, Yukon, Mustang, Midwest City, Del City, Bethany, Choctaw, Piedmont, and the unincorporated ground between them, where the permitting authority has to be established before a section number is quoted.
Send one combo file and find out what got absorbed into what
Send the carrier estimate, whatever measurements and photographs you have, and the declarations page. What comes back the next day sorts the damage by mechanism, prices each side against the amendment the permit office is actually enforcing, and leaves nothing that can be answered with a single blended number.