Code Isn’t Stone —
It’s Process and Judgment 

The day I was truly educated on the building code is one I will never forget. I was a new manager at an architectural firm when asked to address a contentious issue with a local building department regarding a remodel we were designing. The existing building clearly did not meet code and presented both fire and egress concerns.

As part of the remodel, we proposed what we believed was a straightforward solution to correct the condition. Surprisingly, the local building department resisted modifying the non–code-compliant area. It quickly became clear they were not inclined to reconsider. Because I had previously taught classes for this jurisdiction, I was asked to step in and request a formal meeting.

The city arrived well prepared. Present were the building official, senior staff, the fire marshal and the city attorney. On our side were my firm’s AIA principal and the state building official, who happened to be a colleague. I presented the issue, cited applicable code language and walked through our proposed correction. Then the city attorney said something I will never forget: “It is not a code violation—because the stamped plans are the code for this project.”

Who’s Right?

I was stunned. I had just cited the code language directly. My colleague, the state building official, leaned over and quietly said, “Technically, he’s correct. Those approved plans establish compliance for this specific project.” That meeting fundamentally changed how I understood building codes. In less than thirty minutes, I learned that building codes and standards are not immutable documents.

That experience demonstrated that code is not purely static. It is a regulatory framework interpreted, applied and enforced through professional judgment, approvals and project-specific decisions. Once plans are reviewed and approved by the Authority Having Jurisdiction, they establish compliance for that specific project—even when they diverge from strictly prescriptive language. This does not mean code is ignored; it means it is applied through a professional process that includes design judgment and regulatory oversight.

With that perspective, it becomes difficult to argue that something as minor as a stucco control joint—a crack-control detail with no life-safety function—should automatically be labeled a “code defect.” If the overall assembly is code compliant, designed by a licensed architect, approved by the building department and supported by industry guidance such as the Stucco Manufacturers Association, claims that ASTM guide language must be followed without exception become harder to sustain.

This does not mean standards should be ignored. ASTM standards and industry guidelines are valuable tools that help guide good construction practice. But like the building code itself, they are meant to inform professional judgment—not replace it. ASTM standards, like building codes, are tools—not traps.

That Seattle meeting was eye-opening. It taught me that compliance is not about reciting text; it is about process, approval and reasoned application. That lesson applies just as much to stucco control joints as it does to egress corridors.

Practical Guidance for Contractors

If a contractor believes a detail on stamped plans conflicts with code or ASTM standards, a simple Green–Yellow–Red decision model can help guide action.

Green Light: Items that may be unusual but are unlikely to cause damage. Proceed as shown in the contract documents.

Yellow: Items that cause concern and could reasonably result in damage. Notify the architect in writing, provide technical justification, and document potential consequences. Then proceed as directed, even if design changes are not made. This demonstrates standard of care. Avoid proposing independent fixes without documentation, as liability for the solution may later shift to the contractor.

Red: True safety hazards where failure is likely or public safety is at risk. These situations are rare since design professionals and building departments provide oversight. In these cases, responsibility extends beyond contract obligations; protecting the public becomes the priority.

Most construction decisions fall short of this level. They usually involve details, preferences or interpretations rather than life-safety hazards.

Misunderstandings about codes and standards are common. Too often, we assume that “stricter” automatically means “safer.” In reality, codes are applied through professional judgment, regulatory oversight and documented approval. Compliance is not about building the strictest possible assembly; it is about building the approved, documented one.

The best approach is simple: follow the documents, communicate concerns early, and carefully document anything that raises risk concerns.