Vulnerability & Risk Assessment

Start by facing the scale of it. In most Indian cities, the overwhelming majority of buildings predate the seismic provisions now in force, or were built informally with no engineering input at all. Codes only bind new construction; they do not reach back and fix the millions of homes, shops, schools and clinics already standing. So the population of buildings that will actually be loaded by the next hazard is dominated by old, often vulnerable stock - and that is where most of the casualties in past disasters have occurred.

This reframes the resilience problem. Designing a good new building is necessary but nowhere near sufficient; if we care about saving lives at the scale of a city or a district, we have to deal with what is already there. And we cannot deal with all of it. The number of potentially vulnerable buildings vastly exceeds the number of engineers, rupees and years available to assess and strengthen them. Any honest programme therefore has to be a triage: a way of sorting a huge, undifferentiated stock into those that are probably fine, those that need a closer look, and those that are dangerous enough to act on now.

Triage is a medical word on purpose. In a mass-casualty situation you do not treat patients in the order they arrive or spend your best surgeon on someone beyond saving; you sort quickly by severity and treatable-ness, and direct scarce resources where they do the most good. Building assessment works the same way. A cheap, fast screen looks at many buildings and sends most of them away; a more expensive engineering evaluation is spent only on those the screen flags; and strengthening money goes first to the buildings that are both most dangerous and most important - the school full of children, the hospital that must keep working, the crowded soft-storey block. The architect's habit of reading a building - its configuration, age, alterations and condition - is genuinely useful at the front of this funnel, where judgement and speed matter more than calculation.

The first, widest pass is rapid visual screening (RVS) - sometimes called a sidewalk survey because much of it can be done from the street without entering the building. The idea is to look at very many buildings quickly and cheaply, recording a handful of vulnerability-relevant attributes, and to come out with a simple score or flag that says either 'probably acceptable' or 'needs a detailed look'. It is deliberately crude. RVS does not decide that a building is safe or unsafe; it decides only whether a building earns the cost of a proper engineering evaluation. Its job is to be fast and to err on the side of caution.

What does a screener look at? The attributes that the earlier modules taught you to distrust. The structural system and material - is it unreinforced masonry, a non-ductile concrete frame, confined masonry, timber? The configuration - is the plan irregular, is there a visible soft storey (an open, column-only ground floor under heavier floors), a heavy top, pounding risk from a neighbour built hard against it? The apparent age and code era - was it likely built before modern seismic detailing? The condition - obvious cracking, corrosion, tilt, water damage, deterioration. The site - steep slope, visibly made-up ground, flood exposure. And crude measures of consequence - occupancy and importance, because a crowded school matters more than an empty shed. These combine, in standardised schemes, into a score; above a threshold the building is referred on.

Two cautions matter. First, RVS is a screen, not a verdict - its output is a triage flag, and any programme that treats a screening score as a safety certificate is misusing it. Second, it is only as good as the screener's eye and the honesty of what can be seen from outside; hidden additions, altered load paths and poor-quality concrete do not announce themselves from the pavement. Used properly, though, RVS is a powerful way to turn an unmanageable stock into a ranked shortlist - and it is exactly the kind of structured seeing an architect can be trained to do well, as the eyes and early filter of the engineering team.

Buildings that the screen flags move to detailed evaluation, and here the work passes firmly into the hands of a qualified structural engineer. Where RVS was eyes-on-the-street and minutes-per-building, detailed evaluation is drawings, access, measurement, testing and analysis - days or weeks per building - and it is the stage that actually judges whether a building is adequate for the demands the hazard will place on it, and if not, by how much it falls short.

The engineer typically works in tiers of increasing rigour. A first analytical tier might check the building against simple criteria and approximate demand-capacity comparisons; if the result is clearly adequate or clearly deficient, that may be enough to decide. If the building sits in the uncertain middle, the engineer moves to more detailed methods - gathering as-built information, opening up elements to see reinforcement and connections, testing material strengths, and modelling how the structure would respond to the design hazard. The output is not a pass/fail sticker but an informed assessment: which elements are deficient, what the likely failure mode is, how the load path breaks down, and what it would take to bring the building to an acceptable level of safety. That assessment is what makes a sensible retrofit possible, because you cannot strengthen intelligently what you have not diagnosed.

This is also where the principle-first boundary of this course is sharpest. The methods, acceptance criteria, material tests and the design hazard all come from the current codes and the engineer's professional judgement for the specific building and site - never from an architect reading a checklist. In India the seismic demand framework lives in IS 1893 and ductile-detailing expectations in IS 13920, with guidance on the assessment and retrofit of existing buildings issued separately; the relevant documents and their current versions are the engineer's to apply. What an architect should take from this section is humility and fluency: understand what a detailed evaluation is for, what information it needs, and how its findings will shape any intervention - so you can commission it well, supply the drawings and access it requires, and read its conclusions without either over-reading a screening flag or dismissing a real deficiency.

Screening and evaluation produce information; prioritisation turns it into action. Because no city can retrofit everything at once, the central question is order: which buildings get strengthened first? The answer combines two axes that you can hold in your head as a simple grid - how dangerous a building is (its vulnerability and likely failure mode) and how much its failure would cost in lives and function (its occupancy, its importance, whether it is a lifeline the community needs after the event). A lightly occupied, moderately weak shed ranks low. A crowded, brittle school or a hospital that must keep working after the earthquake, with a clear vulnerability, ranks at the very top.

This is why certain building types are assessed and strengthened ahead of others the world over: schools, because they concentrate children; hospitals and emergency facilities, because they must function precisely when the hazard has struck; and dense residential blocks with soft storeys or unreinforced masonry, because they combine high vulnerability with high occupancy. Module 8 argued for treating these as special cases in design; here the same logic drives the order of a retrofit programme. Good prioritisation also weighs feasibility and cost - a cheap, high-impact fix to a very dangerous building may rightly jump ahead of an expensive fix to a less critical one - and it is revisited as money and knowledge change.

Where does the architect add value in all this? Rarely as the signing assessor - that is the engineer - but often as the first eyes, the coordinator and the translator. You can be trained to run or supervise rapid visual screening competently, because reading configuration, age, alteration and condition is close to what you already do. You can assemble the as-built drawings, history of alterations and occupancy information the engineer needs, and arrange access. You can help an owner or an authority understand a technical assessment and its priority, and frame the retrofit that follows as an architectural project, not just a structural patch. And you can brief the specialist sharply - here is the building, here is what worries me, here is who uses it - so that the scarce engineering effort lands on the buildings that most deserve it. That briefing role, done well, is how an architect helps a whole stock get safer, not just one new building.