Disaster Preparedness at the Neighborhood Scale

The academic literature on disaster sociology — particularly the work coming out of the Disaster Research Center at the University of Delaware, active since 1963 and the oldest social science research center focused on disasters — has consistently overturned the intuitive assumptions held by both public officials and ordinary people about how communities actually behave in disasters.

What the Research Shows

The panic assumption is false. People in disasters do not typically panic. They tend to act in organized, prosocial ways — helping neighbors, sharing resources, spontaneously organizing. The panic narrative serves the interests of centralized emergency management (it justifies the need for authoritative control) but is contradicted by evidence from actual events. What does kill people is isolation: individuals without social connections who are not reached in the first hours and who have no one to call on.

The dependency assumption is also false. Government emergency management planning often treats citizens as passive recipients of official response. Disaster research shows the opposite: in major events, the majority of rescues, first aid, damage assessment, and welfare checks are performed by community members with no official role. The formal response system is often arriving to support and coordinate community action that has already been underway for hours.

The vulnerability clustering insight is critical for neighborhood planning. Vulnerability is not randomly distributed. It concentrates geographically — areas with lower income, older housing stock, higher proportions of elderly and disabled residents, lower car ownership, lower social connectivity — are consistently hit harder by disasters and recover more slowly. Neighborhood preparedness planning must be explicit about where these concentrations are and must build additional capacity in these areas rather than assuming uniform baseline capacity across the neighborhood.

Organizational Structure

The CERT (Community Emergency Response Team) program, developed by the Los Angeles Fire Department in 1985 and subsequently adopted nationwide, provides one model for neighborhood-scale preparedness organization. CERT training covers triage, light search and rescue, fire suppression, and disaster medical operations. It is widely available and free. Its limitation is that it is structured around individuals with training rather than around neighborhood organizations with relationships. Training an individual who then has no organizational home for that training produces limited resilience gain. Training a group of neighbors who will coordinate as a unit produces much more.

The San Francisco Neighborhood Emergency Response Team (NERT) model and Seattle's Neighborhood Emergency Teams (NET) program add the organizational layer — geographic assignments, regular meetings, neighborhood-level exercises, and integration with official emergency management. These programs have better outcomes than individual-certification-only approaches because they build the organizational infrastructure alongside the skills.

For communities without access to these programs, the core organizational elements can be built from scratch:

Block captain structure — each block has a primary and backup captain responsible for knowing all households on the block, maintaining a contact list with special needs noted, and conducting welfare checks immediately after an event. The geographic unit of a block or cluster of 10-20 households is small enough to manage with personal knowledge and large enough to be organizationally useful.

Skill and resource registry — a maintained inventory (see concept 300 on community mapping) of who has what skills and equipment. Medical training, language fluency, mechanical skills, construction knowledge, specialized tools, large vehicles. This registry must be updated at least annually and must be accessible to block captains without requiring internet connectivity.

Communication tree with redundancy — primary communication via text or phone app when networks are functional; backup via phone tree when networks are degraded; tertiary via in-person checks when all electronic communication fails. The third layer sounds primitive. It is also the only layer that reliably functions in a catastrophic event. Designing for the worst case provides coverage for all lesser cases.

Shared cache with governance — supplies held in common require governance: who decides what to stock, how costs are shared, who has access and under what circumstances, how supplies are rotated and replaced. These are organizational problems, not technical ones. The technical problem (acquiring a generator or a water filter) is easy. The governance problem (ensuring equitable access under stress) requires relationship and agreement built before the emergency.

The 72-Hour Frame and Its Limits

Emergency management commonly advises individuals to prepare for 72 hours of self-sufficiency. This framing has limitations that neighborhood planning should address.

Seventy-two hours assumes a short-duration event followed by restoration of external support. Many actual disasters — extended power outages, prolonged flooding, pandemic conditions, infrastructure failures in rural areas — extend well beyond 72 hours. Neighborhood plans should address multi-week scenarios for events where external support is seriously degraded.

Individual household 72-hour preparedness is not the same as neighborhood preparedness. A street where every household has a 72-hour kit but no household knows its neighbors is less resilient than a street where half the households have 72-hour kits and all the households know each other and have a communication plan. Social connectivity multiplies the effective resilience of whatever material resources exist.

The most vulnerable community members — elderly, disabled, medically dependent, without cars, without English, without financial resources — are the least likely to have individual preparedness and the most likely to need collective support. A neighborhood preparedness program that focuses on the prepared households is optimizing at the wrong margin. The binding constraint on neighborhood resilience in most events is the condition of the most vulnerable, not the average.

Exercises and Practice

A neighborhood that has never practiced is a neighborhood that has planned. A neighborhood that has practiced is a neighborhood that is prepared. The distinction matters enormously. Under stress, people execute practiced behaviors. Novel behaviors required for the first time under stress are executed poorly or not at all.

Exercises do not need to be elaborate. A tabletop exercise — a group of neighborhood leaders sitting around a table walking through a scenario — identifies coordination gaps, communication failures, resource shortages, and unclear responsibilities with minimal logistical burden. It also surfaces the interpersonal dynamics that will affect real-event performance: who defers to whom, who has information others don't, where assumptions diverge.

Field exercises — a neighborhood evacuation drill, a practice deployment of the shared cache, a block-level welfare check drill — add the physical and logistical dimensions. They reveal things that tabletops cannot: that the shed where the chainsaw is stored has a lock no one can find the key for, that the elderly resident on the corner cannot actually navigate the evacuation route on foot, that the communication tree breaks down after the third link because two people don't have each other's numbers.

Annual exercises, held at consistent times so they become community expectations rather than one-off events, build the muscle memory of collective action. After several iterations, the neighborhood knows what it is doing because it has done it, not because it has read about it. That difference — between theoretical knowledge and practiced capacity — is the difference between a preparedness program and actual preparedness.

Integration with Official Systems

Neighborhood preparedness is most effective when it is integrated with, not isolated from, official emergency management. This means: knowing the local emergency management contacts before an event, understanding the official evacuation zones and routes, registering mobility-limited and medically dependent residents with official programs (many jurisdictions have such registries), and establishing protocols for how block captains report neighborhood status to official coordination points.

The neighborhood does not replace the official system. It covers the gap in the first hours and it multiplies the effectiveness of official resources by ensuring that official responders arrive to an organized community that can report on its own status, has already conducted welfare checks, has already identified who needs assistance, and has already begun stabilization — rather than arriving to a chaotic situation where no one knows anything.

The design goal is a neighborhood that can function for a week without external support and that, when external support arrives, can integrate with it immediately. That goal is achievable with modest resources and genuine relationships. It is not achievable with resources alone.