✕

Picture it: a large mixed-use commercial project in the Southwest. The plumbing contractor has worked through months of coordination meetings, revised submittals and tight sequencing when an inspection threatens to stall progress. The issue centered on domestic water system sizing; on paper, the installation didn’t align neatly with a long-standing prescriptive assumption in the code. At first glance, it looked like a violation.

In many cases, that’s where things spiral — red tags, redesign, delays and uncomfortable conversations about who’s paying for what.

But this time, the contractor took a different approach. Instead of arguing over isolated code language, he stepped back and focused on intent. He referenced the purpose behind the provision, provided hydraulic calculations and documented actual system demand using current methodologies. The system, he showed, met the performance objective the code was written to achieve: safe, reliable water delivery without introducing unnecessary risk.

The tone of the conversation changed. What began as a compliance issue turned into a technical discussion. The inspector reviewed the documentation, accepted the justification and approved the installation without requiring redesign. The project stayed on schedule.

That’s luck, right? Actually, it’s code literacy.

For decades, many in the trades viewed codes primarily as guardrails — install it this way, size it that way, pass inspection and move on. The rules were largely prescriptive, and compliance often felt like a final checkpoint rather than a design tool.

Today, things look very different.

Buildings are tighter, water use is lower and systems are more interconnected. Electrification and sustainability are completely reshaping mechanical design. At the same time, public health concerns — especially around water quality and Legionella risk — are pushing the industry to think beyond minimum requirements.

Now, there’s a meaningful difference between complying with code language and understanding what the code is trying to accomplish.

Contractors who understand how a section is structured, what standard it references and what failure it was designed to prevent can anticipate questions before they’re asked; they submit cleaner drawings, they recognize when a perceived conflict between plumbing, mechanical and energy provisions is actually a matter of interpretation. They can explain — clearly and professionally — why a system works, not just that it passes.

That ability changes a contractor’s position in the room.

Owners are increasingly focused on lifecycle risk, not just passing final inspection. Engineers balancing water efficiency with system performance need partners who understand hydraulics, stagnation and temperature control. Authorities having jurisdiction are managing evolving codes and heavier workloads, and they tend to respond well to professionals who come prepared with thoughtful documentation instead of reactive arguments.

Code expertise is most powerful before drawings are stamped and submitted. grandriver / iStock / Getty Images Plus

Plumbing codes were born out of 19th-century public health crises. They were designed to prevent disease in rapidly growing cities. Over time, they evolved into standardized model codes that brought consistency across jurisdictions and supported modern construction.

Now, those same codes are expanding into areas like resilience, electrification, water quality management and long-term accountability. No longer are they static rulebooks; they’re living frameworks shaping how systems perform over decades.

As that framework grows more layered — with referenced standards, performance paths and sustainability requirements — the professionals who treat code as a strategic tool rather than a hurdle are separating themselves from the pack. On today’s jobsite, the biggest risk isn’t the red tag. It’s failing to understand how the code actually works — and missing the opportunity to use that knowledge to move projects forward instead of slowing them down.

I spoke with IAPMO's Vice President of Technical Services and Research, Christoph Lohr, and several representatives from ICC: Matt Sigler, PMG Executive Director, Kris Stenger, Assistant Vice President, Codes Development, and Dr. LaToya Carraway Technical Staff to discuss how today’s contractor can use a knowledge of codes and standards as a strategic advantage in today’s industry.

Code compliance vs. code intent: the strategic divide

In its simplest terms, code compliance means meeting the written requirements of a given system exactly as they’re published.

But that, the International Code Council (ICC) emphasizes, is only one layer of professional responsibility.

“The difference between complying with code language and understanding code intent is the difference between obeying the law and embracing the purpose behind it,” ICC representatives told me. “Complying with code language takes a literal approach that makes sure every word is met exactly as written, whereas understanding code intent goes deeper by applying expert judgement beyond the written code language and identifying the original purpose of the code.”

That distinction is especially critical when projects don’t fit nicely into prescriptive assumptions, which is increasingly the case – like mixed-use occupancies, electrified mechanical systems, aggressive water efficiency targets and evolving resilience requirements create conditions that may not have been considered in legacy tables or formulas.

