An ASCE 7 edition cannot be selected from a state name alone. The project address, adopted building code, local amendments, permit date, and building scope all matter.
Direct answer. ASCE 7-22 usually reaches a solar project through a building code that references it, especially the 2024 International Building Code. Adoption is not a clean statewide yes or no. Some states set one baseline. Others leave ordinary construction to cities and counties. Confirm the enforcing authority and effective date before fixing the structural design basis.
This guide gives solar permit teams a 51-jurisdiction routing matrix. It does not publish project wind speeds, ground snow loads, exposure categories, or structural conclusions.
The ASCE 7-22 glossary entry defines the standard. Our ASCE wind-load guide covers load application. This article stays on adoption and jurisdiction routing.
Is ASCE 7-22 adopted directly by each state?
Usually, no. ASCE/SEI 7 is a referenced standard. A building code adopts or incorporates a specific edition, often with amendments.
The American Society of Civil Engineers ASCE 7 hub identifies ASCE/SEI 7-22 as the 2022 edition. The legally controlling route still comes from the adopted building code.
That distinction prevents a common plan-set error. Publishing a new standard does not make it enforceable everywhere on the publication date. A state or local authority must adopt a code path that references it.
The reverse mistake also creates risk. A project team can keep using a familiar older edition after the authority has moved forward. The resulting comments can affect loads, detailing, schedules, and calculations.
Design hold. Do not write ASCE 7-22 on a criteria sheet until the authority, adopted code, amendments, and effective date are recorded.
An authority having jurisdiction, or AHJ, can be a city, county, state agency, or another code-enforcement body. The controlling body depends on the project and building scope.
The International Building Code glossary explains the model-code role. The International Code Council adoption resources show why state summaries need local verification.
Which building code edition routes to ASCE 7-22?
The model-code reference is the first filter. The adoption ordinance and amendments are the second.
| Adopted code basis | Referenced ASCE 7 path | Solar design action |
|---|---|---|
| 2024 International Building Code | ASCE/SEI 7-22 | Verify adoption date, amendments, and project scope |
| 2021 International Building Code | ASCE/SEI 7-16 | Do not substitute ASCE 7-22 without written authority |
| 2018 International Building Code | ASCE/SEI 7-16 | Check local amendments and transition rules |
| State-specific building code | Read its referenced standards | Record the state edition and amendment package |
| Local ordinance | Read the adopting ordinance | Record the exact edition, date, and local changes |
The 2024 IBC Chapter 35 references ASCE/SEI 7-22. The 2021 IBC Chapter 35 references ASCE/SEI 7-16.
This handoff matters more than a generic statement that a state uses the I-Codes. A jurisdiction can use a 2021 building-code baseline while another has adopted the 2024 edition. Both can sit inside one state.
Residential projects also require a scope check. The adopted residential code may contain its own prescriptive route. An engineered design can still invoke referenced structural criteria. Record which path the reviewer expects.
Edition rule. The newest standard is not automatically the adopted standard. The project record must show the legal route to the chosen edition.
What does the 51-jurisdiction matrix show?
The matrix is a routing tool, not an engineering input table. It classifies how the current ICC record describes adoption.
Each state name links to the applicable ICC adoption record. Those records were accessed on 26 September 2026. Recheck the source before using a row.
| Jurisdiction | Adoption pattern | What the solar team must verify |
|---|---|---|
| Alabama | Scope-limited | Check the local code for ordinary private work. State agencies control listed scopes. |
| Alaska | Hybrid | Confirm state inspection or a delegated jurisdiction. Then check amendments. |
| Arizona | Local-first | Obtain the city or county adoption ordinance and amendments. |
| Arkansas | Hybrid | Confirm the state agency scope and local building code. |
| California | Hybrid | Verify the state cycle and approved stricter local amendments. |
| Colorado | Local-first | Use the city or county record unless a state-controlled scope applies. |
| Connecticut | Statewide | Use the state code and amendments. Confirm the permit application date. |
| Delaware | Local-first | Use the county or municipal adoption and amendments. |
| District of Columbia | Districtwide | Verify the current District Construction Codes and effective dates. |
| Florida | Statewide | Use the current Florida Building Code, supplements, and local requirements. |
| Georgia | Hybrid | Start with the state minimum. Confirm local enforcement and amendments. |
| Hawaii | Hybrid | Confirm the state code and applicable county amendment. |
| Idaho | Hybrid | Verify the legislatively adopted edition and local rule. |
| Illinois | Statewide | Verify the current state baseline and permitted local requirements. |
| Indiana | Statewide | Use the state code and commission amendments. Confirm project scope. |
| Iowa | Hybrid | Separate state-required provisions from locally adopted codes. |
| Kansas | Local-first | Use the local ordinance unless the project is state-owned. |
| Kentucky | Statewide | Use the current Kentucky Building Code and amendments. |
| Louisiana | Statewide | Use the Louisiana State Uniform Construction Code and amendments. |
| Maine | Statewide | Use the state code. Confirm the community’s enforcement status. |
| Maryland | Hybrid | Use the state performance standards and local amendments. |
| Massachusetts | Statewide | Use the current state code and transition rules. |
| Michigan | Statewide | Use the current Michigan code and state amendments. |
| Minnesota | Hybrid | Confirm jurisdictional administration and the adopted edition. |
| Mississippi | Hybrid | Confirm coastal enforcement or the inland jurisdiction’s adoption. |
| Missouri | Local-first | Use the local adoption. Check separate state-owned project rules. |
| Montana | Hybrid | Confirm state or certified local program jurisdiction. |
| Nebraska | Hybrid | Check the local code against the state baseline. |
| Nevada | Scope-limited | Use the local code for ordinary work. State rules cover state projects. |
| New Hampshire | Statewide | Use the state code and amendments. Verify local administration. |
| New Jersey | Statewide | Use the uniform statewide code and current subcode amendments. |
| New Mexico | Statewide | Use the statewide minimum. Check any home-rule requirements. |
| New York | Statewide | Use the Uniform Code or New York City code, based on location. |
| North Carolina | Statewide | Confirm the effective state code and delayed transition dates. |
| North Dakota | Hybrid | Verify the local ordinance against the state update baseline. |
| Ohio | Statewide | Use the Ohio Building Code and state modifications. |
| Oklahoma | Hybrid | Use the commission code where enforced. Verify local amendments. |
| Oregon | Statewide | Use the current structural specialty code and transition rules. |
| Pennsylvania | Statewide | Use the current Uniform Construction Code and local administration. |
| Rhode Island | Statewide | Use the statewide code and Rhode Island amendments. |
| South Carolina | Hybrid | Check approved local climatic or physical amendments. |
| South Dakota | Hybrid | Confirm the local code or the state prevailing code. |
| Tennessee | Hybrid | Identify state enforcement or an approved local program. |
| Texas | Local-first | Use the municipal adoption. Do not assume one statewide project code. |
| Utah | Statewide | Use the state construction code and legislative amendments. |
| Vermont | Scope-limited | Confirm whether state safety rules or a local rule controls. |
| Virginia | Statewide | Use the Uniform Statewide Building Code and amendments. |
| Washington | Statewide | Use the Washington State Building Code and amendments. |
| West Virginia | Hybrid | Confirm whether the jurisdiction enforces the state-adopted code. |
| Wisconsin | Statewide | Use the applicable Wisconsin code and state amendments. |
| Wyoming | Local-first | Use the city or county adoption and amendments. |
The pattern column describes routing only. It does not announce ASCE 7-22 approval for every project in that jurisdiction.
How do the four adoption patterns change the research path?
The same checklist does not work in every state. Start with the adoption pattern, then choose the evidence path.
Statewide
A statewide code supplies the main baseline. The project team should capture the code title, edition, effective date, amendments, and transition rules.
New Jersey is the clearest example. Its ICC record describes a uniform statewide code and says local amendments are not permitted. Local administration still matters, but the technical baseline is not a city-by-city code selection.
Local-first
The city or county adoption is the controlling starting point for ordinary work. A statewide summary cannot replace the local ordinance.
Colorado, Arizona, Kansas, Missouri, Texas, and Wyoming require this discipline. A design basis copied from another city can be wrong inside the same state.
Hybrid
A state baseline and local action both matter. The local body may enforce, amend, opt in, or operate under a delegated program.
California uses a statewide code while allowing justified stricter local amendments. Alaska can delegate administration to a local program. Those systems are both hybrid, but the legal mechanism differs.
Scope-limited
The state can regulate selected buildings while ordinary private projects follow local codes. State-owned buildings, schools, hospitals, or manufactured buildings may use another route.
The project type is therefore part of the adoption question. Asking only for the state and city leaves the scope unresolved.
| Pattern | First record | Second record | Main failure mode |
|---|---|---|---|
| Statewide | State code page | Amendments and transition notice | Using an expired edition |
| Local-first | Local ordinance | Local amendment package | Copying another city’s basis |
| Hybrid | State baseline | Delegation or local amendment | Missing which layer controls |
| Scope-limited | Project scope rule | Local code | Applying a state rule outside its scope |
What do current state adoption records look like in practice?
The four patterns become clearer when applied to current records. These examples also show why an edition label needs a date and scope.
Connecticut: one state baseline with a permit-date rule
The ICC Connecticut adoption record says the state code is based on the 2021 I-Codes. It identifies the 2022 Connecticut State Building Code for permit applications filed from 1 October 2022.
The record also says local amendments are not permitted. That removes one source of technical variation. It does not remove the need to confirm the permit date and project scope.
The 2021 IBC references ASCE 7-16. A Connecticut criteria sheet should therefore record that edition path instead of assuming ASCE 7-22 from the current calendar year.
New Mexico: statewide minimum with a home-rule check
The ICC New Mexico record lists the 2021 IBC as a statewide minimum. It also notes that some home-rule jurisdictions adopt codes.
That makes New Mexico a useful boundary case. The statewide minimum gives the first edition check. The project team must still identify whether a home-rule jurisdiction controls administration or adds requirements.
The source trail should contain both records when both layers apply. Do not cite the state minimum while leaving the local jurisdiction unidentified.
Ohio: a state code name can hide the model-code year.
The ICC Ohio adoption record says the 2024 Ohio Building Code became effective on 1 March 2024. It also says that code adopts 2021 model editions with Ohio modifications.
The two years describe different things. The first names Ohio’s code. The second identifies the underlying model-code edition.
That distinction is essential for ASCE routing. Reading only the state code title could lead a drafter to assume a 2024 IBC basis. The referenced model code instead sends the team to the 2021 IBC standards list.
New Hampshire: amendment dates belong beside the edition
The ICC New Hampshire record identifies the 2021 IBC within the state building code. It includes amendments approved through 11 April 2025.
The edition and amendment date should appear together in the project evidence. Recording only 2021 IBC loses later state changes. Recording only current New Hampshire code hides the referenced model-code year.
The plan set does not need a long legal history. It needs a precise design basis and a retrievable source.
California: statewide does not mean amendment-free
The ICC California adoption record describes state-level code adoption and local enforcement. It also says local building and fire jurisdictions may adopt stricter amendments with required findings.
The project team therefore needs the state cycle and the local amendment package. A statewide code reference alone does not complete the chain.
California also has specialized state enforcement for named building categories. Confirm the responsible authority before treating the city as the only reviewer.
New Jersey: uniformity changes the second check
The ICC New Jersey adoption record describes a uniform statewide construction code. It says local jurisdictions cannot amend that technical code.
The second check is therefore not a search for a city-specific technical edition. It is a check of the current state subcode, amendments, project scope, and local administration.
This is why the routing pattern matters. Reusing California’s local-amendment workflow in New Jersey wastes time and can create false conflicts.
Texas and Wyoming: the local ordinance is the main evidence
The ICC Texas record says building-code adoption occurs locally. It also lists statutory baselines for named scopes.
The ICC Wyoming record says there is no single statewide building code. Cities and counties adopt and enforce their own codes.
For ordinary solar work, the local adoption record is the central evidence in both states. The state page helps route the search. It does not establish the final project edition.
North Carolina: transition dates can move
The ICC North Carolina record documents legislative delays to the 2024 state code. A title or draft effective date can therefore become stale before a permit is filed.
Save the current official effective-date notice with the project. Then record which code applies to that permit application.
This protects the calculation from a moving transition date. It also gives the reviewer a clear explanation when an older edition remains legally controlling.
What should the project code verification record contain?
Use one evidence record for every project address. A link alone is not enough because web pages change.
The record should contain these fields:
- Project address and parcel jurisdiction.
- Building department and plan-review authority.
- Building occupancy and risk category basis.
- Adopted building-code title and edition.
- Adoption ordinance or state regulation number.
- Effective date and permit transition rule.
- Referenced ASCE 7 edition.
- State and local amendments affecting structural loads.
- Source URL, captured document, and access date.
- Written AHJ clarification for any unresolved conflict.
This is the Edition Evidence Chain. Every link should lead from the project to the authority, code, amendment, and referenced standard.
| Evidence layer | Example record | Why it matters |
|---|---|---|
| Project | Address, occupancy, permit date | Establishes scope and timing |
| Authority | City, county, or state agency | Identifies the enforcing body |
| Adoption | Ordinance, regulation, or code page | Proves the model-code edition |
| Amendments | State and local amendment files | Captures changed provisions |
| Reference | ASCE edition in adopted code | Fixes the structural load standard |
| Confirmation | Reviewer email or portal response | Resolves conflicts before calculation |
The record belongs with the design criteria sheet. It should also be retained with calculation inputs and reviewer correspondence.
Project check. Save the adopting document, not only a bookmark. Record the date and the section that identifies the referenced standard.
What changes on a solar structural plan set?
The adoption decision should appear consistently across the drawings and calculations. A correct calculation can still draw comments when another sheet lists a different code.
Check these locations:
| Plan-set location | Required consistency check |
|---|---|
| Cover sheet | Adopted building code and referenced standard |
| Design criteria | Wind, snow, seismic, rain, and risk-category basis |
| Structural notes | Materials, load combinations, and referenced standards |
| Attachment details | Loads and capacities use compatible design formats |
| Calculation cover | Project address, authority, edition, and revision |
| Equipment schedule | Racking model and tested capacity match the layout |
| Revision log | Code-basis changes are visible and dated |
Do not use a state matrix to choose a wind speed. The site-specific value can depend on address, risk category, topography, and adopted hazard data.
Do not use it to choose a snow load either. Ground snow data, elevation, drifting, sliding, roof geometry, and local criteria can affect the design.
The companion wind and snow load criteria by state guide routes teams to the correct source. It deliberately avoids publishing one project value per state.
The STAAD report acceptance guide explains how the source trail should appear in a calculation package. The AHJ rejection guide shows how mismatched criteria create review comments.
How should local amendments be handled?
Local amendments belong in the input register before analysis starts. They should not appear as a late note after calculations are complete.
First, identify whether the state permits local technical amendments. New Jersey’s uniform system differs from California’s stricter-local-amendment route.
Second, find the actual amendment document. A municipal code landing page can link several cycles. Match the document to the permit date.
Third, compare the amendment against the design basis. Look for changes to wind regions, snow criteria, seismic provisions, special inspections, existing buildings, and administrative submittals.
Fourth, record the disposition. State whether the amendment changes an input, a detail, a note, or only the permit process.
Fifth, ask the AHJ when documents conflict. Preserve the response with the project record.
| Amendment finding | Design response |
|---|---|
| Technical load change | Update inputs and recalculate affected checks |
| Material or fastening change | Update notes, details, and capacity checks |
| Special inspection trigger | Add the required statement or schedule |
| Administrative submittal rule | Add the named document to the package |
| Unclear transition date | Obtain written authority confirmation |
This work should happen before the first calculation issue. Otherwise, one code-cycle correction can force several drawing revisions.
Can ASCE 7-22 be used when an older edition is adopted?
Do not assume that a newer edition can replace the adopted edition. The AHJ, project contract, engineer of record, or owner criteria may impose a specific path.
A contract can request an additional check to a newer standard. That does not automatically change the permit basis. Keep the adopted-code analysis and any supplemental check clearly separated.
An authority can also approve an alternate method under its code process. That decision requires the authority’s documented acceptance. A blog article cannot supply it.
Use this decision sequence:
- Identify the legally adopted code and referenced ASCE edition.
- Identify contractual or owner requirements.
- List conflicts between the two bases.
- Ask the engineer of record and AHJ for direction.
- Record which basis controls each deliverable.
- Keep supplemental calculations labeled as supplemental.
This approach prevents an attractive but unsafe shortcut. A newer edition is not always more conservative for every load effect. Mixing maps, coefficients, and combinations across editions can create an invalid hybrid.
How does this affect schedule and permit risk?
Edition research is a small early task with a large revision radius. It can affect inputs, notes, calculation software, racking checks, and professional review.
The most expensive time to discover the wrong edition is after the layout and attachment pattern are fixed. A changed load can alter attachment spacing, ballast, member demand, and supporting-structure checks.
For multi-state installers, the control is operational. Add an adoption record to intake and block calculation release until it is complete.
| Workflow stage | Release condition |
|---|---|
| Intake | Address and authority confirmed |
| Criteria setup | Adopted code and amendment sources captured |
| Analysis | Referenced ASCE edition recorded |
| Drawing issue | Criteria match every sheet and calculation |
| Resubmittal | Reviewer comments and edition changes reconciled |
Do not maintain one hidden spreadsheet as the only source. Store the project evidence with the project. Then maintain a separate watchlist for upcoming state and local code changes.
How can Heaven Designs support the design record?
Heaven Designs provides solar civil and structural engineering and STAAD Pro reports and calculations for solar project teams.
The useful starting package is not a state name. It contains the site address, authority, adopted code evidence, roof or foundation information, equipment data, layout, and requested deliverables.
Heaven Designs does not use this matrix as project approval advice. The authority and the responsible licensed professional control jurisdiction-specific decisions.
If your team needs help assembling the design inputs and calculation package, send the project record for review. Include the adopting document when available.
Frequently asked questions
Does IBC 2024 always mean ASCE 7-22 applies?
IBC 2024 references ASCE/SEI 7-22. The project must still be inside the adopted code’s scope. Check state and local amendments, effective dates, and transition rules.
Does a statewide code remove the need to contact the AHJ?
No. A statewide baseline reduces edition variation, but local administration still matters. Confirm the permit date, project scope, submittal rules, and amendments allowed by state law.
Can one ASCE edition be used for every city in Texas?
No. The ICC Texas record describes ordinary building-code adoption as local. Obtain the municipal adoption and amendments for the project address.
Why is Colorado marked local-first?
The ICC Colorado record says the state has no ordinary statewide building code. State agencies control selected scopes. Cities and counties generally control ordinary project adoption.
Which ASCE edition applies under IBC 2021?
IBC 2021 Chapter 35 references ASCE/SEI 7-16. Do not replace it with ASCE 7-22 unless the controlling code, amendment, contract, and authority support that decision.
Is the state matrix enough for a structural calculation?
No. The matrix only finds the adoption route. The calculation still needs the project address, risk category, site criteria, geometry, equipment data, and responsible professional review.
How often should the matrix be refreshed?
Review the matrix at least quarterly. Recheck it after a state code-cycle announcement. Every project row still requires verification on the date of use.
What should be saved in the permit file?
Save the adopting regulation or ordinance, amendments, effective-date notice, referenced-standard section, access date, and any written AHJ clarification. Keep them with the design criteria and calculations.
The decision to make before calculation starts
Treat ASCE adoption as a chain of evidence. Start with the project. Identify the authority. Find the adopted code. Read the amendments. Then select the referenced ASCE edition.
The 51-jurisdiction matrix narrows the search. It does not replace it. That limitation is what makes the matrix safe enough to use.