Florida, California and Oregon reference ASCE 7-22 through their adopted building codes. That is not a complete US adoption list. The applicable edition depends on the jurisdiction, project and permit timing. Confirm the building code, amendments and referenced ASCE 7 edition with the authority having jurisdiction, or AHJ, before commissioning the calculation.
A quotation can describe the right mounting family and still arrive with the wrong design basis. The problem may be an outdated code reference, a transition provision that was overlooked, or a calculation copied from another jurisdiction. None can be resolved by changing the standard number on the cover sheet.
This guide is a procurement check for building-code-based solar mounting calculations. It is not a determination of the permit requirements for a particular site. Residential provisions, existing-building work, special structures and local amendments can create different routes. The useful question is not simply whether a state has adopted a new code. It is which requirements govern this application.
Why the edition belongs in the enquiry
The building code and ASCE 7 perform different jobs. A jurisdiction adopts and amends a building code. That code references standards for particular purposes. A published standard does not automatically become a legal requirement everywhere on its publication date. Conversely, a code based on an older model edition may include a specific reference to a newer standard.
That distinction matters when the same racking supplier quotes across several states. A reusable product drawing can be a useful starting point. The project calculation still needs the governing code, applicable loading standard, actual site inputs and the correct structural arrangement. The quotation should identify that basis before the customer treats it as a permit-ready package.
Our ASCE 7-22 technical overview discusses changes in the loading standard. This article addresses the earlier decision: which edition is relevant to the project. It does not reproduce a comparison of wind, snow, seismic or tornado provisions.
State adoption checks, with their limits
The following table is a selected official-source review dated 26 September 2026. It is not a survey of all states and does not say that states outside the table use ASCE 7-16. An effective date, a mandatory date and the date applicable to an individual permit can differ. Check the source and the transition provisions together.
| Jurisdiction | Code basis | ASCE 7 reference or scope | Effective date / transition | Official sources |
|---|---|---|---|---|
| Florida | 2023 FBC, 8th Edition | 7-22 | 2023-12-31 subject to permit applicability | Official source 1 / Official source 2 |
| California | 2025 CBC, 2024 IBC basis | 7-22 with adopted amendments/supplements | 2026-01-01 subject to permit applicability | Official source 1 / Official source 2 |
| Oregon | 2025 OSSC | 7-22 | Effective 2025-10-01; construction provisions mandatory 2026-04-01; Chapter 1 mandatory 2025-10-01 | Official source 1 / Official source 2 |
| Washington | 2021 IBC with state amendments; 2024 code cycle pending | 7-16 general basis; 7-22 Ch. 6 for specified tsunami scope | Current code: 15 Mar 2024. New cycle scheduled 3 May 2027; not yet effective | Official source 1 / Official source 2 / Official source 3 |
| New York excluding separate NYC code path | 2025 Uniform Code and BCNYS, 2024 I-Code basis | 7-22 with NY amendments | New permit applications from 2025-12-31 per state adoption notice | Official source 1 / Official source 2 / Official source 3 |
| New Jersey | 2024 IBC, NJ edition | 2024 IBC route; confirm final adopted references | Adopted 17 Aug 2026; eligible applications have a six-month grace period | Official source 1 / Official source 2 / Official source 3 / Official source 4 |
| Texas | Municipal commercial code framework plus special state programs | Check project jurisdiction and applicable program | No single date assigned in this guide | Official source 1 / Official source 2 |
As of 26 September 2026. Confirm the applicable code, amendments and permit transition with the AHJ before issuing a permit set. Recheck adoption status when the project moves from quotation to submission.
Florida, Oregon and California illustrate why one date column is not enough. Florida's code edition has a stated effective date. Oregon explicitly distinguishes the start of an optional transition from the later mandatory date. California's statewide code takes effect at the start of the stated calendar year, while project applicability still needs the relevant administrative and local requirements.
Washington needs an additional qualification. Its current reference chapter includes an ASCE 7-22 reference for a specified provision alongside the general ASCE 7-16 reference. The newer statewide code cycle is a separate process. Describing the state as either entirely on ASCE 7-16 or already on the new general code basis would hide that distinction.
When a state allows applications under an earlier code during a grace period, the application date and the authority's transition rules become part of the enquiry. Ask the project team to record the applicable basis, not simply forward a headline announcing adoption. Keep a copy or dated reference to the official adoption notice in the project file.
Eight entries to check in the calculation package
The eight entries below are a buyer's completeness check, not a substitute for the required engineering calculations. They help the reviewer connect the document to the project. If one is absent, ask for the missing basis rather than supplying an assumed value yourself.
1. Building code, amendments and loading-standard edition
The cover or design-basis section should identify the adopted building code and the applicable ASCE 7 edition. Include relevant state or local amendments and supplements. “IBC” or “ASCE” alone leaves too much unresolved. Confirm whether the package is a preliminary quotation calculation, a design-development document or a submission intended for the permit authority.
2. Risk Category
State the Risk Category selected for the structure and the basis for that selection. Procurement should obtain the project engineer's requirement; it should not choose a category to obtain a smaller reaction or a lower price. A category used for a different building is not evidence that the same category applies here.
3. Exposure and site assumptions
Identify the Exposure Category and other relevant site assumptions used in the calculation. Site address alone is not a complete exposure assessment. Ask the responsible engineer to confirm the assumptions, especially when a generic supplier worksheet uses a default. Keep any site information supplied by the customer attached to the same document revision.
4. Wind-hazard input and its source
Identify the source, edition basis and retrieval date for the wind-hazard input. If the ASCE Hazard Tool is used, retain the project-specific output and the selections that produced it. A screenshot without the selected edition and location is difficult to audit. The engineer remains responsible for interpreting the input and applying the relevant provisions.
5. Snow input and the corresponding basis
Record the source and edition basis for the snow input, where applicable. Do not carry a value from another project simply because it is in the same state. The package should make clear which environmental inputs apply, which do not, and how the determination was made. This article supplies no replacement snow value or conversion factor.
6. Applicability of additional hazard provisions
Ask the engineer to record whether additional provisions, including the applicable tornado requirements, need consideration. The answer depends on the standard's scope and the project conditions, not the supplier's preferred product. A short applicability statement is more useful than silently omitting a hazard. Detailed technical discussion belongs in the referenced design basis and calculations.
7. Arrangement and design procedure
Identify whether the calculation concerns a roof-mounted or ground-mounted arrangement and the design procedure used. The supporting roof or foundation, module layout, tilt, attachment detail and relevant geometry must correspond to the quoted system. Do not copy a section reference from a roof calculation into a ground-mounted proposal because the rail section happens to be the same.
8. Issue date, revision and linked drawings
The calculation issue date and revision should match the drawing and bill-of-materials references used for the quotation. If a module size, attachment layout or support spacing changes, ask whether the calculation remains applicable. Keep superseded documents identifiable. A current-looking cover page attached to older internal pages is not an adequate revision record.
When the supplier calculated to a different edition
Start by distinguishing a documentation error from a design-basis mismatch. If the calculation is correct but the cover reference is wrong, the engineer should resolve and reissue the document with a traceable correction. If the calculation actually used a different edition, changing the cover is insufficient. Have the responsible engineer reassess the design under the required basis and issue the appropriate revision.
There is no universal multiplier that converts an ASCE 7-16 calculation into an ASCE 7-22 calculation. The input data, relevant provisions and applicability decisions need to be checked together. Nor does using a newer edition automatically make a package acceptable where the adopted requirements differ. The AHJ and responsible designer must resolve any proposed alternative route.
The reassessment may retain some components or require changes. That outcome cannot be promised before the work is done. Ask the supplier to identify the effect on the mounting arrangement, reactions, connections and supporting structure, then update the commercial offer where needed. Keep the design change and the price change connected so the procurement decision is based on the same configuration.
The same principle applies in reverse. A supplier calculation to ASCE 7-22 is not, by itself, a reason to disregard the code basis applicable to the permit. “We always use the latest standard” does not answer the question of which requirements the project must satisfy.
For document-level checks, see how to read a solar mounting calculation report. An input inconsistency, an untraceable revision or a missing reaction schedule deserves attention even when the edition on the cover appears correct.
Put the basis in the quote, then confirm it at submission
A useful enquiry supplies the site and project description, applicable code basis, relevant drawings, module information and the responsible review contact. Mark information that is still preliminary. A supplier can prepare a proposal around stated assumptions, but those assumptions should be visible so the next reviewer can resolve them.
Record who will confirm the adopted edition and who will review the mounting design's interface with the roof or foundation. Those are distinct responsibilities. Do not assume a component supplier's calculation automatically assesses every existing roof member, foundation condition or connection outside the quoted scope.
At the quotation stage, ask for the design assumptions and excluded scope in writing. Before submission, reconcile them with the final project data and local requirements. If the application is delayed into a new transition window, check the governing basis again. A calculation that was prepared earlier should not be treated as permanently current simply because the hardware has not changed.
Some older Solaracks product pages still refer to ASCE 7-16. The calculation basis for the project should follow the requirements confirmed with the AHJ. State the required edition in the enquiry so the engineering and commercial documents can be aligned. A catalogue reference is not a substitute for that project decision.
Our engineering information provides background for preparing that enquiry. Describe a calculation as calculated to the identified standard and project basis. Do not describe a racking product as certified to ASCE 7-22: the loading standard is not a product certification scheme.