“Construction projects can be unpredictable, and understanding the code intent allows contractors and design teams the ability to adapt while still providing the required outcomes,” ICC’s representatives noted.

In other words? Intent literacy provides flexibility without sacrificing safety.

From the perspective of Christoph Lohr, the conversation goes even deeper. He stressed that minimum code text does not always capture emerging performance risks, particularly around water quality and system hydraulics.

“The gap emerges from where many codes do not yet address water quality, system hydraulics, or long term microbial risk, even though those factors directly affect occupant safety,” Lohr explains. “In practice, there are numerous standards and guidance documents that fill this gap, but they are not always formally adopted into code.”

That gap, unfortunately, carries legal implications.

“When a system complies with code but ignores this guidance, the issue often surfaces later in litigation, where the standard of care, not the written code, becomes the benchmark that gets applied,” Lohr says.

Courts routinely evaluate whether professionals acted in accordance with what a reasonably prudent practitioner would have done under similar circumstances. That analysis may include consensus standards developed through processes accredited by the American National Standards Institute, industry guidance documents and widely recognized best practices — not just adopted model code text.

The result is a widening divide between minimum compliance and defensible performance.

For contractors and engineers, that divide represents both risk and opportunity. Those who operate strictly at the prescriptive level may pass inspection, yet leave owners exposed to long-term operational or microbial issues. Those who understand how codes interact with referenced standards and performance guidance can proactively shape safer, more resilient systems.

Code fluency transforms contractors from installers into technical partners. Conversations shift from “Is this allowed?” to “Will this function as intended over time?”

Moving upstream: influence at the design table

Code expertise is most powerful before drawings are stamped and submitted.

ICC underscores that its role extends beyond publishing model codes. “Model codes are the starting point, but there are many additional pieces that must be in place to ensure effective application,” they noted. As systems become more complex, ICC says, “a holistic approach to solutions is required.”

For contractors, that holistic understanding creates leverage early in the design process. ICC emphasizes that having code expertise involved in initial stages “prevents costly delays at time of permitting, potential redesign costs and potential failed inspections.” Moreover, “being able to back up solutions with code justifications brings assurance to designers and can create a trusted relationship that leads to future work.”

In practical terms, that means translating code provisions into actionable design constraints — clarifying pipe sizing strategies, reconciling plumbing and energy requirements, anticipating documentation expectations from authorities having jurisdiction (AHJs), etc.

Lohr offers a concrete example in the Phoenix Central Station project. There, the project team used a performance-based demand methodology — the Water Demand Calculator — to justify right-sizing the domestic water system. “The approach was reviewed, accepted, and approved during the project, avoiding oversizing and unnecessary redesign,” Lohr says. “Following completion of the project, the City of Phoenix moved to adopt the Water Demand Calculator more broadly.”

The lesson is clear: informed application of code intent can influence not only a single project outcome, but future policy direction.

At a day-to-day level, code-literate professionals submit clearer documentation and anticipate inspection concerns. Lohr notes that contractors who understand how codes are structured and interpreted “submit cleaner documentation and anticipate inspection concerns.” In one large commercial project, he adds, “a perceived violation was actually an intent-based compliance issue and documented system performance accordingly. The issue was resolved in the field without redesign or delay.”

The strategic advantage is measurable: reduced frictional cost. Time is money, and minimizing rework, redesign and schedule disruption directly improves project margins.

Contractors who understand code intent engage as technical partners rather than installers. Su Arslanoglu / iStock / Getty Images Plus

Competitive differentiation across the ecosystem

As codes evolve beyond basic health and safety protections into frameworks addressing resilience, sustainability, electrification and long-term system performance, their influence extends all the way across the entire construction value chain. Code literacy is no longer confined to inspectors and plan reviewers; it shapes how contractors bid and build, how engineers design and document, and how manufacturers develop and position products.

Contractors

Code fluency provides contractors with tangible operational benefits.

The International Code Council notes that code knowledge “can help smooth inspections and avoid rework, which often means quicker completion (and time is money).” It also “helps demonstrate a commitment to public health and safety, which can build credibility amongst owners and clients looking to avoid costly issues down the road.”

Stronger relationships with code officials often follow. According to ICC, code fluency “can help contractors stand out in a competitive market by building stronger relationships with code officials to help keep projects on schedule.”

