Dallas, TX

One market, dozens of building departments, and only one of them reviews your roof

Dallas County publishes a list of the cities inside it, and thirty one names sit on that list, the City of Dallas among them. The developed market does not stop at the county line either. Your crew, your price list, and the carrier queue handling the file all move across that whole surface without noticing a thing. The office that adopts and enforces the building code does not move at all, and the adoption record three miles away is a different document with a different date on it.

By Kyle Hamrick, Founder

Texas is a licensed state for us, and the adjuster who runs The Estimate Company holds that license. What it buys on this particular market is narrow and worth naming: your scope gets written by somebody who has sat on the approving side of a supplement queue and watched how fast a desk drops a code line whose authority does not check out.

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 Dallas file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule.

Licensed independent adjuster in South Carolina, North Carolina, Georgia, Texas, and Alabama, writing for contractors nationwide. More about Kyle.

The thing that makes a Dallas file different is administrative, not meteorological

Count the authorities before you count the squares

Hail is why the claim volume here is what it is, and that is the last thing this page will say about the weather. What decides whether a code-driven line survives review has nothing to do with the storm. Dallas County maintains a page listing the cities within it, and thirty one names appear there: Addison, Balch Springs, Carrollton, Cedar Hill, Cockrell Hill, Combine, Coppell, Dallas, DeSoto, Duncanville, Farmers Branch, Ferris, Garland, Glenn Heights, Grand Prairie, Grapevine, Highland Park, Hutchins, Irving, Lancaster, Lewisville, Mesquite, Ovilla, Richardson, Rowlett, Sachse, Seagoville, Sunnyvale, University Park, Wilmer, and Wylie. That count is ours, taken off the county's own published list rather than stated by the county, and it covers one county in a market whose continuous development keeps running well past it.

Each of those is a separate government with its own council, its own adoption votes, and its own review desk. They are peers, not a hierarchy. None defers to the City of Dallas and the City of Dallas has no authority over any of them, so what sits on the ground is not a border you notice crossing but a surface of coequal offices flush against one another, where the same rooflines, suppliers, and crews carry straight through while the reviewing authority changes underneath them.

Three published adoptions, sitting next to each other, disagreeing

This is not a theoretical risk, and it is worth reading the actual records rather than taking a general warning about local adoption on faith. The City of Dallas publishes on its own current city code page that its 2021 International Code Council codes are effective as of May 12, 2023, and that its residential chapter carries Dallas amendments under Ordinance 33099. The City of University Park publishes that it has adopted the 2021 International Building Codes with amendments effective January 1, 2023, naming the 2021 International Residential Code and the 2020 National Electrical Code on its list. The Town of Highland Park publishes that the 2024 International Codes family and the 2023 National Electric Code became effective on January 6, 2025.

Three neighboring authorities inside one county, three separate published answers, and not one of them is in error. A contractor whose week touches all three works under three different sets of adopted requirements, and the estimate written for one of those jobs has no standing on the other two. Nobody announces this. The homeowner does not know it, the crew does not feel it, and the first place it shows up is a struck line on a supplement.

The regional body proves the problem rather than solving it

North Texas has an institution built specifically for this. The North Central Texas Council of Governments states that it has actively promoted the standardization of model construction codes since 1967, and that its Regional Codes Coordinating Committee and five advisory boards of local code professionals recommend uniform amendments for the region, with the stated aim of reducing the variation of local construction codes and making it easier to work from city to city. That effort is real and it has narrowed the gaps. It cannot close them, and the reason is the whole point: a council of governments can encourage adoption and nothing more, so a recommendation governs nothing at an address until the council holding that address votes it in. Which makes the existence of a regional harmonizing body the clearest evidence available that the variation was worth building an institution around. The roof claim inspection checklist carries the field documentation side; the jurisdiction question runs beside it and is settled off the adopting authority's own publication instead.

Which office holds the parcel, and what that office actually published

The City of Dallas publishes its own construction codes and its own effective date

On the City of Dallas current city code page, the construction codes are stated as effective May 12, 2023 or as otherwise noted, with the 2021 International Code Council codes effective as of that date, and the residential chapter listed as the 2021 International Residential Code with Dallas amendments under Ordinance 33099. Permitting for the City runs through its own online portal, DallasNow. That is the record to quote when the City of Dallas is the reviewing authority, and only then. Verify with local building dept Confirm the edition currently in force and anything amended since with the City's own permitting and inspections department before a citation goes into a supplement.

