How Mutual Aid Dispatch Systems Coordinate Help In Real Time

Let me draw a distinction that matters.

Charity is vertical. Someone with resources gives to someone without. The giver is the subject, the receiver is the object. Thank-you letters flow upward. Tax deductions flow downward. Power stays where it was.

Mutual aid is horizontal. Everyone is both giver and receiver, depending on the day. The person who got groceries last month brings soup to the sick person this month. The infrastructure is shared. The power is distributed. No one is "the needy."

Dean Spade's book Mutual Aid: Building Solidarity During This Crisis (2020) made this distinction famous, but the practice is ancient. Every immigrant community that ever landed in a new country survived through mutual aid. Every Black neighborhood that survived Jim Crow survived through mutual aid. Every queer community that survived AIDS survived through mutual aid.

What's new in 2020-2026 is three things: digital coordination, geographic specificity (hyper-local networks at the block or zip-code level), and the reframing of the work as political rather than purely humanitarian.

March 2020 was the stress test. Everything froze simultaneously — jobs, supply chains, social services, healthcare. And the formal safety net (unemployment offices, food banks, emergency services) was overwhelmed or closed.

Into that vacuum, within roughly six weeks, mutual aid networks spun up across the country. Estimates range from 800 to 1,600 new networks depending on who's counting. Town of Ours, a directory project by the Big Door Brigade, tracked over 900.

What most of these networks looked like in week one: - A Google Form to request help. - A Google Form to volunteer. - A Slack or Signal group. - A hand-built spreadsheet trying to match requests to volunteers. - Five to twenty people frantically trying to coordinate.

What most looked like by month three: - Dead. Or barely functional.

What a small minority looked like by month three: - Sophisticated, humming, helping thousands of people a week.

What separated the two? Not scale. Not funding. Not location. It was dispatch.

Bed-Stuy Strong launched March 2020 in Brooklyn. By the end of that year they had served over 10,000 households and delivered over $1.5 million in groceries. Founder Sarah Thankam Mathews wrote about the operations in The New York Review of Books and gave a talk at the Obama Foundation that I'd encourage anyone building a network to watch.

Here's what they actually did.

One intake hotline. One phone number. You called it, a human answered or called you back. No app, no form, no website to navigate. Many neighbors didn't have smartphones or stable internet. A phone call worked.

Intake interview. The person answering did a brief intake: name, address, household size, what they needed, whether they'd ordered before. This conversation did three things: gathered data, triaged urgency, and connected the neighbor to a human voice. That third thing mattered more than the first two.

Shopping captains. A volunteer received the order, went to the grocery store, bought the items (using money from a Venmo pool), delivered to the doorstep. No contact during COVID.

Block-level distribution. Volunteers were assigned by block. You didn't shop for someone 40 blocks away. You shopped for your neighbor three blocks over. Proximity was the design principle.

Debrief loops. After each delivery, the shopper reported back. Anything weird? Anything concerning? The neighbor flagged as needing a wellness check, a mental health referral, a utility bill? The next call back came from a trained volunteer.

Pod structure. Volunteers were organized in small pods of 8-12 people, each with a coordinator. This scaled. The coordinators reported to area leads. The area leads met weekly. The structure was flat enough to move fast and deep enough to catch 10,000 households.

Explicit rest. After three months of full-burn operations, they built in mandatory rotation. Coordinators stepped down for 30-day rests. This preserved people.

The reason Bed-Stuy Strong became the case study isn't that they were the largest — many networks served more. It's that they documented what they did. They published playbooks. They did webinars. They open-sourced their spreadsheet templates. Other networks copied them. The pattern replicated.

Before COVID there was Hurricane Sandy, October 2012. Occupy Wall Street had fizzled as a movement the year before, but the organizing infrastructure was still alive — a network of people who knew each other, had communication tools, and understood how to self-organize.

When Sandy hit, that network rebranded overnight as Occupy Sandy and became one of the most effective disaster response operations in the region — outperforming, by many measures, the Red Cross and FEMA in the first 72 hours.

The operational core:

A church in Sunset Park as a hub. St. Jacobi Lutheran Church in Brooklyn became the central distribution point. Physical location matters. People need somewhere to bring donations, pick up supplies, and coordinate face to face.

An Amazon wedding registry as supply chain. This was the famous innovation. Occupy Sandy created an Amazon wedding registry listing needed items (blankets, batteries, baby formula). Donors across the country bought items off the registry. Amazon shipped directly to the church. This bypassed the normal donations-collection bottleneck entirely.

Google Voice numbers for dispatch. Multiple Google Voice numbers routed to rotating dispatchers. Calls came in, dispatchers matched requests to volunteer crews in real time.

