Fargo, North Dakota
A river that runs the wrong way, and wind with nothing to slow it down
The Red River flows north, out of the confluence near Wahpeton and Breckenridge and on toward Manitoba, which means the metro spends part of every spring managing a predictable water event that has nothing to do with what damaged your roof. What does damage the roof is flatter and closer to home: open plain gives wind nothing to break against, so it scours one slope bare and buries the next one in drift, and a single snow-load number for the whole structure was never true of either slope.
By Kyle Hamrick, Founder
A roof in Fargo and a roof across the river in Moorhead sit inside one contiguous neighborhood, and they are governed by two different states' code and insurance regimes anyway. Each file gets checked against the mechanism that actually produced its damage and against the regulatory side of the river it actually sits on, never against one metro-wide assumption.
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 Fargo file is code mechanism, carrier behavior, and claim pattern, confirmed for the address rather than assumed from a statewide rule. More about Kyle.
What actually shapes a Fargo file, and why a generic plains estimate misses it
The river runs north, which is a scheduling fact, not a roof peril
Most rivers a homeowner grew up near run south, toward warmer water and eventually the ocean. The Red River of the North does the opposite: it forms at the confluence near Wahpeton and Breckenridge and flows north through Fargo and Moorhead on its way to Manitoba and Lake Winnipeg. That direction is a genuine hydrological peculiarity, and it has a real, well-documented downstream consequence for the region: the southern stretch can be thawing while the outlet it drains toward, farther north, is still locked under ice, so meltwater backs up rather than simply running off the way it would on a river flowing the other way.
For a roof file the honest connection stops there. Spring water on the ground does not put water under a shingle from above, and this page does not argue that it does. What the annual water event actually produces is a market organized around a predictable spring window: contractor crews, material yards, and carrier field staff across the metro are all managing the same seasonal event at the same time, every year, and that is a scheduling and staffing reality worth knowing before booking work here, not a peril to price on the estimate itself.
Flat, open plain turns one storm into two different snow loads on one roof
Fargo sits far enough into the northern plains that design cold and the length of the snow season are both serious, but the mechanism that actually separates a Fargo file from a valley-floor cold-climate file elsewhere in the country is wind, not depth of cold by itself. There is nothing between the horizon and a roof out here to slow a sustained wind down, so it does not just pile snow on evenly. It scours a windward slope down to bare shingle while carrying that same snow onto a leeward slope, a valley, or against a parapet on the identical structure, where it can drift several times deeper than the storm's stated snowfall total would suggest.
That is a different mechanism from a valley floor trapping still, sustained cold air under an inversion. Here the cold holds, but the wind is what decides where the weight actually ends up, and a carrier estimate that assigns one snow-load number to the whole roof is treating two slopes that never carried the same load as if they did. Documenting it means walking the roof plane by plane, not reading one figure off a weather report.
One metro, two states, two regulators
Fargo and Moorhead sit close enough together, on opposite banks of the same river, that a contractor can work a job on each side in the same week without changing trucks. What does change crossing that bridge is which state's code adoption framework and which state's insurance regulator actually govern the file. Cass County and the City of Fargo answer to North Dakota's structure; Clay County and the City of Moorhead answer to Minnesota's. Neither side's requirements or carrier behavior can be assumed to apply on the other side just because the street grid does not visibly change at the river.
A supplement that treats Fargo-Moorhead as one uniform jurisdiction because it reads as one metro on a map is guessing on whichever side it was not actually written for.
Two banks, two code regimes, and a plain that does not care which one applies
Confirm the bank before confirming the code
A file address in the 58102 range and a file address just across the river carry the same weather and often the same builder, but they answer to different code adoption frameworks entirely. Citing a requirement without first confirming which state, and which enforcing department within that state, actually reviews the permit for that address is the fastest way to have a correct-sounding citation rejected outright. Verify with local building dept Confirm the state, county, and city jurisdiction for the specific address before any code section enters the supplement.
Existing-building repair triggers are not automatic on either bank
On the North Dakota side, whether an existing-building repair threshold applies at all depends on local adoption rather than a single statewide mandate. On the Minnesota side, the enforcing framework is a separate one again. Reaching for a repair-threshold argument as though it is uniform across the metro invites the same dismissal a mismatched citation earns anywhere. Verify with local building dept Confirm adoption status with the building department that actually has jurisdiction over the specific address.
Manufacturer specification does not stop at either state line
A shingle maker's own install requirements do not care which bank of the river a roof sits on, and they do not soften just because a township runs little or no residential inspection of its own. The starter strip, the fastening schedule, and how far the ice barrier has to run stay warranty conditions either way, and an estimate that reads light local enforcement as no standard at all is skipping a requirement that is still real and still enforceable through the manufacturer.
The carriers writing Fargo-Moorhead, and where a flat-metro assumption comes up short
Nodak Insurance holds real weight on the North Dakota bank as a domestic mutual with deep roots in the state, while Farm Bureau carriers pull comparable weight across the Minnesota side, alongside national names like State Farm and American Family writing both banks at once. When a single wind event scours and drifts the whole metro in one pass, the same desk can end up holding a Fargo file and a Moorhead file from the same storm side by side, and routing each one to the correct state's regulatory framework is a separate step the desk has to get right before either file settles.
The recurring gap on a Fargo file is a scope written as though the whole roof took a uniform snow load, or as though the whole metro sits under one code regime, when neither is true here. A windward slope scoured bare and a leeward slope carrying a deep drift on the same roof carry two different exposure histories, and an estimate that prices them identically leaves the drift-loaded side underpriced. The reinspection supplement covers exactly that situation: a file stalled after a first pass that treated the roof as one surface, now backed by slope-by-slope photos ready for whoever the carrier sends out next.
What gets recovered on a Fargo-Moorhead 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.
Per-slope snow load documentation instead of one figure for the whole roof
Usually omitted
Open, flat terrain lets sustained wind scour a windward slope down to bare shingle while dumping that same snow onto a leeward slope or a valley on the identical structure, sometimes drifted several times deeper there. A carrier estimate that assigns one load number to the whole roof is averaging two slopes that never carried the same weight.
Ice and water shield extended past a single course at eaves
Code driven
Design cold this far into the northern plains means an eave can sit under snow and refreeze cycles for a genuinely long stretch of the winter, and a single course of membrane stops almost none of the backed-up meltwater once a drift-loaded eave starts to melt from beneath. Sourcing the exact required run for the specific jurisdiction is a separate step, but a first estimate that stops at one course rarely reflects what a drift-heavy eave actually needs.
Ridge, hip, and soffit closure against wind-driven fine snow
Usually omitted
Wind on open plain does not drop snow onto a ridge from above, it forces it sideways into any gap the ridge assembly leaves open, and fine dry snow packs into an attic on a clear day with nothing falling from the sky. An estimate priced for the cap shingle alone skips the closure detail that is the actual defense against that intrusion.
Starter course at eaves and rakes
Usually omitted
There is no tree line or built-up neighborhood out here to slow a gust down before it hits a roof edge, so wind arrives sustained rather than broken into gusts the way it would in a more sheltered market, and the starter strip is the specific product rated to hold against that. A carrier estimate frequently bundles its cost into the shingle field total instead of pricing it as its own line.
Decking replaced where fastener withdrawal is found on tear off
In scope
Years of a summer-to-deep-winter swing this wide slowly walks a fastener out of the decking underneath it, and nothing about that shows from a ground-level inspection. A crew only finds it once the shingles are stripped and a boot on the deck reveals give that was not there to see when the carrier's own estimator looked at the roof.
Full replacement under the adopted existing-building repair threshold, where one has been adopted
Verify with local building dept
Neither bank of the river guarantees an automatic threshold: North Dakota leaves that decision to the political subdivision, and the Minnesota side runs its own separate framework again. A supplement leaning on this argument has to name which jurisdiction actually set a trigger point before the line survives a desk review, and the answer is not the same for a Fargo parcel and a Moorhead parcel just because they sit blocks apart.
Overhead and profit on multi-trade files
In scope
When one storm reaches the roof, the siding, and a top-floor ceiling at the same house, somebody has to sequence which trade goes on the property first before the next hard freeze locks the calendar down, and that sequencing cost does not change depending on which bank of the river the crew happens to be working that week.
Interior water and insulation damage found after the tarp comes off
Usually omitted
Snow driven sideways into a ridge or soffit gap does not announce itself the day it happens. The insulation and drywall it soaked stay wet and hidden until a tarp comes off weeks later, and by then the damage postdates the first estimate by a wide enough margin that it has to be scoped on its own.
Crew and material scheduling premium during the spring water-event window
Verify with local building dept
The weeks each spring when the metro is occupied with the river's own thaw sequence are a known scheduling constraint for every crew, yard, and adjuster working both sides of the river, not a hidden cost. Whether a specific file's timeline actually crossed that window is worth confirming before assuming a delay premium applies.
Detach and reset on satellite dishes, roof-mounted vents, and window air conditioning units
Usually omitted
Satellite mounts, extra vent stacks, and window units run seasonally are common fixtures across this housing stock, and every one of them has to come off before tear off starts and go back on once the field is down. A desk estimate written from measurements alone, without a crew actually walking the roof, tends to skip this labor entirely.
Drip edge and rake metal matched to the assembly, not the age of the original roof
Code driven
Older housing stock across both sides of the metro predates current edge-metal requirements, and a carrier estimate written like a simple repair frequently prices the rake edge to match whatever the roof had rather than what the replacement assembly is required to carry.
Emergency tarp labor priced for the crew actually dispatched, not a flat urban rate
Verify with local building dept
A crew called out to a loss beyond the immediate Fargo-Moorhead core is burning drive time on the way there regardless of whether the paperwork accounts for it, and settling what the carrier will actually pay for that mileage belongs at the front of the file, not as an argument raised after the tarp is already up.
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
Not skimmed. We pull the estimate apart against your measurements and photos, marking every line where a single flat snow-load figure or a generic edge detail does not match what that specific roof, and that specific slope, actually shows.
- 02
Which side of the river, and which code regime, gets confirmed before anything is cited
Cass County and the City of Fargo run under one state's framework. Clay County and the City of Moorhead run under another's. We confirm which bank the address sits on and which building department actually has jurisdiction before a code line goes into the supplement in writing.
- 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
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.
Fargo questions we get from contractors
Why does it matter that the Red River flows north through Fargo?
Most rivers a homeowner has heard of run toward the equator. This one runs the other way, out of the confluence near Wahpeton and Breckenridge, north through Fargo and Moorhead, and on toward Manitoba. That direction means the southern stretch of the river can be thawing while the northern stretch it is trying to drain into is still locked up, so the water backs up rather than simply running off. None of that is a roof claim by itself, and it does not put water under a shingle. What it does is set a predictable annual window every spring where crews, material yards, and carrier field staff across the metro are all managing around the same event at the same time, and that scheduling reality is worth knowing before you book a crew here.
Does spring flooding on the Red River affect a roof insurance claim?
Not directly, and we do not write it that way. Flood coverage sits in a separate policy and a separate claim process from wind and hail coverage on a roof, and nothing about river flooding puts water under shingles from above. Where the spring water event actually touches a roof file is indirect: it is the weeks where contractor crews, adjusters, and material suppliers across Fargo-Moorhead are all occupied with the same annual event, which is a scheduling and staffing fact, not a peril that damages the roof itself.
How does wind change snow load on a Fargo roof compared to a more sheltered market?
This terrain is flat enough that a storm's wind keeps most of its speed all the way to the roof instead of losing energy to hills or tree cover first, and that changes where the snow it carries actually lands. One slope can come out of a storm swept nearly clean while the slope on the far side of the same ridge is holding a deep drift the falling-snow total alone would never predict. A single number describing the whole roof's snow load hides that split, and the only way to capture it honestly is to look at each slope on its own.
Fargo is in North Dakota and Moorhead is in Minnesota. Does that split matter for a claim?
It matters more than the shared metro area and shared street grid suggest. Cass County, North Dakota and Clay County, Minnesota sit on opposite banks of the same river and the same contiguous housing market, but each state runs its own code adoption framework and its own insurance regulatory regime. A contractor working both sides of the river in the same week is working under two different sets of rules depending on which bank the roof sits on, and a supplement written as if one regime governs the whole metro is wrong for whichever side it was not built for.
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?
A standard file gets written same day or next day and goes to the carrier the following day. Larger jobs touching more than one trade run one to three days past that, a timeline we tell you up front instead of letting you find out partway through. Payment works the same way everywhere: 15 percent of whatever the supplement actually adds, and nothing owed on a file that adds nothing.
Fargo and the North Dakota market
Fargo anchors the eastern edge of the wider North Dakota market, with Grand Forks running its own file up the same river valley to the north, and Bismarck and Dickinson sitting further west along the Missouri River corridor and into the Bakken, along with Minot in the north-central part of the state. Moorhead, directly across the river in Minnesota, shares the metro's street grid and its wind-driven snow pattern but answers to a separate state's code and insurance framework, confirmed by address rather than assumed from either side.
Send one Fargo file and let the actual slope-by-slope load set the scope
Send over the carrier's number, your own measurements, and the pictures taken before the tarp went on, along with the address so we can confirm which bank of the river and which building department actually governs the file. What comes back is scoped to the slope that was scoured and the slope that was drifted, not a single flat number for the whole roof.