Building Codes Overview: Structural Requirements Explained

How US Building Codes Are Organized and Enforced
The United States does not operate under a single federal building code. Instead, codes are developed by standards organizations, adopted by state legislatures or state building departments, and enforced by local jurisdictions through plan review and inspection. This layered system means a structural engineer in Texas may work under slightly different requirements than a colleague in Oregon, even when both reference the same model code.
At the top of the hierarchy sit model codes—documents produced by organizations such as the International Code Council (ICC). States adopt these models, often with amendments, and localities may layer on additional modifications. Enforcement falls to the Authority Having Jurisdiction (AHJ), typically a city or county building department. The AHJ reviews construction documents, issues permits, and dispatches inspectors to verify field compliance. When a project departs from prescriptive requirements, the engineer of record must provide calculations demonstrating that the alternative approach meets the intent of the code—a process called an alternate means and methods request.
Understanding this hierarchy is essential before diving into any specific provision. A code section that appears mandatory in the model document may be amended, deleted, or supplemented by the state or local AHJ. Always confirm which edition and which local amendments govern a project before beginning structural design.
The International Building Code (IBC): Scope and Structural Provisions
The International Building Code, published by the ICC, serves as the primary model building code for most US states. It covers occupancy classifications, fire resistance, means of egress, accessibility, and—critically for structural engineers—the structural design requirements that govern how loads are determined and resisted.
Structurally, the IBC does not stand alone. Chapter 16 establishes the framework for structural design: it defines load types (dead, live, wind, seismic, snow, flood, and others), specifies how loads must be combined, and mandates that structural systems be designed in accordance with referenced standards. Rather than containing detailed design equations itself, the IBC points to ASCE 7 for load determination and to material-specific standards for member design. This referencing structure keeps the IBC manageable while allowing technical standards to evolve with engineering research.
Occupancy category—now called Risk Category in current editions—directly affects structural requirements. A Risk Category IV essential facility such as a hospital must be designed for higher seismic and wind demands than a Risk Category II office building of identical geometry. The IBC also establishes minimum construction document requirements, specifying what calculations, drawings, and special inspection programs must accompany a permit application. For structural engineers, Chapter 17 on special inspections is particularly important: it defines which structural elements require third-party inspection and testing, and it assigns responsibility between the engineer of record, the special inspector, and the contractor.
ASCE 7: Load Combinations and Minimum Design Requirements
ASCE 7, Minimum Design Loads and Associated Criteria for Buildings and Other Structures, is the document structural engineers interact with most directly when establishing design demands. Published by the American Society of Civil Engineers, it is referenced by the IBC and functions as the technical backbone for load determination across all material types.
ASCE 7 organizes loads into chapters covering dead loads, live loads, flood loads, wind loads, snow loads, rain loads, seismic loads, and atmospheric ice loads. Each chapter provides maps, tables, and equations that translate site-specific conditions into design forces. Wind design, for example, requires the engineer to determine the basic wind speed from hazard maps, select an exposure category based on surrounding terrain, and apply a series of pressure coefficients that account for building geometry and component location. Seismic design follows a similarly systematic process: the engineer identifies the mapped spectral response accelerations for the site, adjusts for local soil conditions using a site class, and arrives at a design spectral acceleration that feeds into the equivalent lateral force procedure or a modal response spectrum analysis.
Load combinations in ASCE 7 are perhaps the most universally applied provisions in structural engineering. The code provides both strength design (LRFD) combinations and allowable stress design (ASD) combinations. A typical LRFD combination such as 1.2D + 1.6L + 0.5S reflects the statistical likelihood that dead load, live load, and snow load will not all reach their maximum values simultaneously. Engineers must check all applicable combinations and design for the governing case. Importance factors embedded in wind and seismic provisions automatically increase design demands for higher Risk Category structures, tying back to the IBC's occupancy framework.
Material-Specific Standards: ACI, AISC, NDS, and TMS
Once design loads are established through ASCE 7, the engineer selects structural members and connections using material-specific standards. The four most commonly encountered in US practice are ACI 318, the AISC Steel Construction Manual and its companion specifications, the NDS for wood, and TMS 402/602 for masonry.
ACI 318, Building Code Requirements for Structural Concrete, governs the design of reinforced and prestressed concrete members. It specifies strength reduction factors, minimum reinforcement ratios, development length requirements, and detailing rules for seismic regions. Seismic detailing in ACI 318 is particularly extensive: special moment frames and special structural walls require specific hoop spacing, lap splice locations, and coupling beam proportions that differ substantially from ordinary or intermediate systems.
The AISC Specification for Structural Steel Buildings covers the design of steel members and connections using both LRFD and ASD approaches. The companion Seismic Provisions for Structural Steel Buildings addresses ductile detailing for moment frames, braced frames, and other lateral systems. Connection design—often the most labor-intensive part of steel design—is guided by the AISC Steel Construction Manual, which provides prequalified connection tables alongside the underlying design equations.
The National Design Specification for Wood Construction, published by the American Wood Council, governs sawn lumber, glued-laminated timber, structural composite lumber, and cross-laminated timber. NDS uses an ASD format with adjustment factors that account for load duration, moisture content, temperature, and size effects. The Special Design Provisions for Wind and Seismic supplement addresses lateral system design for wood-frame and heavy timber structures.
TMS 402, Building Code Requirements and Specification for Masonry Structures, covers unreinforced, reinforced, and prestressed masonry. Like ACI 318, it includes seismic detailing requirements that escalate with the Seismic Design Category assigned to the project. Engineers working with masonry must also coordinate with TMS 602, the companion specification that governs materials and construction quality.
How IBC, ASCE 7, and Material Standards Work Together
The relationship among these documents is hierarchical and sequential. The IBC establishes the legal framework and references ASCE 7 for load determination. ASCE 7 produces factored design demands—forces and moments—that the engineer then uses as inputs to the material standard. The material standard converts those demands into required member sizes, reinforcement quantities, or connection capacities.
Consider a reinforced concrete shear wall in a high-seismic zone. The IBC assigns the building a Risk Category based on occupancy. ASCE 7 uses that Risk Category, along with site-specific spectral accelerations and the building's structural system, to assign a Seismic Design Category (SDC) and compute the design base shear. The SDC then triggers specific detailing requirements in ACI 318—SDC D, E, or F requires special reinforced concrete shear walls with closely spaced boundary element hoops, minimum web reinforcement ratios, and capacity-based design of connections. Each document hands off to the next, and an error or misinterpretation at any link in the chain can propagate into an unsafe or non-compliant design.
This interdependency also means that code updates in one document can affect design outcomes even when the others remain unchanged. A revision to ASCE 7's wind speed maps, for instance, changes design wind pressures without any alteration to the IBC or AISC. Engineers must track which edition of each standard is in force for a given project and verify that all referenced documents are compatible editions—the IBC specifies which edition of ASCE 7 and the material standards it references, and mixing editions can introduce inconsistencies.
Code Adoption by State and Local Jurisdictions
Code adoption in the US is a state-level decision, and the landscape is genuinely varied. Most states have adopted some edition of the IBC, but the edition in force ranges from the 2012 IBC in some jurisdictions to the 2021 IBC in others. A handful of states maintain their own legacy codes or have adopted the IBC with substantial amendments that effectively create a hybrid document.
California is the most prominent example of a state with extensive amendments. The California Building Code incorporates the IBC as its base but adds California-specific seismic provisions, energy requirements, and accessibility standards. Florida similarly amends the IBC to address its hurricane exposure, flood hazard, and high-humidity environment. New York City historically maintained its own building code and has only recently aligned more closely with the IBC framework, retaining significant local modifications.
Local jurisdictions—cities and counties—may add another layer. A municipality in a high-wind coastal area might adopt stricter wind speed requirements than the state baseline. A city with a history of expansive soils might require geotechnical investigations for projects that the state code would not mandate. Engineers practicing across multiple jurisdictions must maintain current knowledge of local amendments and cannot assume that familiarity with the model code alone is sufficient for compliance.
The practical implication is straightforward: before starting structural calculations on any project, confirm the governing code edition and all applicable local amendments with the AHJ. Many building departments publish this information on their websites, and a pre-application meeting can resolve ambiguities before they become costly mid-design corrections.
Navigating Code Updates and Amendment Cycles
The ICC publishes new editions of the IBC on a three-year cycle, with the most recent editions being 2018 and 2021. ASCE updates ASCE 7 on a similar cycle. Material standards follow their own schedules: ACI 318 was last updated in 2019, AISC's Specification in 2022, and NDS in 2018. Because adoption lags publication by several years in most states, engineers routinely work with editions that are one or two cycles behind the current published version.
Tracking changes between editions matters because provisions can shift meaningfully. The transition from ASCE 7-10 to ASCE 7-16 introduced updated wind speed maps that changed design pressures in many regions. ACI 318-19 reorganized its chapter structure significantly compared to ACI 318-14, which created navigation challenges for engineers accustomed to the older layout even when the technical content was similar. AISC's 2022 Specification introduced changes to connection design and stability provisions that affect routine steel design tasks.
A practical approach to managing code cycles involves three habits. First, maintain a project log that records the governing code edition for each project at the time of permit application—this becomes critical if the project extends across an adoption date or if questions arise during construction. Second, subscribe to code change notifications from the ICC, ASCE, and the relevant material standards organizations; most offer free email updates. Third, when a new edition is adopted locally, invest time in a structured review of the changes before the first project under the new code arrives. Waiting until a deadline-driven project to learn a new edition is a reliable path to errors. Code literacy is a continuous professional obligation, not a one-time credential.
Example
Key Structural Standards Referenced by the IBC: Scope and Primary Use
| Standard | Publishing Organization | Primary Scope | Design Format |
|---|---|---|---|
| IBC (2021) | International Code Council (ICC) | Overall building requirements; load framework; special inspections | Prescriptive / Performance |
| ASCE 7-22 | American Society of Civil Engineers | Dead, live, wind, seismic, snow, and other load determination; load combinations | LRFD and ASD combinations |
| ACI 318-19 | American Concrete Institute | Reinforced and prestressed concrete member and system design | LRFD (strength design) |
| AISC 360-22 | American Institute of Steel Construction | Structural steel member and connection design | LRFD and ASD |
| AISC 341-22 | American Institute of Steel Construction | Seismic detailing for steel lateral systems | LRFD and ASD |
| NDS 2018 | American Wood Council | Sawn lumber, glulam, CLT, and other wood products | ASD (with LRFD appendix) |
| TMS 402-22 | The Masonry Society | Reinforced, unreinforced, and prestressed masonry | LRFD and ASD |
FAQ
What is the difference between a model code and an adopted code? A model code is a document published by a standards organization—such as the IBC published by the ICC—that has no legal force on its own. It becomes an adopted code when a state legislature or state building department formally enacts it, typically with amendments. The adopted code is what carries legal authority in a given jurisdiction, and it may differ from the model code in edition year, deleted sections, or added local requirements.
Why do structural engineers use both ASCE 7 and material-specific standards like ACI 318? ASCE 7 and material standards serve different purposes in the design process. ASCE 7 determines the magnitude of the loads—gravity, wind, seismic, snow—that a structure must resist. Material standards such as ACI 318 or AISC 360 then govern how structural members and connections are sized and detailed to resist those loads safely. Neither document is sufficient alone: ASCE 7 does not tell you how to design a concrete beam, and ACI 318 does not tell you what loads to apply.
How does Risk Category affect structural design requirements? Risk Category (I through IV) reflects the consequences of a building's failure to society. Higher Risk Categories trigger increased design demands in two ways. First, ASCE 7 applies importance factors to wind and seismic loads, directly increasing the forces a structure must resist. Second, higher Risk Categories result in higher Seismic Design Categories, which activate more stringent detailing requirements in ACI 318, AISC 341, NDS SDPWS, and TMS 402. A hospital (Risk Category IV) will therefore require more robust structural systems and more rigorous detailing than a warehouse (Risk Category I) of similar size.
How should an engineer handle a project that spans a code adoption date? The governing code is generally the edition in effect at the time the building permit application is submitted and accepted by the AHJ. If design begins under one edition and the jurisdiction adopts a new edition before permit submission, the engineer should confirm with the AHJ which edition applies. Some jurisdictions allow a grace period during which either edition may be used; others require immediate compliance with the new edition. Document the governing edition clearly in the project record and on the construction documents to avoid ambiguity during plan review or future inspections.
What is an alternate means and methods request, and when is it used? An alternate means and methods request is a formal submission to the AHJ proposing a design approach that differs from the prescriptive requirements of the adopted code but achieves equivalent or superior structural performance. It is used when a project's geometry, materials, or performance objectives make strict prescriptive compliance impractical or when an innovative system offers demonstrable advantages. The engineer of record must provide calculations, test data, or other technical evidence supporting the equivalency claim. The AHJ reviews the submission and may consult a peer reviewer before granting or denying approval.
Are LRFD and ASD interchangeable for structural design? Both LRFD (Load and Resistance Factor Design) and ASD (Allowable Stress Design) are accepted by ASCE 7 and most material standards, and when applied correctly they produce designs with comparable reliability. They are not interchangeable in the sense that you cannot mix load combinations from one format with resistance equations from the other. LRFD applies load factors greater than 1.0 to nominal loads and uses a capacity reduced by a resistance factor; ASD uses unfactored loads and compares stresses to allowable values that include a safety factor. Most modern practice favors LRFD for concrete and steel, while wood design has historically used ASD, though NDS now includes an LRFD appendix.
Read next
Learn more