ASCE 7 Minimum Design Loads and Associated Criteria

Course 71 | 3 Contact Hours | 0.3 CEUs

Module 1: ASCE 7 load classification

Learning Objective

Understand ASCE 7 load classification and load combination requirements

Practice Framework

Every structural design decision starts with the same question: what forces must this building resist? ASCE 7 answers that by sorting the loads a structure must resist into distinct families rather than treating them as interchangeable. Dead load is the constant, permanent weight of construction; live load varies with occupancy and use; and a wider set of environmental loads — wind pressure and suction, snow that accumulates and drifts unevenly, seismic force generated by the structure's own mass resisting ground motion, rain that can pond faster than a roof drains, and soil and groundwater pressing against below-grade elements — behave differently again. Classifying a load into the wrong family at the outset can undermine a design that looks careful in every other respect.

The building code does not spell these provisions out itself: IBC Chapter 16 incorporates ASCE 7 by reference rather than restating its content, so the governing technical requirements for how a load is determined live in the referenced standard, not the chapter that points to it. Recognizing when a topic is governed this way, and which standard to consult, is a core plan-review skill.

Field Application Scenario

Consider a review where early drawings show a straightforward office layout, but a later submittal adds a dense-storage mezzanine and a server room with heavier-than-typical equipment loads. Because live load is occupancy-driven rather than fixed, a change like this has to be caught before it disappears into later plan sets. A careful reviewer confirms the calculations reflect the areas actually shown as storage or equipment space, and checks whether the change also shifts the risk category the design depends on — not just whether the floor is strong enough.

Common Mistakes and Corrections

A recurring mistake is treating classification as a one-time step, so a later change in occupancy or storage use never gets checked against the load assumptions it should affect; a related one is confusing load families, assuming a variable load behaves like the constant weight of construction itself. The correction is to revisit classification at every submittal: confirm which family a force belongs to, verify occupancy shown on the drawings matches the structural assumptions, and trace any late change to every family it could affect.

Code Reference: ASCE 7 - The code establishes minimum requirements for asce 7 load classification to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.

Key Takeaways

• ASCE 7 sorts loads into distinct families — dead, live, and environmental loads such as wind, snow, seismic, rain, and soil or groundwater pressure.
• Misclassifying a load's family at the outset can undermine an otherwise careful design.
• IBC Chapter 16 incorporates ASCE 7 by reference; the governing technical requirements live in the referenced standard, not the chapter itself.
• A late change in occupancy or use can shift live load assumptions and risk category together — trace it to everything it touches.
• Treat load classification as something to revisit at every submittal, not a box checked once at the start.

Module 2: wind

Learning Objective

Apply wind and snow load calculation procedures

Practice Framework

Wind load behaves as a pressure-and-suction problem rather than a single number: moving air pushes directly against the surfaces it strikes and pulls away from the surfaces on the opposite and side faces of a building. A structure's overall lateral system resists that cumulative effect, while individual envelope elements — a window, a wall panel, a section of roofing — can face sharper, more localized pressure than the whole-building average, especially near corners, edges, and ridges. Uplift, suction lifting a roof surface away from the structure beneath it, is the wind failure mode most examiners recognize on sight, which is why fastening and anchorage for roofing and rooftop equipment deserve focused attention. How severely a site experiences wind depends heavily on exposure — how open or sheltered the terrain is — and on building height and shape.

Snow load follows a related but distinct logic: accumulation depends on regional climate and roof geometry, drifting toward valleys, parapets, and obstructions rather than settling as a uniform blanket — so the features easiest to overlook are often where accumulation is heaviest. Both wind and snow are site-specific loads — the values a project uses come from hazard data tied to its actual geographic location — so a reviewer's role is verifying the correct values were used and applied consistently, not deriving them independently.

Field Application Scenario

Consider a coastal project whose design documents state an exposure and enclosure classification established early in design, before later architectural drawings add a substantially larger storefront opening. Enlarging or adding openings can shift a building's enclosure classification even when its overall shape hasn't changed, so a careful reviewer asks whether the pressures used for the glazing, doors, and surrounding components still reflect the building as currently designed — and, at the inspection stage, confirms the roofing, flashing, and glazing actually installed match what was reviewed.

Common Mistakes and Corrections

A common error is applying one wind pressure value across a building without rechecking whether corners or areas near large openings face different demands than the general field; a related one treats snow as a flat, uniform number rather than a load that drifts by roof geometry. The correction is to check both scales — the whole-building system and the individual components most exposed to concentrated pressure or drift — while confirming site-specific values match the project location.

Code Reference: ASCE 7 - The code establishes minimum requirements for wind to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.

Key Takeaways

