Concrete wall drift: American Society of Civil Engineers (ASCE) 7-22—0.005h, Model?

A practical guide to deciding when nonlinear response-history analysis justifies the added modeling cost for the ASCE 7-22 concrete shear wall drift limit of 0.005h. It emphasizes verifying the live, complete option and comparing like-for-like totals and terms before commitment.

How It Works

ASCE 7-22 limits the design story drift ratio of a concrete shear wall to 0.005h, where h is the story height. The limit is therefore a displacement allowance equal to one-half of one percent of that story height. For a 10-foot story, 0.005 × 10 feet gives 0.05 foot, or 0.6 inch. The check is performed at the story level: the relative horizontal displacement of the floor above the floor below is divided by the story height. A larger ratio indicates greater deformation, but the ratio alone does not establish whether the wall system passes.

The term design story drift refers to the drift used for seismic design, as distinguished from drift reported by a service-level or other assessment. A nonlinear response-history analysis differs from a linear elastic analysis by allowing the model to represent stiffness loss, yielding, and other nonlinear behavior as earthquake demands develop. The analysis can therefore capture deformation that a simpler model may not reproduce. Its result remains a modeled response under specified records, not a guarantee that the wall will experience exactly that drift in an earthquake.

The verification workflow is straightforward: construct and converge the structural model; apply the required nonlinear properties and loading combinations; run the prescribed set of ground-motion records; scale or modify the records according to the applicable ASCE 7-22 procedure; extract story drifts at the required locations; and compare each result with the 0.005h limit and the associated acceptance criteria. The analysis files, input assumptions, record information, and calculation extracts should be retained so that an engineer can reproduce the result. A report that provides only a final drift ratio does not provide a complete verification trail.

Before committing to this more demanding workflow, confirm that the analysis option is actually permitted for the building and that the engineer has the current, complete requirements rather than a summary of the story-drift table. Obtain the live ASCE 7-22 provisions, referenced chapters, applicable commentary, and any project-specific addenda. Then compare the full deliverables on the same basis: required analyses, model complexity, record preparation, quality-control effort, peer review, schedule impact, and total professional hours. Also compare the defined terms: one provider’s “nonlinear analysis” may mean a sophisticated nonlinear model, while another may include additional service-level simulations that are not required for the same decision.

Nonlinear response-history analysis earns its added cost when representative loading, realistic wall behavior, and defensible acceptance checks materially improve confidence in the design—and the project can absorb the additional modeling, documentation, and review effort. It is not justified merely because the method is more advanced. The decision is sound when the complete ASCE 7-22 option has been verified, the comparison uses like-for-like deliverables and terms, and the resulting evidence is more conclusive than the less elaborate method it would replace.

Key Factors to Consider

Before committing to nonlinear response-history analysis, use a three-part decision screen: confirm that the conventional approach does not establish compliance, determine whether nonlinear analysis can materially change the governing design outcome, and verify that the required model can be developed and audited at a reasonable total effort. The analysis earns its added cost when it resolves a controlling uncertainty—not merely because it produces more detailed results.

First, check the governing numerical values. For each story, record the applicable story height, calculated displacement, resulting drift ratio, and the ASCE 7-22 limit being evaluated. Confirm that every number comes from the same geometry, loading direction, and design basis used in the analysis. Pay particular attention to the peak values selected from the response history and to any larger value obtained from a governing combination. A result cannot support a decision if the reported displacement and the checked ratio do not reconcile.

Second, assess whether the nonlinear model is likely to affect a controlling member, connection, or system response. Identify in advance what a successful analysis would change. If it cannot alter reinforcement demand, wall boundary detailing, collector behavior, overturning response, or another governing design decision, the added modeling effort may not produce a useful answer. This is a decision threshold, not a presumption that nonlinear analysis is required or unnecessary.

