The Ice and Water Shield Code Supplement Line Item, Documented Right

Ice and water shield is the line item that gets left off more initial scopes than almost anything else on a roof estimate, and it is also the one that gets the most pushback when you add it back. That combination is exactly why it is worth getting right. When the membrane is genuinely required by the building code in your jurisdiction, it is a real material with a real cost, real labor, and a real reason to be on the estimate. When you can show the code section, show the existing conditions, and show the math, it stops being a negotiation and starts being a documentation exercise.

This is written for the estimator, owner, or production lead who is preparing an accurate repair estimate and a supplement request, and who wants the ice barrier line to read like it was written by someone who has actually pulled the soffit back and measured the overhang. We will cover what the code actually says, where the membrane is required versus merely a good idea, how the Xactimate calculation works so your quantity is defensible, what photos and notes hold up under review, the worked numbers on a few common roof geometries, and the compliance boundaries you must respect so your documentation stays on the right side of the line.

A note on what we are and are not doing here. You, the contractor, can inspect a roof, document its condition with photographs, identify what the code requires for the repair you are performing, and write an accurate, code-aligned estimate that reflects your scope of work. You hand that estimate to the property owner. The owner files with their carrier, and the carrier decides what is and is not covered under the policy. We are going to make your documentation airtight. We are not going to tell you how to argue coverage, interpret a policy, or promise an outcome, because those are not your job and, in most states, not legal for you to do for a fee. More on that near the end, because it matters.

What the ice barrier line item actually is

Strip away the insurance vocabulary for a second. The physical thing is a self-adhering, polymer-modified bitumen membrane, roughly 36 inches wide off the roll, with a peel-off release liner and an aggressive rubberized-asphalt adhesive that bonds to the deck and self-seals around fastener shanks. Brand names get used as the generic term constantly, but the code does not care about the brand. It cares about a self-adhering polymer-modified bitumen sheet, or two layers of cemented underlayment, installed in the locations the code specifies.

The purpose is to stop water that gets driven backward or upward against the normal direction of drainage. At the eaves, that is the classic ice dam: snow melts higher on a warm roof plane, runs down, refreezes at the cold overhang, and ponds behind the dam until it finds its way under the shingles and through the deck. In valleys and around penetrations, it is wind-driven rain and the simple reality that those are the lowest-pressure, highest-flow paths on the roof. The membrane seals the deck so that when water gets where it should not be, it still cannot get into the structure.

In an insurance-aligned repair estimate, this shows up as a discrete line with its own code, unit, quantity, and price. In Xactimate the workhorse code is RFG IWS for ice and water shield, priced in SF (square feet), with regional pricing pulled from the current price list for that ZIP and date of loss. There are sibling items and modifiers for valley applications, full-deck applications, and for the membrane being installed over a steeper pitch where labor goes up. The code itself is not the hard part. The quantity and the justification are where estimates get won or lost.

Why it gets dropped from the first scope

Three honest reasons, in roughly the order you will see them:

1. The adjuster scoped underlayment, not the ice barrier. A standard synthetic or felt underlayment line covers the field of the roof. The ice barrier is a separate, code-driven layer at specific locations. If the original scope only carries RFG FELT or a synthetic underlayment line, the eave and valley membrane is simply missing, not denied.
2. The roof was old enough that nobody knows what is under the shingles. On a tear-off you cannot always see the existing eave membrane until the old roofing is off. The first inspection may have been from the ground or off a ladder at the eave, and the membrane question never got asked.
3. The local code amendment was not on the adjuster's radar. Ice barrier is a geographically triggered requirement. An adjuster covering a wide territory, or one new to a jurisdiction with a local amendment, may not know that this specific county requires it where the base code would not, or requires more of it.

None of those are adversarial. They are gaps. Your documentation closes the gap by showing the code that applies and the conditions on this specific roof.

What the code actually says

The governing language in most of the country is IRC Section R905.1.2, Ice barriers, in the International Residential Code. The text has been remarkably stable across the 2015, 2018, 2021, and 2024 editions. Read it slowly, because every clause maps to a quantity or a photo.

The core requirement: in areas where there has been a history of ice forming along the eaves causing a backup of water, as designated in Table R301.2, an ice barrier shall be installed for asphalt shingles, metal roof shingles, mineral-surfaced roll roofing, slate and slate-type shingles, and wood shingles and shakes.

The composition: the ice barrier shall consist of not fewer than two layers of underlayment cemented together, or a self-adhering polymer-modified bitumen sheet, used in place of normal underlayment.

