Architects - How to Make Your Scheme Easier to Engineer

Every architect has had the phone call. It's usually a few weeks after the structural engineer received the latest set of drawings, and it starts with some version of: "So, about that cantilever…"

A scheme that's hard to engineer isn't necessarily a bad scheme. But it often becomes a slower, more expensive, and more compromised one — because problems that could have been solved with a pencil at concept stage end up being solved with steel, money, and goodwill much later on. The good news is that most of what makes a building easy to engineer is also what makes it easy to build, easy to cost, and often easier to love. Structural logic and architectural clarity tend to walk hand in hand.

Here's how to keep them walking together.

1. Start with a Regular Grid if possible

A consistent structural grid is the single biggest gift you can give your engineer — and, by extension, your budget and programme.

Regular column spacing, repeated bay sizes, and predictable spans allow the structure to be rationalised: the same beam sizes, the same connection details, the same slab depths, repeated across the building. That repetition isn't just tidy — it saves money on fabrication, speeds up approvals, and gives contractors confidence when pricing.

Irregular grids aren't forbidden, but they should be a deliberate design decision, not an accident of room-by-room planning. If your plan genuinely needs a shifted column or a widened bay for a specific reason — an open lobby, a stairwell, a big-span space — that's fine of course. What causes pain is when every floor has slightly different geometry with no organising logic behind it, forcing the engineer to design a bespoke structure for what looks, on the outside, like an ordinary building.

Rule of thumb: if you can sketch your grid on a napkin and it still makes sense, your structural engineer will thank you.

2. Align Your Loadbearing Elements — Vertically

This sounds obvious, but it's the single most common source of late-stage structural headaches: columns, walls, and cores that don't line up from floor to floor.

Loads want to travel straight down. Every time a column shifts position between levels, that load has to be picked up by a transfer beam or transfer slab — extra structure, extra depth, extra cost, and often a coordination problem with services and ceiling heights below. A single transfer condition might be unavoidable and justified. A building full of them is a building where the structure is fighting the architecture on every floor.

Before you finalise floor plans, overlay them and check whether columns line up from the top floor to the foundations and whether loadbearing walls sit on walls or beams below. Where you do need an offset, is there a clear, generous structural zone to accommodate it?

Vertical alignment is not always obvious at plan view, and is invisible in a rendered image but immediately visible in a section. However, we find that sections are not always considered or produced at feasibility or even at Planning Approval stage — which is why it often gets missed.

3. Bring the Structural Engineer in Early — Really Early

Not at planning submission. Not after the client has fallen in love with a specific massing. At concept.

Early structural input isn't about letting the engineer design the building — it's about getting a sense-check on the big moves before they calcify: the grid, the core position, the primary spans, the transfer conditions, the foundation strategy on a difficult site. A good structural engineer at this stage will flag the moves that are expensive or awkward while they still cost nothing to change — a pencil line on a sketch rather than a redesign of a floor that's already been through three rounds of client sign-off.

This also builds trust. An engineer who's been in the room since day one understands the design intent and will work to protect it, rather than encountering an unfamiliar scheme cold and defaulting to the most conservative structural solution.

4. Avoid Late Structural Changes

Structural changes get exponentially more expensive the later they happen — not just in engineering fees, but in the knock-on redesign of services, cladding, fire strategy, and cost plans that were coordinated around the original structure.

A few habits reduce the risk of late surprises:

• Freeze the grid before you freeze the finishes. Don't let interior design decisions — a moved partition, a bigger kitchen island — creep into structural zones without checking.

• Flag "wish list" moves early, even ones you're not sure about. A cantilevered corner or a column-free room is far easier to accommodate if it's discussed as an option at concept stage than if it's requested after the structural scheme is issued for tender.

• Treat structural drawings as live, not final, until they're actually final. A quick email — "does this still work if we move the stair half a metre?" — is far cheaper than finding out after issue.

  
  

Late changes are rarely caused by bad decisions. They're usually caused by good decisions made too late.

5. Coordination in Practice

A few real-world examples of the kind of coordination that separates an easy scheme from a difficult one:

• Service zones and structural zones overlapping. A beam that drops exactly where the mechanical duct needs to run isn't a structural failure or a services failure individually — it's a coordination failure. Cross-check structural depths against services zones early, floor by floor, not just in a typical bay.

• Stair and lift cores not lining up between levels. Cores are often the primary lateral stability system in a building. If a core shifts in plan between floors to suit a layout change, you're not just moving a stair — you're redesigning how the building resists wind and seismic load.

• Glazing and cladding grids fighting the structural grid. A curtain wall mullion pattern that doesn't relate to the column spacing behind it often means extra secondary steel just to give the facade something sensible to fix to.

• Cantilevers and setbacks treated as afterthoughts. A dramatic overhang can be entirely achievable — but it needs to be sized and resolved with the engineer from the outset, not squeezed in after the internal layout is fixed.

None of these are really "structural" problems in isolation. They're coordination problems that show up in the structural drawings first.

Practical Checklist

Before issuing a scheme for structural design development, it's worth running through a short list:

1. Is there a consistent structural grid, with any exceptions clearly justified?

2. Do columns and loadbearing walls align vertically through all levels, foundations included?

3. Has the structural engineer reviewed the scheme at concept stage, not just at detailed design?

4. Are transfer conditions minimised, and where unavoidable, given generous structural depth?

5. Have service zones been checked against structural zones, floor by floor?

6. Do cores align through the building and provide clear lateral stability?

7. Does the cladding or facade grid relate sensibly to the structural grid behind it?

8. Are any cantilevers, long spans, or unusual geometries flagged and discussed early, with the engineer's input?

9. Is there a process for structural sign-off before interior layouts are locked in?

10. Is everyone — architect, engineer, services consultant — working from the same current set of drawings?

    
    

The Bigger Picture

None of this is about making architecture more conservative. Some of the most exciting buildings ever built have complex, unconventional structures — but they were resolved that way deliberately, with the structural engineer as a collaborator from the earliest sketches, not a service provider brought in to make sense of decisions already taken.

A scheme that's easy to engineer isn't a compromise on ambition. It's simply one where the structural logic and the architectural intent were developed together — which, more often than not, produces a better building, delivered with fewer surprises, for less money, in less time.

That's not a lesser outcome. It's usually the better one.