Playbooks

Mid-Size City Communication Network

5,000–100,000 residents6–24 months$20,000–$200,000

Regulatory references (licensing, frequencies, equipment certification) reflect US rules (FCC) unless otherwise noted. Requirements differ outside the US — verify with your national radio authority before operating. Full disclaimer →

Mid-size cities have more potential than smaller communities — more volunteers, more partner organizations, more infrastructure to build on — but also more complexity: multiple jurisdictions, competing priorities, and political dynamics that don't exist at neighborhood scale.

Stakeholder Mapping and Partnership

Months 1–3

Identify key stakeholders

  • Emergency management office (most important — they have authority and resources)
  • Public health department
  • Hospital system
  • Utility companies (electric, water, gas)
  • clubs and ARES/RACES groups
  • Community organizations (Red Cross, Salvation Army, community foundations)
  • Universities (radio clubs, technical expertise, infrastructure access)
  • Local government IT departments

Build the right partnerships

  • Emergency management is the anchor. They need what you're building; you need their authority, access to facilities, and potential grant funding. Get an MOU early.
  • Universities are underutilized. Engineering departments can provide student volunteers, rooftop access, and technical expertise. Radio clubs are often already active. Computer science departments may support software development.
  • Utilities know where the failures will be. Their emergency communication plans reveal the gaps you're filling. They also often have towers and rooftop access.

Document the current state

Before proposing anything, map what exists:

  • All and their coverage
  • ARES/RACES activation history and current membership
  • EOC capability and current communication plan gaps
  • Elevated sites available for infrastructure

Backbone Infrastructure

Months 3–12

AREDN network

is the right backbone technology for city-scale resilient communication. It provides full IP networking — VoIP, email, data — over licensed bands, with no dependence on commercial infrastructure. See mesh networking overview →

Minimum viable backbone: 5–7 AREDN at strategic high points covering the city with overlapping coverage. Each node should be at a location with:

  • Generator-backed (EOC, hospital, fire station, utility facility). See power options →
  • Structural mounting for directional antennas
  • A trained operator on site

Hardware: Ubiquiti Rocket M AC with sector antennas for backbone links; Ubiquiti NanoStation for local coverage. Check arednmesh.org for current supported hardware — models change frequently.

Meshtastic city mesh

In parallel with AREDN (which requires ham licenses), deploy a mesh for text messaging and position sharing that any resident can use:

  • 15–20 router at elevated locations across the city
  • Solar-powered where possible
  • Use the LongFast or LongSlow preset for extended range — avoid manually setting SF12, which causes network congestion and duty-cycle violations
  • City-wide channel available to all residents

Anchor Points

Months 6–12

Identify 20–30 anchor points as communication hubs. Prioritize:

  • EOC and backup EOC
  • All hospitals and major medical facilities
  • All fire stations
  • Public libraries (open to all, widely distributed, often generator-backed)
  • Community centers
  • Schools used as shelters

Each anchor point gets

  • An (if licensed operator on site) or node
  • A programmed or licensed radio. Compare radio options →
  • A trained communication volunteer
  • Printed communication plan and frequency cards

Community Distribution

Months 12–24

Licensing program

Organize quarterly licensing classes. Target: 1 licensed per 100 residents. Partner with local emergency management and Red Cross to fund exam fees for low-income participants.

Neighborhood deployment

Work outward from anchor points. Each neighborhood gets:

  • A designated communication liaison (licensed or operator)
  • A
  • A place in the city-wide net

Not sure where to begin at neighborhood scale? See the Neighborhood Network playbook →

Integration with official emergency management

Formalize the relationship with a Memorandum of Understanding (MOU) that defines:

  • Roles and responsibilities during EOC activations
  • Communication protocols for passing traffic to emergency management
  • Training and exercise participation requirements
  • Equipment access and storage at EOC facilities

Participate in all city emergency management exercises. This is how you build the relationships that make the system work when it matters. See also: Emergency Response Activation playbook →

← All playbooks · See case studies