The extent: it shall extend from the lowest edges of all roof surfaces to a point not less than 24 inches inside the exterior wall line of the building.

The steep-slope addition: on roofs with a slope equal to or greater than 8 units vertical in 12 units horizontal (8:12), the ice barrier shall also be applied not less than 36 inches measured along the roof slope from the eave edge.

There is one wrinkle worth knowing if you work across code editions. Between the 2021 and 2024 IRC, the substance of R905.1.2 did not change in any way that affects your quantity. The notable editorial adjustment was the removal of the word "also" and a paragraph break in the steep-slope sentence. If an adjuster or reviewer tells you the requirement changed in 2024, the honest answer is that the measured requirements did not. Knowing that keeps you credible.

Translating the code text into a quantity

The phrase that trips people up is "24 inches inside the exterior wall line." That is not 24 inches up the roof. It is 24 inches horizontally, measured into the building past the inside face of the exterior wall. To get the membrane coverage you actually install, you have to add the parts of the roof that sit outside that point and then convert the whole horizontal distance to a distance along the slope.

Walk it from the outside in:

• The overhang / soffit projection from the fascia to the exterior wall face.
• The wall thickness itself (the framing plus sheathing plus cladding, commonly 6 to 8 inches on a 2x4 wall with siding, more on a 2x6 or masonry wall).
• The 24 inches required past the inside face of that wall.

That horizontal run is the base of a right triangle. The rise is set by the roof pitch. The hypotenuse is the actual length of membrane up the slope, and that is what determines how many 36-inch courses you need.

The geometry is just the Pythagorean relationship, A squared plus B squared equals C squared, where A is the horizontal run, B is the vertical rise over that run for the given pitch, and C is the slope length you install.

The eave math, worked out

Let us do it with real numbers so the quantity on your estimate is something you can defend with a tape measure on the truck.

Take a common builder-grade house: 12-inch overhang, a 2x4 exterior wall at roughly 6 inches of total thickness, and a 4:12 pitch.

Horizontal run (A):

• Overhang: 12 inches
• Wall thickness: 6 inches
• Required interior depth: 24 inches
• Total A = 42 inches

Vertical rise (B) over that run at 4:12:

At 4:12, the roof rises 4 inches for every 12 inches of horizontal run. Over 42 inches of run, the rise is 42 times 4 divided by 12, which is 14 inches.

Slope length (C):

C = the square root of (42 squared + 14 squared) = the square root of (1,764 + 196) = the square root of 1,960, which is about 44.3 inches.

So on this roof, code-required coverage up the slope at the eave is about 44.3 inches. A single 36-inch course does not reach it. You need a course and a half, with a 2 to 4 inch lap between courses, so the realistic installed coverage is closer to two courses' worth of material once you account for the lap and the trimming waste. This is the single most common reason a one-course eave assumption underestimates the quantity.

Now watch how pitch changes everything while the horizontal requirement stays fixed.

Two things to notice. First, even at a low 4:12 you are already past a single course, which is why the one-course assumption is wrong on almost every real eave with an overhang. Second, the slope length grows as pitch grows, which is intuitive once you see it: the same 42 inches of horizontal coverage stretches out longer along a steeper plane.

The 8:12 steep-slope trigger

On roofs at 8:12 or steeper, R905.1.2 adds the requirement that the ice barrier be applied not less than 36 inches measured along the roof slope from the eave edge. Read carefully: this is a floor, not a replacement for the 24-inch-interior rule. You still owe whichever produces more coverage. On the 8:12 line in the table above, the 24-inch-interior calculation already gives about 50.5 inches of slope length, which exceeds the 36-inch steep-slope minimum, so the interior rule governs. The steep-slope minimum matters most on roofs with short or nonexistent overhangs, where the interior calculation alone could fall short of 36 inches of slope coverage. Either way, the practical answer on a steep roof is the same: two courses at the eave, documented.

Valleys and penetrations

The IRC eave language is the part everyone quotes, but valleys are where the supplement quantity often lives, and where local amendments and manufacturer installation instructions do real work.

The base IRC does not mandate ice barrier in open or closed valleys the way it mandates it at the eave. However, two things frequently push valley membrane into the required column:

1. Manufacturer installation instructions. Shingle manufacturers commonly specify ice and water shield, or a comparable membrane, centered in valleys for the warranty to be valid. Under the code, roof coverings must be installed per the manufacturer's instructions, so a valley membrane called out by the shingle maker becomes a code-backed requirement through that route. Pull the actual installation guide for the shingle you are installing and cite the page.
2. Local amendments. Many cold-climate and storm-prone jurisdictions amend R905.1.2 to require ice barrier in valleys, around penetrations, at sidewalls, or even across the full deck. These amendments live in the locally adopted code, sometimes in a municipal supplement, sometimes in a state code. The amendment text is the citation, not the base IRC.