Peer cities publish their own records, and those records are not copies

University Park publishes an adoption of the 2021 International Building Codes with amendments effective January 1, 2023, listing the 2021 International Residential Code and the 2020 National Electrical Code among them. Highland Park publishes that the 2024 International Codes family and the 2023 National Electric Code became effective January 6, 2025, and that its adopted energy code now requires a builder to engage a certified third-party energy inspector and submit two adopted regional energy forms. Two cities, two publications, neither one derived from the other or from the City of Dallas. Verify with local building dept Read the adoption off the specific authority holding the address, from that authority's own page, every time.

A recommended regional amendment is not an adopted one

NCTCOG's Regional Codes Coordinating Committee and its advisory boards develop recommended regional amendments and the Executive Board approves them for distribution, most recently the 2024 Final Recommended Regional Amendments approved on March 27, 2025. Distribution puts the document in front of every council in the region. It does not put it into force at any address. Citing a regional amendment as though it were binding is the fastest way to lose an argument that would have held if the local enactment had been confirmed first. Verify with local building dept Check that the reviewing city actually enacted the amendment being relied on before it appears in writing on a scope.

Why the carrier side has no reason to track any of this

We are not going to characterize how any individual carrier behaves in this market, because we have not opened a source that would support it and a confident guess about a named company is not worth what it costs when it is wrong. What can be said structurally is that claim operations are organized around events and file counts, not around municipal boundaries. A storm footprint crosses a dozen city limits without giving a queue one reason to subdivide, so the working unit on the carrier side becomes the metro, and the metro is precisely the unit with no adoption record attached to it.

That produces error in both directions rather than one. A code upgrade genuinely owed under the reviewing city's adopted edition gets left out, because whoever priced the file worked from a regional default. Or one gets written in against an edition the reviewing city never enacted, which is worse for the contractor, because it hands the desk a legitimate reason to strike the line and to read the rest of the scope with suspicion. Both come from the same missing step, and the step is cheap.

Where a file has already stalled on that dispute, the reinspection supplement is the route back, with the adopting authority's own publication in hand before anyone climbs back on the roof. Where the settlement was cut by an aging adjustment rather than by a scope dispute, depreciation recovery is the separate fight.

What gets recovered on a Dallas 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.

  • Reviewing authority established on the parcel before any code line is drafted

    Verify with local building dept

    Dallas County publishes thirty one cities on its own list of the cities inside it, and the developed market runs past that county line as well. Which council adopted the book governing this address is a question with a real answer, and it is the answer every other code-driven line on the file depends on. Settle it first and the rest of the scope stops being guesswork.

  • Adopted edition and effective date named from the reviewing city's own published record

    Code driven

    The City of Dallas publishes that its 2021 International Code Council codes took effect May 12, 2023, with the residential chapter amended under Ordinance 33099. That sentence is defensible on a City of Dallas permit and worthless on a permit being pulled by a neighboring council with a different published date. Quote whichever record actually governs, and quote it from that authority's own page.

  • Regional amendment checked for local enactment before it is cited as binding

    Verify with local building dept

    The North Central Texas Council of Governments writes recommended regional amendments and encourages jurisdictions to take them up as their own adoption process allows. A recommendation carries no force at an address until the council with that address votes it in, so a citation to the regional amendment on its own is an argument a desk adjuster can decline without doing any research at all.

  • Third-party energy inspection and jurisdiction-specific compliance forms priced as real cost

    Code driven

    The Town of Highland Park publishes that under its adopted energy code a builder has to engage a certified third-party energy inspector and submit two adopted regional energy forms. Where a reviewing authority imposes a step like that, somebody pays for it, and if the estimate is silent the contractor absorbs it out of the job's margin without ever having argued the point.

  • Drip edge at eaves and rakes on full replacement

    Code driven

    Every adoption record read for this page names a current-cycle residential code, and older housing throughout the market went up before full-perimeter coverage was routine. The line survives review when it is tied to the reviewing authority's own adopted edition instead of to a general statement about what modern code requires.

  • Underlayment brought to the reviewing authority's adopted standard on a full tear off

    Code driven

    Once the covering is stripped to the deck the underlayment question opens under whichever residential code that particular office enforces, and the offices in this market are not all enforcing the same edition year. An estimate that assumes a single metro-wide answer gets this line wrong in one direction or the other, and both directions cost somebody money.

  • HVAC condenser and rooftop equipment detach and reset

    Usually omitted

    No crew shingles underneath a condenser pad, a dish mount, or a bolted rooftop unit, so it comes off, the deck gets worked and resealed, and it goes back. That sequence is on the invoice whether or not the desk that priced the file from photographs allowed for the unbolt and the reseal.

  • Overhead and profit on multi trade files

    In scope

    When one loss puts roofing, siding, fencing, and interior finish work on a single schedule under one coordinator, the coordination itself is the billable function. The count of trades on the file decides the line, and it decides it identically no matter which of this market's building departments happens to be reviewing the permit.

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

  1. 01

    Your number gets checked against the parcel rather than against the metro

    We pull the carrier file apart item by item against your measurements and photographs, watching specifically for code language written for the market at large instead of for the office that will actually review this permit.

  2. 02

    The reviewing authority gets identified and its own published adoption gets quoted

    Which council holds the address decides which adoption record is citable, and in this market that is a live question rather than a formality. We name the office, take the edition and effective date from that office's own publication, and check whether any regional amendment being relied on was actually enacted locally.

  3. 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. Written same day or next day, submitted next day. One to three extra days on large commercial and multi structure work.

  4. 04

    We stay on the file until the carrier answers

    Follow-up, desk adjuster calls, and reinspection support when the carrier sends someone back to the roof. 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.