Lohr reinforces that contractors who understand code intent “engage as technical partners rather than installers, focusing discussions with engineers on whether systems will actually function as intended, not just whether they pass review.”

That shift in perception — from installer to advisor — enhances long-term market positioning.

Engineers

Engineers face expanding expectations tied to resilience, sustainability and public health. ICC stresses that professionals with “sophisticated building code literacy are better equipped to design buildings that not only safeguard people but also function effectively, last over time and more easily adjust to changing needs.”

Lohr adds that engineers increasingly must integrate standards and emerging guidance documents to protect clients — and themselves — from liability exposure. As enforcement and litigation trends evolve, demonstrating alignment with the broader “standard of care” becomes essential.

Code literacy, in that context, is both technical competency and professional protection.

Manufacturers

For manufacturers, participation in consensus development processes is strategic.

Lohr notes that evolving codes do not necessarily slow innovation. “Leading manufacturers who stay abreast of industry changes and requirements often develop products to industry challenges faster than those who don’t,” he says. The low-flush toilet transition illustrates that principle. When federal water conservation mandates reduced allowable flush volumes, manufacturers that embraced engineering innovation — rather than resisting change — ultimately emerged as trusted leaders. “The manufacturers who lead this effort are still considered by many to be the leading manufacturers they trust to bring new technologies forward,” Lohr explains.

Education pipeline: from apprentice to master

If code literacy is a strategic advantage – and we certainly think it is – it cannot begin at the permit counter. It has to be built deliberately over the course of a career.

The International Code Council frames code education as a progression; one that mirrors how responsibility expands in the field.

Apprentice: understanding why

At the apprentice level, the goal is simple: foundational awareness. According to ICC, early training should focus on understanding why codes exist in the first place, along with trade-specific basics.

“The most important early lesson is that codes are written in an attempt to prevent failure and improve health and safety. When contractors understand that codes exist to prevent health, safety and reliability issues, the requirements stop feeling arbitrary,” Lohr explained.

When apprentices understand that trap seals prevent sewer gas intrusion, and that pipe sizing tables were developed to mitigate pressure fluctuations and system stress, codes stop being abstract.

Beginner: applied code

As technical skills deepen, so should applied code knowledge. ICC identifies this stage at the point where you should be able to apply code provisions in real-world tasks; pipe sizing, backflow protection, etc.

At this stage, installers should begin to see how codes intersect with constructability. Why does a vent offset matter? What happens hydraulically when ultra-low-flow fixtures are installed in legacy distribution systems? Applied literacy reduces field corrections, and improves first-pass inspections.

Journeyman: intersections and interpretation

Roughly between years four and ten, the journeyman stage introduces complexity.

According to ICC, this level should include “understanding conflicts between plumbing, mechanical and energy codes and how referenced standards figure into the bigger picture.” The modern code environment is layered, after all. “Journeyman also should develop the ability to evaluate construction drawings and work closely with code officials.”

This is often where literacy becomes visible. Recognizing whether a perceived conflict is truly noncompliant or simply required clarification prevents escalation.

Master: design and mentorship

At the master level, ICC describes a professional capable of designing and installing systems based on code requirements and teaching other how to both interpret and apply them.

This stage is less about memorizing sections, and more about understanding structure. Masters know how provisions are organized, how standards and incorporated by reference, and how to document compliance in a defensible manner.

They serve as translators and teaching: helping younger tradespeople understand not just what the code says, but what it is trying to accomplish.

So, how do you begin your journey to master? With system complexity rapidly accelerating, static classroom instructions are no longer sufficient.

Thankfully, there are resources. “ICC is expanding its on‑demand learning options, giving professionals greater flexibility in how and when they train. The organization is also updating its credentials to reflect tech‑driven competency requirements through our Credential of Learning Achievement (CLA) program.” Digital platforms allow contractors and engineers to access update code commentary, compliance tools and training modules without leaving the jobsite for extended periods.

In addition, ICC Preferred Provider Network connects professionals with specialized, technology-focused training providers.

“ICC also hosts events and awareness campaigns that emphasize tech‑enabled safety and construction practices, helping building safety professionals stay current in a fast‑changing industry. This approach ensures that contractors have access to current, flexible and practical training that evolves alongside the technologies and systems they encounter in the field.”

