Tectonic Hazards: Additional Detailed Specific Examples
| Distinction | First Term | Second Term | Why It Matters |
|---|---|---|---|
| Event metric | Magnitude (energy released) | Intensity (observed effects) | Prevents misuse of scale data in impact arguments |
| Effect type | Primary impact | Secondary impact | Supports causal sequencing and better structure |
| Response phase | Immediate response | Long-term recovery | Aligns actions with realistic time horizons |
| Risk framing | Hazard probability | Vulnerability/exposure | Explains unequal outcomes between places |
| Management logic | Prediction limits | Preparedness capacity | Shows why planning can work even without exact forecasts |
Use a repeatable paragraph frame: cause -> impact chain -> response -> evaluation of effectiveness. This structure ensures your answer stays analytical and prevents drifting into narrative storytelling. It also helps you include both physical geography and human geography in each paragraph.
Always make at least one explicit comparison between contrasting contexts, because comparison demonstrates transfer-level understanding. Strong comparisons explain why the same tectonic mechanism produces different social outcomes under different governance and infrastructure conditions. This is often the difference between mid-band and top-band responses.
Check claim-evidence alignment before finishing so each conclusion is supported by an appropriate indicator. If your claim is about resilience, use rebuilding quality, preparedness improvement, or livelihood recovery rather than only casualty counts. A quick alignment check improves precision and marks.
Misconception: 'Bigger magnitude automatically means bigger disaster.' Disaster severity depends on exposure, building standards, emergency access, and social vulnerability, not magnitude alone. Correct this by linking physical metrics to human-system conditions.
Pitfall: mixing response actions without timing, such as placing reconstruction measures inside immediate relief discussion. This weakens evaluation because short-term and long-term goals are different. Label each action by phase to keep your logic clean.
Pitfall: listing impacts without mechanisms, which reads as memorization rather than understanding. Examiners reward cause-and-effect chains that show how one disruption triggers another. Add connectors like 'therefore,' 'which led to,' and 'as a result of' to make reasoning explicit.