Dallas questions we get from contractors

How many separate building departments can one Dallas-area roofing crew work under in a week?

More than most estimates assume. Dallas County publishes its own list of the cities inside it, and thirty one of them appear on that list, counting the City of Dallas itself. Every incorporated city on it runs its own council, its own adoption record, and its own review desk, and the built-up market keeps going past the county line in several directions. That means the office reviewing a re-roof permit can change from one job to the next without the crew leaving the same continuous stretch of development, which is a different problem from knowing you crossed into a neighboring city.

Do neighboring Dallas-area cities actually adopt different code editions, or is that theoretical?

It is on the record in each city's own publication, and the three we opened do not agree with each other. The City of Dallas publishes that its 2021 International Code Council codes took effect May 12, 2023, with its residential chapter carrying Dallas amendments under Ordinance 33099. The City of University Park publishes that it adopted the 2021 International Building Codes with amendments effective January 1, 2023, listing the 2021 International Residential Code and the 2020 National Electrical Code. The Town of Highland Park publishes that the 2024 International Codes family and the 2023 National Electric Code became effective January 6, 2025. Three neighboring authorities, three different published answers, and none of them is wrong.

There is a regional codes body for North Texas. Does that not solve the patchwork?

It reduces the variation and it cannot remove it, and the distinction matters on a supplement. The North Central Texas Council of Governments states that it has promoted standardization of model construction codes since 1967, and that its Regional Codes Coordinating Committee and five advisory boards recommend uniform amendments for the region and encourage jurisdictions to adopt them as expeditiously as their local process allows. Encourage is the operative word. Its 2024 Final Recommended Regional Amendments were approved for distribution by its Executive Board on March 27, 2025, and distribution is not adoption. A regional amendment becomes enforceable at an address only when the council with that address votes it in, so the correct citation is still the adopting city's, never the region's.

What actually goes wrong on a Dallas supplement when the wrong authority is assumed?

The argument gets thrown out on a technicality rather than on the merits, and the line item goes with it. A code-driven item is only as good as the adoption record behind it, so a scope that cites the City of Dallas effective date on a property whose permit is being pulled somewhere else has handed the desk adjuster a clean reason to strike the line without ever reading what the roof needs. The item may well have been owed. It was not defended. Establishing the reviewing office before a citation is drafted is cheaper than arguing a struck line back onto the estimate.

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. The standard fee is 15 percent of supplemental recovery, and a file with no additional approved recovery owes nothing on that claim.

Dallas and the Texas market

Dallas sits inside the wider Texas market, east of Fort Worth, north of Austin and a long way north of Houston. Work reaches this desk from Richardson, Garland, Irving, Mesquite, Carrollton, Grand Prairie, Plano, Frisco, McKinney and the rest of the surrounding cities, and each of those files is written against the adoption record published by the authority that will actually review that permit, never against the City of Dallas record by default.

Send one file and find out whose code it is actually under

Send us the carrier number, the measurements, and the declarations. We establish which of this market's building departments holds the address, take the adopted edition and effective date from that department's own publication, check any regional amendment for local enactment, and hand back a supplement no desk adjuster can strike for citing the wrong government.