urAnimalControl
Nobody should need to know whose job it is.
A resident with a loose dog, an injured cat or a welfare concern should be able to say what they saw and have it reach whoever is actually responsible. Officers get the field side of the same record.
One report. One accountable journey.
Follow a fictional demonstration from the public form through dispatch, field work, identity review and supervisor-governed records. These are live mobile screens from the working demo sandbox.
Demonstration only — every person, address, animal and case shown below is fictional.
Step 01
A resident reports what they observed
No account is required. The form separates observation from conclusions and makes the reporting choice explicit.

Live mobile workflow · fictional demonstration data Step 02
The report becomes an agency call
The original words, routed authority, fictional location and public reference stay together for dispatch.

Live mobile workflow · fictional demonstration data Step 03
Field work continues offline
An officer can queue an update on the device and synchronize it when the connection returns.

Live mobile workflow · fictional demonstration data Step 04
Identity remains a human decision
Microchip and urLifePrint candidates are suggestions. No scan or model result silently creates a permanent identity.

Live mobile workflow · fictional demonstration data Step 05
A supervisor records the determination
The allegation, direct observation, rationale and human decision remain distinct and reviewable.

Live mobile workflow · fictional demonstration data Step 06
Disclosure and preservation are governed
A versioned disclosure package records redactions, while a legal hold preserves the underlying demo records.

Live mobile workflow · fictional demonstration data
Field context that reads like a report
LABRIE turns terrain, weather, access and nearby features into an officer-readable snapshot, with an interactive USGS topographic view when the map matters.
Your units, by default
A topographic response view
Context preserved with the incident


Field equipment with an accountable chain
Responder tag kits remain visible from readiness through handoff, return and supervisor recount. These mobile screens use isolated fictional demonstration records.
Step 01
Know what is ready before deployment
Supervisors can see each responder kit, its assigned jurisdiction and whether every expected tag is physically accounted for.

Live mobile workflow · fictional demonstration data Step 02
Reconcile every handoff
Issue, transfer, return and recount events preserve who handled a kit and when, without replacing the underlying history.

Live mobile workflow · fictional demonstration data Step 03
Escalate discrepancies for review
A supervisor recount records the discrepancy and its audit trail so missing equipment becomes visible work, not a silent inventory edit.

Live mobile workflow · fictional demonstration data
For residents
Jurisdiction is our problem, not yours. Say what you saw and where; we match the location to the responsible authority where we have one on file.
Report a concern
In progress
Lost and found
Anonymous if you need it
For officers — what exists today
Being straight about this matters more than a longer list. Signing in gives you the field tools that are actually built.
Scan in the field
Stray holds
Calls and dispatch
Bites and rabies
Disposition
Compliance
Intake and custody
Evidence and field context
Deliberately deferred integrations
These interfaces are outside the first working journey and remain disabled until they have a registry entry, an agency agreement and their own security review.
CAD, RMS and courts
Planned
Public health and disaster command
Planned