Lesson 10.2Lesson 10.2 · Codes, Practice & the Bigger Picture
The Architect's Role & the Team
A safe building in a hazardous place is an ensemble achievement - the architect conducts, the structural, geotechnical and fire engineers play, and resilience is won at the seams between them
The architect rarely does the structural calculation - but the architect decides, at the first sketch, how hard that calculation will be.
No one designs a resilient building alone. It is the work of a small team of specialists - a structural engineer, a geotechnical engineer, a fire engineer, and others - each holding knowledge the others lack, working within a concept the architect sets. The architect is rarely the deepest expert in any single hazard, and should never pretend to be. But the architect is uniquely placed to see the whole building, to convene the team, and to make the early decisions that determine how safe, and how affordable, the building can be made.
This lesson is about that collaboration: who is on the resilience team and what each member owns; why the architect's early, conceptual choices make everyone else's job possible or impossible; why engaging the specialists from the first sketch is the single most cost-effective resilience measure there is; and what it means to be a good client of knowledge you do not hold yourself. Coordination, it turns out, is not an administrative chore around the edges of design - it is where resilience is won or lost.
Architect = conductor, not soloist. Bring the engineers a sound concept, from the first sketch. Resilience lives at the seams.
Resilience is a team sport - who is on it
Resilience is never delivered by one person. A safe building in a hazardous place is the product of a small team of specialists, each holding knowledge the others do not, working to a shared concept. Knowing who is on that team - and what each of them carries - is the first step to coordinating them well.
The structural engineer is the architect's closest partner in resilience. They take the building's form and configuration and turn it into a system that can carry gravity, wind and earthquake forces safely to the ground - sizing members, choosing the lateral system, and specifying the reinforcement and detailing (to IS 1893, IS 875 and IS 13920) that let it survive a severe event. The geotechnical engineer investigates the ground: the soil profile, bearing capacity, the water table, and the site-specific dangers of liquefaction, settlement and slope instability that Modules 2 and 5 raised. Their report is the foundation - literally - of everything above. The fire engineer (or fire-safety consultant) owns the life-safety logic that Module 7 touched: escape routes, compartmentation, detection and suppression, and the fire that so often follows an earthquake.
Around these sit others whose decisions bear on resilience: the MEP / services engineer, whose pipes, tanks, generators and plant are the lifelines that must keep working or fail safely; the surveyor and, where needed, hydrologist who establish levels and flood data; the contractor and site supervisor, whose workmanship decides whether the engineered design is actually built; and the client, who sets the brief, the budget and the tolerance for risk.
At the centre of this group, and uniquely placed to see the whole, is the architect. The architect is rarely the deepest specialist in any one hazard - and should never pretend to be. But the architect is usually the one who holds the whole building in mind, convenes the others, and makes the early spatial and formal decisions within which every specialist then works. That central, coordinating position is the architect's real contribution to resilience: not doing the engineering, but making sure the right engineering happens, early, and fits together. A building fails at the interfaces - between structure and soil, between frame and fit-out, between design and construction - and it is the architect, more than anyone, who is positioned to watch those seams.
Structural, geotechnical, fire, services - each holds knowledge the others lack. The architect convenes them.
Who owns which decision
It helps enormously to be explicit about ownership, because confusion about who decides what is itself a source of risk. Decisions fall, roughly, into three baskets.
The architect owns the concept - and the concept sets the ceiling on how resilient and how affordable the building can be. Where it sits on the site, its plan shape and regularity, its height and massing, its weight, the basic structural idea, the continuity of the load path, and the spatial arrangement of escape and refuge - these are architectural decisions, made early, that the rest of the team then works within. An irregular, top-heavy, soft-storey concept on a bad part of the site cannot be rescued by brilliant engineering later; a simple, regular, well-sited concept makes every specialist's job easier and the building cheaper to make safe.
The specialist engineers own the binding technical decisions within that concept. The structural engineer owns the design forces, the member sizes, the lateral system and the reinforcement detailing. The geotechnical engineer owns the foundation type, the bearing and settlement checks, and the site-specific soil hazards. The fire engineer owns the egress calculations, fire ratings and suppression strategy. These are not areas where the architect should overrule the specialist on a hunch - they are the places where binding, code-compliant values live, and where a licensed professional carries the legal and ethical responsibility.
But the most important decisions are shared at the interface, and this is where coordination earns its keep. The position of a shear wall is a structural decision with enormous architectural consequence - and vice versa. The finished-floor level is a flood, a drainage, a structural and an access decision at once. The way a heavy stone facade is fixed back to the frame is structural, architectural and a non-structural-safety question together. Resilience is often won or lost not inside any one discipline but in the conversations between them - which is exactly why the architect's coordinating role matters so much.
The practical discipline is simple to state and hard to do: make ownership explicit, in writing, early. Agree who decides what, record the assumptions each discipline is relying on from the others, and revisit them as the design develops. Most coordination failures are not failures of competence but of communication - a value assumed by one party and changed by another, an interface nobody owned. Naming the owner of each decision is how a team stops those gaps from opening.
Engage from the first sketch - why early is everything
If there is one piece of practice advice that saves more buildings than any other, it is this: bring the engineers in at the first sketch, not after the design is fixed. The reason is a simple and well-known relationship that every experienced designer learns to respect - two curves that cross as a project matures.
Early in a project, at concept and schematic stage, your ability to influence the building's resilience is at its highest: siting, form, configuration, the structural system and the load path are all still fluid, and changing them costs almost nothing but thought. As the design develops, those decisions harden - drawings are detailed, the structural grid is set, approvals are sought - and the cost and difficulty of change climbs steeply. By the time a soft-storey problem or a dangerous irregularity is noticed on a detailed drawing, fixing it may mean redesigning the whole building; noticed on site, it may be impossible. The two curves cross early, and the lesson is unmistakable: the decisions that matter most for resilience are made when it is cheapest to get them right.
This is why engaging the structural and geotechnical engineers at concept stage is not a luxury or an added cost - it is the single most cost-effective resilience measure available. A structural engineer glancing at a concept sketch can flag a soft storey, a plan irregularity or a heavy, badly distributed mass in minutes, while it is still just lines on paper. A geotechnical engineer consulted before the site plan is fixed can steer the building away from the worst ground, or call for the investigation that changes the foundation strategy. A fire engineer involved early shapes the cores and escape routes that are almost impossible to retrofit. Called in late, every one of these specialists is reduced to damage control - making the best of a concept that has already locked in its vulnerabilities.
There is a cultural dimension here too. Treating the engineer as a late-stage checker who 'makes the architecture stand up' wastes their most valuable contribution and breeds the adversarial relationship that produces unsafe compromises. Treating them as a design partner from day one - sketching together, testing structural ideas against architectural ones - produces buildings that are both better and safer, because resilience was designed in rather than bolted on. Early engagement is not just good risk management; it is good design practice.
Two curves cross early: influence high and cheap at concept, change costly later. Engage the team at the first sketch.
Being a good client of specialist knowledge
Coordinating specialists well is a skill in its own right, and it rests on an attitude: being a good client of knowledge you do not yourself hold. The architect who coordinates resilience best is not the one who knows the most structural engineering, but the one who asks the best questions, listens to the answers, and creates the conditions in which specialists can do their best work.
Several habits mark the good client. Brief clearly and early: tell the engineers what the building must do, the hazards it faces, the client's tolerance for risk and disruption, and the importance of the building (a hospital that must stay operational is a different brief from a warehouse). Ask, do not assume: when you do not understand why the engineer wants a wall here or a deeper foundation there, ask - the explanation almost always contains a resilience principle you can carry forward. Surface the interfaces: actively raise the seams between disciplines - how the facade fixes back, where the services penetrate, how the fit-out attaches - because these are where coordination fails. Respect the specialist's domain: push back and debate, but do not overrule a licensed engineer on a binding safety matter to save cost or preserve a detail; that is how fatal compromises are made, and the responsibility is not yours to carry alone.
Equally, being a good client means not abdicating either. 'The engineer will handle it' is not a resilience strategy if the concept you hand them is already compromised. The architect who shrugs off structure as someone else's problem tends to produce exactly the irregular, soft-storey, badly sited concepts that no engineer can fully fix. The principle-literacy this whole course builds is what lets you be a genuine partner - to understand enough to brief well, to recognise when something is wrong, and to know which questions to ask - without pretending to a competence you do not have.
Think of the architect as the conductor of a small orchestra of specialists. The conductor plays no instrument during the performance, yet the music depends entirely on them: on choosing the players, setting the tempo early, keeping everyone in time, and listening for where the parts must fit together. Resilience, in the end, is an ensemble achievement. The architect's job is to make sure the whole team can do theirs - and that begins with humility, communication and the respect that treats specialist knowledge as something to be drawn out, not overridden.
Professional responsibility (licensed engineer)
Binding structural, geotechnical and fire-safety design
These are the legal province of the licensed specialist applying the current code - not the architect. Engage them early and defer binding values to them.
IS 1893 / IS 875 / IS 13920 (via the structural engineer)
Seismic, wind and ductile-detailing design the engineer works to
The architect coordinates to these; the values and checks are the engineer's. Verify the current editions for your project.
Geotechnical investigation report
Soil, bearing, foundation and site-specific hazards
A site-specific investigation by the geotechnical engineer - never assumed. It underpins every decision above ground.
Workshop - a coordination plan for one project
Good coordination is planned, not hoped for. In this workshop you will take a project (real or imagined) and draw up a simple plan for who is on the team, who owns which decision, and when each specialist is engaged - the document that turns good intentions into resilient practice.
A project brief (real or imagined), this lesson, and a notebook. The skill is coordination, not calculation.
Goal: a one-page team-and-coordination plan for one project Inputs: a project brief (real or imagined) with a known hazard context, this lesson Time: ~45 minutes
- 1List the TEAM for this project: the specialists you would engage (structural, geotechnical, fire, MEP, surveyor as needed) and, for each, the one-line reason they are essential given this building's hazards and type.
- 2Draw an OWNERSHIP table: list the key resilience decisions (siting, configuration, structural system, foundation, load path, egress, finished-floor level, facade fixing) and mark each as owned by the architect, the engineer, or shared at the interface.
- 3Mark the ENGAGEMENT timing: against each specialist, write the project stage at which you would first involve them - and challenge yourself to move each one earlier, to concept stage, noting what they could catch there.
- 4Identify three INTERFACES - seams between disciplines (for example structure-and-soil, frame-and-fit-out, design-and-construction) - where coordination is most likely to fail on this project, and note how you would actively manage each.
- 5Write a one-paragraph BRIEF to your structural engineer for the concept review: the hazards, the building's importance, the client's tolerance for disruption, and the specific questions you want them to answer while the design is still just lines.
You’ll walk away with
A one-page coordination plan: the team and why, an ownership table, engagement timing, three watched interfaces, and a concept-stage brief to the engineer - a reusable template for starting any project on a resilient footing.
Three altitudes on the same idea
Read the band that fits you — or all three.
This lesson is about the heart of your professional role. You are the conductor of the resilience team - rarely the deepest specialist, always the one who holds the whole building in view, convenes the engineers, and makes the early concept decisions within which they work. Own the concept (siting, configuration, weight, load path) that sets the ceiling on resilience; engage the structural, geotechnical and fire engineers from the first sketch; make decision-ownership explicit in writing; watch the interfaces where disciplines meet; and be a good client of specialist knowledge - asking, listening, respecting the domain, and never overruling a safety judgement or abdicating the concept.
You are part of the team too, and your interfaces with the structure matter. How fit-out, partitions, heavy units, ceilings and cladding attach to the building is a resilience question that sits between your work and the structural engineer's (Module 7). Bring yourself into the coordination rather than working in isolation at the end: agree fixings and details with the structural engineer where they interact with the building, raise your interfaces actively, and treat the engineer as a partner whose knowledge keeps your beautiful interior from becoming a hazard in a shake. Being a good client of specialist knowledge applies to you as much as to the architect.
Learn the collaboration now, because it is how real buildings are actually made safe. You are not expected to be a structural, geotechnical or fire engineer - you are expected to understand enough to coordinate them well: to know who owns which decision, to recognise an interface, to grasp why engaging them early is the cheapest resilience there is, and to practise being a good client of knowledge you do not hold. The principle-literacy this course builds is exactly what lets you do that without a second degree. Start the habit now - in studio, bring 'structural thinking' into your concept, and imagine the engineer you would ask.
“Resilience is the structural engineer's job - the architect designs the building and then hands it over to be 'made to stand up'.”
Do it yourself
Reason it through from the team's point of view.
- 1Name the three core engineers on a resilience team and say, in one line each, what each one owns.
- 2Give two examples of a decision that is 'shared at the interface', and explain why neither discipline can own it alone.
- 3Explain the two crossing curves - ability to influence and cost of change - and what they imply about when to engage engineers.
- 4What does it mean to be a 'good client' of specialist knowledge? List three habits.
- 5Why is 'the engineer will handle the structure' a dangerous attitude for an architect to hold at concept stage?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01The discipline of structural engineering — Wikipedia - Structural engineering, 2026.
- 02Geotechnical engineering and the ground — Wikipedia - Geotechnical engineering, 2026.
- 03Fire protection and life safety — Wikipedia - Fire protection, 2026.
- 04Architecture and the coordinating role — Wikipedia - Architecture, 2026.
We have mapped the codes and the team that applies them. But the codes rest on a historical record that is quietly shifting - so next we ask how to design for a changing climate and a future that may not resemble the past.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →