After Hurricane Katrina in 2005, FEMA researchers studying neighborhood survival outcomes found one variable that predicted recovery speed better than income level, proximity to services, or individual preparedness: whether neighbors had relationships with each other before the storm. Households embedded in active social networks — people who knew names, shared resources informally, and checked on each other — recovered faster and with less permanent loss than isolated households with identical resources.
The research finding is not that community is nice to have. It is that community is a preparedness multiplier. A household with a two-week food supply and three trusted neighbors is more resilient than a household with a six-month supply and no relationships. The math works because no individual household can anticipate every scenario — but a small network of people with different skills, resources, and information channels covers far more ground.
Why a Small Network Outperforms Solo Preparedness
The limits of individual preparedness are physical and temporal. One household cannot watch its own property while evacuating, cannot assist an injured person and also secure a perimeter, cannot monitor radio traffic while cooking, cannot know what is happening two blocks away. A network of five households that have agreed on basic coordination distributes all of these tasks without requiring anyone to do more than their share.
The other thing a network provides is information. During the 2020 derecho that knocked out power across the Midwest for up to two weeks, households with neighborhood group chats had real-time updates on where ice was available, which roads were passable, when power was restored to specific areas, and which neighbors needed help. Households without those channels operated on rumor and made worse decisions as a result.
Think of a neighborhood network as distributed capacity, not a club. You are not joining something or asking others to join something. You are identifying who is around you, what they have, and what they can do — and making sure they know the same about you. The network already exists. You are just making it legible.
Who to Include — and How to Assess It
Start with geography, not ideology. The most useful neighbors in an emergency are the ones physically closest to you — not the ones whose politics or lifestyle choices most closely match yours. Proximity matters because it determines response time, shared infrastructure (same power grid, same water main, same evacuation route), and the ability to physically assist each other.
Within that geographic constraint, there are four qualities worth assessing before you invest in a relationship:
Reliability in ordinary life. Someone who follows through on small commitments — returning borrowed items, showing up when they say they will — is likely to follow through under pressure. The inverse is also true. You learn this through low-stakes interactions before you need it for high-stakes ones.
Practical skills or resources you lack. A neighbor with medical training, a generator, a truck capable of towing, a ham radio license, or significant food storage changes what your network can handle. You do not need to approach this transactionally — but knowing what each person brings changes how you coordinate.
Awareness of their own surroundings. Some people notice things. They know which houses on the street are vacant, when new people have moved in, what the normal pattern of activity looks like. In an emergency, situational awareness is a scarce resource and people who naturally develop it are disproportionately valuable in a network.
Stability. Renters turn over. Families move. Someone who has been in the neighborhood for several years and appears likely to remain is a more durable network node than someone who arrived six months ago and may leave in six more.
Exclude anyone who is volatile under stress, who talks significantly more than they act, or who treats emergency preparedness as primarily an identity rather than a practical project. A five-person network with one unreliable member is less functional than a four-person network without them. Keep the group small enough that each person's reliability can be assessed directly.
How to Start the Conversation Without Making It Weird
The most common reason people do not build neighborhood relationships is social friction — specifically, the fear that approaching a neighbor about emergency preparedness will read as alarmist, paranoid, or ideologically charged. This fear is usually overstated, but the framing of the initial conversation matters.
The conversation that works is not "I'm building an emergency preparedness network and I'd like you to join." That framing immediately requires the neighbor to evaluate a commitment they know nothing about. The conversation that works is much smaller: an exchange of phone numbers with a specific rationale.
"Hey — I realized we've been neighbors for two years and I don't have your number. Given everything going on lately, it seems like a good idea to have a way to reach each other if something happens on the street." That is the entire conversation. Most people say yes. Most people find it reasonable. No ideology required, no formal commitment asked for, no group to join.
From there, the relationship builds through ordinary interactions — and through low-stakes tests. Asking to borrow something. Offering to bring in a package. Mentioning something you noticed. These interactions reveal character and build the familiarity that makes coordination natural rather than awkward when the stakes are higher.
What the Network Actually Needs to Agree On
A neighborhood network does not need bylaws, regular meetings, or a formal structure. It needs four agreements, reached informally, that everyone remembers without having to look them up.
A check-in signal. Something simple that indicates a household is okay — a porch light on, a flag in a window, a specific position of a planter. The absence of the signal after a defined period is the trigger to physically check on that household. This removes the ambiguity of "should I knock on their door" and replaces it with a shared, pre-agreed system.
A shared communication channel. A group text thread is sufficient for most purposes. It should include every household in the network, have a clear name that everyone recognizes, and be used occasionally for non-emergency neighborhood information so it does not feel clinical when an actual emergency happens. A channel that only activates in emergencies is one where people may not notice messages quickly.
Known vulnerabilities. Every network should know which households include people who will need assistance evacuating or sheltering — elderly residents, people with mobility limitations, households with infants, people who are medically dependent on power. This information does not need to be documented anywhere formal. It needs to be known by the people who would act on it.
A loose resource map. Who has a generator. Who has significant food and water storage. Who has medical training. Who has a vehicle that can carry more than one household's worth of gear. Who has tools. None of this needs to be exhaustive — even a rough awareness of what exists in the network prevents redundant purchasing and reveals gaps worth filling.
-
First Exchange numbers with two to three immediate neighbors The ones physically closest. Use the straightforward framing above. This takes ten minutes and requires no commitment beyond a phone number.
-
First Create a group text with those neighbors Name it something neutral — the street name works. Use it once or twice for non-emergency neighborhood information in the first month so it doesn't sit dormant.
-
First Identify which households have people who need assistance You probably already know this from ordinary observation. If not, the phone number exchange conversation often surfaces it naturally.
-
Over time Build a loose mental map of resources in the network Through ordinary conversation. Not an interrogation — just paying attention when people mention what they have or what they do.
-
Over time Agree on a check-in signal Raise it as a practical question once the relationship is established. "If something happened and you couldn't reach anyone, what would be a good way to know you were okay?" Most people engage with this naturally.
-
Over time Expand to four or five households if the right people are available Bigger is not better past a point. Five households that coordinate well outperform fifteen that do not. Quality of relationship matters more than network size.
Maintaining the Network Without It Becoming a Job
The failure mode for neighborhood networks is attrition through over-formalization. Groups that schedule monthly meetings, assign roles, and produce documentation tend to collapse within a year because the overhead exceeds what ordinary neighbors are willing to sustain. The networks that persist are the ones where the maintenance cost is near zero.
Near-zero maintenance looks like: using the group text occasionally for genuinely useful neighborhood information. Waving when you see people. Noticing when something looks different and mentioning it. Helping when help is asked for. These are the behaviors that keep relationships functional without requiring anyone to treat preparedness as a hobby or a second job.
The one structured thing worth doing once a year is a five-minute check-in on whether the resource map has changed. Someone moved out and a new household moved in. Someone acquired a generator. Someone's medical situation changed. The group text is sufficient for this — it does not require a meeting.
Most of the value in a neighborhood network comes from the first two steps — exchanging numbers and knowing who needs help. Everything else improves on a foundation that already functions. Start there. The rest builds itself if the relationships are real.