Crisis Activation

*The need:* When disaster strikes, official systems fail exactly when most needed.

When disaster strikes (storms, violence, pandemic, raids) existing systems fail exactly when they are needed most. This recipe pre-builds lightweight infrastructure (communication channels, resource maps, story collection, mutual aid networks) that can activate instantly when a crisis hits, so communities self-organize in the absence of official help rather than waiting for bureaucracy or top-down allocation. Prepare during calm because a crisis is too late to organize, treat the first 48 hours as the ones that matter most, treat information as being as vital as physical resources, document stories immediately, and keep the infrastructure warm between crises with small activations.

How it works

1. Map the crises your community faces, such as floods, ICE raids, violence, or blackouts.
2. Build response templates before you need them.
3. Create an activation protocol: who decides it is time, and how to alert the group.
4. Run practice activations for small needs.
5. When a crisis hits, activate within hours, not days.
6. Focus on information, stories, resources, and connection.
7. Document everything for next time.
8. Sunset when no longer needed, but keep the infrastructure ready.

Ingredients

• 5-7 committed activators
• pre-established channels (WhatsApp/text trees)
• a list of who has what
• a trusted space
• pre-written templates
• an activation protocol

Minimum resources: Free if volunteer, better with an emergency fund.

You'll know it's working when

• response activates in hours not days
• official responders ask the community what's needed
• 'the community showed up before anyone else'

Field tips

• prepare during calm
• first 48 hours matter most
• information is as vital as physical resources
• keep infrastructure warm with small activations

Building from (real projects)

• Sandy Storyline
• Boulder Reporting Lab Pop-Up Newsroom
• FYLPRO COVID-19 Task Force

Details

• size: meal
• patterns: mobilizing_collective_response, deepening_understanding_of_place
• civic need: wellbeing.safety, wellbeing.physical, belonging.connection, agency.power
• field tips: prepare during calm, first 48 hours matter most, information is as vital as physical resources, keep infrastructure warm with small activations
• source tag: CB
• timeliness: emergency
• ingredients: 5-7 committed activators, pre-established channels (WhatsApp/text trees), a list of who has what, a trusted space, pre-written templates, an activation protocol
• source note: From the Civic Media Cookbook: 'Producing Civic Media: Recipes to Produce Civic Media Through Participation, Power and Community' — Jihii Jolly and Jennifer Brandel, with the News Futures Working Group (2026).
• how it works: Map the crises your community faces, such as floods, ICE raids, violence, or blackouts., Build response templates before you need them., Create an activation protocol: who decides it is time, and how to alert the group., Run practice activations for small needs., When a crisis hits, activate within hours, not days., Focus on information, stories, resources, and connection., Document everything for next time., Sunset when no longer needed, but keep the infrastructure ready.
• building from: Sandy Storyline, Boulder Reporting Lab Pop-Up Newsroom, FYLPRO COVID-19 Task Force
• min resources: Free if volunteer, better with an emergency fund.
• need it meets: When disaster strikes, official systems fail exactly when most needed.
• practice kind: recipe
• success signals: response activates in hours not days, official responders ask the community what's needed, 'the community showed up before anyone else'
• charter alignment: news_as_care, doocracy
• participatory nature: collective_action, collective_care
• conceptual ingredients: reciprocity, trust