Information a Structural Engineer Needs to Get Started

Architecture and structural engineering are strongest when they begin with clarity. The more complete the early exchange of information, the more efficiently the structural system can be developed and coordinated with the design.

In early design phases, some information is still taking shape. When assumptions are clearly discussed and documented, the team can move forward confidently and adjust efficiently as decisions are finalized.

The following inputs help a structural engineer engage productively and support the design from day one..

Architectural plans and design intent

Current plans, sections, and elevations are essential, even if they are still evolving. Just as important is understanding intent:

• Are long spans or column-free areas critical?

• Are certain ceiling heights fixed?

• Are there large openings or façade features that must remain uninterrupted?

• Is future expansion anticipated?

Clear priorities help ensure the structural system supports the architecture rather than constrains it.

Building use and loading

Structural design is driven by occupancy and use. Offices, residential units, assembly spaces, storage areas, and rooftops all carry different load requirements under code.

Provide clear information about occupancy classification, anticipated live loads, rooftop equipment, and any specialty spaces such as gyms or high-density storage. This ensures the structure is sized appropriately from the outset.

Lateral system preferences and constraints

Wind and seismic resistance requires a lateral system — shear walls, braced frames, or moment frames — that must be deliberately located within the plan. Where these elements can and cannot go is one of the most consequential early conversations between architect and structural engineer.

Identify any areas where lateral elements would be problematic: open facades, flexible floor plates, key circulation paths, or spaces where visual continuity is critical. Equally useful is knowing where consolidation is acceptable. The earlier these preferences are understood, the more the structural system can be shaped around the architecture rather than imposed on it.

Site and geotechnical data

Foundation design depends on soil conditions. A geotechnical report provides information about bearing capacity, settlement potential, groundwater, and seismic site class.

If final data is not yet available, sharing preliminary findings or timelines helps manage expectations and avoid overly conservative early assumptions.

Site adjacency and below-grade conditions

On constrained urban sites or projects with below-grade program, additional information is needed from the outset.

Adjacent structures, shared walls, property line conditions, and existing below-grade infrastructure can all influence foundation strategy, excavation approach, and structural sequencing. For projects with basements or below-grade parking, the depth, extent, and waterproofing expectations of that program should be clearly established early, as they directly affect foundation and wall design.

Where these conditions exist, sharing any available survey data, neighboring building records, or utility information allows the structural engineer to identify constraints and risks before they surface mid-design.

Material preferences and performance goals

If the team has preferences for steel, concrete, mass timber, or other systems, that should be discussed early. Sustainability goals, including embodied carbon targets when applicable, vibration criteria, durability expectations, and supply considerations all influence system selection.

Clarity here prevents mid-design shifts that require significant rework.

Budget and schedule

Structural decisions affect major cost drivers such as framing quantities and foundation scope. While structural engineers do not set the budget, understanding financial expectations helps align system recommendations.

Delivery method and schedule also matter. Fast-track projects, design-build delivery, or early foundation packages require coordination from the beginning.

Code and jurisdictional requirements

Local amendments, resilience goals, and special inspection requirements can significantly influence structural design. Discussing these early avoids late-stage compliance adjustments.

Renovation and existing conditions

For renovations, additions, or adaptive reuse, existing drawings and investigation data are critical. Information about the original structural system, prior modifications, and observed deficiencies allows for realistic feasibility assessment.

Without it, early concepts may require substantial revision.

Clarify assumptions

If some information is still pending, identify it clearly. A shared understanding of what is known, what is assumed, and what may change keeps the team aligned and reduces friction later. The clearer those answers are, the more predictable the design process becomes.

When architects and structural engineers exchange information early and openly, the result is smoother coordination and fewer surprises throughout the project.