Vetting Guidelines

Vetting Guidelines

Different roles require different levels of vetting. This guide covers how to vet appropriately for each security level.

Vetting Levels Overview

Level	Roles	Vetting Required
Low	Broadcast members	None
Medium	Patrollers	Basic questions
High	Verifiers	Form + references
Highest	Admins	Reference + interview

Low Risk: Broadcast (No Vetting)

Anyone can join broadcast channels, but manage them appropriately:

Best Practices

• Limit details shared (confirmed info only)
• Use general language (“activity in the area”)
• Never post identifying photos
• Regular reminders about appropriate sharing
• Admin monitoring for misuse

Rules for Unvetted Channels

Include in channel description:

This channel is for community alerts only.
- Only confirmed, general information is shared here
- Do not share locations of vulnerable individuals
- Do not share names or identifying details
- For more involvement, contact @admin

Medium Risk: Patrollers

Vetting Process

1. Set chat to require admin approval

2. When someone requests to join, ask:

   • How did you get connected to this group?
   • What are your cross streets? OR What’s your favorite spot in our neighborhood?
   • Have you been trained in rapid response/ICE Watch?
   • Are you available for at least one shift per week on average?

3. Evaluate responses:

   • Are they actually in the neighborhood?
   • Do they seem familiar with the area?
   • Is their interest genuine?
   • Any red flags in how they communicate?

4. If they pass: Add to chat

5. If uncertain: Ask additional questions or check with other admins

6. After joining: Send protocols document and confirm they understand

Red Flags

• Vague about location
• Unfamiliar with neighborhood landmarks
• Asks unusual questions about network members
• No apparent connection to the community
• Pushy or aggressive about joining

High Risk: Verifiers

Verifiers have access to sensitive location data and volunteer movements.

Vetting Process

1. Create an encrypted vetting form (e.g., on CryptPad)

Sample form questions:

• Full name
• Phone number (for Signal)
• Neighborhood / cross streets
• How did you hear about us?
• Why do you want to be a verifier?
• Have you attended ICE Watch training? When/where?
• Do you have flexible availability to respond?
• Can you provide a reference (someone in the network or allied org)?
• Any relevant experience (legal observation, community organizing, etc.)?

Example form: https://cryptpad.fr/form/...

2. Require references

   • Reach out to the reference directly
   • Confirm they can vouch for the person
   • Ask about reliability and judgment

3. Send protocols document

   • Share verifier protocols
   • Ask questions to ensure understanding
   • Require explicit acknowledgment

4. Check with your team

   • If anything feels off, discuss with other admins
   • Trust your collective judgment

Requirements for Verifiers

• Must be trained
• Must be available for regular shifts
• Must be connected to the community (live nearby or work in area)
• Must be on Signal
• Must have references
• Not recommended: Active duty law enforcement or military

Highest Risk: Admins

Admins have full access and make critical decisions.

Vetting Process

1. Start with existing verifier

   • Admins should come from proven verifiers
   • Already has track record with network

2. Require trusted reference

   • Someone you trust personally who can vouch
   • Not just any network member

3. Schedule a phone/video call

   • Get to know them
   • Discuss their interest and capacity
   • Review protocols together
   • Ask about their approach to difficult situations
   • Answer their questions

4. Probationary period

   • Start with limited admin responsibilities
   • Pair with experienced admin
   • Graduate to full access over time

Admin Interview Questions

• Why do you want to take on admin responsibilities?
• How much time can you commit?
• How would you handle [scenario]?
• What’s your experience with tense situations?
• Do you have any concerns about this work?
• Is there anything we should know?

Ongoing Security

Vetting isn’t one-time:

Monitor for Concerns

• Unusual questions about other members
• Sharing information inappropriately
• Inconsistent stories
• Behavior changes
• Reliability issues

If Concerns Arise

1. Discuss with admin team
2. Limit access if needed
3. Have a conversation with the person
4. Remove from sensitive channels if necessary
5. Document for future reference

Regular Review

• Periodically review member lists
• Remove inactive members from sensitive channels
• Update protocols as needed
• Retrain on security practices

Vetting is Not Discrimination

Vetting exists to protect:

• Vulnerable community members
• Active volunteers
• The network’s effectiveness

It’s okay to:

• Take time before adding someone
• Ask questions
• Trust your instincts
• Decline membership

It’s not okay to:

• Exclude based on race, ethnicity, religion
• Use vetting as gatekeeping for power
• Ignore red flags because someone is connected

Resources

• Example vetting form template: https://cryptpad.fr/form/#/2/form/view/...
• Example verifier protocols: https://drive.proton.me/urls/...