A cascading task board. Requests came in, were broken into tasks, tasks were assigned to crews. Each crew reported back on completion. This ran 24/7 for weeks.

Affinity groups for specialized work. A medical group. A mold-remediation group (Sandy left flooded basements that needed professional mold removal). A childcare group. A mental health group. Each operated autonomously within the larger dispatch.

Radical transparency. Meeting notes were public. Financial ledgers were public. This built trust fast. Volunteers knew what was happening and could self-organize around gaps.

The post-mortem research on Occupy Sandy (most notably a Homeland Security-funded study in 2014) concluded that the network's horizontal structure, pre-existing relationships, and transparent operations made it more agile than the formal emergency response, not less.

Mutual Aid Medford & Somerville (MAMAS) is a smaller network worth studying because it's still running, five years in. Most mutual aid networks die when the acute crisis ends. MAMAS adapted.

Their stages:

Phase 1 (March-July 2020): Acute response. Grocery deliveries, prescription pickups, rent support. Pure crisis mode.

Phase 2 (July 2020-2021): Stabilization. They formalized a mutual aid fund (no 501c3, no gatekeeping — people asked, money went out). They organized by neighborhood and built intake routines.

Phase 3 (2022-present): Infrastructure mode. They now operate as a standing community infrastructure. They have a paid coordinator. They have ongoing programs. They have a rainy-day fund. They are an institution without becoming institutional.

The key insight from MAMAS: mutual aid doesn't have to be a flash mob. It can become the standing furniture of a neighborhood. Like a volunteer fire department, except for the kinds of crises that aren't fires.

Let me break down the operational components.

6.1 The intake. One channel, or at most two. Phone number plus form is fine. More than that and people get lost.

