Setting Up the Model
The structural analysis model in Revit is its own separate layer that lives inside the same file you've been modeling with. You don't export to get there. You toggle it on from the Analyze tab, and Revit builds a skeleton version of your geometry using analytical lines and points. The physical beams become lines running through their centroids. Columns do the same, though they sit at the grid intersection or the center of the cross section depending on how you placed them. Walls are just lines. Slabs turn into planar surfaces. This simplification is what makes the export to structural analysis software possible, and it's also where things break when you don't pay attention. Getting the analytical model right is the difference between a clean run and spending three hours debugging why your moments look wrong. The big issue nobody warns you about is that Revit does not always place analytical points where engineers expect them. I had a project last year where a heavy steel moment frame was returning null reactions at every base plate. Turned out the columns were offset from the grid by four inches to match the architectural layout, and the analytical model had snap-pointed to the grid line instead of the column center. The load path was floating in empty space. I ended up manually repositioning each analytical point with the Move Analytical Point tool and then running a reconnect to make sure the beam-to-column joints matched back up. Took about twenty minutes and saved me from sending garbage to RISA. You should check your analytical model before you export anything. Go to the Analyze tab, click Show/Hide Analytical Model, and walk through every level. Zoom in on connections. Make sure the analytical lines actually meet at nodes. If they're overlapping but not connected, Revit treats them as separate elements and your analysis will reflect that gap. It sounds obvious but I've seen it on models from firms that should know better.
Export Workflow
From the Analyze tab you have Export to Structure. That takes your analytical model and writes it out as a .rvt analysis file or sends it directly to ETABS, SAP2000, RISA-3D, or STAAD.Pro depending on what's installed. The export map matters more than people realize. You define it in Manage tab, Export Map. Each Revit structural element type maps to a specific analysis element type in your target software. A Revit Steel Column becomes a frame element in ETABS. A Revit Foundation becomes a solid element or a set of springs, depending on your mapping. Get this wrong and your boundary conditions are completely off. I use ETABS as my primary export target and my map looks like this: Structural Framing maps to Frame, Columns map to Frame, Foundations map to Springs with hardcoded stiffness values, and Braces map to Truss elements. The Truss mapping is important because braces in Revit carry axial force only by default, and if they export as Frame elements they'll introduce bending that doesn't exist in reality. That extra stiffness shows up in your drift calculations and makes the model look stiffer than the building actually is.
Load Combinations
Revit can generate load combinations if you set them up in the Loads tab. You define load cases, assign them to elements, and then combine them using codes like ASCE 7 or Eurocode. The combinations export to your analysis software along with the model. But here's the thing most people don't catch: Revit's combination engine is basic. It handles the standard dead plus live plus wind cases without issue. When you get into seismic or thermal or construction sequence combinations, it starts fumbling. I had a multi-story concrete building where the construction sequence loads were supposed to apply in stages, and Revit just applied everything at once because it doesn't support staged construction in its internal load engine. I exported the raw load cases and built the sequence combinations manually in ETABS instead. If you're doing simple residential or light commercial work, Revit's built-in combination tools are fine. For anything involving seismic design category D through F, or any structure where construction sequencing matters, export the individual load cases and handle the combinations in the analysis software. It takes about ten extra minutes and prevents you from getting a compliant report that's built on wrong load data.
Get the Full Details
Common Pitfalls
The most frequent problem I see is analytical model skew from complex geometries. Curved beams, skewed columns, non-orthogonal bracing, diagonal walls carrying structural load. Revit tries to simplify these into straight analytical lines and points, and the simplification introduces errors that are sometimes small and sometimes large enough to matter. I worked on a diagrid facade project where the analytical model straightened every diagonal member. The resulting frame was geometrically different from the physical model. Stresses came out wrong, especially at the joints where multiple diagonals met. I ended up extracting the diagrid as individual members in Tekla Structures and imported those into ETABS instead of relying on Revit's analytical export. Another issue is mesh quality when exporting slabs and walls. Revit exports slab analytical models as planar surfaces, which some analysis software will auto-mesh and others won't. If your software requires a finite element mesh and the exported surface has no subdivision, you get one giant element covering the whole floor. That's not usable for stress checking or deflection analysis. I usually subdivide the analytical slab surface in Revit before exporting, or I rebuild the mesh in the analysis software with a 4-foot element size to start. Material assignment during export is also worth watching. Revit maps materials based on your export settings, but if you've used a custom material override on a family, the export might pull the base material instead of the override. I lost an entire afternoon once because a set of steel beam families had their overridden to high-strength steel, but the export was reading the default steel definition. The yield strength in ETABS was wrong by about 30 percent. I fixed it by checking the exported material list against the Revit schedule before running any analysis.
When It Doesn't Work
Revit's structural analysis is not a full finite element solver. It doesn't do nonlinear analysis, buckling checks, or detailed connection design. If you need pushover analysis, time history, or soil-structure interaction, Revit won't give it to you. The analytical model is a preprocessor, not an analysis engine. For those cases you export to a dedicated structural analysis program and do the heavy lifting there. Even for linear static analysis, if your building has more than five stories or uses a structural system with significant P-Delta effects, I'd recommend exporting to ETABS or SAP2000 rather than relying on Revit's internal calculation tools. The results are comparable for simple cases but the reporting and verification tools in dedicated software are far more mature. Also worth noting: Revit's analytical model does not automatically update when you change the physical model. If you move a column, shorten a beam, or change a wall's structural role, you have to refresh the analytical model manually. Hit the Update Analytical Model button on the Analyze tab. If you skip this step and export an outdated analytical model, you're analyzing a building that no longer exists. I set a habit of updating the analytical model right before every export. Five seconds of work that has prevented at least three real mistakes for me.
