Fayetteville, AR
One code text runs the whole corridor, so the divergence has to be found somewhere else
Fayetteville's own Building Safety Division says it plainly: the City's codes come straight from Arkansas State building standards, added to in local review rather than voted through an independent city ordinance. Springdale, Rogers, and Bentonville publish that same state text on their own sites. What actually differs from one office to the next is not the code, it is the design values and the amendment layer each city has published on its own, plus what the Boston Mountains grade does to a roof plan a flat-lot template never anticipated.
By Kyle Hamrick, Founder
A supplement that treats Fayetteville, Springdale, Rogers, and Bentonville as four copies of the same code is only half wrong. The document is genuinely shared. What is not shared is which office actually reviewed the permit, and a file that skips that confirmation is guessing at the one thing that was never uniform to begin with.
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 Fayetteville file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule. More about Kyle.
What makes a Fayetteville file different from the fragmentation story next door
Shared text, separate offices, and the mistake that shape invites
Fayetteville's own Building Safety Division states directly on its own site that the City's building, electrical, energy, mechanical, plumbing, and gas codes are taken directly from Arkansas State building standards and added to when reviewing for Fayetteville. There was no separate city council vote adopting an independent Fayetteville code cycle the way some cities run one. The current codes list published on the City's own page names the 2021 Arkansas Fire Prevention Code, the same statewide three-volume document that the Arkansas Department of Labor and Licensing states applies statewide, including rural and unincorporated land with no local building department at all.
Springdale, Rogers, and Bentonville each publish that same state code list on their own sites as well. Bentonville's own building codes page states plainly that the city enforces the most recently adopted Arkansas Fire Prevention Code, naming a City of Bentonville amendment specifically to the fire volume while listing the building and residential volumes as the state's own unmodified editions. That is not four cities running four rulebooks. It is one rulebook administered through four separate front doors, and the mistake this shape invites is the opposite of the one a truly fragmented metro invites: assuming that because the text matches, the office does not need confirming.
The one confirmed local layer sits in Rogers, not Fayetteville
Rogers publishes its own Design Requirements table directly on its own site, naming a specific snow load, a specific wind design speed, a seismic design category, and a frostline depth for that city, values a structural calculation actually needs and that a generic statewide default does not supply. Fayetteville's own published material does not carry an equivalent table in the same location. That does not mean Fayetteville lacks applicable design values. It means a figure pulled from Rogers' page does not automatically transfer to a Fayetteville permit file without the reviewing office confirming it separately, and a supplement that assumes one city's published number covers the whole corridor is making the same error in reverse that assuming a uniform code text would make.
Boston Mountains grade, and what it does to a roof plan
Fayetteville sits on the outskirts of the Boston Mountains, on ground that rolls and grades in a way the flatter country held by its neighbors closer to the Arkansas-Missouri line generally does not. A house built into that kind of lot tends to stagger roof planes to follow the slope rather than sitting under one simple gable, which produces more valley length, more step flashing at each elevation change, and more total roof plane per square foot of house than a comparable build on level ground. None of that is a code argument. It is a measurement argument, and it is the piece a satellite-based squares count misses first on a hillside property, because the tool sees total area and not how many separate planes and transitions that area is actually cut into.
One state text, four reviewing offices, and where each one actually differs
Fayetteville reviews against the state text, and says so itself
Fayetteville's own Codes and Regulations page names the Building Safety Division as the enforcing office and states that the City's codes come directly from Arkansas State building standards, added to in local review. The current codes list on the City's own site names the 2021 Arkansas Fire Prevention Code among the documents currently in force. Verify with local building dept Confirm the current amendment status with the Division before a citation goes in writing, since the added-to-in-review language leaves room for local practice that is not always published in the same place as the base code list.
Rogers reviews against the same text, plus its own published design values
Rogers' own Codes & Ordinances page lists the identical 2021 Arkansas Fire Prevention Code volumes by name, then adds a City of Rogers Design Requirements table naming its own snow load, wind design speed, seismic design category, and frostline depth. A supplement written for a Rogers address can cite that table directly. Verify with local building dept Do not carry those figures into a Fayetteville or Bentonville file without confirming the reviewing office there publishes the same values.
Bentonville names its own amendment to one volume, not all three
Bentonville's own Building Codes page states that the city enforces the most recently adopted Arkansas Fire Prevention Code and separately names a City of Bentonville amendment to Volume I, the fire volume, while listing Volumes II and III, building and residential, as the state's own unmodified editions on the same page. That is a real local layer, but it sits in a different volume than most residential roof work touches, which means a Bentonville amendment argument built for a fire-code question does not transfer to a residential roofing file the way it might in a jurisdiction that amended the residential volume directly.
The carriers writing this corridor, and what shared code text does to their read
Farm Bureau, Nationwide, Allstate, Farmers, and State Farm write a real share of the residential book across Northwest Arkansas the same way they do statewide, and Shelter Insurance holds real regional penetration here as well. None of that is unique to Fayetteville, and no single carrier's share of this specific city is asserted here, since the figure was not reachable from a primary source. What is worth knowing on a Fayetteville file specifically is what a shared code text does to a desk adjuster's habits: a reviewer who has handled files from Rogers or Bentonville already knows the base document, so a citation built on that same 2021 Fire Prevention Code text does not get the pushback a genuinely unfamiliar code basis would draw. The resistance shows up instead on the design-value and amendment layer, where a desk adjuster working corridor volume at speed may assume every city's local layer looks like the one they saw on the last file and wave off a figure that actually belongs to a different office's own table.
Policies written across this corridor carry the same wind and hail deductible structures and roof payment schedules seen statewide, tied to the dwelling limit and keyed to reduce payout on an aging covering, and a scope that was genuinely earned on the merits can still come back short once that math is applied. Where a settlement was already cut on that basis, depreciation recovery is the separate fight. After a wide hail day moves through the corridor, catastrophe crews get staffed on volume across all four cities at once, and the reinspection supplement is built for the file that stalls waiting on a second visit, jurisdiction and design values already settled before the representative makes the trip back out.
What gets recovered on a Fayetteville 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 office confirmed for that address, separate from confirming the code
Verify with local building dept
Fayetteville's own Building Safety Division reviews against the same Arkansas Fire Prevention Code that Springdale, Rogers, and Bentonville each administer, so naming the code correctly does not by itself tell a reviewer which office actually issued the permit. A supplement that assumes the two questions have one answer is treating a shared document as if it were a shared department.
2021 Arkansas Fire Prevention Code Volume III items, cited to the state text Fayetteville reviews against
Code driven
Fayetteville's own current-codes list names the 2021 Arkansas Fire Prevention Code, the 2021 IRC and IBC with state amendments, as the standard the Building Safety Division reviews against. The citation names that statewide document directly rather than inventing a Fayetteville-specific edition the City itself does not claim to have adopted separately.
Design values confirmed against the reviewing city's own table, not assumed from the code text alone
Verify with local building dept
Rogers publishes its own Design Requirements table naming a specific snow load, wind design speed, seismic design category, and frostline depth for that city. Fayetteville's own published material does not carry an equivalent table in the same place, and a value read off a neighboring city's page does not travel to a Fayetteville permit file without separate confirmation from Fayetteville's own reviewing office.
Underlayment and fastening addressed as a slope-driven question on hillside lots
Verify with local building dept
A roof built into a graded hillside lot on the edge of the Boston Mountains carries more roof plane per square foot of house than a comparable roof on level ground, and the current code's underlayment and fastening requirements apply to every one of those extra planes the same as the main field. Confirm the applicable requirement with the reviewing office before pricing a slope-heavy roof off a flat per-square assumption.
Valley metal sized to actual valley count, not a percentage of total roof area
Usually omitted
A cut-up hillside roof plan produces more linear feet of valley per square than a simple gable does, and a carrier estimate written from a satellite measurement tool can undercount valley length on a roof with multiple intersecting slopes reacting to a graded lot. The fix is measuring the actual valley runs on that specific roof, not applying a citywide ratio.
Step flashing at grade and elevation changes on hillside construction
Usually omitted
Houses built into a slope frequently stagger roof planes at different elevations to follow the grade, and every one of those elevation changes needs its own step flashing run where a flatter lot would need none at all. A first estimate written to a standard suburban template does not anticipate that count.
Starter course at eaves and rakes
Usually omitted
No matter which of the four cities' offices reviewed the permit, the shingle manufacturer's own installation instructions still call for a dedicated starter strip beneath the first course, and a carrier line that treats it as part of the field shingle count is dropping a purchase the manufacturer requires regardless of the reviewing office.
Ridge cut, vent, and cap priced as three separate operations
Usually omitted
Cutting the ridge slot, seating a vent unit, and capping over it are three distinct purchases and three distinct labor tasks in Xactimate, not a single operation that happens to run along the ridge. Folding all three into a single ridge cap line is the fastest way a Fayetteville estimate loses two of the three.
Layer count and legality of a second tear off
Code driven
A meaningful share of the older housing closer to the University area and the historic downtown corridor carries a second covering laid over the first, and once the deck confirms that, the shared state code's layer limit decides whether a simple recover is even a lawful option on that roof.
Soft metal impact documented before the roof comes off
In scope
Hail hard enough to bruise a shingle mat leaves the same signature on the gutter face, the flue cap, and the AC condenser fins, and that evidence disappears the morning tear off starts. It has to be photographed and captioned while it is still on the house, regardless of which of the four cities' offices eventually reviews the permit.
Gutter, downspout, and gutter apron on graded lots
Usually omitted
A hillside lot concentrates roof runoff into fewer downspout runs carrying more volume per run than a flat-lot house of the same size, and the added stress on gutter hangers and apron seams during a storm event is a real damage mechanism a carrier's ground-level photo rarely captures.
Interior ceiling, insulation, and drywall loss surfacing after the fact
Usually omitted
By the time a carrier's first inspection happens, wind-driven rain that found a lifted ridge or a torn field has not yet worked its way down to where anyone can see it, so the stain that shows up on the ceiling a few days later is new evidence for the file, not a dispute over what the original walkthrough should have caught.
Overhead and profit on multi-trade, slope-driven files
In scope
A hillside property that takes roof, gutter, and retaining or drainage repair from the same storm event needs a supervisor sequencing more than one trade around the site's own grade constraints, and that supervision earns its own line independent independent of which city's office issued 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
- 01
The reviewing office and the code text get confirmed as two separate questions
We do not assume that naming the 2021 Arkansas Fire Prevention Code settles which department issued the permit. Fayetteville, Springdale, Rogers, and Bentonville each review against that same state text through their own office, and the supplement names the office along with the code.
- 02
Design values get pulled from the reviewing city's own published table where one exists
Rogers publishes its own snow load, wind design speed, and seismic design figures. Where the reviewing city has not published an equivalent table, the file states that plainly rather than borrowing a neighboring city's numbers.
- 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.
- 04
We stay on the file until the carrier answers
We keep pushing on follow-up calls and desk adjuster contact until the carrier answers. If a representative gets scheduled to walk the roof again, the reviewing office and the applicable design table are already documented, so that trip goes straight to the disputed line items instead of relitigating which office governs the address.
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.
Fayetteville questions we get from contractors
Does Fayetteville run its own separately adopted building code, the way some cities do?
No, and that is worth knowing before a supplement leans on a Fayetteville-specific code citation. The City's own Building Safety Division states directly on its own site that Fayetteville's building, electrical, energy, mechanical, plumbing, and gas codes are taken directly from Arkansas State building standards and added to when reviewing for Fayetteville. There was no separate council vote adopting an independent Fayetteville code cycle the way a city with its own ordinance would run. The current codes list published on the City's own page names the 2021 Arkansas Fire Prevention Code, the same statewide document that governs unincorporated Washington County the same way it governs the city.
If the code text is the same across Fayetteville, Springdale, Rogers, and Bentonville, why does the city on the address still matter?
Because the departments enforcing that shared text are not the same office, even where the document is. Rogers publishes its own Design Requirements table on its own site, snow load, wind design speed, seismic design category, and frostline depth among the values listed, and that table is a City of Rogers page, not a Fayetteville one. Bentonville names a City of Bentonville amendment specifically to the fire volume of the code, while its building and residential volumes are listed as the state's own unmodified editions. Two properties built to the identical state code text can still answer to two different local supplements once the design values or the amendment layer diverge, and confirming which office reviewed the permit is a separate step from confirming which code applies.
Does the Ozark terrain change what a Fayetteville roof needs written into a claim?
The city sits on the edge of the Boston Mountains rather than on the flatter ground held by its neighbors closer to the Arkansas-Missouri line, and that terrain shows up on a roof as slope variety within a single subdivision rather than as a uniform pitch across the block. A hillside lot built to catch drainage off a steeper grade carries more valley, more step flashing at grade changes, and more cut-up roof plane than a comparable house on level ground nearby, and a scope written to a flat per-square average misses what the terrain actually put on that roof.
How much does a 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.
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.
Fayetteville and the wider Arkansas market
Fayetteville sits inside the wider Arkansas market, and the shared-code, separate-office reality argued here is specific to Northwest Arkansas rather than a statewide pattern. Springdale, Rogers, and Bentonville review against the same state code text through their own building departments and are not discussed here as if one city's local layer applies to another's. Fort Smith and Jonesboro sit outside this corridor entirely and run their own peril and jurisdiction questions.
Send one file and find out which table actually applies
Send the carrier's estimate, your own measurements, photos of the damage, and the declarations page. We confirm which office reviewed the permit, whether a published design value table applies, then return a corrected scope within one business day.