The Silent War Between Your Architect and Structural Engineer Is Costing You Lakhs

You finish a beautiful architectural design. Columns on a clean 6m × 7m grid, windows aligned to them, the staircase sitting perfectly between them. You issue it to the structural engineer. Three weeks later the structural drawing comes back and the columns have moved — a corner column now 2 metres in, your 7m bays now 6.5m and 7.5m, an exterior column relocated to the interior.

"The loads don't work with your spacing," the engineer says. "I've optimised the grid." "But my layout depends on those columns." "That's your problem. I've designed a safe structure." So you redesign for two weeks. A bedroom shrinks 100mm because a column is now in the wrong place. The staircase turns awkward. This plays out on almost every project — architect and engineer never actually work together, they work in sequence, and the building gets compromised in the handoff.

When Beam Depths Destroy Your Design

Same problem, different shape. You design 4-metre ceilings and specify finishes around them. The engineer calculates a 900mm-deep beam for your 10m span. You'd allowed 300mm for slab, 150mm for ducts, 250mm for false ceiling — and now a 900mm beam leaves only 600mm below the slab. The false ceiling won't fit. The ducts won't fit. The beam is exposed and the proportions are ruined. "Can you reduce the beam depth?" "Only if you reduce the span or the load." You can't do either — the span is set by your layout. So you drop the ceiling 400mm and the room feels 10% smaller, all because nobody coordinated before designing.

The Coordination Gap

Architects and engineers speak different languages. The architect thinks spatially — "this room needs to feel open." The engineer thinks structurally — "this floor carries X load over Y span." When the two collide, the architect usually gives, because the engineer can wave the flag of "safety" against mere "aesthetics."

But here is what most engineers don't say: there is almost always more than one structural solution. A 10m span can be a 900mm beam on a 6m × 7m grid, or a 700mm beam on a 5m × 6m grid, or a 1000mm beam on 8m × 8m. The engineer picks whichever is most comfortable for them — not whichever respects the architecture. A young engineer places columns where the maths happens to land. An experienced one places them where they work structurally and architecturally. The difference is a coordination meeting before the structural design even begins.

Who Changed My Design?

Three months into construction, the engineer calls: "Foundation problem — we need to move column C7 by 400mm." That column sits in a hallway. Now the corridor is misaligned, a door frame is crooked, and the column is already half-cast. It's flagged as a safety issue, so you have no choice. The building gets a permanently awkward hallway because a structural decision was made with zero architectural input. In a healthy project, every structural change triggers an architectural review and vice versa. In most projects, the architect finds out weeks too late.

Building a Real Working Relationship

The book lays out how good architects and engineers actually collaborate — and it's mostly about sequencing meetings before design, not firefighting during construction:

• Concept meetings before any design. A 30-minute conversation — "I want a 7m living-room span"; "I can do it with a 750mm beam along one edge, or a 700mm beam if we drop to a 6m column spacing" — replaces four weeks of back-and-forth redesign. Both sides make small compromises; both stay satisfied.
• A shared, locked column grid. Architect and engineer use one coordinate system and both sign off on the grid before design starts. The architect designs around it, the engineer designs for it, and there are no surprises.
• Regular sync meetings. Every two weeks they review progress and catch conflicts — a duct heading for a beam, a new wall affecting the structure — while they're still easy to solve.
• A change-control protocol. No silent changes. In a Mohali project, the engineer needed to shift the grid 300mm and emailed first: "This affects your layout at C5 and D7 — acceptable?" The architect replied: "C5 is fine; D7 moves a column into the stairwell — adjust E5 instead." The engineer could, and did. That is collaboration.

The Principle: Coordinate Before Final, Change-Control After

If the engineer wants to change a column, beam or slab, the architect approves it. If the architect wants to move a wall or opening, the engineer confirms the structural implication. Coordinated projects look intentional; uncoordinated ones look compromised — and the difference is entirely about time spent in meetings before construction rather than problem-solving during it. Most Indian architects treat coordination as extra work. Good ones treat it as core work.

How Secured Engineers Pvt. Ltd. Ends the War

The silent war is structural only because architecture, structure and MEPF sit in three different offices that meet once it's too late to change anything cheaply. At Secured Engineers Pvt. Ltd., these disciplines are one integrated team from concept. The column grid is agreed and locked together, beam depths and slab assumptions are coordinated before drawings are finalised, and every change runs through a single change-control loop — so ducts don't hit beams, ceilings don't collapse onto your proportions, and your building looks intentional, not improvised. That coordination is exactly where the lakhs are saved.

From the upcoming book by our founder — get notified at launch. Want your architecture, structure and MEP coordinated under one roof? Talk to our engineers.