Design & Engineering

How Steel Buildings Are Designed:
A Step-by-Step Engineering Process

March 16, 2026

Lead

The steel building design process turns an owner's requirements and site conditions into a structural system that can be checked, detailed, fabricated, and erected. It begins with a defined brief and design basis, then develops load paths, analysis, members, connections, and coordinated information for the other project teams.

These steps follow a logical order, but design is iterative. Analysis can change the framing concept; connection design can change member sizes; and revised crane data, openings, or foundation assumptions can require earlier work to be checked again. This article explains the structural engineering process. For the wider sequence covering quotation, fabrication, and installation, see the steel structure project workflow.

At a Glance

  • The project brief establishes what the building must accommodate; the design basis establishes the criteria against which it will be checked.
  • A structural concept needs continuous load paths and a workable stability system before member sizes are optimized.
  • Analysis results are demands to be checked. A software model does not, by itself, prove that the completed building will behave as assumed.
  • Members, connections, secondary steelwork, and foundations must be coordinated as parts of one system.
  • Design information needs a stated purpose and revision status before another party uses it for pricing, permitting, fabrication, or construction.

Step 1: Define What the Building Must Do

Design begins with the building brief, not with member sizing. The engineer needs enough information to understand the building's function, geometry, operational constraints, and foreseeable changes.

Important inputs commonly include:

  • Site location and intended occupancy or industrial use
  • Overall length, width, eave height, roof profile, and required clear spans
  • Bay spacing and locations where internal columns are acceptable
  • Doors, loading bays, wall openings, canopies, and penetrations
  • Cranes, monorails, mezzanines, platforms, conveyors, tanks, and suspended services
  • Roof-mounted equipment, solar panels, ceilings, and fire-protection systems
  • Cladding and roofing systems, including their connections to the frame
  • Clearances for production, storage, vehicle movement, and maintenance
  • Fire-resistance, durability, and future-expansion requirements
  • Site access, transport limits, erection equipment, and planned construction sequence

“Crane required” or “solar-ready” is not a complete design input. The engineer may need equipment loads, operating positions, support locations, relevant dynamic effects, maintenance requirements, and manufacturer information. An undefined item should remain an open decision or an explicitly stated assumption; it should not silently become a model input.

The first useful output is a controlled brief stating what is confirmed, what remains provisional, who will supply missing information, and when each decision is needed.

Step 2: Establish the Design Basis

The design basis turns the brief and site information into a controlled set of engineering criteria. It identifies the governing jurisdiction and adopted standards, relevant editions, loading criteria, serviceability requirements, exposure conditions, fire requirements, and agreed design responsibilities.

Site information may include:

  • Wind region, terrain or exposure, topography, and building openings
  • Snow criteria where applicable
  • Seismic parameters, ground conditions, and the building's applicable risk classification
  • Rain, temperature, flood, or other relevant environmental actions
  • Geotechnical information and foundation recommendations
  • Atmospheric or chemical exposure affecting protection and durability
  • Adjacent structures, utilities, and site restrictions

Different standards perform different jobs. In a US design framework, ASCE/SEI 7-22 addresses loads and associated criteria, while AISC 360 addresses structural steel design. In the Eurocode framework, EN 1991 addresses actions on structures and EN 1993 addresses steel design. The applicable adoption, edition, local amendments, and National Annex must be confirmed for the particular project. The steel structure design standards guide explains these roles in more detail.

The design basis should also identify responsibilities. Depending on the contract, different parties may design the main frame, secondary steelwork, connections, foundations, cladding support, crane runway, stairs, platforms, and temporary works. The team needs to know who supplies loads, who designs each interface, and who reviews it.

The main output is a design-basis document that the responsible parties can review before detailed analysis proceeds.

Step 3: Develop the Structural Concept and Load Paths

The engineer develops a framing arrangement that carries each relevant action through a continuous load path to the foundations. For a typical single-storey building, the task goes beyond choosing a portal frame or truss. It includes how roof and wall actions reach the primary frames, how longitudinal forces reach the bracing system, and how columns deliver reactions to their bases.

