Sighting Intake · Command Center · Field Response

The Sighting Flow: From “I think I saw that loose pet...” to Verified, Actionable Information

What happens after someone reports a possible sighting? Each step is designed to protect pets, families, and Finders while turning chaotic tips into calm action and scientifically-based best practices.

High-Level Flow

A sighting moves through three lanes: Reporter, Command Console, and Field Finders. Only credible, location-ready sightings become deployments.

Visual Overview

1
Sighting is submitted
A member of the public, pet owner, or Finder submits a sighting via web, mobile, or QR-coded poster.
Best signals: time seen, exact-ish location, direction of travel, behavior, and a photo (only if safe).
2
Automatic mission matching
The system attempts to match the sighting to active missions nearby using species, description, and location.
If it doesn’t match, it’s queued for manual review before any field action.
3
Command Console triage
A trained Console Operator checks credibility, safety, and consistency with Behavioral GPS guidance.
Sightings get tagged: high priority, monitor, or no action.
4
Map placement + ring comparison
Verified sightings are placed on the mission map and compared to search rings to identify likely corridors.
The console updates the mission’s “last credible sighting” and refreshes guidance.
5
Deployment to Finders (if warranted)
Only when a sighting is credible and safe does the console issue assignments to trained Finders in-zone.
Assignments include: staging location, observation goals, and strict “do not chase” rules.
6
Outcome + feedback loop
Field teams report outcomes (confirmed, negative, moved, safety concern). The console logs and adapts the plan.
When appropriate, reporters can receive updates if their sighting helped.