> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stru.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Wind & Seismic Loads

> Give a project address, risk category, and exposure, and get the site's wind, seismic, and snow design parameters with references, then a load calc package built from them

## From Address to Load Package

Give the agent the project address, the risk category, and the exposure, and it looks up the site's wind, seismic, and snow design parameters and returns them with the governing references. From there, ask for the load calc package and the parameters flow straight into it.

Any project that needs site hazard data starts the same way: an office building, a water treatment structure, a pedestrian bridge, a telecom mast. The brief is what makes it work, so give the inputs up front:

```text The site brief theme={null}
Get the wind, seismic, and snow design parameters for
2200 Harbor Ave, Portland, OR 97201 (Office Building Demo).
Risk Category II, Exposure C, Site Class D, per ASCE 7-22.
List every parameter with the section, table, or hazard map
it comes from.
```

Address, risk category, exposure, site class, and code edition: a complete brief gets a complete deliverable.

***

## Step-by-Step

<Steps>
  <Step title="Send the site brief">
    The agent returns the design parameters for the location: wind speed, seismic ground motion values, snow load, each tagged with the reference it comes from.

    <Frame>
      <img src="https://mintcdn.com/struai/aJeDnguak6OWj2zX/images/site-hazard-parameters-answer.png?fit=max&auto=format&n=aJeDnguak6OWj2zX&q=85&s=b8c5c974f153f6b494d8e4319759aced" alt="The site brief and the returned wind design parameters, each value listed with its source figure, table, or section" width="1785" height="1123" data-path="images/site-hazard-parameters-answer.png" />
    </Frame>
  </Step>

  <Step title="Check the references">
    Every parameter should trace to a section, table, or hazard map. For any value you will cite in a submittal, ask the agent to quote the source text, the same habit that makes [code questions](/workflows/code-questions) reviewer-ready.
  </Step>

  <Step title="Ask for the calc package">
    One load type per request lands cleanly: the wind package first, then seismic, then snow, each building on the parameters already on the table.

    ```text The wind package theme={null}
    Using those parameters, build the wind load calc for the
    MWFRS: design pressures for each wall and roof zone, with
    the equations and coefficients shown. Deliver it as a calc
    package I can check line by line.
    ```

    The deliverable side of this (formats, downloads, checking the sheet) is covered in [Mathcad Calc Sheets](/workflows/mathcad-calc-sheets).

    <Tip>
      **Put it on your letterhead.** Set the project name, number, calc by, checked by, and your company logo once, and every package comes out branded. See [Branded Reports](/workflows/branded-reports).
    </Tip>
  </Step>

  <Step title="Have it read the numbers back">
    Before the package leaves your desk, ask the agent to walk you through the governing value in the finished file:

    ```text The read-back theme={null}
    Walk me through the governing wind pressure in the finished
    file: which zone, which equation, and which coefficients
    produced it.
    ```

    A number you have heard explained is a number you can defend.
  </Step>
</Steps>

***

## Where the Loads Go Next

The parameters and pressures feed directly into the rest of the design:

* **Element checks**: carry the loads into beam, column, and footing checks. See [Design Checks](/workflows/design-checks).
* **Analysis models**: apply them as load cases in an ETABS or SAP2000 model. See [Build ETABS & SAP Models](/workflows/build-etabs-sap-models).

You are the engineer of record: verify the parameters against the governing hazard data for the site before they drive a design.

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Mathcad Calc Sheets" icon="file-invoice">
    The calc package deliverable: formats, downloads, checking

    [Mathcad Calc Sheets](/workflows/mathcad-calc-sheets)
  </Card>

  <Card title="Design Checks" icon="square-check">
    Carry the loads into element design checks

    [Design Checks](/workflows/design-checks)
  </Card>

  <Card title="Build ETABS & SAP Models" icon="cubes">
    Apply the loads as cases in an analysis model

    [Build ETABS & SAP Models](/workflows/build-etabs-sap-models)
  </Card>

  <Card title="Branded Reports" icon="stamp">
    Header fields and your logo on every deliverable

    [Branded Reports](/workflows/branded-reports)
  </Card>
</CardGroup>

<Info>
  **Questions?** Email **[support@stru.ai](mailto:support@stru.ai)** or [book a call](https://cal.com/bhosh).
</Info>