Concept decisions may include:

  • Primary framing system, bay spacing, and single-span or multi-span layout
  • Column, rafter, beam, or truss arrangement
  • Roof and wall bracing locations
  • Connection stiffness assumptions
  • Purlin and girt arrangements and any assumed restraint they provide
  • Movement joints or another movement strategy
  • Preliminary base conditions and foundation interfaces
  • Shipping-piece lengths, splices, and transport strategy

The concept must accommodate the building's operation. Removing wall bracing to create an access opening, for example, requires an alternative force path; moving the opening on an architectural drawing alone does not solve the structural problem.

Structural efficiency is broader than minimum steel weight. A heavier scheme can sometimes reduce connection complexity, fabrication work, transport difficulty, or erection demands. The guide to choosing the right steel structure examines that decision in greater depth.

Typical outputs include concept drawings, a preliminary member layout, an identified stability system, and assumptions requiring confirmation.

Step 4: Determine Design Actions and Analyze the Structure

Once the concept is sufficiently defined, the engineer establishes the actions and represents the structure in an analytical model.

Depending on the project, actions may include self-weight, permanent finishes and services, imposed loads, wind, snow, seismic effects, rain, temperature, cranes, machinery, stored materials, and relevant construction-stage effects. The governing standard determines which actions and combinations apply to the required design situations. The load combination in steel structure design article explains why loads cannot simply be checked one at a time.

A model is a representation of the intended structure. Its results depend on assumptions such as:

  • Member geometry, offsets, releases, and effective lengths
  • Support conditions and foundation restraint
  • Connection stiffness in the global model
  • Bracing, diaphragm, and secondary-member participation
  • Load positions, tributary areas, and eccentricities
  • Imperfections and second-order effects where required
  • Tension-only or compression-only behavior where relevant

Those assumptions must match a feasible built arrangement. A roof panel, purlin, or connection cannot be credited with providing restraint merely because the software model assumes that restraint exists.

The engineer checks the model's load paths, reactions, deformed shapes, equilibrium, force patterns, and sensitivity to important assumptions. Software output does not validate an incorrect input or an incomplete stability system.

Analysis produces forces, moments, displacements, stability effects, connection demands, and support reactions. These are demands for subsequent checks, not proof on their own that the building is adequate.

Step 5: Design Members, Stability Systems, and Connections

The engineer compares analysis demands with the resistance and serviceability requirements of the governing design framework. Main members, secondary members, bracing, and connections must be checked in the roles they will perform.

Depending on the member and project, checks can cover tension, compression, bending, shear, combined actions, local effects, overall buckling, and the required restraint. Serviceability can involve deflection, lateral movement, vibration, roof drainage or ponding sensitivity, cladding compatibility, and crane alignment.

AISC 360 provides requirements for structural steel design and construction within its US scope. In the European framework, EN 1993 addresses steel design through its applicable parts, used with the other relevant Eurocodes and national provisions.

Connection design must agree with the structural analysis. If a joint is assumed to provide significant rotational restraint, its actual detail must support that behavior. A nominally pinned joint still needs to transfer its specified actions. Bolts, welds, plates, stiffeners, and local member effects are checked as relevant; fatigue, ductility, or seismic detailing may also matter for a particular project.

Connection choice has practical consequences for shop access, site assembly, tolerances, coating, and inspection. The bolted versus welded connections guide compares those considerations.

This stage can send the process backward. A failed deflection check may change member depth. A difficult connection may change the framing layout. Each revision can alter stiffness, weight, reactions, or forces elsewhere in the structure.

Step 6: Coordinate Foundations and Other Interfaces

The steel frame and foundations must transfer forces as one system, even when different organizations design them. Under the agreed allocation of responsibility, the superstructure designer communicates the geometry and reactions needed for foundation design.

Interface information may include:

  • Compression, uplift, shear, and moment reactions for relevant design situations
  • Which reaction components act together in the same combination
  • Base-plate dimensions, grout needs, and bearing assumptions
  • Anchor-rod arrangement, projection, and setting requirements
  • The intended shear-transfer method
  • Column orientation, base levels, and setting-out coordinates
  • Assumed base restraint or rotational stiffness

