ScopeQueue Carrier estimate in, justified supplement package out.

Ice and Water Shield Code in Ohio: What the Rule Says, and How to Document It

· 10 min read

Eave ice barrier is an easy line for an adjuster to strike, because striking it looks like a judgment call about local weather.

It is not a judgment call. Ohio made that call in writing, for the whole state. What is still open to dispute on a file is usually not the code at all. It is whether you can show what was on the deck before the tear-off.

Ohio already answered the question the adjuster is asking

The model code language makes the ice barrier conditional. It applies where the climatic and geographic design criteria table at R301.2 designates a history of ice forming at the eaves and backing water up under the covering. In many states, parts of that table are left blank for each local jurisdiction to fill in.

Ohio filled that entry in. In the Ohio Board of Building Standards version of the table, Table 301.2(1), the ice barrier underlayment entry is filled in as required, and a footnote designates every jurisdiction in Ohio as having a history of local damage from ice damming, tied by cross-reference to the ice barrier sections for the covered roof types. The Board's own rule change summary for the 2019 edition describes the Ohio version of that table as fixing constants for the state rather than leaving them to each department.

Read that again, because it changes what you argue. The trigger is not a winter design temperature. There is no county line in Ohio where the requirement stops. An adjuster asking you to establish that ice dams occur in Ashtabula, or in Butler, is asking you to re-prove what the state table already designates. The winter design temperature in that same table is a local figure and serves other purposes. It is not the switch for this line item.

What the requirement actually says

Ohio adopts roof assemblies as rule 4101:8-9-01 of the Ohio Administrative Code. The ice barrier section inside it is 905.1.2. In plain terms:

That last line matters in the direction that costs you money. A detached garage falls under the exception. Claiming it there anyway hands a reviewer a clean, correct reason to distrust the rest of the file. Leave it off.

The real fight is quantity, not whether

Start with the phrase all roof surfaces. Dormer eaves. Porch eaves. Lower runs on a cut-up roof. If the carrier estimate carries eave membrane only along the main eave runs, walk the diagram slope by slope before you write anything else.

Then the measurement, which is where the money sits. The 24 inches runs inside the wall line, not out from the drip edge, and the rule measures it up the slope from where the projected outside face of the wall meets the deck. So the width you actually need is the overhang projection, plus the thickness of the wall assembly, plus 24 inches, measured along the slope. On a house with even a modest overhang, that already exceeds a single 36-inch course.

Warrensville Heights publishes a short ice-guard sheet for contractors that puts the arithmetic in writing: most of the time six feet of ice guard is needed, and a three-foot roll will not be enough once the overhang is 18 inches or more. That is one department's guidance, not statewide policy, but the geometry is identical everywhere in Ohio, and it is a building official putting the math on paper.

This is the strongest kind of supplement item, because it is not an opinion. It is a tape measure. Photograph the overhang with a tape in the frame and the quantity argument largely makes itself.

"There was only 30 lb felt there"

That denial is really a statement about pre-loss condition: the carrier is paying to put back what was there, and what was there was felt.

There are two separate responses, and blending them is what loses the line.

On the code: a single dry-laid layer of 30 lb felt is underlayment. Section 905.1.2 calls for either two layers cemented together or a self-adhering membrane. One layer of felt is neither. That is a factual statement about published rule text, and a reviewer can check it.

On coverage: whether an ice barrier that genuinely was not there before the loss gets paid is a policy question, not a roofing question. It lives in the ordinance-or-law provision of your customer's policy, if that policy has one, along with whatever limits attach. Do not argue it as a roofing fact. Give it its own heading, label it for what it is, and have the homeowner ask their carrier what their policy provides.

Keep those two in separate sections. Mixed into one paragraph, a reviewer who strikes the coverage argument strikes the code argument along with it.

"Ice barrier isn't required in valleys"

Here the adjuster is half right, and the half they are right about is worth getting straight before you write.