Third, price the commitment as a complete effort. Before authorizing the work, obtain a written scope covering model construction, material and component modeling, loading, damping assumptions, nonlinear properties, acceptance criteria, computational runs, review, and deliverable documentation. Compare like-for-like totals and terms: include internal labor, software time, peer review, revisions, and any later model maintenance. The analysis package should have a defined and verifiable basis — traceable inputs and documented acceptance checks — rather than an unverified output.

Make the final commitment only when the scope is live, complete, and tied to a specific decision. Confirm that required inputs are available, that the acceptance procedure is agreed upon before results are generated, and that the cost estimate covers the full path from model preparation through usable documentation. If the nonlinear analysis cannot answer a clearly identified controlling question, or if its inputs and review requirements remain unresolved, the additional cost is not yet justified.

Common Mistakes

Common mistake 1: treating the first conventional-analysis result as proof that nonlinear response-history analysis is required. A wall that narrowly exceeds a drift check is not, by itself, a sound reason to purchase the extra analysis. Before committing, verify whether the trial model reflects the complete load path, including wall orientation, wall-to-diaphragm connections, foundation restraint, and the stiffness used to calculate story drift. For example, suppose the preliminary wall model gives a 120-foot building a 4-inch displacement over a 10-foot story, so the computed ratio is 0.0040. Do not alter that number to create a reason for a more elaborate analysis; instead, test the model inputs and confirm whether the result remains the governing condition after the building is represented consistently.

Common mistake 2: accepting an analysis package that is complete in appearance but incomplete in scope. “Nonlinear response-history analysis” can describe several deliverables. Verify the live submittal against the governing documents: accepted ground motions, the number of records, scaling rules, damping assumptions, nonlinear wall and connection models, convergence criteria, and the required output format. ASCE 7-22 should be cited as the governing source for the applicable requirements, but a report that merely says “nonlinear analysis performed” is not a sufficient scope document. Ask the engineer to map each deliverable to a specific acceptance check before authorizing the work.

Another pitfall is comparing a conventional-analysis fee with only the quoted price of nonlinear response-history analysis. That is not a like-for-like comparison. The relevant total must include every downstream task that may be triggered: analysis-model preparation, additional design iterations, wall and connection redesign, drawing revisions, independent checking, and resubmittal. Keep these as separate line items rather than burying them in an undefined allowance. The same rule applies to terms: record what is included, what is excluded, who owns subsequent revisions, and when additional work becomes a change.

Finally, do not let a polished report substitute for traceability. Require the final package to identify the input files, calculation assumptions, acceptance results, and any conservatisms or unresolved issues. If the nonlinear model predicts a result but the drawings or specifications still embody an earlier design, the verification has not reached the decision it was intended to support. A practical pre-commitment rule is simple: accept the option only when its scope is complete, its assumptions are traceable, and its cost and terms are stated on the same basis as the conventional alternative.

Insider Tactics

The most useful insider tactic is to create a written “commitment gate” before authorizing nonlinear response-history analysis. The gate should identify the exact design question that the analysis must resolve, the acceptance criteria for the answer, the model inputs that will be controlled, and the deliverables required for review. Then require the conventional-analysis package and the nonlinear-analysis package to be evaluated against that same gate. This prevents an expensive analysis from being commissioned simply because it is feasible, rather than because it can resolve a consequential compliance issue. It also creates a record showing what was known before the decision was made.

A second tactic is to run a low-cost pilot before committing to the full model. Start with the most unfavorable or least certain modeling assumption, substitute a defensible preliminary model, and determine whether the resulting answer could plausibly change the governing design outcome. If even a bounded pilot does not reveal a decision-relevant difference, pause and revisit the purpose of the analysis. If the pilot identifies a potentially decisive assumption, refine only that assumption first. This staged approach limits rework: the initial effort is spent on determining whether further modeling has value, not on completing an analysis whose result may not affect the project.

Time the commitment gate to coincide with the earliest point when the project team can still act on the result. Place it before design geometry, wall selection, or reinforcement decisions become fixed, but after enough conventional-analysis information is available to define the unresolved question. Schedule a technical review with the structural engineer, discipline leads, and reviewer immediately after the pilot—not after a complete submission package has been assembled. Early review can expose missing information or an incorrect question while changes remain practical.