Information also flows back from the foundation designer. Foundation stiffness, settlement, anchor capacity, or another constraint may require a change to the steel-frame model. A base shown as “fixed” in analysis does not gain that restraint simply because a large base plate appears on a drawing; the connection and foundation must justify the assumed behavior.

Coordination extends to the building envelope, roof drainage, doors, cranes, services, platforms, and process equipment. Their loads and attachment details can affect steel members, while frame movement can affect their performance.

The construction stage needs an explicit interface too. The completed building may rely on bracing, connections, or other stabilizing elements that are not yet effective during a particular erection stage. The contract should allocate erection engineering and temporary-stability responsibilities to the appropriate qualified parties.

Step 7: Complete and Release Design Information

Checked engineering must become coordinated information that others can use. Depending on the contract and jurisdiction, the package may include:

  • Design drawings and general notes
  • Member sizes, steel grades, and schedules
  • Connection requirements or completed connection details
  • Design actions and foundation or equipment-interface reactions
  • Material, bolt, weld, coating, and fire-protection specifications
  • Movement, tolerance, inspection, and camber requirements where relevant
  • Calculation reports and design records
  • Models or data exchanges when required by the contract
  • Identified assumptions, exclusions, and delegated-design items

Design drawings and fabrication drawings are not automatically the same deliverable. The responsibilities of the engineer of record, specialty engineer, manufacturer, and detailer must be established for the project. In US structural-steel practice, AISC 303 provides a framework for standard practices, while the project documents define its particular scope and process.

Each issue should state its purpose and revision status. A drawing issued for review, pricing, permitting, fabrication, or construction may authorize different actions. Even a correct current design can be undermined if a superseded drawing or model remains in use.

Fabrication and erection feedback may identify bolt-access problems, welding constraints, unavailable plate sizes, shipping limits, lifting needs, or difficult splice locations. Resolve these issues through the defined design and approval process before the affected work is released.

Why the Design Process Loops Back

The seven steps describe the work's logical order; they rarely happen only once. A new input can invalidate assumptions used in several completed steps.

Common triggers include:

  • A change of building location or governing jurisdiction
  • A new crane, mezzanine, solar array, ceiling, or heavy service
  • Different cladding, roof buildup, or fire-protection requirements
  • Moved or enlarged doors and other openings
  • Removal of a column or bracing line
  • Revised dimensions, bay spacing, or clear height
  • Updated ground information or foundation assumptions
  • Different steel availability, shipping-piece lengths, or splice locations
  • A change in responsibility for connections or delegated design

A controlled change records the revised input, checks the affected analysis and interfaces, updates the necessary drawings and specifications, and issues a traceable revision. It distinguishes a proposed alternative from an approved design change.

Confirming key inputs at an agreed milestone does not make later changes impossible. It makes their effect on engineering, procurement, cost, and schedule visible before the team accepts them.

What to Prepare Before Detailed Design

The following information helps the engineering team begin with fewer unresolved assumptions:

  • Confirmed site address and governing authority
  • Building use, occupancy, and relevant service requirements
  • Dimensioned architectural or operational layout
  • Required spans, heights, openings, and acceptable column positions
  • Crane, equipment, platform, storage, and suspended-service data
  • Roofing and wall-system information, including attached equipment
  • Ground investigation results or a date for receiving them
  • Fire, durability, thermal, and envelope requirements
  • Planned expansion and future loads that the current design must accommodate
  • Responsibility matrix and required deliverables
  • Known fabrication, transport, and erection restrictions
  • Decision schedule and named approvers

An unavailable item should be marked pending, with an owner and a required date. Its absence can then be managed without disguising an assumption as a confirmed requirement.

Conclusion

Steel building design develops through connected decisions: define the requirements, establish the design basis, create load paths, analyze the response, check members and connections, coordinate interfaces, and release controlled information.

A sound calculation is only one part of the result. The inputs must be traceable, the model must reflect the intended details, foundations and other systems must be coordinated, and each change must be checked wherever it affects the design.

You May Also Like

Need Help With Your Project?

From engineering and fabrication to delivery,
we can help you develop a steel structure solution tailored to your project requirements.

Start Your Project