One thing is clear: code literacy is more than a one-time certification event. It is continuous professional development.

Misconceptions about code development

A persistent misconception in the field is that codes are written behind closed doors by regulatory staff who haven’t seen a jobsite in years, or maybe ever.

“There are misconceptions that the codes are developed in a vacuum by the staff of the International Code Council,” ICC told me. “When in fact, ICC is the conveyer of the process in which codes and standards are developed.”

Model codes are produced through a consensus process that invites participation from code officials, engineers, contractors, manufacturers and industry group. ICC’s role is to facilitate that process, publish the codes and support long-term sustainability through technical resources.

The process is open; in fact, contractors can attend hearings, engineers can testify. Standards referenced by codes are often developed under accreditation by the American National Standards Institute, ensuring balanced stakeholder representation.

For companies that treat code as a static rulebook, that process might seem distant. But, for those who actively engage, it represents a significant strategic opportunity. Participation provides early insight into regulatory trends, and allows stakeholders to influence how emerging technologies are addressed. It creates visibility within the industry, and builds relationships with regulators and peers.

The strategic takeaway is simple: involvement shapes the competitive landscape. Those who participate help define the rules. Those who abstain adapt to them after adoption.

The legal and financial dimension

For decades, many contractors viewed code compliance as a binary outcome: pass inspection, close permit, move on. But, both ICC and IAPMO stress that the risk environment has shifted.

Lohr is direct about where the vulnerability lies. “When a system complies with code but ignores this guidance, the issue often surfaces later in litigation, where the standard of care, not the written code, becomes the benchmark that gets applied.”

That distinction is critical.

Model codes establish minimum requirements enforceable by authorities having jurisdiction. The standard of care, by contrast, reflects what a reasonably prudent professional would have done under similar circumstances — often informed by referenced standards, manufacturer instructions, emerging guidance documents and known failure modes.

According to the International Code Council, “Model codes are the starting point, but there are many additional pieces that must be in place to ensure effective application,” they explained. As system demands grow and technologies evolve, ICC says, “a holistic approach to solutions is required.”

Contractors who understand not only what the code says but why it says it can document their decisions more thoroughly. Engineers who integrate referenced standards into their design narrative create a defensible record of due diligence.

ICC emphasizes that code fluency “helps demonstrate a commitment to public health and safety, which can build credibility amongst owners and clients looking to avoid costly issues down the road.” That credibility is not merely marketing language; it has contractual implications. Owners increasingly evaluate teams based on lifecycle reliability and risk mitigation, not just lowest bid.

Lohr underscores that contractors who understand code intent “engage as technical partners rather than installers, focusing discussions with engineers on whether systems will actually function as intended, not just whether they pass review.”

That focus on functionality over minimum compliance aligns directly with litigation trends centered on outcomes. Performance — not just inspection approval — is what ultimately gets evaluated.

There was a time when code knowledge meant surviving inspection. It was defensive, reactive. It was about avoiding the red tag. But now, that era is fading.

Today, the regulatory environment is layered with sustainability mandates, electrification requirements, resilience benchmarks and water quality expectations. Codes increasingly reference consensus standards and performance paths. Documentation expectations extend beyond the permit phase into commissioning and operations.

Professionals who understand only the words on the page may achieve literal compliance, but those who understand structure, intent and referenced standards influence outcomes.

Lohr reinforces that early and deep code literacy changes professional trajectory. “When contractors understand that codes exist to prevent health, safety, and reliability issues, the requirements stop feeling arbitrary.” That mindset shift transforms compliance from obligation into opportunity.

ICC dispels the notion that code development is remote or inaccessible: “The process is open to anyone who wants to be involved.” Participation shapes requirements. Engagement builds foresight. Foresight builds competitive advantage.

In a market where margins are tight and accountability is expanding, firms that treat code as paperwork will likely continue to operate at the minimum threshold. Firms that treat code as strategic infrastructure — integrated into education, design strategy, documentation and product development — will define the next phase of plumbing and mechanical performance.

Code knowledge once equaled inspection survival. Now, it equals influence, profitability and long-term relevance.

And as codes continue their evolution from prescriptive rulebooks to performance-driven frameworks, operational fluency will increasingly separate those who merely comply from those who lead.