Skip to main content
AREProject Planning & Design

Resolving Code Conflicts: Overlapping Requirements, Amendments, and Most Restrictive Provision

How architects identify, analyze, and resolve conflicts between overlapping building codes, amendments, and jurisdictional requirements by applying the most restrictive provision doctrine, equivalency clauses, waivers, and alternative compliance methods.

2 min read201 words

Why Code Conflicts Matter in Project Planning

Every real building project sits at the intersection of multiple codes. The IBC governs structure and fire safety. Energy codes set envelope and mechanical performance thresholds. Accessibility standards layer on additional dimensional requirements. Local amendments tighten (or occasionally relax) state-adopted model code provisions. Federal projects add yet another tier, like the GSA P100 standards that explicitly override adopted codes when conflicts arise.

The result? Overlapping, sometimes contradictory, requirements that an architect must untangle before a single line gets drawn. Miss a conflict and the project stalls at plan review, or worse, during construction.

Resolving these conflicts is not a mechanical exercise. It demands evaluative judgment: which code governs, which provision is most restrictive, whether an equivalency or waiver is available, and how to document the resolution so the authority having jurisdiction accepts it. The ARE tests exactly this skill under Objective 2.3, expecting you to analyze how multiple codes interact and determine the governing requirement when they collide.

This topic covers the hierarchy of code authority, the most restrictive provision doctrine, amendment and local modification processes, equivalency and alternative compliance paths, and the waiver and variance procedures architects use when strict compliance creates conflicts with other legitimate project goals or constraints.

Want to track your progress and access more study tools?

Create a free account