Browse the full Resources Index
A repair estimate that simply lists materials and labor tells only part of the story when local building codes require something different from what was originally on the structure. Code items are the line entries that exist because a jurisdiction’s adopted code, not the original construction, dictates what must go back. Distinguishing them from ordinary repair or replacement items is a matter of documentation discipline as much as construction knowledge, and it matters because the two categories are often treated differently under a policy.
Properly documenting a code item starts with identifying the authority having jurisdiction, meaning the city, county, or state body that adopted and enforces the applicable code, along with the edition in force at the time of the loss. Minnesota, for example, has adopted versions of the International Residential Code and International Building Code with state-specific amendments, and municipalities can layer on additional requirements. An estimate that cites a code item should reference the specific section, such as a requirement for ice barrier extension in colder climate zones or a minimum decking attachment schedule triggered by a full roof replacement, rather than a general statement that code required more work.
Common examples in residential roofing include drip edge at eaves and rakes where none previously existed, ice and water shield extension requirements tied to climate zone, and re-nailing or replacing sheathing when an inspection during tear-off reveals fastening that does not meet current standards. On the exterior, code items can also arise from electrical, plumbing, or egress requirements triggered by the scope of repair, particularly when a jurisdiction requires bringing an affected system up to current code once a wall or roof assembly is opened.
Timing adds another layer of complexity, since code editions do not update on a fixed nationwide schedule. The International Code Council publishes new model code editions on a multi-year cycle, but individual states and municipalities adopt, amend, and enforce those editions on their own timelines, sometimes lagging the model code by several years and sometimes modifying specific provisions before adoption. A property in one Minnesota municipality can be subject to a different code edition, or a different local amendment, than a comparable property in a neighboring city, which means an estimate written against a generic or outdated code reference can misstate what the actual authority having jurisdiction currently requires. Confirming the edition and any local amendments in effect at the permit date, rather than assuming a national default, is a basic step in supporting any code item listed on an estimate.
Because code items are frequently disputed, an estimate benefits from separating them clearly from the base scope of repair, with a citation to the specific code provision and an explanation of why the loss and repair scope triggered it. Photographs, permit correspondence, or a written confirmation from the local building department can support that documentation. An appraiser reviewing an estimate with code items is evaluating whether the item is properly identified and consistent with the physical scope of damage; whether the policy affords coverage for code-related costs, often addressed through an ordinance or law provision, is a coverage determination that belongs to the policy language and the parties, not to the appraisal panel.
This article is general education about how the appraisal process commonly works. It is not legal advice, and specific procedures can vary by state and policy.
Russ Lis is a working property insurance appraiser and umpire based in Minnesota, serving clients nationwide. Contact Appraisal Resolution.