The real problem isn't the checklist — it's sending plans that aren't frozen
If you're the project architect coordinating the structural kickoff, the question behind the question is usually "how do I hand off once, instead of three times?" The most expensive mistake in architect-to-SE coordination isn't forgetting an item on a list. It's sending plans that are still moving. A structural engineer can start a framing layout off an 80%-baked plan — but every time you shift a stair, widen a corridor, or move a shear-relevant wall after handoff, you don't just nudge a line. You can invalidate a load path, force a beam to be resized, push a column into a space it can't live in, and trigger a re-analysis that costs both offices real hours. The SE is laying out a system where elements depend on each other; an architectural change that looks cosmetic to you can ripple through their gravity and lateral scheme. So the goal of a good handoff is twofold: give them everything below, and be honest about what's frozen versus what's still in flux — because they'll sequence their work completely differently depending on which is which.
The core geometry package: plans, sections, grid, and elevations
This is the non-negotiable backbone. Without a coordinated set of these, the SE is guessing — and a guessing engineer either stops and waits or makes conservative assumptions you'll pay for in oversized members.
- Approved/frozen floor plans for every level, plus the roof plan — at a consistent, stated scale, with the level that's actually frozen clearly marked.
- A building section (ideally more than one) showing floor-to-floor heights, plenum/ceiling zones, and any level changes, splits, or mezzanines. The SE sizes members and checks clearances against these.
- The column grid and gridline dimensions — the shared coordinate language both disciplines will reference for the rest of the job. Lock this early; renumbering a grid mid-project is painful for everyone.
- Exterior and key interior elevations, so the SE understands parapet heights, cantilevers, large openings, and where lateral elements (braced frames, shear walls) can and can't go.
- Core and stair/elevator locations — these are prime candidates for the lateral system, so the SE needs them fixed, not floating.
The loading inputs: how the building will actually be used
Geometry tells the SE what to draw; loading tells them what it has to carry. This is where architects most often under-communicate, because the information lives in your head or in the program, not on the plan.
- Occupancy and use for each area, so the SE can assign the correct live loads. The governing building code (IBC and the locally adopted version) sets minimum live loads by occupancy — the SE applies them, but only if you've told them whether a space is office, assembly, storage, residential, or mechanical.
- Special, heavy, or non-standard loads called out explicitly: green/blue roofs and their saturated soil weight, pavers, planters, swimming pools, water features, libraries and high-density storage, heavy equipment, and any vehicular loading (loading docks, drive lanes, parking on structure, fire-truck access over a podium).
- Rooftop and mechanical equipment — units, screens, solar arrays, and their locations and approximate weights, so the SE can plan for point loads and equipment support before the framing is committed.
- Hung loads and future flexibility the client expects (heavy ceilings, monorails, anticipated tenant fit-outs), so capacity is designed in rather than discovered to be missing later.
The site and constraint inputs that change the whole foundation
Two more inputs determine whether the SE can design a foundation and a workable structure at all — and they're easy to forget because they don't live in your architectural model.
- The geotechnical report (or its status). The SE cannot finalize foundations — footing type, allowable bearing pressure, settlement, whether you're on spread footings, mats, or piles — without geotech recommendations. If the report isn't back yet, say so; the SE will start the superstructure and hold the foundation. Knowing it's pending is very different from assuming it exists.
- Architectural constraints stated as hard rules, not discovered later: "no column in this gallery," "this lobby must be column-free," "this opening can't be interrupted," required clear spans, and any transfer conditions where a column or wall above can't continue to the ground. Transfers (transfer beams or girders) are expensive and deep — the SE needs to know about them at kickoff so they can plan depth and coordinate it against your ceiling heights, not bolt it on after the fact.
- Known existing conditions for renovation/addition work: any record drawings, prior structural information, and which existing elements must remain. An SE walking into an adaptive-reuse project blind will assume the worst.
- The project phase and schedule (SD, DD, CD) and what level of structural deliverable you need at each gate, so their effort matches the design's maturity.
A simple handoff discipline that prevents the rework loop
Treat the structural kickoff as a transmittal with a status note, not a file dump. Send the package above with three things attached: (1) a clear statement of what is frozen versus in-progress, (2) the design phase and the date of the set, and (3) the open questions you already know about ("foundation pending geotech," "penthouse massing may grow," "client still deciding on the green roof"). This lets the SE triage — they'll lock the gravity system where the plan is solid and defer the volatile zones — instead of fully designing something you're about to change. The reverse is also true: when the architecture does move after handoff, send a clean, marked-up delta rather than a silently re-saved file, so the SE can see exactly what shifted and what it touches. Coordination friction between the two disciplines is almost never about competence; it's about ambiguity over which lines are load-bearing decisions and which are still sketches.
| Item to hand off | Why the SE needs it | Freeze before handoff? |
|---|---|---|
| Frozen floor plans (all levels) + roof plan | Defines bays, spans, and where structure can live | Yes — core geometry |
| Building section with floor-to-floor heights | Drives member sizing and clearance/plenum checks | Yes |
| Column grid + gridline dimensions | Shared coordinate language for both disciplines | Yes — lock early |
| Exterior & key interior elevations | Locates lateral elements, parapets, cantilevers, openings | Yes |
| Occupancy / use by area | Sets code-required live loads | Yes |
| Special & heavy loads (green roof, equipment, vehicles, pools) | Avoids undersized members and missed point loads | Yes — call out explicitly |
| Geotechnical report (or status) | Required to finalize foundation type and bearing | If pending, say so |
| Constraints & transfers (no-column zones, clear spans) | Lets SE plan transfers and depth at kickoff, not later | Yes — state as hard rules |
| Phase + set date + what's still in flux | Lets SE sequence frozen vs. volatile zones | Always include |
Frequently asked
Do the floor plans really have to be frozen before I send them to the structural engineer?
Not perfectly frozen, but stable in the zones that drive structure: bay sizes, the column grid, core and stair locations, and floor-to-floor heights. The SE can start off a near-final plan if you flag what's still moving. What causes rework is sending a plan you fully expect to change in a structurally significant way without saying so — the SE designs to it, then has to re-do work when it shifts.
What if the geotechnical report isn't back yet — can the structural engineer still start?
Yes. The SE can begin the superstructure (framing, the gravity and lateral systems) using the geometry and loads, and hold the foundation design until geotech recommendations arrive. The important thing is to tell them the report is pending rather than letting them assume one exists. Foundation type, allowable bearing, and settlement all depend on it, so foundations are the piece that genuinely waits.
Why do special loads like a green roof or rooftop equipment matter so much at kickoff?
Because they change member sizes and load paths from the start. A saturated green roof, pavers, mechanical units, solar arrays, or vehicular loading on structure add weight that standard occupancy live loads don't cover. If the SE learns about them after the framing is laid out, members may need to grow — which can affect depths, ceiling heights, and cost. Calling them out at handoff lets the capacity be designed in rather than retrofitted.
What's a transfer condition and why does the structural engineer need to know early?
A transfer happens when a column or wall above can't continue straight to the foundation — usually because the architecture wants a column-free space below (a lobby, a gallery, a parking level). The load is then carried by a transfer beam or girder, which is typically deep and expensive. The SE needs to know at kickoff so they can plan the member depth and coordinate it against your ceiling heights, instead of discovering it after the section is set.
Who on the architecture team should coordinate the structural kickoff?
Typically the project architect, who owns the coordinated set and understands which decisions are locked versus still in design. They assemble the geometry package, confirm occupancy and special loads with the team, check the geotech status, and frame the constraints — then run the handoff as a transmittal with a clear freeze status rather than a raw file drop.