An alert goes out. Actionable information comes back.

A participating agency uses Sentinel to prepare public information through the available publishing features. The agency decides its purpose, contents, and public instructions.

Lucas brings information from the participating agencies a resident follows into a single citizen experience. Following multiple agencies reflects the way people move across municipal boundaries.

Where reporting is active, a resident can send a tip connected to a post or direct a standalone submission to a selected participating agency.

The receiving agency is responsible for its review and decisions. Neither submission nor delivery guarantees a response.

Profile visibility, location permission, information sharing, and records after delivery have practical limits. Our trust pages explain those limits and link to the published consumer policies.

Consider an illustrative public request about a missing item. A department publishes the relevant description and asks for information. A follower reads the detail, recognizes a potentially useful observation and provides a factual account through the supported reporting path. The receiving department then decides whether the information belongs with a case or needs another action.

The value is in the continuity of that exchange: a clear request, understandable context and an identifiable recipient. A notification alone is only the beginning. Every stage should make sense to the person using it, including the privacy choices and the limits on review or response.

An observation can become relevant while someone is outside the issuing department’s city. The intended Lucas and Sentinel network allows the citizen experience to span places while preserving agency responsibility. The available reporting path and recipient still need to be checked; geography does not grant unrestricted access to another department’s records.

That creates an opportunity for participation beyond a single roadside observation point. It also creates an obligation to explain the workflow honestly. Relevance, lawful sharing and agency review remain essential. The network is intended to help information reach the appropriate place, not to turn residents into investigators.

An example department publishes a request about a missing child. It provides the description it is prepared to release, an approximate relevant period and a route for information. A resident who follows that participating department opens the update in Lucas and reads the details.

Later, the resident remembers seeing a child with some of the described features near a community building. They describe what they saw, identify the place and label the time as approximate. The account does not claim to confirm an identity or explain the full situation. It gives the agency information it can assess alongside other material.

The department receives the submission through the supported workflow and decides what to do with it. This fictional sequence explains the intended relationship between the products. It is not a recovered-property story, a real agency partnership or a promise of a response.

Following a department changes which sources a resident chooses to keep up with. It does not enroll the person in every local warning service. Reading an update gives the department’s account at a particular time; a later correction can change what the reader should do.

Sending a tip is another decision. The submission can include personal information in the account or attachment, regardless of some profile-visibility settings. Once delivered, the agency may hold its own copy under its policies and legal obligations.

The resident app and department workspace therefore connect distinct decisions rather than removing them. Useful design makes the source, recipient and next step understandable. The complete Terms and Privacy Policy explain the consumer service’s conditions and information practices.

Source: Lucas Privacy Policy, effective September 14, 2026 · Lucas Terms of Service, effective September 14, 2026

An automated license plate record concerns a vehicle observation. A resident’s account can describe a person, an item or an event that was not captured by that camera. Neither kind of information explains every circumstance by itself. Both require a source, relevant detail and assessment.

Official emergency warnings serve another role again. Wireless Emergency Alerts can reach compatible phones through participating carriers without a department-app subscription. Keep those channels enabled and use current official instructions in an emergency.

Lucas and Sentinel are intended to add a dedicated place for participating department updates and relevant community information. To understand the current fit, residents can check availability and department participation; agency teams can review the product and operating requirements with us.

Source: National Weather Service: Wireless Emergency Alerts