The intake form asks (at minimum): - Name / how to reach you - Address or cross streets - What you need (open-ended field crucial — don't over-structure) - How urgent - Household size / anyone with specific needs

What intake should not ask: - Income verification - ID - Documentation status - Deservingness proof of any kind

Mutual aid is not a means-tested program. If someone asks, they get. The only filter is: is this within scope? If a billionaire asks for grocery delivery, they get grocery delivery (and usually they don't ask).

6.2 The triage. A dispatcher reads the incoming request within 24 hours (ideally within 2-4 for urgent needs). They sort into categories: - Urgent (medical, food insecurity today, housing crisis) — act within 12 hours - Standard (groceries this week, rides to appointments) — act within 48 hours - Referral (needs professional services we can't provide) — route to appropriate agency - Out of scope (someone trying to use the network for something that's not mutual aid)

Triage requires judgment. It's a skill. Train your triagers. Give them decision rules. Back them up with a group chat so they can ask when unsure.

6.3 The match. Match variables: - Geographic proximity (smaller is better) - Volunteer availability in the window needed - Skills required (some requests need specific things — a car, a fluent Spanish speaker, someone with childcare experience) - Trust level (repeat volunteers with demonstrated reliability get harder tasks) - Capacity (don't burn out a volunteer by giving them three requests when they said they could do one)

6.4 The execution. The volunteer does the thing. This is the actual work. Most networks overweight everything else and underweight this — but the execution is where the relationship between volunteer and neighbor happens, and that relationship is the whole point.

6.5 The follow-up. Did it arrive? Did it work? Is there a next need? Is there a concern (wellness, safety, mental health) that needs a warmer handoff?

Networks that follow up build long-term relationships. Networks that don't stay transactional.

6.6 The debrief. Weekly (at minimum) debrief among dispatchers and coordinators. What worked? What didn't? What gaps are we seeing? Who's burning out? What do we need more of?

This is the part most networks skip. Don't skip it. This is where learning happens.

I've watched or heard about dozens of mutual aid networks. The failures cluster.

Failure 1: The founder cluster burns out. The 5-8 people who started the thing end up doing 90% of the work. They burn out together around month six. If there's no succession plan, the whole network goes with them. Mitigation: from week one, be actively training your successors. Distribute the dispatching role across at least 15 people.

Failure 2: Request overwhelm. Word spreads. Requests flood in. The intake can't keep up. New volunteers can't be onboarded fast enough. Quality drops. Mitigation: build an onboarding pipeline early. Set explicit capacity limits and communicate them. Temporary pauses on new intake are sometimes necessary and healthy.

Failure 3: Money problems. Either you raised no money and can't buy groceries, or you raised a lot of money and don't have accounting infrastructure to handle it. The second one is more dangerous — it invites conflict, suspicion, and sometimes legal issues. Mitigation: decide early whether you're a money-moving network or a person-matching network. If money, set up clear ledgering from day one. Consider fiscal sponsorship through an existing 501c3 rather than getting one of your own.

Failure 4: Conflict between volunteers. Six months in, two coordinators hate each other. Factions form. Side meetings happen. The network splits or withers. Mitigation: have explicit conflict resolution processes from the start. Name a mediator. Surface tensions in debriefs. Don't let them fester.

Failure 5: Mission drift. The network started as emergency groceries. Now someone wants it to do housing advocacy, someone else wants a community garden, someone else wants political education. All are worthwhile. None fit in one operation. Mitigation: be clear about scope. Spin off other projects rather than cramming them in.

Failure 6: The neighbor who tests limits. Every network gets one. A person who calls every day, sometimes with real needs, sometimes not, who drains dispatcher time. This is almost always someone with unaddressed mental illness or substance issues. Mitigation: assign one dispatcher as the primary contact for this person. Refer to professional services. Set limits compassionately but firmly.

Framework A: The 10-Person Starter Network. Before you launch publicly, have 10 committed people. Five can do intake/dispatch. Five can do delivery/execution. Run a quiet beta for two weeks in your immediate neighborhood before any public announcement.

Framework B: The Three-Channel Rule. Pick three communication channels and stick to them. Example: (1) a phone number for intake, (2) a Signal group for dispatchers, (3) an email list for monthly updates. More than that fragments attention.

Framework C: The 1-3-5 Volunteer Commitment. Ask volunteers to commit to 1 task a week for 3 months, and reassess at 5 months. Specificity beats "come help when you can." Specificity makes people show up. Ambiguity gives them an out.

Framework D: The Pre-Crisis Stand-Up. Build the network before the disaster. Get 30 neighbors into a group chat. Do a dry run. Practice the intake. When the crisis comes, you'll already have the muscle. This is the difference between the Sandy networks that were ready and the ones that scrambled.

Exercise 1: Map your block. Walk your block or building. Note which doors you know and which you don't. In the next month, introduce yourself to three you don't. This is the substrate on which any dispatch system runs — actual human connection at the proximity level.

Exercise 2: Stand up a seven-person network. Put seven people you trust in a group chat. Call it something simple (your street name plus "Aid"). Set a simple principle: "If anyone here needs help, say so in this chat. If you can help, say so." Run it for six months with zero infrastructure beyond the chat. See what emerges.

Exercise 3: Audit your local mutual aid landscape. Search "[your neighborhood] mutual aid" and see what exists. Join one. Volunteer for one shift. Notice how the dispatch works — or doesn't. Take notes. You're learning the system from the inside.

Exercise 4: Build a personal dispatch fund. Set aside a small amount every month ($20, $50, whatever you can). Label it "mutual aid" in your accounting. Commit to distributing it within 30 days when a request reaches you. This trains your own readiness.

Exercise 5: Write the one-pager. If your network went viral tomorrow, what would you need? Write a one-page document: intake process, volunteer onboarding, dispatch workflow, point of contact. This forces clarity. Share it with two others. Revise.

For the reader who wants the academic substrate:

- Spade, Dean. Mutual Aid: Building Solidarity During This Crisis (and the Next). Verso, 2020. - Chenoweth, Erica, and Maria Stephan. Why Civil Resistance Works. Columbia University Press, 2011. Not directly about mutual aid but foundational on horizontal organizing. - Solnit, Rebecca. A Paradise Built in Hell: The Extraordinary Communities That Arise in Disaster. Viking, 2009. The origin text for understanding why disaster uncovers human cooperation. - Kropotkin, Peter. Mutual Aid: A Factor of Evolution. 1902. The OG. - Big Door Brigade. Various organizing guides. bigdoorbrigade.com. - Aldrich, Daniel P. Building Resilience: Social Capital in Post-Disaster Recovery. University of Chicago Press, 2012. Research on why disaster recovery tracks social capital more than it tracks formal aid. - Homeland Security study on Occupy Sandy: "Project Recovery — Case Study of Occupy Sandy." 2014. - Mathews, Sarah Thankam. Various essays on Bed-Stuy Strong. - Mutual Aid Disaster Relief. Field guides at mutualaiddisasterrelief.org.

Here's what bothers me. Every community has people who want to help. Every community has people who need help. The failure isn't of will. The failure is of connection.

Dispatch is connection. It's the wire that lets electricity flow from the source to the need.

If every U.S. zip code (roughly 42,000) had one competent dispatch system with a group of 30 trained volunteers — that's 1.26 million volunteers — basically every food-insecure household, every homebound senior, every family drowning in medical bills could get connected to neighbor-level help within 48 hours.

That's not utopia. That's a spreadsheet problem.

The premise of Law 1 is if every person said yes, world hunger ends. Dispatch is the mechanism by which yeses become groceries. It is not glamorous. It is the hinge the whole thing turns on.

Build the dispatch system. Build it now, before the next thing. Practice it on small needs so the muscle is there when a big need arrives.

That's the work.