Aurora, IL
One city, four counties, one building department. An Aurora permit answers to the city, never to whichever county the lot sits in
Aurora's own land sits across Kane, DuPage, Will, and Kendall counties, and the city runs its own Division of Building and Permits with its own adopted code, separate from all four of the county governments around it. Aurora sits inside the Chicago metro's adjuster and reinspection footprint, not at arm's length from it, so the divergence here is not distance from a carrier desk. It is which document that desk's citation actually has to answer to once it reaches this city.
By Kyle Hamrick, Founder
The mailing address on an Aurora property gives no hint of which of the four counties the parcel sits in, and it does not need to for the permit itself, because the city issues that permit regardless. What it does need confirmed is which document the city is actually holding the file against, which is not always the document a contractor reaches for first.
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 Aurora file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule. More about Kyle.
What sets an Aurora file apart from the counties wrapped around it
One city government, four separate counties underneath it
Aurora's incorporated land extends across Kane, DuPage, Will, and Kendall counties, and the city runs a single Division of Building and Permits that issues every permit inside its limits, regardless of which of the four counties a particular address sits in. That part is straightforward. What trips a file up is the code underneath the permit. Each of the four counties runs its own separate building department for the unincorporated land and small villages it actually governs, and none of those four county codes applies inside Aurora's city limits. A contractor pulling a code reference for the county shown on a map, rather than the city shown on the deed, is citing a document Aurora's own reviewer has no obligation to recognize.
That is a structural fact about the permit process, not a peril and not a carrier behavior, and it is true of Aurora specifically in a way it is not true of a single-county suburb nearby. A file built on a county citation for an Aurora address does not fail because the citation is wrong on its own terms. It fails because it is aimed at an authority that never had jurisdiction over that permit to begin with.
The August 2026 wind event, named and dated
A severe storm system crossed the Chicago area on August 11, 2026, and a National Weather Service meteorologist working the event described straight-line winds in the 80 to 100 mile per hour range covering entire communities. A gust of 97 miles per hour was recorded at Aurora Municipal Airport specifically, one of the higher readings from that system anywhere in the region. Confirmed tornadoes touched down elsewhere in the same system, in southern Cook County and eastern Will County, and reported damage ran south of Interstate 90 across Kane, DuPage, central Cook, Will, and Kendall counties, the same four-county footprint Aurora itself spans.
Straight-line wind at that speed does not always leave a roof looking obviously damaged from the ground. The tab can still lie flat while the seal bond has already let go and the mat has cracked along the fastener line underneath it. A file that names the date, the reported wind speed, and the recorded gust at Aurora's own airport is arguing from a documented system rather than asking a reviewer to take a homeowner's memory of when the damage happened.
Inside the Chicago metro's adjuster footprint, not outside it
Aurora sits inside the Chicago metro's adjuster coverage and reinspection scheduling, on the same rotation as Naperville or Schaumburg, not on the far side of a real driving distance from a carrier's regional desk. That is a different situation entirely from an independent metro running its own claims workflow at real remove, a claim this page is not making. The divergence on an Aurora file is not about how far a reinspection has to travel. It is about whether the citation that reinspection carries actually names the authority that issued the permit.
Aurora runs its own adopted code, and it is not the newest one nearby
The city's own adopted cycle, stated on its own permit application
The City of Aurora's own roofing permit application names the applicable codes directly: the 2015 International Building Code, the 2015 International Residential Code, and the 2018 International Energy Conservation Code, with the city's own Building Code and Electrical Code amendments applying on top. That is the document Aurora's Division of Building and Permits measures a re-roof permit against, city-wide, regardless of which of the four counties the specific address sits in. Verify with local building dept Check the current amendment status with Aurora's own Division of Building and Permits before that citation ever goes in writing.
The county code most contractors reach for does not apply here
Kane County has adopted the 2021 International Residential Code for the unincorporated land and select villages it governs. That is a newer edition than the one Aurora's own city building division uses, which is exactly the trap: a contractor who assumes Aurora tracks whatever the surrounding county recently adopted ends up citing an edition Aurora's permit was never measured against. DuPage County, Will County, and Kendall County each run the same arrangement, building permit authority over their own unincorporated land and select villages, none of it reaching inside Aurora's city limits.
Confirm the city document before the code citation goes out
Because Aurora's own building division, not any of the four surrounding counties, is the authority that actually reviews the permit, confirming the city's currently adopted edition gets settled while the file is still being assembled, well ahead of a reviewer questioning a citation pulled from the wrong government. Getting that step out of order turns a clean, defensible code argument into a credibility problem on the rest of the file.
The carriers writing Aurora, and where a wind file gets flattened
State Farm and Allstate write a large share of the residential roofs in Aurora, the same two names that dominate the wider Chicago metro book, with Country Financial, American Family, Travelers, Erie, and Nationwide picking up most of what is left. None of that carrier mix is unique to Aurora, which is exactly why an Aurora file cannot win on naming the company on the policy. It wins on the jurisdiction and the storm record underneath the claim instead.
After a wide event like the August 2026 wind system, a carrier's regional desk in this metro processes volume on a schedule built around throughput, and a file that walks in with the wrong code authority named gets flagged before anyone reads the scope itself. The recurring move on an Aurora file is jurisdictional first, evidentiary second: name the city's own adopted edition rather than the county's, and name the storm date and the recorded gust rather than leaving the timing generic, and the conversation moves to the line items. Skip either step and the file stalls on a technicality that had nothing to do with the roof.
None of that replaces reading the actual policy before a number goes out the door. Forms written in this market carry percentage wind and hail deductibles keyed to the dwelling limit, and some carry roof payment schedules that price an aged covering out on a discounted basis, and either one can quietly take back a recovery that was won correctly on scope. Where a settlement was already reduced on that basis, depreciation recovery is the separate fight. Where a carrier needs to send someone back out to confirm a disputed item after a volume event like this one, reinspection supplement work keeps the evidence package ready before that second visit gets scheduled.
What an Aurora roof file actually recovers
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.
Code citation confirmed against the City of Aurora's own adopted edition, not the county's
Code driven
Aurora's own roofing permit application names the 2015 IBC, the 2015 IRC, and the 2018 IECC with the city's own amendments layered on, an older cycle than the 2021 edition the surrounding county governments have separately adopted for the unincorporated land around Aurora. A citation pulled from whichever county's code happens to cover the parcel's location on a map gets rejected at plan review, because the city, not the county, issues the permit inside Aurora's limits.
Storm date and mechanism documented to the named August 2026 event
In scope
A file that ties the damage to the confirmed straight-line wind event of August 11, 2026, with the 97 mile per hour gust recorded at Aurora Municipal Airport, is arguing from a dated, reported system rather than asking a reviewer to take the homeowner's word for when the roof was hit. Naming the event and the recorded gust for that specific location is the single strongest piece of context a wind file can carry into review.
County of record confirmed before any permit history search is run
Verify with local building dept
An Aurora address can land inside Kane, DuPage, Will, or Kendall County, and even though the building permit itself always comes from the city regardless of which one it is, other records tied to that parcel, recording, assessment, some utility easements, still route through whichever of the four counties the land actually sits in. Skip that confirmation and a records search can come back clean for no better reason than having been pointed at the wrong county entirely.
Straight-line wind damage documented as displaced material, not just lifted tabs
In scope
Winds in the range reported for the August 2026 event do not always leave a shingle field looking dramatic from the ground. The mat can crack along the fastener line while the tab still lies flat, and a photograph that does not caption what the camera is actually showing invites a reviewer to read an old, weathered roof instead of storm damage from a specific, dated system.
Starter course at eaves and rakes
Usually omitted
A shingle field survives 80 to 100 mile per hour gusts because the strip underneath the first course was actually bonded down, full stop, and no manufacturer stands behind a wind rating on a roof where that strip was skipped as its own step. The purchase and the labor for it are their own line, not a rounding error folded into the field.
Ridge cut, vent, and cap priced as three separate operations
Usually omitted
Sawing open the ridge board, seating a vent in the slot, and running cap shingle back over it are three distinct jobs, not one, and folding them into a single flat ridge-cap price is the arithmetic shortcut we catch most often on an Aurora estimate, especially after a wind event where the ridge is usually the first place to show it.
Soft metal impact documented before the roof comes off
In scope
Where hail rides along inside the same system as a wind event, the gutter face, downspout elbow, and condenser fins hold a reading that survives even when the shingle field itself looks inconclusive in a photo, and once tear off starts that morning, the reading is gone for good.
Fence line and exterior siding on the storm-exposed elevation
Usually omitted
Wind strong enough to lift and displace roofing material almost always takes the fence line and the siding on that same exposed elevation with it, in that same pass of weather. Scope the claim as roof-only and that other damage waits to be found on a second trip, well after the file already went in the first time.
Decking condition and fastening pattern confirmed once the covering is off
Verify with local building dept
Aurora's own adopted code, not the county's, governs what the exposed deck has to meet once the covering comes off, and confirming that requirement against the city's current edition rather than a generic assumption is what turns an observed shortfall into a defensible line rather than a guess.
Downed tree and debris impact assessed on the roof plane, separate from ground cleanup
Usually omitted
A storm system that drops large trees across a neighborhood, as the August 2026 event did across the Chicago area, produces roof-level impact from limbs and debris that a ground-level tree removal invoice does not capture. That impact gets documented on the roof itself, separately from whatever a landscaping crew already cleared.
Gutter, downspout, and gutter apron
Usually omitted
The same gusts that pull roofing material loose also rack the gutter line and dent the downspout in the same pass, and the apron underneath rarely survives a tear off crew working around it even when nobody planned on touching it. A scope built off a roof-level photo set alone stops at the edge of the fascia and misses all of it.
Overhead and profit on multi-trade files
In scope
Roof, gutter, fence, and siding damaged on one address by the same storm means somebody has to line up more than one crew without them tripping over each other on the same driveway. That coordination burden, not the dollar total on the estimate, is the reason this line exists at all.
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 estimate gets read line by line against the roof
Your measurements, your photos, and the carrier's own figure get set side by side, line by line, so every place the written assembly falls short of what the roof actually needs is marked before anything gets cited, confirmed for the city's own requirement rather than assumed from whichever county the parcel happens to sit in.
- 02
The permit authority gets named correctly, and the storm gets dated
We cite the City of Aurora's own currently adopted edition, not a county reference, and where the damage traces to the August 2026 wind event, we name the date and the recorded gust rather than leaving the timing to the adjuster's assumption.
- 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 calling the desk adjuster and stay ready to support a reinspection whenever a representative gets sent back to look at the roof. Figure on roughly three weeks before the carrier answers as a rule of thumb, and this file remains open on our side until that answer actually arrives.
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. 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.
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.
Aurora questions we get from contractors
Why does spanning four counties matter for an Aurora claim?
Aurora is a single incorporated city with one municipal government, but the land under it sits across Kane, DuPage, Will, and Kendall counties, and each of those counties runs a building department that governs the unincorporated land and small villages around Aurora, not Aurora itself. A citation built around a county's own adopted code does not apply to a permit pulled at an Aurora address, because Aurora runs its own city building division and its own separately adopted code, regardless of which of the four counties the parcel happens to sit in. The mailing address does not change which document governs. The city limit does.
Does Aurora follow whichever county's code applies to that piece of land?
No, and that assumption is the single most common mistake we see on an Aurora file. Aurora's own Division of Building and Permits issues the permit and administers the city's own adopted building and energy codes with the city's own local amendments, the same document regardless of whether the specific address happens to sit in Kane, DuPage, Will, or Kendall County. A contractor who pulls the county's adopted code for that county, on the theory that the parcel sits inside it, is citing a document Aurora's plan reviewer has no obligation to recognize for a permit issued by the city.
What actually happened in the August 2026 storms, and why does it matter for an Aurora roof?
A severe storm system crossed the Chicago area on August 11, 2026, and the National Weather Service meteorologist working the event described straight-line winds in the 80 to 100 mile per hour range covering entire communities, with a gust of 97 miles per hour recorded at Aurora Municipal Airport specifically. Confirmed tornadoes touched down elsewhere in the same system, in southern Cook County and eastern Will County, and reported damage ran south of I-90 across Kane, DuPage, central Cook, Will, and Kendall counties, the same four-county footprint Aurora itself spans. A roof that took damage in that event took it from a documented, named, dated system, not from generic wear, and the file should say so.
What edition of the code does Aurora's own building division actually enforce?
Aurora's own roofing permit application states the applicable codes directly: the 2015 International Building Code, the 2015 International Residential Code, and the 2018 International Energy Conservation Code, with the city's own Building Code and Electrical Code amendments layered on top. That is an older code cycle than the 2021 edition Kane County has adopted for the unincorporated land it governs, which is exactly the trap: a contractor who reaches for whatever edition the surrounding county uses, assuming Aurora tracks the newer document, cites the wrong one. Check with Aurora's own Division of Building and Permits on where the amendment currently stands ahead of writing that citation, because a city council can revise an adopted edition whenever it chooses.
Is Aurora a Chicago suburb for claims purposes?
For adjuster coverage and reinspection scheduling, yes, and that is a different situation than a metro that runs its own independent claims desk at real distance from Chicago. Aurora sits inside the Chicago metro's adjuster footprint, so a carrier's regional desk treats an Aurora file the same way it treats a file from Naperville or Schaumburg, on the same reinspection rotation and the same catastrophe staffing. The divergence on an Aurora file is not about distance from that desk. It is about which building department the desk's citation has to answer to once it lands on this specific address.
What does turnaround look like on an Aurora file, 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 that produces no additional approved recovery owes nothing on that claim.
Aurora and the wider Illinois market
Aurora sits inside the wider Illinois market, adjacent to and inside the same adjuster footprint as Chicago, a different situation from Rockford, which runs its own independent metro claims workflow at real distance from that same desk. Files also come in from Naperville, Elgin, and Joliet, each answering to its own building department, never Aurora's.
Send one Aurora file and see which document it was actually built against
Hand over the carrier's figure, your own measurements and photos, and the declarations page, and we take it from there. We confirm the City of Aurora's own currently adopted code rather than a county reference, name the storm date where the August 2026 event applies, and check the specific roof against what the city's own division actually requires.