A structural design is only as dependable as the information behind it. Before analysis starts, the team should be able to state the intended use of the building, its geometry, the materials, the codes being applied and the loads it is expected to carry. If any of those is still open, the design is provisional, and the drawings should say so.

Structural design is also a systems problem. Gravity and lateral loads travel through slabs, beams, columns, bracing, joints and foundations to the ground, and a change to one element rarely stays local.

Write the design basis down

The design basis is a short record of the use, geometry, material grades, load assumptions, applicable standards and any special equipment. It lets a reviewer, a contractor and the next engineer see what the design was meant to achieve. Where the brief is incomplete, list which conclusions depend on the missing inputs. A hidden assumption cannot be checked by anyone.

Typical inputs include imposed loads for the occupancy, wind and seismic parameters for the site, soil data for the foundation, and any heavy equipment such as water tanks, generators or rooftop plant.

  • Intended use and any unusual loads, including future extensions.
  • Standards and project criteria in force, with their editions.
  • What is known about the ground and what is still assumed.

Follow the load path, not just member sizes

Checking beams and columns one by one can still miss how a building behaves as a whole. Trace each load from where it is applied to where it reaches the ground, and look at the joints and foundations on the way. A new opening in a slab, for example, can push load into a neighbouring beam that was never sized for it.

Changes to openings, material grades, equipment positions or support locations can alter the load path, which is why analysis and drawings both need to be revisited when they happen.

Before drawings go to site

Compare the calculations with the drawings that will actually be used. A calculation that relies on a restraint or connection the drawing does not show leaves a gap between what was analysed and what gets built.

  • Member marks, details and foundation reactions agree across the package.
  • Revision and issue status are clear, so sketches are not mistaken for construction drawings.
  • Review comments and the responses to them are kept together.