Reviewing ICE Reports
Understand the process of reviewing reports before publication.
Reviewing ICE Reports
Reviewing ICE reports is one of the most sensitive and impactful responsibilities in the ICE Tea ecosystem. It ensures that public information is trustworthy β protecting our communities with truth, not panic or misinformation.
Info
This course is for certified dispatchers and reviewers only. If youβre here, your choices impact real-world safety and trust.
Why Review Reports?
Before a report is published:
- It must be verified for accuracy and safety.
- It must comply with privacy and metadata standards.
- It should deliver clear, actionable information β not rumors or speculation.
Reviewers are the final human checkpoint before the report enters the public heatmap or dispatch system.
The Report Review Lifecycle
[Report Submitted]
β³ [Automated Filters] (spam, GPS errors)
[Human Review]
β³ [Reject]
β³ [Verify]
β³ [Publish] or [Archive]
What You Receive in a Report
Each submission may include:
- π Location (GPS and typed address)
- π Time (auto-recorded + manual)
- π Description (who/what/where)
- πΈ Optional Media (photos or video)
- βοΈ Contact Option (may be anonymous)
Advanced reviewers may also see:
- π Prior reports from same IP/device
- π§ Duplicate detection flags
- π§Ύ Media metadata (EXIF, GPS, timestamp)
Valid Reports: What to Look For
Component | What Youβre Looking For |
---|---|
Location | Real place that matches the pin or street name |
Time | Recent and realistic (not days old) |
Description | First-person, focused on visible facts |
Media | Optional, but should support the claim |
Reasons to Reject a Report
- Vague or secondhand info: "I heard ICE is nearby"
- Disinformation signs: reused text, panic words, outdated timestamps
- False or troll-like: GPS in oceans, random insults
- Unverifiable: No clear time, place, or context
- Duplicate: Same device sent similar text within minutes
If unclear but not suspicious, use βSend Backβ to request more detail.
Examples: What Would You Do?
β Example A
βSaw 4 ICE agents outside the courthouse on 7th Street at 10:30am. Black SUV, CA plates.β
Accept β Includes all necessary info.
β Example B
βTheyβre everywhere. ICE is rounding up people!β
Reject β Too vague and panic-inducing.
π‘ Example C
βICE checkpoint on Main & Rose, 3 cars turning people away.β
Needs clarification β Ask for details. Are these ICE agents? Whatβs visible?
Respecting Anonymity
Many submitters are undocumented or at risk.
- π« Never try to identify or trace a user.
- π΅οΈββοΈ Do not search media metadata beyond the platform.
- π If faces or license plates are visible, redact or reject.
Even well-meaning leaks can endanger real lives.
When In Doubt: Use Context
Use your regional knowledge and recent activity logs:
- Is the location known for ICE patterns?
- Is the report consistent with others in the system?
- Does the timestamp make sense?
Warning
Be cautious of panic reports, sudden shifts in tone, or reused language.
Red Flags for Disinformation
Watch for:
- π© Timestamps 6+ hours old labeled as βurgentβ
- π© Reports that reuse identical phrases across time/zones
- π© Panic language: βTheyβre everywhere!β / βMass raids!!β
- π© Media mismatch: different weather, time of day
- π© GPS in the ocean or unrelated countries
Tag and escalate these when in doubt.
Notes for Escalation
If something feels off:
- π§ Use βTag for Senior Reviewβ if available
- βοΈ Leave a moderation note explaining your concern
- π± Use internal comms (Signal/Discord) for rapid escalation
Publish, Send Back, or Reject?
Action | Use When |
---|---|
β Publish | All required info is present and trustworthy |
π Send Back | Missing key details, but not malicious |
β Reject | Clearly false, harmful, duplicated, or unverifiable |
Always log your decision. The audit trail builds long-term trust.
Legal & Ethical Boundaries
- π« Do not use reverse-search tools outside platform guidance.
- π§ Do not share media with friends or on social media.
- π‘οΈ Redact all personally identifying visuals unless explicitly authorized.
Reviewer Tools
You may use:
- πΊοΈ Heatmap comparison tab
- π°οΈ Timestamp converters (if multiple timezones in play)
- π§Ύ Metadata tools (in-app only)
Never export or manipulate report data externally.
Tips for Reliable Reviewing
- Keep the live heatmap open for side-by-side checking.
- Look for subtle cues like agent description and street names.
- Donβt rush: quality > quantity.
βOur credibility lives or dies in the details. Be rigorous. Be human. Be brave.β
Summary
- You are the final checkpoint for accuracy and harm prevention.
- Use evidence, not urgency, to guide decisions.
- Respect privacy and community risk.
- Escalate uncertainty β and protect trust in the process.
π Knowledge Check
What is the primary purpose of the report review process?
You should reject any report that is submitted anonymously.
Which of the following are valid reasons to reject a report during review?
What information should you confirm when reviewing a valid report?
A report says: "ICE at Elm & 22nd. Two vans. One person detained. Happened 15 mins ago." No media is attached. The location checks out and is known for activity. What should you do?
It is acceptable to share submitted media with other volunteers outside the review platform if urgent.
If youβre unsure about a reportβs authenticity, what should you do before publishing?
Which detail might suggest a report is disinformation or fake?
A report includes a close-up image of a detaineeβs face. What is the correct action?
π« You must register and log in to mark this lesson as qualified. Registering helps us track progress, verify training, and build trust across our network.
You can use your Dispatch login here if you already created an account there. Likewise, creating an account here will let you use the same credentials on Dispatch.
Complete and pass the quiz above to unlock this button. Youβll need at least 80% correct.