Finally, compare proposed effort on a like-for-like basis. Use the same project scope, model boundaries, deliverable expectations, review level, and support period for every estimate. Separate engineering time from model development, checking, documentation, revisions, and coordination; then total all applicable categories. Do not compare a preliminary conventional-analysis effort with a finished nonlinear-analysis deliverable, or count only computer time while omitting the human review required to make the result usable. Record exclusions explicitly so that the totals have matching terms. The practical question is not whether nonlinear response-history analysis is “cheaper,” but whether the fully scoped incremental effort is justified by a result that can materially guide the next design decision.

Comparison

Start with a like-for-like numerical comparison rather than a generic preference for more sophisticated analysis. Consider a 10-foot story with a 0.005h drift allowance of 0.60 inch (0.005 × 10 feet = 0.05 foot = 0.6 inch, consistent with the example earlier in this article). If the conventional analysis reports 0.75 inch and nonlinear response-history analysis reports 0.54 inch after applying the same loading direction, acceptance criteria, and reporting convention, the conventional result exceeds the allowance by 0.15 inch, while the nonlinear result remains below it by 0.06 inch.

The conventional approach wins when it produces a compliant result with a clear margin, when the project scope makes nonlinear modeling disproportionate, or when the governing code provisions do not support that analysis route. Check the complete live option before committing: confirm the current software and model versions, load combinations, wall properties, damping assumptions, acceptance criteria, and output sign conventions. An incomplete comparison can change a 0.006-inch positive margin into a negative one merely by mixing analysis outputs.

Nonlinear response-history analysis wins in the illustrated case because it changes the compliance outcome, not merely because it produces more detailed output. Here, the total reduction is 0.21 inch: 0.75 minus 0.54. Relative to the 0.60-inch allowance, the conventional analysis has a 25 percent overrun (0.15 ÷ 0.60), while the nonlinear result has a 10 percent margin (0.06 ÷ 0.60). These ratios are comparison aids, not substitutes for code checks.

Before selecting the nonlinear option, compare the same quantities on both sides: maximum story drift, displacement demand, acceptance threshold, margin, number of controlling records or runs, number of directionally controlling results, and the total modeling and review effort required. Do not compare one peak output from the nonlinear model against a different quantity from the conventional model. Re-run the arithmetic with the actual project values and document which complete option produces the governing result.

For this example, nonlinear response-history analysis is the winner because it converts a 0.015-inch shortfall into a 0.006-inch compliance margin. The practical rule is to choose it when the added modeling effort can materially and defensibly change the governing design outcome; otherwise, retain the conventional approach when it establishes compliance on a complete, consistent basis.

What to do next

Frequently Asked Questions

What does h represent in the ASCE 7-22 concrete shear wall drift limit?

The variable h is the story height.

How is design story drift checked at a given story?

The check divides the relative horizontal displacement of the floor above the floor below by the story height.

Does a story drift ratio by itself determine whether the wall system passes?

No, the ratio alone does not establish whether the wall system passes.

What displacement allowance corresponds to a 10-foot story under the stated limit?

The allowance is 0.05 foot, or 0.6 inch.

When is nonlinear response-history analysis identified as the cost-justifying case?

It is the cost-justifying case when its results support a decision despite the added modeling cost.

What should be checked before committing to a nonlinear response-history analysis option?

Verify the live, complete option, confirm the full option rather than relying on a partial description or isolated figure, and compare like-for-like totals and terms on the same scope.

Quick answers

Also worth reading: Steel frame earthquake analysis for 12-story: 18% base shear cut vs cost: Steel frame earthquake analysis for · 020hsx vs 0.035hsx: ASCE 7-22 and ASCE 41-22 Drift Limits: 020hsx vs 0.035hsx: ASCE 7-22 · High early strength bridge concrete: 3,000 psi at 3 days, set gates before pricing: High early strength bridge concrete: