Version 2.1

Reviewing ICE Reports

Understand the process of reviewing reports before publication.

22 min readΒ·Qualified Lesson

Reviewing ICE Reports

Tech & Comms Track
Observation & Legal Track

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

ComponentWhat You’re Looking For
LocationReal place that matches the pin or street name
TimeRecent and realistic (not days old)
DescriptionFirst-person, focused on visible facts
MediaOptional, 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?

ActionUse When
βœ… PublishAll required info is present and trustworthy
πŸ”„ Send BackMissing key details, but not malicious
❌ RejectClearly false, harmful, duplicated, or unverifiable

Always log your decision. The audit trail builds long-term trust.


  • 🚫 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.