• Wind is a pressure-and-suction problem: windward surfaces generally see pressure pushing in, while other faces and much of the roof see suction pulling out.
• Individual envelope components can face sharper localized pressure than the whole-building average, so both scales need separate evaluation.
• Uplift is the classic wind failure mode; fastening and anchorage deserve close attention in design and in the field.
• Snow accumulates unevenly, drifting toward valleys, parapets, and obstructions rather than settling as a uniform layer.
• Wind speed and ground snow values come from site-specific hazard data; the reviewer verifies the correct values were used rather than deriving them.

Module 3: seismic design requirements

Learning Objective

Understand seismic design requirements and risk categories

Practice Framework

Seismic demand works differently from every other load family: wind and snow act on a structure from outside, while seismic force is generated from within. An earthquake shakes the ground, and it is the building's own mass, resisting that motion, that creates the internal forces the structure has to resist — which is why heavier and taller buildings tend to face more severe seismic demand than lighter, shorter ones, and why irregular buildings, where mass or structural elements are not distributed evenly, tend to concentrate that demand at specific points instead.

Risk category ties seismic design to the consequences of failure rather than a building's size or cost: an ordinary building, one whose failure would pose a substantial hazard to the community, and one the community depends on remaining operational after a design event are treated differently, and that grouping shapes how much conservatism the design must provide. Seismic hazard also varies by geographic location and by the soil a building sits on — softer or looser soils can amplify ground motion — so a geotechnical report is a direct input into seismic design, not a disconnected submittal.

Field Application Scenario

Picture a review for an essential facility — a fire station or hospital wing — sited where seismic activity is a real design driver. Because its function places it in an elevated risk category, the code expects more conservative design and detailing than an ordinary building would receive. A thorough review confirms the risk category on the cover sheet, general notes, and life-safety plans all agree, and that the geotechnical information in the calculations matches the site, while recognizing that a later change in function, such as adding a shelter use, may raise that risk category.

Common Mistakes and Corrections

The most consequential mistake is treating risk category as an administrative field rather than the input shaping seismic design, confirming occupancy without checking whether the structural design reflects the conservatism it calls for; a related one is assuming standard soil conditions without an actual geotechnical report. The correction is to reset the classification whenever occupancy, function, or site information changes: verify the geotechnical data matches the project site, and require a coordinated update across every affected discipline.

Code Reference: ASCE 7 - The code establishes minimum requirements for seismic design requirements to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.

Key Takeaways

• Seismic force is generated internally by a structure's own mass resisting ground motion, unlike the externally applied force of wind or snow.
• Heavier, taller, and irregular buildings tend to face more severe seismic demand, since irregular geometry concentrates force rather than distributing it evenly.
• Risk category groups buildings by the consequences of failure and drives how conservative the seismic design must be.
• Seismic hazard and soil conditions are both site-specific; a geotechnical report is a direct input into seismic design, not a disconnected submittal.
• A reviewer confirms risk category matches actual occupancy and site conditions; assigning or recalculating it is the engineer of record's responsibility.

Module 4: ASCE 7 load classification

Learning Objective

Apply load classification consistently across design, load-combination, and coordination decisions

Practice Framework

Classifying loads correctly is only half the job; the other half is understanding how classified loads act together. Real structures rarely experience every possible load at its individual maximum simultaneously, so ASCE 7's load combination provisions identify which realistic pairing — dead load with live load, or those loads together with wind — governs a given design condition. ASCE 7 supports two design philosophies for working with those combinations: allowable stress design, which compares combined loads against a structure's allowable capacity, and strength design, sometimes called load and resistance factor design, which applies factors to loads and material strength separately and compares the two directly. Both are permitted, and a reviewer's task is confirming which one a submittal uses and that it is applied consistently, not favoring either approach.

Some load families are easy to overlook. Rain and ponding on a low-slope roof is a self-reinforcing failure mode: added water weight can deflect a roof further, allowing more water to collect. Below grade, soil pressure and groundwater-driven hydrostatic pressure both act on foundation and retaining walls, and special or impact loads cover less routine scenarios a project may need to anticipate. Working out how these loads combine and govern a specific design is the engineer of record's responsibility; a reviewer confirms the submittal addresses the relevant families, not re-performs the calculation.

Field Application Scenario

Consider a low-slope roof design where the calculations address snow and wind thoroughly but never connect to the drainage narrative: if primary drainage were blocked, is there a secondary path for the water to leave, and did the design account for the added weight if not? A parallel case is a below-grade parking structure where the geotechnical report notes high groundwater but the structural notes don't reflect hydrostatic pressure against the walls — a gap worth flagging before approval, not after excavation begins.

Common Mistakes and Corrections

