For emergencies, call 911.Lucas + Sentinel · Detailr Corp

Why Lucas and Sentinel

A clearer connection between residents and departments.

Consider Lucas and Sentinel when your goal is to connect identifiable public updates with useful incoming information. Evaluate the full workflow and the responsibilities behind it.

One connected exchange, two distinct experiences

Lucas gives residents a place to read participating departments’ information and contribute relevant observations. Sentinel gives authorized agency staff a workspace for publishing and review. That connection is the central reason to consider the products together: the public request and the information it brings back belong to the same task.

Start an evaluation with that complete exchange. Ask what the resident sees, where the reply goes and who owns the next action. A channel that reaches people still needs a staffed process for what comes back.

Source: See the connected workflow

Follow relevant departments across your routine

Home, work and family may involve different jurisdictions. Lucas supports following more than one participating department in one resident app, with the issuer kept visible. That can make an update easier to place in the right local context.

Confirm participation for each department you want to follow. A researched city page is a guide to sources, not proof that its agency has joined Lucas.

Source: Explore following departments

Keep the issuing agency recognizable

A resident should be able to identify the department behind an update. Lucas is intended for vetted participating agencies rather than an open feed where anyone can present themselves as a department. Recognizable sources help people choose where to look for clarification.

Read the issuer, publication time and subsequent instructions before acting on or forwarding a message. Vetting does not make every message complete or remove the need for corrections.

Source: Read about agency updates

Give a request a defined geographic purpose

Sentinel’s public-alert workflow is built around the affected area, the message and the requested action. An area-specific request can explain which observations are relevant without treating every person in a region as the audience for every notice.

During a demonstration, inspect how staff choose the area and how the resident understands it. Ask separately about supported devices and notification permissions; a selected boundary is not a delivery guarantee.

Source: Review area-specific requests

Give residents enough context to contribute

An alert can draw attention to a fuller agency update. Residents can use that detail to understand the place, time and information requested, instead of trying to infer the whole situation from a short notification.

For a fictional evaluation, publish a clearly labelled test request about observations from a defined place and time. Ask a reviewer unfamiliar with the scenario to explain what it asks. This tests the clarity of the example; it is not an investigative result.

Source: Understand useful observations

Direct information to a participating agency

Where reporting is active, Lucas supports information connected to an agency update and standalone tips to a selected participating agency. Choosing the intended recipient helps distinguish a useful submission from a public comment that may never reach the responsible team.

Check the recipient and the supported attachment options before sending. Use 911 for an emergency. A tip channel is not dispatch, and submission does not promise immediate review or a personal reply.

Source: Choose the right reporting channel

Keep incoming work connected to its review status

Sentinel’s published product description includes reviewing tips, updating their status and connecting them to cases. This gives a department concrete tasks to examine during evaluation: find the submission, understand its context and record what happens next.

Use marked test material to follow a handoff. Verify the exact current actions, including assignments and internal notes, against the application your department would use. A status field does not establish staffing, response time or an outcome.

Source: Inspect tip management

Preserve the distinction between agencies

A shared resident experience does not require a shared police command. Sentinel is designed around department workspaces, while Lucas connects the sources a resident follows. This distinction matters when an agency decides who publishes information and who handles a submission.

Ask how the current implementation enforces the boundaries your agency needs. Do not infer unrestricted cross-agency access or a security certification from a workspace diagram.

Source: Review agency boundaries

Make personnel access part of the evaluation

The Sentinel listing describes joining with a department code and department approval before data becomes visible. Agency administration and personnel responsibilities are therefore practical parts of the conversation, not just background setup.

Inspect an authorized test account’s approval and ask how role changes or departures are handled. Record software behavior and the agency’s own authorization procedure separately so one is not mistaken for the other.

Source: Evaluate personnel access

Start with an operational evaluation

The implementation and evaluation resources help a department define a publishing owner, review responsibility, escalation route and questions for the team. The useful next step is a demonstration against your process, rather than a claim that every department needs the same setup.

Jacob Brink leads product and business direction; Trey Everett Hugan leads technical development. Bring one real operating need to the discussion, using fictional material for the demonstration and keeping sensitive reports out of the business inquiry channel.

Source: Use the evaluation worksheet

Who the products fit and what to check first

For a resident, the starting questions are whether the relevant department participates and which current app features are available. Keep official city, county and emergency warning channels as well. Lucas is not a live police-radio service or a substitute for emergency assistance.

For an agency, the fit depends on the communication task, authorized users, staffing, records requirements and the implementation you can demonstrate. If you need certified controls, a specified delivery commitment or integration with an existing system, obtain the corresponding evidence before relying on it.

Use the ten reasons as evaluation criteria, not a comparative ranking. An appropriate demonstration should show which requirements are met, which need clarification and which belong to another channel or system.

Source: Notification limits · Discuss an agency evaluation

Your next step

A clearer way to stay informed and contribute.