Building Neighborhood Disaster Preparedness Networks

Why Neighborhoods Are the Right Unit for Mesh Networks

The first 72 hours after a major disaster are the most critical for community survival - and they are precisely when official emergency services are most overwhelmed and least available. FEMA and Ready.gov recommend being prepared to be self-sufficient for at least 72 hours (and current guidance often recommends longer - several days to two weeks; see ready.gov). A neighborhood-scale mesh network provides:

• Hyperlocal situational awareness: Who needs help on your block? Who has medical training? Which houses are damaged? Mesh can carry this communication when phones are down - but only where a path of powered, in-range nodes exists, and delivery is best-effort with no guarantee.
• Resource coordination: "I have a generator and can share power." "We need insulin in the refrigerator on Elm Street kept cold." Short mesh messages coordinate resources without driving through blocked streets. Privacy note: mesh messages are typically broadcast and may be unencrypted. Avoid broadcasting sensitive personal or medical details and specific vulnerable-person locations on open channels; use direct messages or a private channel and exercise basic privacy judgment.
• Connection to official emergency services: A mesh node at the neighborhood EOC staging area, connected to the official mesh network, bridges the neighborhood to city-level response.
• Community resilience: Neighbors who have trained together and have communication tools recover faster and experience less psychological distress during disasters.

CERT Teams and Neighborhood Preparedness Groups as Mesh Early Adopters

Community Emergency Response Teams (CERT) - FEMA-trained volunteer groups that provide immediate disaster response at the neighborhood level - are natural mesh early adopters. CERT teams:

• Already train for disasters; mesh is a natural addition to their toolkit
• Have an organizational structure that can absorb mesh training
• Have a relationship with city OES that provides legitimacy for mesh integration
• Are geographically distributed across the community - ideal for mesh coverage

How to approach your local CERT team: Contact the CERT coordinator through your city's OES or Fire Department (CERT programs are usually run by Fire). Offer a free 30-minute demonstration. Propose providing 2 - 3 Meshtastic nodes for CERT team use. Ask to be included in the next CERT exercise.

The Block Captain Model

The most scalable neighborhood mesh model assigns one mesh node to each block captain - a neighbor who has volunteered to be the communication point for their immediate block. The block captain:

• Maintains a Meshtastic node (typically a small, low-cost device like a WisBlock Meshtastic kit)
• Knows how to send and receive messages on the neighborhood channel
• Serves as the communication relay for neighbors who don't have mesh nodes
• Reports to a neighborhood zone leader (who reports to city OES)
• Checks in during exercises and activations

The number of block captains needed depends heavily on terrain, antenna height, building density, and node placement - there is no fixed node count that guarantees whole-neighborhood coverage. Rather than assuming a flat figure (e.g., 8-12) gives adequate coverage for all occupied blocks, plan your node count from an on-site walk test / range survey (see below). Block captain nodes can also relay for neighbors who have their own Meshtastic devices (phones running the app, personal nodes, etc.).

Coverage Mapping for Your Neighborhood

Before committing to node placement, map your coverage. Two approaches:

Walk Test Method

1. Place one node at the proposed location of the primary relay (highest point accessible: roof, upper floor).
2. Walk the entire neighborhood with a second node (phone running Meshtastic).
3. Send test messages every 100 meters. Mark locations where messages fail to deliver on a map.
4. Identify coverage gaps. Add relay nodes at elevated points within the gap areas.
5. Repeat walk test after adding relays.

Coverage Prediction Method

1. Use a radio propagation prediction tool (HeyWhatsThat, RadioMobile, or SPLAT!) to model 915 MHz coverage from each proposed node location.
2. Input antenna height and terrain data, and compute the LoRa link budget rather than assuming a fixed number. Link budget = TX power (dBm, up to +30 dBm conducted under Part 15.247) + TX antenna gain + RX antenna gain - RX sensitivity (dBm). Note that RX sensitivity is spreading-factor-dependent (roughly -120 to -148 dBm; see the Semtech SX1262 datasheet), so a single "~140 dB" figure is only a rough placeholder, not a "medium-range Meshtastic" constant.
3. Overlay coverage predictions on a neighborhood map to identify gaps before physical deployment.
4. Verify predictions with a walk test after deployment.

Integrating with City OES

City Office of Emergency Services (OES) departments vary widely in their receptiveness to amateur mesh technology. Approach strategically:

1. Start with the CERT liaison. If your city has a CERT program, the CERT coordinator is your best entry point. They already work with volunteers and understand non-professional capabilities.
2. Request to participate in city exercises. Most OES departments hold annual exercises. Request observer/participant status and demonstrate mesh alongside official comms.
3. Offer to complement, not compete. Never suggest mesh replaces city radio systems. Position it as "last-mile neighborhood comms" that fills a gap city systems don't cover.
4. Provide documentation. After exercises, provide written reports showing mesh performance and how it integrated with official operations.
5. Pursue MOU/Letter of Support. A formal letter of support from the OES director significantly increases the group's credibility when recruiting block captains and securing sites. Any MOU should be reviewed by counsel and should allocate liability and insurance, and explicitly state that the mesh network is supplemental, volunteer-run, and best-effort - not a guaranteed or primary emergency service.

Equipment Storage and Rotation Plans

A neighborhood mesh program is only as good as its equipment. Establish a storage and rotation plan to ensure equipment is operational when needed:

Battery longevity note: keeping a node permanently at 100% on a USB charger ages its internal lithium battery over time. Continuous float charging is acceptable for readiness, but plan to replace internal cells periodically and do not assume the battery will hold full capacity after years of float charging. For nodes kept in a cache rather than powered, store the internal lithium battery at roughly 40-60% state of charge and top up to full only before deployment.

Equipment Rotation Policy

• LiFePO4 batteries: inspect annually. Many LiFePO4 packs last 8-10+ years, but for life-safety standby consider replacement at 5-7 years or when capacity drops below 80% (check the cell/pack datasheet).
• LiPo/Li-ion power banks: replace after 2 - 3 years or if capacity has dropped below 80%
• Meshtastic nodes: firmware-update annually; replace hardware after 5 - 7 years or if hardware fails
• Coaxial cable: inspect annually; replace any cable with cracked jacket or corroded connectors
• Antenna mounts: inspect annually; replace if corrosion is visible on structural hardware

Annual Testing Exercise Plan

An annual exercise keeps skills sharp, identifies equipment problems before a real disaster, and provides a regular community engagement opportunity. Template:

Neighborhood Preparedness Network Checklist

• ☐ Neighborhood or CERT team organizational structure established
• ☐ Block captain model defined; at least 50% of blocks have a mesh-equipped captain
• ☐ Coverage map completed; coverage gaps identified and addressed
• ☐ At least one pre-positioned relay node at highest accessible point in neighborhood
• ☐ Reserve node cache established (minimum 2 spare nodes)
• ☐ All captains trained on Meshtastic operation (send/receive/check battery)
• ☐ Channel configuration documented and shared with all participants
• ☐ Neighborhood mesh coordinator identified and trained
• ☐ OES or CERT coordinator briefed; relationship established
• ☐ Annual exercise scheduled and completed at least once
• ☐ Equipment inventory and maintenance log current
• ☐ Connection to city-level mesh infrastructure established (or in progress)