Channel Structure
Channel Structure
Section titled “Channel Structure”Effective rapid response requires organized communication channels with appropriate security levels. This guide covers the recommended channel structure.
Recommended Channels
Section titled “Recommended Channels”| Channel | Platform | Purpose | Membership | Risk Level |
|---|---|---|---|---|
| Relay | Signal | Cross-neighborhood coordination | Admins of citywide teams | Highest |
| Admin | Signal | Central RR coordination | Core admin team | Highest |
| Verifier | Signal | Verification requests and reports | Admins, Verifiers, Mobile Support | High |
| Patrol | Signal | Patrol communication | Admins, Patrollers, Mobile Support | Medium-High |
| Broadcast | Signal/WhatsApp | Community alerts | Community members | Low |
| Social Media | IG, FB, etc. | Public information | Public | Low |
Channel Details
Section titled “Channel Details”Relay Channel
Section titled “Relay Channel”Purpose: Cross-neighborhood coordination of rapid response
Use for:
- Tipping off other neighborhoods of activity
- Sharing resources (e.g., plate information)
- Strategizing across networks
Membership: Admins of citywide teams only Vetting: Highest - must be highly vetted
Rapid Response Admin Channel
Section titled “Rapid Response Admin Channel”Purpose: Central coordination
Use for:
- Coordinating schedules
- Updating crucial info (e.g., new plates)
- Strategizing
- Incident management
Membership: Core admin team only Vetting: Highest - must be highly vetted
Rapid Response Verifier Channel
Section titled “Rapid Response Verifier Channel”Purpose: Share verification requests and confirmed sightings
Use for:
- Requesting verification of sightings
- Reporting verification results
- Coordinating verifier deployment
Membership:
- Admins
- Verifiers
- Mobile Support
- Additional stakeholders (other RR team admins, school patrol leads)
Vetting: High - should be highly vetted
Community Patrol Channel
Section titled “Community Patrol Channel”Purpose: Share patrol observations and requests
Use for:
- Patrol assignments
- Observations during patrol
- Coordination between patrollers
Membership:
- Admins
- Patrollers
- Mobile Support
Vetting: Medium-High - at least lightly vetted
ICE Watch Broadcast Channel
Section titled “ICE Watch Broadcast Channel”Purpose: Inform community members of ICE activity
Use for:
- Confirmed activity alerts
- Daily debriefs
- All-clear notifications
Membership: Community members, vulnerable individuals Vetting: None required - public-facing
Important: Only share confirmed information in broadcast channels.
Social Media
Section titled “Social Media”Purpose: Public information sharing
Use for:
- Confirmed alerts
- Know Your Rights information
- Community resources
- Training announcements
Membership: Public Vetting: None - public facing
Channel Security Levels
Section titled “Channel Security Levels”Highest Security (Admin, Relay)
Section titled “Highest Security (Admin, Relay)”- Require personal reference from existing trusted member
- Phone/video interview
- Protocol review and agreement
- Ongoing participation expectations
- Immediate removal if trust violated
High Security (Verifier)
Section titled “High Security (Verifier)”- Encrypted form submission
- Reference check
- Training verification
- Protocol acknowledgment
Medium Security (Patrol)
Section titled “Medium Security (Patrol)”- Admin approval required to join
- Vetting questions via Signal
- Protocol review
Low Security (Broadcast, Social)
Section titled “Low Security (Broadcast, Social)”- No vetting required
- Information shared should be safe if seen by anyone
- No sensitive details (exact locations during active incidents, volunteer info)
Best Practices for Each Channel Type
Section titled “Best Practices for Each Channel Type”In Vetted Channels (Admin, Verifier, Patrol)
Section titled “In Vetted Channels (Admin, Verifier, Patrol)”- Share SALUTE details including specific locations
- Discuss strategy and deployment
- Coordinate in real-time during incidents
- Share volunteer information as needed
In Unvetted Channels (Broadcast)
Section titled “In Unvetted Channels (Broadcast)”- Limit detail - Share only necessary information
- Use general language - “activity confirmed in the area” vs. “ICE at 123 Main St”
- Delay sensitive updates - Vetted channels first, broadcast after situation stabilizes
- No identifiers - Never post photos or names of detained individuals
- Standardized phrases - Use agreed formats like “Status: Clear” or “Verification: Pending”
Managing Channel Discipline
Section titled “Managing Channel Discipline”During Active Incidents
Section titled “During Active Incidents”Keep channels clear for operational communication:
“We have an active verification in progress. Please keep the chat clear unless you have something to report or verify.”
After Incidents
Section titled “After Incidents”“All clear. Thank you for the response. Regular chat may resume.”
Unrelated Messages
Section titled “Unrelated Messages”Redirect non-urgent discussion to appropriate channels or times.
Platform Recommendations
Section titled “Platform Recommendations”Signal (Preferred)
Section titled “Signal (Preferred)”- End-to-end encrypted
- Disappearing messages option
- Username feature hides phone numbers
- Groups up to 1000 members
WhatsApp (Backup for Broadcast)
Section titled “WhatsApp (Backup for Broadcast)”- More widely used in some communities
- Broadcast channels keep phone numbers private
- Owned by Meta - less secure than Signal
- Useful for reaching people already on WhatsApp
- Regular SMS/text
- Facebook Messenger
- Instagram DMs
- Any platform without end-to-end encryption
Setting Up Signal Groups
Section titled “Setting Up Signal Groups”- Create new group
- Set group name clearly (e.g., “[Area] ICE Watch Verifiers”)
- Add description with rules
- Set admin permissions appropriately
- Enable “Admin Approval” for joining if applicable
- Consider disappearing messages settings
- Add initial trusted members
See Signal Setup for detailed instructions.