The big idea: Pre-event management is everything a place does before a geophysical hazard strikes to lower human vulnerability — the risk of death, injury and damage.
You cannot stop an earthquake or eruption. But you can predict it, warn and evacuate people, plan where they build, and design buildings to survive — so the same hazard kills far fewer people in a prepared place than an unprepared one.
Vulnerability = how exposed and unable to cope a population is. Pre-event strategies attack vulnerability, not the hazard itself.
The four families of pre-event strategy
- Prediction & monitoring — instruments (seismometers, GPS, gas sensors) watch for warning signs of an eruption or quake.
- Warning & evacuation — sirens, phone alerts, drills and evacuation routes move people out of the danger zone in time.
- Land-use zoning — mapping the hazard, then banning or limiting building in the most exposed zones.
- Resilient building design — hazard-proof construction: cross-braced frames, lava-diversion walls, slope gabions and netting.
Before vs after the event: Pre-event = prediction, warning, zoning, resilient design (this micro).
Post-event = the emergency response and recovery after the hazard hits (the next micro). The exam usually asks about the pre-event stage — the cheaper, life-saving 'prepare' side.
How this is tested: Paper 1 Option D asks you to Explain how a named strategy lowers vulnerability — sometimes one strategy for [3], often two strategies marked 3 + 3 for [6]. You name the strategy, then give a chain of how it cuts deaths or damage, with an example.
Every strategy has a strength and a limit — knowing both is what powers the [10] essay later.
| Strategy | What it does | Strength | Limit | Real example |
|---|---|---|---|---|
| Prediction & monitoring | Instruments (seismometers, GPS, gas sensors) watch for warning signs | Can give days of notice for an eruption | Earthquakes still cannot be predicted reliably | GPS + gas monitoring at Etna detects magma rising |
| Warning & evacuation | Sirens, apps and drills move people out of the danger zone in time | Saves lives even when property is lost | Useless if the warning is late, ignored or unreachable | Japan's earthquake early-warning gave Tohoku (2011) seconds' notice |
| Land-use zoning | Bans or limits building in the most exposed zones (low coast, lahar paths) | Cheap and permanent once mapped | Hard to enforce where land is scarce or poverty forces people in | Lahar hazard maps after Nevado del Ruiz (1985, ~23,000 deaths) |
| Resilient building design | Hazard-proof construction (cross-bracing, lava walls, slope gabions) | Buildings stay standing and shelter people | Expensive, so poorer places cannot afford it | Cross-braced design kept Chile 2010 losses far below Haiti 2010 |
Answering an 'Explain how a strategy reduces vulnerability'
- Name the strategy (e.g. land-use zoning).
- Give the mechanism — the chain (maps the lahar path → bans building there → fewer people exposed).
- Link to lower vulnerability (so fewer people are killed or made homeless). Add an example for the third mark.
Tie it to vulnerability, not the hazard: You cannot change the size of an eruption — so never write 'it stops the eruption'. Write that the strategy reduces the number of people exposed or helps them survive. Zoning → fewer people in the danger zone → fewer deaths.
Know your predicted grade
Take timed mock exams and get detailed feedback on every answer. See exactly where you're losing marks.
No strategy is perfect — each works in some places and fails in others. The [10] essay is won by knowing where each strategy succeeds and where it falls short, anchored to real named events. Below are the case studies that power a top answer.
Haiti 2010 vs Chile 2010 — building design: Weeks apart, Haiti had a magnitude 7.0 quake and Chile a far larger magnitude 8.8. Yet Haiti suffered around 220,000 deaths and Chile only a few hundred.
Why? Chile enforced earthquake-resistant building codes (cross-braced, flexible frames); poverty-stricken Haiti did not. Lesson: resilient design saves lives — but only if a country is rich enough to afford and enforce it.
Tohoku 2011 — warning works, but limits remain: Japan's earthquake early-warning system gave people and trains tens of seconds of notice before the 2011 quake, and sirens triggered tsunami evacuation.
But the tsunami was higher than the sea walls were built for, so over 18,000 people still died. Lesson: warning and defences save many lives, yet a hazard larger than planned for can overwhelm them.
Eyjafjallajokull 2010 & Nevado del Ruiz 1985 — prediction's value: Iceland's Eyjafjallajokull (2010) was closely monitored, so people were evacuated and no one died locally — though the ash cloud grounded European flights.
By contrast, Nevado del Ruiz (Colombia, 1985) had hazard maps warning of lahars, but warnings were not acted on and a mudflow killed about 23,000 people in Armero. Lesson: prediction only saves lives if the warning is communicated and acted on.
Lava diversion — Etna and Heimaey: Engineers have diverted lava away from towns: barriers and channels on Mount Etna, and seawater spraying that chilled and slowed a flow on Heimaey, Iceland (1973).
Lesson: engineering can protect property from slow lava flows — but it is costly and useless against fast hazards like pyroclastic flows or earthquakes.
How this is tested — the markband essay: Paper 1 Option D ends with a [10] essay marked on markbands, using the big AO3 verbs: Examine, Evaluate, or To what extent. The recurring question is how effective pre-event strategies (technology and planning) are at reducing vulnerability.
Top band (9-10) needs both: an evidenced explanation of a range of strategies and a balanced critical evaluation that weighs their success against cost, technology, funding and level of development across places — finishing on a clear judgement.
Always weigh by development level: The strongest judgement links effectiveness to wealth and governance: the same strategy that saves lives in Japan or Chile is unaffordable or unenforced in Haiti. Use that contrast as your central argument.