For the valley quantity, the membrane is installed centered in the valley line, typically one 36-inch course running the full length of each valley, lapped over the eave membrane at the bottom. So the valley quantity in square feet is roughly the valley length in linear feet times 3 (for the 36-inch / 3-foot width), before lap and waste.

Penetrations, sidewalls, and chimney bases are handled as flashing membrane and are usually documented as part of the flashing scope rather than the eave/valley ice barrier line, but if a local amendment specifically calls for ice barrier at those locations, document them separately so the quantity is traceable.

Building the line item so it survives review

Here is the part that actually moves estimates. A correct quantity with no documentation gets questioned. A correct quantity with three good photos and a clean code citation gets approved. The work is in the package, not the argument.

The Xactimate mechanics

In Xactimate, the ice and water shield line is built in square feet. Older versions exposed an EAVE and VAL variable you could multiply, and you will still see legacy calculation strings like (EAVE*3)+(VAL*3) floating around, the logic being that multiplying linear feet of eave and valley by 3 converts to the 36-inch membrane width. In current versions you frequently enter the eave and valley square footage directly. Either way, your job is to make the SF quantity match the geometry you measured and photographed.

A clean build looks like this:

• Line item: RFG IWS, Ice & water shield
• Unit: SF
• Quantity: the sum of your eave coverage SF and valley coverage SF, calculated from the slope-length math above, with lap and waste applied per your normal waste convention
• Pricing: left at the published price-list value for the ZIP and date of loss; do not hand-key prices, because a modified unit price is the fastest way to get a whole estimate flagged
• F9 note attached (covered next)

Keep eave and valley as separate sub-quantities in your working notes even if they land on one line, so that if anyone asks how you got the number you can show the two pieces.

The F9 note that does the heavy lifting

The F9 note (the line-item note in Xactimate) is where you state, briefly and factually, why this line exists. A strong F9 note does three things and nothing more: it cites the code, it states the existing condition, and it states the scope. It does not argue, plead, or speculate about coverage.

A template you can adapt:

