On a large building project, structural engineering provides geometry that other disciplines need to work with: columns, beams, slabs and walls that mechanical, electrical, façade and fire teams may attach to or thread through. Coordination takes more than people communicating well. It requires a technical process with an agreed sequence, clear information and a way to resolve conflicting requirements before they reach site.
Structure is the reference geometry, not just another trade
Structural elements have constraints on where they can sit because they carry loads and resist movement. Ductwork and cladding brackets have constraints of their own, so the design team needs to establish where adjustment is possible rather than assume another discipline can move. Early structural decisions, including column grids, floor-to-floor heights and slab depths, provide reference points for developing the other systems. Those decisions need testing against the requirements of the whole project.
Structural input should therefore inform the concept while other disciplines are still developing their layouts. A grid that conflicts with the intended spaces, or slab zones that leave insufficient room for services, can create redesign work across several packages. Resolving those questions together helps the team avoid building separate designs around incompatible assumptions.
Why early involvement changes the whole project
Bring structural input into the concept stage, before the architectural layout is treated as fixed. Late changes to column positions or floor depths can affect ceiling voids, risers, façade brackets and fire compartmentation. Moving a column on paper is a different proposition from changing it after steel has been fabricated. The point is to test the arrangement while the team still has workable options.
Where architects and contractors lack the structural expertise a scheme needs, external input can help, particularly on projects that mix unusual spans, ground conditions, or heritage constraints. In those cases it’s worth bringing in specialist support for complex projects early enough that the structural scheme is actually shaping the design, rather than reacting to it. Geotechnical findings – borehole data, settlement tolerances, ground bearing capacity – need to feed into structural decisions at the same stage, not after foundation design is already fixed.
BIM only works if the model discipline is there
Clash detection tools can help teams review models together, but they don’t solve coordination on their own. Their usefulness depends on the information modelled and the revisions being compared. A structural model that is behind the current architectural layout might pass a particular check while missing a conflict in the live design. Agree which versions are under review and keep the shared Common Data Environment current.
Structural engineers need to issue clear, specific information: penetration allowances through beams and slabs, load capacities at particular grid points, deflection limits that affect partition and glazing tolerances. Without that data, MEP and façade teams are guessing, and guessing is exactly what BIM was supposed to eliminate.
Where coordination actually breaks down
The interface between structure and services deserves close attention. A duct route that calls for a large penetration through an already-cast transfer beam can create a difficult problem. The team needs a structural assessment of what, if anything, can be altered, rather than assuming core drilling will solve it. Resolving the route in the design model gives the disciplines a chance to compare options before site work restricts them.
The same logic applies to façade coordination. Cladding fixings need to work with the frame as built, so the teams should agree tolerances for frame position and movement. Communicate those allowances clearly enough that the façade design does not depend on the structure matching an idealised drawing without variation.
Fire engineering adds another interface. Ask the structural, services and fire teams to agree responsibility for checking structural fire resistance and the firestopping of penetrations. The coordinated drawings should make those details visible, so a service route is not approved without its effect on the fire strategy being considered.
Avoidable errors can turn into additional design work, material changes and delays. A coordination review should therefore identify the unresolved issue, the person responsible for resolving it and the decision needed next. General agreement that everyone will communicate is less useful than a specific action attached to a specific interface.
Formal mechanisms beat informal goodwill
Formal mechanisms give the team a way to work together: a design responsibility matrix that identifies package owners, sequenced coordination workshops and regular model reviews. Temporary works, including propping, falsework and excavation support, also need reviewing against the permanent structure and construction sequence. Ask the project advisers to confirm the applicable coordination duties and who will fulfil them, rather than assuming that naming a framework settles responsibility.
None of this replaces good communication. It gives good communication something concrete to act on – a shared model, clear numbers, and an agreed sequence for who needs what information and when.