A frequent mistake is checking gravity loads carefully while treating combinations involving wind or seismic as an afterthought, even though those often govern lateral elements rather than gravity members alone; another is overlooking rain and ponding where a secondary drainage path is assumed but never confirmed on the drawings. The correction is a checklist that treats combinations, not individual loads, as the design condition, confirming ponding and below-grade pressure were not silently dropped, while keeping the reviewer focused on completeness rather than re-performing calculations.

Code Reference: ASCE 7 - The code establishes minimum requirements for asce 7 load classification to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.

Key Takeaways

• Real structures experience realistic combinations of loads acting together, not every family at its individual maximum at once.
• ASCE 7 supports both allowable stress design and strength design as valid philosophies; a reviewer confirms which one is used and applied consistently.
• Rain and ponding on low-slope roofs is a self-reinforcing failure mode worth specific attention.
• Soil pressure and hydrostatic pressure both act on below-grade elements and need to be reflected in their design.
• The engineer of record owns the load combination calculations; the reviewer verifies completeness and consistency, not re-deriving results.

Module 5: wind

Learning Objective

Verify wind and snow design criteria through plan review and field inspection

Practice Framework

Everything this course covers about wind and snow eventually has to show up in one place a reviewer can actually check: the design criteria or general notes sheet at the front of the structural drawings, where a design team states the risk category, the wind and snow criteria used, and the lateral system the building relies on. A reviewer's first move on any structural submittal is confirming that sheet exists and is complete, since every downstream calculation is only as trustworthy as the criteria it was built from.

Once that sheet is present, the review has four things to confirm: that the parameters are actually there rather than left blank; that they are appropriate to the project's actual location, use, and occupancy; that they are consistent with what appears in the calculations and the architectural and life-safety drawings; and that the load path those criteria imply is traceable to the ground, since criteria that never connect all the way down to the foundation have not demonstrated compliance.

Field Application Scenario

A plans examiner opens a submittal for a mid-rise building and finds a general notes sheet listing material properties but never actually stating a risk category, a wind or snow criterion, or which lateral system the building relies on. The calculations further into the package appear thorough, but without a design criteria sheet stating what they were built to satisfy, the reviewer cannot confirm they use the right inputs for this project rather than boilerplate carried over from a previous job. The correct response is to return the submittal and require a complete design criteria sheet before review can proceed — the structure cannot be verified against criteria the drawings never state.

Common Mistakes and Corrections

The clearest failure pattern is a missing or incomplete design criteria sheet, since a submittal that never states its risk category or its wind and snow criteria cannot be meaningfully reviewed no matter how detailed the calculations appear elsewhere; a related pattern is a submittal that addresses average roof conditions but never separately confirms uplift at edges and corners or drift at valleys and obstructions. The correction is consistent: require the missing information before proceeding, and confirm concentrated conditions received the same attention as the general roof field.

Code Reference: ASCE 7 - The code establishes minimum requirements for wind to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.

Key Takeaways

• The design criteria or general notes sheet states risk category, wind and snow criteria, and the lateral system — confirm it exists and is complete first.
• Verify criteria along four dimensions: present, appropriate to the project, consistent across every discipline, and connected by a traceable load path to the foundation.
• A submittal without a complete design criteria sheet should be returned rather than approved based on calculations alone.
• A late change in occupancy or use should always be checked against the risk category the design depends on.
• Uplift at roof edges and corners, and drift at valleys and obstructions, deserve the same explicit attention as the general roof field.

Summary

ASCE 7 Minimum Design Loads and Associated Criteria gives structural design its starting point: a standardized way to classify the loads a building must resist and determine which realistic combination of those loads governs a given design condition. This course worked through the load families themselves — dead, live, and the environmental loads of wind, snow, rain, and seismic activity, along with soil and groundwater pressure on below-grade elements — the site-specific hazard data wind, snow, and seismic criteria depend on, the risk category concept that scales design conservatism to the consequences of failure, and the load combination provisions and design philosophies that turn classified loads into an actual design condition.

Across every module, the reviewer's role stayed consistent: confirm a design's stated criteria are present, appropriate, and internally consistent across every discipline, and trace whether the load path those criteria imply is complete down to the foundation. The engineer of record owns the underlying calculations and site-specific values; the reviewer's task is verification, not re-derivation. IBC Chapter 16 points to ASCE 7 rather than restating it, which is why fluency with these concepts, not just the building code's own chapters, is what separates a review that catches real structural gaps from one that only checks what's spelled out closest at hand.

Additional Resources

• ASCE 7 — Primary code reference for this course
• ICC continuing education standards
• Local jurisdiction amendments and supplements
• Industry best practices and technical bulletins