Most structural students meet ETABS the same way. A project deadline arrives, someone passes down a model file from the year above, the grid and section sizes get edited, forces come out, and the numbers go into the report. The project passes. Then at the first interview the question comes — "did you assign a rigid diaphragm, and why?" — and there is no answer.
This article sets out a different route: learning ETABS from scratch in eight weeks, using your own project as the exercise, but in the order a practising engineer works. It also lists the concepts to secure before opening the software, the modelling errors our lecturers see most often when marking student models, and what to learn after ETABS.
ETABS in coursework and ETABS in a design office
The same software, used so differently that students who are good at it in university still have to relearn it at work.
| ETABS in coursework | ETABS in a design office | |
|---|---|---|
| Purpose | Forces to size reinforcement and write the report | A design package that survives review and can be built from |
| Analytical model | Usually given, or inherited | The engineer decides: frame or frame-wall, rigid diaphragm or not, fixed base or springs |
| Loading | A few basic cases, combinations from an example | Dead, live, static and dynamic wind, seismic; combinations to the current code |
| Checking results | Rarely; the software is trusted | Mandatory: modes, storey drift, total reactions, hand checks |
| Deliverable | A table of forces | A clean model, an assumptions sheet, check reports, data for SAFE and the drawings |
| Time on modelling | A day or two | Days to weeks, revised as the architecture changes |
The biggest gap is the checking row. In an office, ETABS results are not trusted until the engineer can show they are reasonable. That is the skill the path below spends the most time on.
Concepts to secure before opening the software
ETABS does not replace structural mechanics; it computes very fast from the assumptions you feed it. Before week one, check that you can explain the following. If not, spend a week revising — it is the week that saves the most time later.
- Analytical models and supports: fixed, pinned, roller; when a column base is fixed and when the foundation is better modelled with springs.
- Structural systems for multi-storey buildings: frames, walls, cores, combined systems; where lateral load goes and how it reaches the foundations.
- The rigid diaphragm: why the assumption is reasonable for ordinary concrete slabs, and when it is not, such as slabs with large openings or long thin slabs.
- Loads and combinations: dead, live, partial factors, basic and special combinations under Vietnamese codes.
- Dynamics: periods, mode shapes, participating mass; why you look at the first mode before trusting any number.
- Stiffness and cracking: second moment of area, and how cracking changes deflections and force distribution.
- Reading force diagrams: the shape of bending and shear diagrams for continuous beams and frames under lateral load, so that a wrong result looks wrong.
Third-year students have covered all of this. The problem is rarely that the theory is missing; it is that the theory has not been connected to the buttons. The path below makes that connection, and it is also how the Institute's ETABS – SAFE – SAP2000 course is organised: each session ties one structural concept to one concrete operation on the model.
An eight-week path using your own project
The path assumes eight to ten hours a week and a multi-storey building project to work on. Each week ends in something checkable.
| Week | What you learn | End-of-week deliverable |
|---|---|---|
| 1 | Interface, units, grids and levels; materials and sections; framing the columns, beams and slabs of your project | Geometry model at the right dimensions, verified against plan and section |
| 2 | Walls, cores, edge beams, slabs; rigid diaphragms; column base restraints; slab meshing | Complete model, floor mass comparable with a hand calculation |
| 3 | Dead and live load to code; wall loads; mass source | A load table with traceable origins; total vertical reaction within a few per cent of hand calculation |
| 4 | Modal analysis: periods, mode shapes, participating mass; fixing the model until the behaviour makes sense | A one-page modal report explaining the first three modes |
| 5 | Static and dynamic wind, seismic action to Vietnamese codes; load combinations | Fully loaded model; roof displacement and storey drift checked |
| 6 | Reading and checking forces: beams, columns, walls; comparing against a hand-calculated plane frame | Cross-checked force tables; at least one error of your own found and fixed |
| 7 | Member design: beam, column and wall reinforcement; exporting results for the report | Preliminary reinforcement schedule, verified against one hand-designed beam and column |
| 8 | Exporting loads to SAFE for slabs and foundations; presenting the model, assumptions and defence pack | A model package: clean file, assumptions sheet, check report |
Three rules go with the path.
Weeks two to four cannot be shortened. This is what separates someone who understands the model from someone who presses buttons. Students routinely jump from week one to week seven because the project only needs forces, and that is exactly why they relearn it at work.
Every total gets a hand check. Total vertical load, floor mass, an approximate period, the moment in one beam. Fifteen minutes by hand, then compare. More than a few per cent apart means an error, and the error is in the model more often than in the hand calculation.
Keep an assumptions sheet. Write down everything you chose: diaphragm or not, stiffness modifiers, base restraint, mass source. That sheet is what you take to your project defence and to your interview.
Modelling errors students make most
Drawn from what our lecturers see most often when marking student models.
No rigid diaphragm, or one assigned without understanding. Without it, lateral load distributes to the frames incorrectly and nodes on one floor move independently. Assign it to a slab with a large stair opening, or a very thin slab, and the model becomes too stiff instead. "Did you assign a diaphragm, and why?" is a classic interview question because the answer reveals the depth of understanding immediately.
A fixed base by default, without thinking. For pile caps and large strip footings, fixed is often acceptable. For pad footings on soft ground it is not. At minimum you should know which assumption you are making.
Mass source forgotten or wrong. Modal behaviour and seismic load depend on mass; omit the wall loads or take the wrong live-load participation factor and every period is wrong from that point on.
A torsional first mode, ignored. That is a sign the model or the structural scheme has a problem, such as eccentric walls or an off-centre core. Students often never open the modal table, or open it without knowing what to look for.
Slab mesh too coarse or too fine. Too coarse and load transfers to the beams incorrectly. Too fine and the model runs for hours without changing the answer.
Sections and materials declared one way, designed another. The model uses one concrete grade and the report another; columns change section up the building but the model carries one section throughout.
Total reactions never checked. The cheapest check there is, and the least performed: total vertical reaction must equal the hand-calculated total load. A discrepancy means a load is missing or misapplied.
Trusting the result because the software produced it. The software computes exactly what you declared. ETABS, SAP2000 and SAFE compared describes a small experiment where the same frame gave forces more than ten per cent apart because of a few default settings.
How long it takes, and what comes next
For a student whose theory is solid, eight weeks along this path, or a taught course with someone correcting the model, reaches the level of building, analysing and checking a model of an ordinary multi-storey building. That is enough to defend a project with confidence and to pass an entry-level structural test. Designing a real high-rise takes another year or two in an office alongside a lead engineer.
After ETABS, the order our lecturers recommend:
- SAFE — immediately after, because slabs and foundations are where ETABS stops; every building design office uses the pair.
- SAP2000 — for structures outside the building envelope and for a deeper grasp of analytical models; moving across from ETABS takes a few sessions. The Institute's SAP2000 course suits anyone heading towards industrial, steel or infrastructure work.
- Revit Structure — to turn the design into a model and drawings, which the larger design offices now require. See Revit Architecture, Structure or MEP?.
- Tekla Structures — if you are heading into structural steel, pre-engineered buildings or precast concrete.
As for AutoCAD: if you are not yet fluent, learn it alongside from the start, because structural drawings are still produced and exchanged in CAD at most firms. Which software should a new civil engineer learn? sets out the full order by job role.
Frequently asked questions
What year should a student start with ETABS?
Third year, after structural mechanics and reinforced concrete, and before the major concrete project. Earlier and the foundation is missing; later and the final-year project gets rushed.
Do I need SAP2000 before ETABS?
No. For multi-storey buildings, going straight to ETABS is more efficient. SAP2000 comes later if needed, and roughly two thirds of the knowledge transfers.
How powerful a computer does ETABS need?
A coursework model runs comfortably on an ordinary laptop with 8 to 16 GB of memory. Real high-rise models with fine meshes and dynamic analysis need more, but that is the office's problem, not the student's.
Does learning ETABS online work?
Yes, provided the instructor can see your model and correct it directly. The hard part of ETABS is spotting modelling errors, and that needs experienced eyes on your actual file, not a video.