The ice barrier section is written about eaves. Lowest edges, measured inside the wall line. It is not a valley provision. If your narrative stretches that section to justify valley membrane, you have handed the reviewer a clean strike, and the strike will be correct.

Valley lining is its own requirement in its own section: 905.2.8.2 in the Ohio rule, R905.2.8.2 in the model code, with its own material options and widths depending on how the valley is built. Cite it separately. Two line items, two citations, two paragraphs. A valley item can be entirely right on the merits and still fail because it was filed under the eave section.

The argument is about the roof before the loss

The strongest version of this line item never mentions a code upgrade at all.

If the previous roof already had an ice barrier at the eaves, then putting one back is not an upgrade. It is the pre-loss condition. Nobody has to reach for ordinance-or-law coverage to restore what was already on the deck.

So the question stops being does the code require it and becomes what was on that deck the day before the storm. That is an evidence question, and evidence is something you can go get:

These are the homeowner's records to request. Have them ask the building department how it releases permit files, since practice varies from department to department. A dated third-party record is something a reviewer can verify without taking your word for it, which is exactly what a paragraph of code argument cannot offer.

Photographs, and which ones must happen before the shingles come off

Photographs are the part of this file a reviewer can actually check, and there is a hard deadline on them: after tear-off, a photo of membrane cannot be tied to a location. A sheet of self-adhered material on the lawn or in the dumpster does not show where it came from, and it gets treated accordingly.

Shoot these before you touch anything:

Then during tear-off, not after:

Two habits quietly undercut otherwise good photos. Cropping, which strips out the location reference that made the photo evidence in the first place. And metadata: some field apps strip EXIF on export, so keep the originals with their timestamps and submit those.

If you are assembling the rest of the roof file, our line-item list covers the other items that ride along with an eave rebuild and why each one typically gets bounced.

Write the edition and the department on the file

This is the cheapest credibility available on the whole file.

"Code requires ice and water shield" is not a citation. A reviewer cannot check it, so they discount it. Name three things instead:

  1. The rule. In Ohio, roof covering requirements are adopted by the Ohio Board of Building Standards as rules in the Ohio Administrative Code, chapter 4101:8. Roof assemblies sit in rule 4101:8-9-01, and the ice barrier section inside it is numbered 905.1.2. Ohio's rule text drops the R prefix the model code uses, so R905.1.2 is the model-code designation for the same section. Write both so the reviewer lands on it the first time.
  2. The edition and its effective date. The 2019 Residential Code of Ohio took effect July 1, 2019, based on the 2018 edition of the model residential code with Ohio amendments, and the Board has amended rules in that chapter since. Editions change, so do not cite from memory. Confirm what your department enforces, and write down the edition and date that applied to the permit or inspection you are relying on.
  3. The department. Name the certified building department with jurisdiction, and the permit number if you have one.

One Ohio-specific note before you argue with a department. The residential code is written to apply uniformly across the state, and its administration provisions require a local authority that adopts additional requirements within the code's scope to notify the Board of Building Standards, which then determines whether the local regulation conflicts with the state code. A local authority can add through that process; it is not free to set a different baseline for the same requirement on its own. That cuts both ways. "Our city doesn't require that" and "our city requires more than that" are both claims that need a source and a date before they go in writing.

The pattern

The code half of this item is settled in Ohio and takes two sentences. The documentation half is the part you control, and most of that work happens while the shingles are still on the roof.

This article is general information about published building code and is not legal advice, and it is not an interpretation of any insurance policy. Code editions and local enforcement vary and change; confirm the applicable edition and text with the building department that has jurisdiction. For coverage questions, the policy language and the carrier are the authority.

This is what ScopeQueue does with a file

You can work through all of this by hand, and plenty of good contractors do. ScopeQueue reads the carrier estimate and your photographs and drafts the same file for you to check — with the reason written under each item, and the code section left blank wherever it cannot be verified.

Try it on one file — free

More