Skip to content

Starting a Network

Building a rapid response network from scratch requires patience, relationships, and organization. This guide covers how to get started.

  • Is there an existing network in your area?
  • Who else is doing this work locally?
  • What organizations serve immigrant communities here?
  • What resources do you have to contribute?

If a network exists: Join it rather than starting a competing one. Reach out, get trained, and plug in.

If nothing exists: Read on.

Your community:

  • Who lives in your neighborhood?
  • What languages are spoken?
  • Where do people gather?
  • What are the specific threats?

Your resources:

  • Who do you know who might join?
  • What organizations might partner?
  • What time can you commit?
  • What skills do you bring?

Start with people you trust:

  • Friends who care about this issue
  • Members of organizations you belong to
  • Neighbors you know well
  • Colleagues or classmates

When talking to potential members:

  • Explain what rapid response means
  • Be clear about the commitment
  • Listen to their concerns
  • Don’t pressure anyone

Your initial team (3-5 people) should:

  • Be committed to this work
  • Have time to contribute
  • Represent some diversity (skills, availability, connections)
  • Trust each other

Agenda for your first organizing meeting:

  1. Why are we doing this?
  2. What does rapid response look like?
  3. What are our goals?
  4. What resources do we have?
  5. What do we need?
  6. What are our next steps?

Geographic area:

  • Neighborhood-focused
  • City-wide
  • County or region

Start small. It’s easier to expand than to contract.

What will you do?

  • Community alerts
  • Patrol/monitoring
  • Response to incidents
  • Documentation
  • Family support
  • Legal connection
  • Know Your Rights education

Start with what you can do well. Add services as you grow.

Flat structure:

  • Everyone shares responsibilities
  • Decision-making is collective
  • Works for very small groups

Tiered structure:

  • Admins coordinate
  • Verifiers confirm reports
  • Patrol members observe
  • Broadcast reaches wider community

Most networks use some form of tiered structure.

Signal is recommended because:

  • End-to-end encryption
  • Disappearing messages option
  • Group functionality
  • Free and widely used

Basic structure:

  1. Admin channel - Coordinators only
  2. Verifier channel - Verified rapid responders
  3. Patrol channel - Neighborhood monitors
  4. Broadcast channel - Wider community alerts

Establish:

  • Who can post to each channel
  • What kind of information goes where
  • How to verify before broadcasting
  • When to use which channel
  1. Verification protocol - How to confirm reports
  2. Broadcast protocol - When and what to share
  3. Response protocol - How to respond to incidents
  4. Safety protocol - How to keep people safe
  5. Vetting protocol - How to add new members

Keep them:

  • Clear and simple
  • Easy to follow under stress
  • Realistic for your capacity
  • Updated as you learn

Everyone should:

  • Read the protocols
  • Practice scenarios
  • Ask questions
  • Know where to find them

Create different entry points:

  1. Broadcast only - Receive alerts (low barrier)
  2. Patrol - Monitor and report (medium barrier)
  3. Verifier - Confirm reports, respond (higher barrier)
  4. Admin - Coordinate operations (highest barrier)
  • Partner organizations
  • Community events
  • Know Your Rights trainings
  • Word of mouth
  • Faith communities
  • Mutual aid networks

New members should:

  1. Understand the mission
  2. Receive training
  3. Know their role
  4. Have access to resources
  5. Feel welcomed

Reach out to:

  • Immigrant rights organizations
  • Legal aid societies
  • Faith communities
  • Labor unions
  • Community centers
  • Mutual aid networks
  • Legitimacy
  • Resources
  • Volunteers
  • Expertise
  • Connections
  • Physical space
  • Communicate clearly
  • Respect their expertise
  • Follow through on commitments
  • Share credit
  • Build relationships, not just transactions

All members should be trained on:

  • Mission and goals
  • Know Your Rights
  • SALUTE reporting
  • Communication protocols
  • Safety protocols
  • Their specific role

Regular trainings:

  • Refreshers on protocols
  • Updates on ICE tactics
  • New member orientations
  • Scenario practice
  • Create your own materials
  • Adapt existing resources
  • Partner with experienced organizations
  • Bring in experts when needed

Before going public:

  • Test your systems
  • Run scenarios
  • Work out kinks
  • Build confidence

When ready:

  • Announce through partners
  • Host a launch event
  • Open recruitment
  • Begin operations

Be clear about:

  • What you can do
  • What you can’t do
  • How to reach you
  • Response times

Common mistake: Adding people faster than you can train them.

Better approach:

  • Grow slowly
  • Train thoroughly
  • Build trust
  • Expand capacity before expanding membership
  • Share leadership
  • Rotate responsibilities
  • Prevent burnout
  • Celebrate successes
  • Rest when needed

Regularly assess:

  • What’s working?
  • What’s not working?
  • What have we learned?
  • What do we need to change?
  • Start with what you have
  • Do what you can
  • Build slowly
  • Partner for capacity
  • Are alerts reaching people?
  • Is the channel too noisy?
  • Are people trained?
  • Is the commitment clear?
  • Share the load
  • Create rotation schedules
  • Set boundaries
  • Take breaks as a team
  • That’s normal at first
  • Learn from each incident
  • Get training
  • Connect with experienced networks
  • United We Dream
  • National Immigration Law Center
  • ACLU
  • Immigrant Defense Project
  • States at the Core (STAC)
  • Local immigrant rights organizations
  • Legal observer trainings
  • Protect RP (Chicago)
  • NYSLYC ICE Watch (New York)
  • Local models in your region

Phase 1: Foundation

  • Assessed community needs
  • Formed core team
  • Defined scope and services
  • Chose communication platform

Phase 2: Development

  • Created communication channels
  • Wrote basic protocols
  • Developed training materials
  • Connected with partners

Phase 3: Launch

  • Trained initial members
  • Tested systems
  • Soft launched operations
  • Public announcement

Phase 4: Growth

  • Ongoing recruitment
  • Regular training
  • Continuous improvement
  • Sustainable practices