A code upgrade supplement asks the carrier to pay for work the current building code requires and the carrier's first scope left off. It holds up because a repair has to meet the code in force today, not the code that was in force when the roof was built. Three items come up on roofing files more than any others: ice and water barrier at the eaves (IRC R905.2.7.1 in the 2018 editions, IRC R905.1.2 in the 2021 editions), drip edge at the eaves and the rakes (IRC R905.2.8.5), and a re-nail of the existing decking on a full tear-off. To get any of them approved, name the item, cite the section that requires it, cite the adopted edition that puts that section in force, and keep the code items in their own block. A reviewer can say yes to a citation. Nothing else on the page gives them a reason to.
Why do first-pass scopes miss code items?
Two habits put a first-pass scope behind the code. The first is assembly speed: the scope is written from a template for the property, and a template carries the standard line roster, never the local adopted code edition. The second is like-for-like logic: the carrier pays to restore the roof to the condition it was in, and the roof was built under an older code. When a jurisdiction adopts a newer edition, every re-roof in that jurisdiction inherits requirements the old roof never had. The condition is not the argument. The code is.
That is why a code upgrade is the cleanest supplement line there is. It does not ask the reviewer to agree with a judgment call. It asks them to agree with a citation, and there is nothing on the form for them to weigh against it.
The three items that carry most roofing files
Ice and water barrier, and the climate trigger
Where the average January daily mean temperature is 25 degrees or below, an ice barrier is required from the roof edge to at least 24 inches inside the exterior wall line. That is IRC R905.2.7.1 in the 2018 editions many states still use, and IRC R905.1.2 in the 2021 editions. Two things go wrong on a re-roof: the barrier is left off a roof that requires it, or it is written for the eave alone when the shingle manufacturer's instructions extend it to valleys and penetrations. The manufacturer instruction is the stronger argument of the two, because the carrier is paying to install that product the way its instructions require.
Drip edge, at the eaves and the rakes
Drip edge is cheap per foot, which is exactly why it gets treated as a rounding error until you count the quantities. The code is specific: drip edge is required at the eaves and the rake edges of shingle roofs, and adjacent pieces have to overlap by at least 2 inches (IRC R905.2.8.5). The usual miss is a scope that pays the eaves and skips the rakes, or the reverse. Measure both and write both.
Re-nailing the decking on a tear-off
On a full tear-off, the deck gets exposed and re-fastened before the new underlayment goes down. That step comes from the shingle manufacturer's installation instructions, and it is worth checking your own state's code for additional fastening rules on a re-roof. Re-nailing is its own line with its own labor, and it is routinely absent from a template scope. Walk the deck at tear-off and log the fastening pattern; the photo of the deck mid-tear-off is what backs the line.
How do you write a code upgrade line?
Four parts, in order.
- The item: what is being added, in plain words. "Ice and water barrier at the eave" beats "miscellaneous code items."
- The requirement: the section that requires it, written the way a code book writes it. IRC R905.2.8.5, not "code requires this."
- The adopted edition: the edition your jurisdiction has actually adopted. A citation to an edition your state has not adopted hands the reviewer a reason to say no.
- The scope gap: one line on why the item is not already on the scope. The scope priced a re-roof under the old code; the re-roof is being built under the new one.
Keep the code items in their own block, separate from quantity corrections and condition work. A reviewer evaluates a citation differently than a judgment call, and mixing the two makes every line look negotiable. Say what the item is, cite the section, cite the edition, and stop. There is no column on the review form for emphasis, and there is a column for the code section.
How does a converted scope fit in?
The code block answers what the roof requires. The carrier's scope answers what was priced. The comparison between the two is the whole job, and it starts with getting the carrier's PDF out of read-only form. Converted into Xactimate structure, the scope sits next to your own estimate line for line, and the difference is a working list instead of a stack of paper. Every line keeps the price it had on the PDF, and any line that cannot be matched to a code keeps that price and is flagged for review instead of being guessed at.
The point of the comparison is the gap. While competitors convert what is already on the PDF, ESXPress identifies and restores what the carrier omitted. That is the difference between a file you retype and a supplement you can prove.
Ready to see what a carrier scope left off your next file? Start free. 5 conversions a month, no card required. The PDF to Xactimate page covers how the conversion works, and the supplement software and supplement guide pages cover what to do with the list once you have it.
Related reading: the taxonomy of what carriers omit, the hail claim code items, and the code upgrade supplement glossary entry. The roofing code index groups the SEL families a supplement needs.
Review required: AI-assisted content requires professional review. Verify every line item, price, and total against your actual scope before submission.