When Codes Collide: Making Sense of the IRC with Glenn Mathew
Why Building Codes Feel So Confusing
If you've ever opened a code book and felt like three people were arguing on the same page, you're not alone. Builders, inspectors, and homeowners all share this sentiment. On the BS and Beer Show, code educator Glenn Mathew often explains why it feels this way, especially with the International Residential Code (IRC), the primary model code for one- and two-family homes in the United States. The short answer is that the IRC is not a single, unified voice; it's a compilation of various sources.
The IRC as a Kind of Frankenstein
Glenn describes the IRC as a sort of Frankenstein—not in a frightening way, but more as something "stitched together from many parts." Different sections of the IRC are derived from various source codes and organizations. For instance, energy rules come from the energy code, gas rules from a fuel gas code, and electrical rules from the National Electrical Code. Additionally, the IRC references other documents, such as pool codes, property maintenance codes, or wildland-urban interface rules in fire-prone areas. All this content was written at different times, by different groups, with different priorities. When you encounter contradictions, you're usually seeing the seams where these pieces meet. This doesn't mean the whole thing is broken; it just means you sometimes need to know which part is speaking and what problem it aims to solve.
Who Wins When Rules Clash
The IRC anticipates conflicts and provides a few simple tiebreakers. First, a broad rule usually speaks first, followed by a more specific rule that adds detail for a particular situation. If these two don't align, the more specific rule generally prevails, as it is tailored to your scenario. If two specific rules seem to disagree, you often end up either doing the more restrictive thing or finding a detail that satisfies both simultaneously. This second option is common in real projects because a wall, roof, or slab usually has to meet several code sections at once.
There's also a hierarchy when incorporating outside references. If a referenced standard contradicts the main IRC text, the IRC text prevails. If a listed product’s manufacturer instructions conflict with a generic line in the code, the manufacturer’s instructions usually take precedence, as they reflect how the product was tested and approved. While not perfect, this approach helps sort through the noise.
Codes as Recipes, Not Just Orders
Glenn suggests shifting your perspective from viewing the IRC as a giant list of orders to seeing it as a cookbook. There are sections with strict “you must do this” rules for basic safety and health. Surrounding these are optional recipes you can choose from.
Some examples of these recipes include:
A method to build a shallow frost-protected foundation for a heated building
A different approach to protect an unheated slab from frost
A simple table for energy efficiency, indicating where to place R-values
Details for using exterior insulation to keep wall sheathing warm enough to avoid condensation
Insulation appears in many of these sections, much like eggs in breakfast, dinner, and dessert. In the frost recipe, insulation keeps the soil warm enough to prevent heaving. In the energy recipe, it ensures occupant comfort and controls bills. In the vapor control recipe, it keeps the inside face of the sheathing above the dew point to prevent moisture. The IRC doesn't know which combination of recipes you've chosen for your house, so it can't connect those dots for you. That responsibility lies with you and your design team. You choose the menu and then add up the ingredients.
Prescriptive Versus Performance Paths
Much confusion arises in the energy section, particularly around the different compliance paths. The prescriptive path is like a basic dinner recipe. You consult a table, find your climate zone, and it tells you what R-value to use in your walls, ceilings, and slab edge. If your house is fairly typical, this path is straightforward and predictable, which is its purpose.
The performance and energy rating paths are more like hiring a chef. You compare your design to a standard reference house using energy modeling or a rating system. This approach offers more freedom and flexibility but also involves more calculations and judgment.
When used effectively, these flexible paths are ideal for:
Unusual architecture
Very low energy designs
Projects where the basic tables don't quite fit
When used poorly, they can become a way to bypass inconvenient details. For example, cutting cavity insulation in one area and claiming to “make it up” elsewhere may look good in software but doesn't protect comfort or durability in real life. Code writers are aware of this, so newer editions include minimum backstops to prevent any part of the building from being compromised just because the numbers balance out on paper.
Glenn emphasizes that none of these paths are inherently good or bad. They are tools. You can achieve a robust or risky house with any of them, depending on how thoughtfully you use them and how well you coordinate with the rest of the code.
A Quick Word on Vapor and Condensation
Glenn also reminds us that energy rules aren't the only place where R-value is relevant. Moisture control has its own set of recipes. For example, the IRC includes tables showing how much continuous exterior insulation you need if you opt for a more vapor-open interior paint instead of a strong interior vapor barrier. The goal here isn't comfort but to keep the wall sheathing warm enough to prevent indoor humidity from condensing on the cold side in winter.
If you later decide to increase your cavity insulation from a 2x4 wall to a 2x6 wall without changing the exterior, you cool the sheathing down even more. This often means revisiting the exterior insulation recipe to ensure moisture control remains effective. It's the same theme: one material, several different jobs, and you must ensure all those demands align.
Final Pour
The key takeaway from Glenn’s perspective on codes is that the International Residential Code isn't trying to design your house for you. It's setting a minimum safety standard and providing a comprehensive set of recipes so you can build something safe, durable, and efficient without starting from scratch. Insulation, vapor control, frost protection, and energy targets each have their own chapters, created at different times for different reasons. The magic happens when you integrate these elements into a cohesive assembly that works in the real world.
If you treat the IRC like a blunt instrument, it will feel cumbersome and frustrating. However, if you approach it as a dense, occasionally quirky cookbook, it becomes a resource you can rely on while engaging in the real work of design, coordination, and judgment. This approach allows builders, designers, and even curious homeowners to move beyond “just to code” and toward creating buildings that are genuinely comfortable and enjoyable to live in.