Ice barrier required per IRC R905.1.2 as adopted by [jurisdiction]. Membrane to extend from lowest roof edge to 24 in. inside the exterior wall line; [8:12 or steeper: minimum 36 in. along slope]. Eave measured slope coverage [X] in. requires [2] courses of 36 in. membrane. Valley membrane required per [shingle manufacturer] installation instructions, p. [X]. Existing roof has [no ice barrier present / single-course eave only], documented in attached photos [#-#]. Quantity reflects measured eave LF [X] and valley LF [X] converted to SF with standard lap.

Notice what that note does. It names the code section. It names the adopting jurisdiction, because the base IRC only applies as your locality adopted and amended it. It states the measured condition. It points to the photos. It shows the math path from linear feet to square feet. Every clause is a fact you can stand behind.

If an adjuster cannot see the membrane requirement after reading that note and looking at those photos, the issue is not your documentation.

The photo set

Photos are the part contractors skimp on and reviewers rely on most. For the ice barrier line, capture:

1. A wide shot of the eave or valley in context, so location is unambiguous.
2. A tape-in-frame shot of the overhang depth and, where visible, the existing membrane (or its absence) at the eave once a course is lifted or during tear-off.
3. A pitch shot using a pitch gauge or level app, with the reading legible, because pitch drives the slope-length quantity and the 8:12 trigger.
4. A valley shot showing length and existing condition.
5. A code or manufacturer-page photo is optional but powerful: a screenshot of the adopted code section or the shingle installation page included in the file removes any doubt about what you are citing.

Time-stamped and geotagged photos are worth setting up if your documentation app supports it. The metadata quietly answers the "is this the right house" and "is this current" questions before anyone asks.

A field workflow you can run every time

Consistency is what turns this from a fight into a routine. Here is a sequence that produces a defensible ice barrier line on every roof.

1. Pull the adopted code before you quote. Confirm which IRC edition your jurisdiction is on and whether there is a local amendment to R905.1.2. This is a five-minute lookup that determines whether you are at the eave only or eave plus valleys plus full perimeter.
2. Measure the overhang and wall thickness. Tape the soffit projection and estimate wall thickness from the construction type. These feed the horizontal run A.
3. Read the pitch and write it down. Pitch sets the rise B and tells you if the 8:12 rule is in play.
4. Run the slope-length math for the eave and confirm courses needed. Use the table earlier as a sanity check.
5. Measure eave LF and valley LF. These convert to SF for the quantity.
6. Document existing conditions. Photograph what is and is not currently installed. On a tear-off, get the deck shots before the new membrane goes down.
7. Build RFG IWS in SF with the calculated quantity, published pricing, and a clean F9 note.
8. Assemble the photo set and attach it. Wide, tape-in-frame, pitch, valley, and optionally the code page.
9. Hand the complete estimate to the homeowner. They file it. The carrier decides coverage. You move on to production.

If you run that same nine-step loop on every roof, the ice barrier line stops being the thing you dread and becomes one of the most consistently documented items in your file.

Worked example: a full eave-plus-valley quantity

Let us put a whole house together so the numbers are concrete.

The roof: a 6:12 hip-and-valley house. Total eave length around the perimeter is 160 linear feet. There are four valleys totaling 60 linear feet. Overhang is 12 inches, wall thickness 6 inches, jurisdiction adopts the IRC at the eave and the shingle manufacturer requires valley membrane.

Eave slope coverage per the table: at 6:12 with a 42-inch run, slope length is about 47 inches, which rounds to two 36-inch courses. Two courses with a 2-inch lap cover about 70 inches of slope; you only need 47, so on a low-overhang or no-overhang section a single course plus a partial might do, but with a 12-inch overhang two courses is the honest call. For quantity, the installed eave membrane is 2 courses x 3 ft width x 160 LF, which is 960 SF before lap, or roughly the slope-length-driven figure if you prefer to bill the measured 47 inches of coverage rather than two full courses. State your convention in the F9 note so the basis is clear.

Valley coverage: 60 LF of valley x 3 ft membrane width = 180 SF before lap.

Total before waste: if you bill installed-course coverage at the eave, you are in the neighborhood of 960 plus 180, around 1,140 SF; if you bill measured slope coverage you will land lower. The point is not which number is universally correct, because conventions differ; the point is that your number is reproducible from the measurements in your file. A reviewer who can rebuild your quantity from your own photos and notes is a reviewer who approves it.

This is also where being honest about your convention pays off long-term. If you consistently bill installed courses, document that you bill installed courses, and your numbers will be consistent across every estimate you submit. Consistency reads as credibility.

What pros get wrong

A short list of the mistakes that turn a clean line into a flagged one.

• Assuming one course at the eave. As the table shows, almost any real overhang plus the 24-inch interior requirement pushes you past 36 inches of slope coverage. One course is usually short.
• Measuring 24 inches up the slope instead of inside the wall. The 24 inches is horizontal and interior. Mixing up the reference point shorts the quantity and, worse, signals to a reviewer that you did not read the code.
• Forgetting the wall thickness in run A. It is only 6 to 8 inches, but it is real coverage and it is part of the horizontal run.
• Citing the base IRC when a local amendment governs. If your county amended R905.1.2 to require full-perimeter or valley membrane, cite the amendment, not the base code. Citing the weaker requirement undersells your own scope.
• Hand-keying the unit price. Leave pricing at the published value for the date of loss. A modified price is the single fastest way to get an estimate pulled apart.
• Thin photos. A wide shot with no tape and no pitch reading does not document a quantity. Three good photos beat ten bad ones.
• Arguing coverage in the F9 note. The note states facts and code. It does not argue what the policy should pay. Keep it clean.

Where roof-targeting data fits before you ever climb a ladder

Everything above is about documenting one roof correctly once you are on it. There is a separate problem upstream: deciding which roofs are worth being on in the first place. After a storm rolls through a territory, the roofs most likely to genuinely need an eave-and-valley membrane assessment are the older roofs in the path of the worst wind and hail, on houses in jurisdictions where the ice barrier requirement actually bites. Driving the whole zip code to find them is slow and burns labor on roofs that are five years old or sat at the calm edge of the cell.

This is the gap RoofPredict is built for. It works from aerial imagery and storm physics to tell a roofing contractor which roofs in a territory are most likely due, house by house: a roof-age range per address derived from imagery, plus a storm exposure model run per roof rather than per neighborhood. It is not a lead-buying service and it does not file or handle anything. It ranks doors, routes, and your own list so your crews knock the roofs that the storm most likely wore out and the roofs that are aging out anyway, then enriches your existing CRM or mailing list with those roof-age and storm signals.

The honest limits matter, and they map directly to the rest of the page. Roof age comes back as a range, not a build date, because imagery dates an installation window, not a day. Storm exposure is expressed as odds, not proof, because a model is a probability, not a certainty that any specific roof was damaged. You still have to climb the ladder, measure the overhang, read the pitch, and document the existing condition before you write a single line. What the data buys you is that the ladder you climb is far more likely to be on a roof where the membrane assessment, and the rest of the scope, was warranted in the first place. The targeting decides where to spend the day; the documentation workflow in the sections above decides whether the day's estimates hold up.

The compliance line you do not cross

This is the part that protects your license and your business, so read it as carefully as the code text.

As a roofing contractor, you are allowed to inspect a roof, document its condition with photographs, identify what the building code and the manufacturer's instructions require for the repair you are performing, and prepare an accurate, code-aligned repair estimate for your own scope of work. You may state facts about your scope to anyone who asks, including the carrier, and you hand your estimate to the property owner. That is all squarely within a contractor's lane.

What you may not do, in most states, is anything that amounts to acting as the homeowner's representative against their insurer for a fee. That is unlicensed public adjusting, and it carries real penalties. Concretely, do not do the following:

• Do not negotiate, adjust, or "handle" the claim on the homeowner's behalf.
• Do not interpret the policy or tell the homeowner what is or is not covered. Coverage is the carrier's call and the policy's language, not yours.
• Do not promise a specific payout, a specific approval, or that the ice barrier line will be paid.
• Do not promise that a deductible will be waived, absorbed, eaten, or made to disappear. Offering to cover a deductible is illegal in many states and is insurance fraud framing everywhere.
• Do not advertise or imply a "free roof."
• Do not represent the homeowner against the insurer.

The safe frame, said plainly: you document thoroughly, you write an accurate estimate that reflects what the code and the manufacturer require for your scope, and you give it to the homeowner. The homeowner files. The insurer decides coverage. Your ice and water shield line is strong because the code is clear and your photos are clear, not because you argued it. If the documentation is right, you rarely need to argue anything, and you stay entirely inside the contractor's lane.

Teach this to your sales team explicitly. A rep who tells a homeowner "we'll get your ice and water shield covered and eat your deductible" has just exposed the company to a regulatory complaint and possibly fraud. A rep who says "the code requires ice barrier here, we'll document it thoroughly in the estimate, and you'll file that with your carrier" has done the job correctly and stayed protected. The difference is a sentence, and the sentence matters.

A reusable checklist

Pin this near the estimating desk.

• Confirmed the adopted IRC edition and any local amendment to R905.1.2 for this jurisdiction.
• Measured overhang depth and noted wall thickness for horizontal run A.
• Read and recorded the roof pitch; flagged 8:12-or-steeper if applicable.
• Calculated eave slope length and confirmed number of 36-inch courses.
• Measured eave LF and valley LF; converted to SF for quantity.
• Pulled the shingle manufacturer's valley membrane requirement and noted the page.
• Photographed wide, tape-in-frame, pitch reading, valley, and existing condition.
• Built RFG IWS in SF at published pricing for the date of loss; did not hand-key the price.
• Wrote an F9 note citing code section, jurisdiction, existing condition, and quantity basis.
• Stated the eave and valley sub-quantities in working notes for reproducibility.
• Kept all coverage decisions with the homeowner and carrier; no payout, deductible, or coverage promises anywhere in the file.
• Handed the complete, documented estimate to the homeowner to file.

Material, brand, and why the code does not care which one you use

Estimators get into avoidable fights by writing a brand name into the line item. The code language is generic on purpose: it asks for a self-adhering polymer-modified bitumen sheet, or two layers of cemented underlayment. Any membrane that meets the relevant standard and is listed for the application satisfies it. Writing the specific product you intend to install is fine in your own notes and useful for the homeowner, but in the estimate the line should read as ice and water shield, the generic code-required item, with the product spec living in your scope notes rather than baked into the line description.

There are real product distinctions worth understanding so you spec correctly on the roof, even though they do not change the line item itself:

• Granular-surfaced versus film-surfaced (smooth-top). Granular-surfaced membranes give better foot traction and are common at eaves under shingles. Smooth-surfaced, high-temperature membranes are used under metal panels and in valleys where you want a clean slip surface. If you are installing under metal, spec a high-temperature membrane rated for the panel system; a standard eave membrane can soften and ooze under a hot metal roof.
• Standard versus high-temperature adhesive. The adhesive's temperature rating matters under dark shingles in hot climates and especially under metal. Spec to the deck-surface temperature the assembly will actually see.
• Sanded-back versus split-back release liners. This is an installation-speed and detailing difference, not a performance one, but it affects your labor and your crew's preference.

None of these change the RFG IWS line or its square footage. They change which product your scope notes call for, and getting them wrong causes real callbacks (membrane bleeding through metal seams is a classic). Spec it right on the roof; keep the line item generic in the estimate.

Standards a reviewer may ask about

Two reference standards come up. ASTM D1970 is the standard specification for self-adhering polymer-modified bituminous sheet materials used as steep-slope roofing underlayment for ice dam protection. When a reviewer or building official asks what the membrane has to meet, ASTM D1970 is usually the answer at the eave. Knowing the standard exists, and that the membrane you spec meets it, is the difference between sounding like you read a blog and sounding like you read the code.

The price-list discipline that keeps estimates clean

The fastest way to get an otherwise-correct estimate pulled apart is to touch the unit price. The published price list for the property's ZIP and the date of loss already carries a market-derived unit price for ice and water shield that bundles material and labor. Leave it alone. If your real cost is higher because you are installing a premium high-temperature membrane, the place to address that is the product spec and, if warranted, a separate documented line for the upgrade, not a hand-keyed override on the base item.

A few price-list habits that read as professional:

1. Match the date of loss, not today. Prices move. The estimate should reflect the price list in effect at the date of loss, which is the convention everyone reviewing it expects.
2. Do not stack the membrane on top of a full-roof underlayment line for the same area twice. The ice barrier covers specific eave and valley zones. The field underlayment covers the rest. If your underlayment line is calculated for the full roof area and your ice barrier is also calculated for the eave and valley, make sure you are not double-counting the same square footage. Either subtract the eave and valley area from the field underlayment or note clearly that the membrane replaces underlayment in those zones, which is exactly what the code language ('used in place of normal underlayment') anticipates.
3. Let waste fall out of the calculation, not a separate fudge factor. Your lap and trim waste is already implied when you bill installed courses. Adding a separate waste percentage on top of a course-based quantity double-dips. Pick one convention and state it.

That second point, the underlayment overlap, is one of the most common quantity errors and one of the easiest for a reviewer to catch. The code itself tells you the membrane is used in place of normal underlayment at the eave, so the eave area should not carry both a full underlayment charge and a full membrane charge for the same square footage. Document which layer covers which zone and the math is clean.

Reading the pitch correctly, every time

The pitch reading is load-bearing in two ways: it sets the rise in your slope-length math, and it determines whether the 8:12 steep-slope rule is in play. Get it wrong and both your quantity and your code citation drift.

Three reliable ways to read pitch, in rough order of accuracy:

• A pitch gauge or speed-square at the rake against the underside of the roof or a rafter. This is the cleanest reading when you have access.
• A level and tape on the roof surface: hold a level horizontal, measure 12 inches out, and measure the vertical drop to the roof. The drop in inches over 12 is the pitch. A 4-inch drop over 12 inches horizontal is 4:12.
• A phone level app as a quick field check, with the reading photographed for the file. Treat it as confirmation, not gospel, on borderline pitches near the 8:12 trigger.

On a roof with multiple planes at different pitches, read and record each plane that carries eave or valley membrane. A house with a low main roof and a steep front gable can have one plane under the 8:12 rule and one over it, and the quantities differ accordingly. Photograph each reading. A single pitch reading on a multi-pitch roof is an invitation for a reviewer to ask which plane it came from.

Borderline pitches and rounding

When a roof reads right at 8:12, document it precisely, because that reading flips the steep-slope minimum on. A roof that gauges at 8.5:12 is comfortably over; a roof that reads 7.5:12 is under. If you are genuinely on the line, take two readings on the same plane and photograph both. The honest, documented reading protects you either way. Do not round up to capture more membrane and do not round down to dodge the steep-slope rule; record what the roof actually is.

Detached structures, additions, and the edges of the rule

The base code requirement attaches to the building. Real properties have garages, additions, porches, and accessory structures that complicate it.

Detached accessory structures without conditioned space. The 2024 IRC carries an exception that detached accessory structures not containing conditioned floor area are not subject to the ice barrier requirement, on the logic that an unheated detached garage does not generate the warm-roof-cold-eave melt cycle that drives ice dams. If you are roofing a detached, unheated garage, confirm whether your adopted edition and local amendments carry that exception before you put eave membrane on the estimate. Putting it on where the code exempts it is the mirror image of leaving it off where the code requires it, and both undercut your credibility.

Heated additions and bump-outs. Conversely, a heated sunroom or addition with its own eave generates its own ice-dam risk and carries its own eave membrane requirement. Measure and document its eave separately. The original house and the addition are two sets of eave linear feet, and a reviewer who sees them broken out trusts the number.

Porches and overhangs over unconditioned space. A porch roof over open air does not have a warm interior driving melt at its own eave, but it often ties into the main roof, and the main roof's eave membrane requirement still governs where the planes meet. Think about where the conditioned space is and where the cold eave is; that is the physical logic the code is encoding.

The takeaway is to map the heated envelope of the structure before you quote. The ice barrier requirement follows the heated building. Detached and unconditioned structures are where the exceptions live, and knowing them keeps your estimate honest in both directions.

Tear-off documentation: the deck shots that settle everything

The strongest ice barrier documentation comes off a tear-off, because you can show exactly what was and was not there before. On a roof where the existing covering is coming off anyway, build a deck-shot routine into the production sequence:

1. Before the new membrane goes down, photograph the bare deck at the eave and in each valley. This shows whether any existing membrane was present and its condition.
2. If an old membrane is present and being removed, photograph it in place and then removed. A brittle, failed, or single-narrow-course old membrane is exactly the existing condition that supports installing code-compliant coverage now.
3. Photograph the new membrane going down with a tape showing the up-slope coverage. This is the proof that you installed what the code requires, which matters for your workmanship file even after the estimate is settled.
4. Photograph the courses and laps so the installed quantity is visible.

These deck shots do double duty. They support the estimate quantity, and they protect you on workmanship if there is ever a future leak claim at the eave. A contractor who can produce a tape-in-frame photo of two courses of membrane installed to code at the eave is a contractor who is hard to second-guess. Store them with the job file alongside the estimate.

A note on roofs you cannot open before quoting

Sometimes you have to quote before tear-off, off a ground or ladder inspection, and you genuinely cannot see the existing membrane. The honest move is to state that in the file: note that existing eave membrane condition is not visible pre-tear-off, that code requires the membrane regardless of what is found, and that you will document the existing condition at tear-off. That is a true, defensible position. It cites the code as the basis (the requirement does not depend on what was there before) and commits to documenting conditions when they become visible. It is far stronger than guessing.

When the requirement is full-deck

Some jurisdictions, particularly in severe ice-dam climates, amend the code to require ice barrier across the entire deck rather than only at the eaves and valleys. If your adopted local code carries a full-deck requirement, the quantity is straightforward, essentially the full roof area, and the membrane genuinely replaces field underlayment everywhere rather than only at the eave.

The documentation discipline is the same but the stakes on the underlayment-overlap point go up. With full-deck membrane you almost certainly should not also carry a separate full-roof synthetic underlayment line, because the membrane is the underlayment everywhere. Carrying both is the clearest possible double-count. Cite the specific full-deck amendment by section, calculate the area, and make sure the field underlayment line is removed or reduced accordingly. A full-deck membrane estimate that also bills full field underlayment for the same area is the kind of error that gets a contractor's whole file scrutinized, so it is worth a deliberate check.

Working with a third-party estimating service

Many contractors hand their supplement estimating to an outside service rather than keeping it in-house. That can be a good fit, but it does not move the compliance line, and it does not relieve you of owning the documentation. A few things to keep straight if you outsource:

• You still capture the field documentation. The estimating service can build the line item and write the F9 note, but they were not on the roof. The photos, the tape-in-frame overhang shot, the pitch readings, and the existing-condition shots are yours to capture and provide. A service can only estimate what you documented.
• You still own the code lookup, or you confirm theirs. A national service may not know your specific local amendment. Confirm that the citation in the F9 note matches your adopted code rather than only the base IRC.
• The compliance boundary is yours. A third party writing your estimate does not let anyone in the chain promise a payout, eat a deductible, or interpret coverage. The same do-not-say rules apply to your reps, your office, and any service acting on your behalf.

Outsourcing the estimate build is fine. Outsourcing the documentation, the code accuracy, or the compliance discipline is not something you can actually do, because those stay attached to you and your license.

Bringing it together

The ice and water shield code line item is not complicated once you separate the three things that actually matter: the code that requires it, the geometry that sets the quantity, and the documentation that makes it reproducible. Get the adopted code and any amendment right, run the slope-length math so your courses and square footage match the roof, attach a clean F9 note and a tight photo set, and keep every coverage judgment with the homeowner and their carrier. Do that on every roof and the line stops being a point of friction.

Upstream, the cheapest way to make all of this pay is to spend your documentation effort on the roofs that most likely need it. Storm-modeled, per-roof targeting with an imagery-derived age range, the kind of signal RoofPredict adds to your own list, points your crews at the doors most likely to be genuinely due, so the careful estimating work above lands on roofs where it was warranted. The targeting tells you where to go. The workflow tells you how to document it so it holds. Together they turn a frequently-missed line item into one of the most consistently defensible parts of your file.

FAQ

What is the Xactimate code for ice and water shield?

The primary code is RFG IWS (Ice & water shield), priced in square feet (SF). Pricing should be left at the published value in the price list for the property's ZIP and the date of loss rather than hand-keyed. Valley and full-deck applications are handled with the same item at the appropriate quantity, and steeper pitches may carry a labor modifier. Keep eave and valley sub-quantities separate in your working notes so the total is reproducible.

Where does the building code actually require ice and water shield?

IRC R905.1.2 requires an ice barrier at the eaves in jurisdictions with a history of ice forming along the eaves, as designated in Table R301.2. It must extend from the lowest roof edge to a point 24 inches inside the exterior wall line, and on roofs 8:12 or steeper, at least 36 inches measured along the slope. Valleys, penetrations, and full-perimeter coverage are commonly added by local amendments or by the shingle manufacturer's installation instructions. Always confirm the adopted edition and local amendments for the specific jurisdiction.

How do I calculate how much ice and water shield is required at the eave?

Build a right triangle. The horizontal run is the overhang depth plus the wall thickness plus the 24 inches required inside the wall line. The rise is set by the pitch (4 inches per foot at 4:12, and so on). The slope length you install is the square root of run squared plus rise squared. For a 12-inch overhang, 6-inch wall, and 4:12 pitch, that is about 44 inches of slope coverage, which needs two 36-inch courses once you account for the lap. Almost any real overhang pushes you past a single course.

Why is ice and water shield so often missing from the first scope?

Usually because the original scope carried only underlayment, which is a separate field layer, not the code-driven eave and valley membrane. Other common reasons are that the existing membrane could not be seen until tear-off, or that the adjuster was not aware of a local amendment. None of these are adversarial; they are documentation gaps that you close by citing the adopted code and showing the existing conditions with photos.

Does the 2024 IRC change the ice barrier requirement?

Not in any way that changes your quantity. Between the 2021 and 2024 editions, the measured requirements (24 inches inside the wall line, 36 inches along the slope on 8:12-or-steeper roofs) are the same. The notable editorial change was removing the word 'also' and adding a paragraph break in the steep-slope sentence. If someone claims the requirement materially changed, the accurate answer is that the measurements did not.

What should go in the F9 note for the ice barrier line?

Three things and nothing more: the code citation (IRC R905.1.2 as adopted by the named jurisdiction, plus any amendment or manufacturer instruction for valleys), the existing condition you documented, and the quantity basis showing how eave and valley linear feet became square feet. State facts only. Do not argue coverage or what the policy should pay in the note; that is the carrier's decision, not the contractor's.

Is ice and water shield required in valleys?

The base IRC mandates it at the eave, not automatically in valleys. Valley membrane usually becomes required through one of two routes: the shingle manufacturer's installation instructions (which the code requires you to follow), or a local amendment that explicitly calls for valley or full-deck membrane. Cite whichever actually applies, and pull the manufacturer's installation page so you can reference it by page number.

Can I tell a homeowner that ice and water shield will be covered by their insurance?

No. Coverage is the carrier's decision under the policy, and promising a specific approval, payout, or that a particular line will be paid can amount to unlicensed public adjusting in many states. Your role is to document the roof thoroughly, write an accurate code-aligned estimate for your scope, and hand it to the homeowner. The homeowner files, and the insurer decides coverage. Keep all coverage statements out of your sales conversations and your file.

How many photos do I need to document the ice barrier line?

At minimum: a wide shot establishing location, a tape-in-frame shot of the overhang depth and existing membrane condition, a legible pitch reading, and a valley shot. A screenshot of the adopted code section or the manufacturer's installation page is optional but removes doubt. Time-stamped and geotagged photos quietly answer the 'right house' and 'current' questions before anyone asks. Three strong, relevant photos beat a pile of vague ones.

How does roof-targeting data like RoofPredict relate to estimating ice and water shield?

It works upstream of the estimate. RoofPredict uses aerial imagery and per-roof storm physics to rank which roofs in a territory are most likely due, returning a roof-age range per address plus a storm-exposure model run per roof, so crews knock the doors most likely to genuinely need an assessment. It does not file, handle, or decide anything. The age is a range, not a build date, and exposure is odds, not proof, so you still climb the ladder and document every roof yourself. The data decides where to spend the day; the documentation workflow decides whether the day's estimates hold up.