When someone asks me what keeps a building standing, the short answer sounds almost trivial: every load needs a continuous path down to the foundation. The long answer is the whole discipline of structural engineering, but that central idea — load path — is the thread connecting every concept that actually matters in design: which loads need to be resisted, what it means for a structure to “fail,” and why ductility and redundancy matter as much as raw material strength.

Load Types: Dead, Live, and Seismic

Every structure is designed to resist a combination of loads of different natures. Dead loads are the structure’s own weight plus everything permanently attached to it: concrete, steel, finishes, fixed equipment. Live loads vary over time — people, furniture, occupancy use — and are estimated using code-specified values by occupancy type. Seismic loads, on the other hand, aren’t gravitational loads at all but inertial forces: when the ground moves during an earthquake, the structure’s mass generates horizontal forces proportional to its own mass and acceleration, and those lateral forces usually govern the design in high seismic hazard zones, which cover a large part of Colombian territory under the NSR-10 code.

The combination of these loads — not each one in isolation — is what a structural engineer actually designs to resist, using factored load combinations that reflect the probability of several critical loads occurring simultaneously.

Limit States: Serviceability and Strength

Modern structural design doesn’t just aim for a structure that “won’t collapse” — it aims for adequate behavior at two distinct levels:

  • Serviceability limit state: the structure must perform well under normal use conditions, without excessive deflections, uncomfortable vibrations, or cracking that compromises durability, even if an extreme event never occurs.
  • Strength (or ultimate) limit state: under extreme loads — a design-level earthquake, an exceptional live load — the structure must not collapse, although it’s allowed to sustain controlled damage.

This distinction matters because designing only for strength produces structures that may be safe against collapse but uncomfortable or short-lived day to day, and designing only for serviceability produces structures that fail brittlely under an extreme event.

Ductility and Redundancy: Why They Matter as Much as Strength

Two concepts separate a well-designed structure from a merely “strong” one:

Ductility is a structural element or system’s ability to deform significantly beyond its elastic limit before failing, dissipating energy in the process. In seismic zones, designing ductile details — for example, correct transverse-reinforcement confinement in reinforced-concrete columns — is what gives a structure the capacity to survive an earthquake beyond its design level without collapsing, even if it ends up visibly damaged.

Structural redundancy means having more than one possible load path. In a redundant system, if one element fails locally, the load can redistribute to neighboring elements instead of triggering a chain-reaction collapse. This was a central criterion in a real project I designed under NSR-10: the Teatrino, a semicircular reinforced-concrete amphitheater for roughly 450 people, where the curved geometry and column layout were explicitly conceived so no single element would be a single point of failure for the system.

From Code to Digital Model

Designing under NSR-10 and working as a BIM specialist taught me that these principles — load path, limit states, ductility, redundancy — don’t live only in the calculation, they live in the 3D model that coordinates structure, MEP, and architecture before the first cubic meter of concrete is poured. If you’re curious how these fundamentals translate into the specific requirements of Colombia’s building code, and what changed in its most recent revision, continue with the NSR-10 review and updates, the natural next step after understanding why a well-designed structure doesn’t fall.