MFA and deployment-bound sessions
Mandatory MFA enrollment, password policy, lockouts, refresh rotation, issuer and audience checks, and session revocation support authenticated agency access.
Patrol routing and coverage decision support
Turn patrol priorities into coordinated coverage.
GuidePost turns agency-approved historical incident patterns, patrol geography, and current fleet context into coordinated, inspectable patrol routes, then carries that context through interruptions and post-shift review.
- Place-based
- Fleet-aware
- Policy-governed
One coordinated shift
Watch command intent become field activity.
GuidePost keeps the plan, the interruption, the recovery, and the record in one continuous operating picture.
Illustrative GuidePost-managed manual dispatch workflow using a representative scenario and street-network geometry. No live agency or incident data. Assignment authority varies by agency configuration.
- Command coordinates coverage.Five units begin from one shared patrol plan.
- Command defines a patrol objective.Riverside North needs visible presence and a three-minute dwell.
- Unit B receives the focus route.GuidePost weighs proximity, priority, freshness, and shared coverage for the eligible officer.
- The directed objective is completed.Unit B reaches the focus and completes the assigned dwell.
- A service call interrupts Unit E.In this illustrative GuidePost-managed workflow, command assigns the closest estimated responder, with Unit C shown as fallback.
- The phone receives and acknowledges the assignment.The acknowledgement confirms receipt only; command retains dispatch authority.
- Vehicle guidance stays read only.The same route, objective, ETA, and status remain visible while actions stay on the primary phone app.
- Command clears the call.The assignment remains current until the authorized lifecycle event is received.
- Patrol resumes afterward.GuidePost refreshes Unit E's complete patrol route from its credible post-call position.
- Review turns the shift into evidence.Leadership sees representative coverage, directed-patrol distance, priority presence, route adjustments, and a next-shift action.
Illustrative shift recordInspect the evidence behind this shift.
Explore coverage, GPS, route-quality, timeline, heatmap, and export evidence without lengthening the autoplay story.
Product surfaces
One operating state, carried to each role.
Command
Fleet, coverage, and calls in one scoped picture.
Command can inspect patrol objectives, current routes, active resources, coverage context, open calls, candidate ranking, assignment ownership, and route availability. Consequential actions remain permission-scoped and auditable.
- Bounded patrol focus and dwell objectives
- Manual or configured automatic GuidePost assignment
- Visible alternatives and factual degraded states
Map layersStreet riskPatrol density
5 active unitsRiverside North · objective completeSouth River · coverage needed
Call 21-043 · priorityUnit E assignedAcknowledged · route available
Officer phone and PWA
The primary field surface for actions and recovery.
The phone keeps the current patrol or dispatch assignment, route guidance, dwell objective, connection state, and status actions together. Assigned-call acknowledgement confirms receipt; it does not reject or transfer dispatch ownership.
- Native phone and officer PWA surfaces
- GPS buffering, replay, and reconnect state
- Large field controls with explicit route notices
Route available
Receipt acknowledgedPrimary app
Vehicle
Route awareness that stays read only.
CarPlay and Android Auto presentations derive from the primary officer and device state. They show route, maneuver, objective, ETA, status, and degraded prompts, but do not authenticate, acknowledge calls, change status, mutate routes, or repair sessions.
- Read-only CarPlay and Android Auto presentations
- Primary-app prompts for actions and exceptions
- Distribution and physical head-unit gates remain deployment-specific
0.8 mi remaining
2 minETA 18:21
- Objective
- Respond
- ETA
- 2 min
- Status
- On call
Use primary phone app for acknowledgement and status
Review
Turn the route history into an inspectable shift record.
Review connects coverage gaps, officer comparison, GPS reliability, hotspot and dwell evidence, repeated corridors, route-quality evidence, filtered events, heatmap availability, recommendations, and authorized exports.
- Evidence retains time, scope, and operational context
- Heatmap and timeline views remain filterable
- Audit and export access follows permission scope
Operational resilience
Degraded is a state to explain, not a location to invent.
When signal or connectivity degrades, GuidePost keeps the current assignment visible, labels stale information, buffers eligible updates, and recovers from the last credible state.
No replacement location is fabricated. The officer stays assigned to call 21-043.
The device reports the buffered count. Dispatch ownership and the current assignment remain intact.
The field surface shows a route notice and directs the officer to the primary app or agency procedure.
Patrol resumes only after the call clears and GuidePost has a credible position from which to refresh the route.
Inspect the illustrative shift record
South River remained the clearest coverage gap at 58%. Unit B logged a three-minute Riverside North dwell with 98% representative GPS reliability. Unit E retained the dispatch assignment through connection and route state, then resumed patrol after command cleared the call. Review includes repeated-corridor, route-quality, filtered timeline, heatmap, audit, and authorized export availability.
How GuidePost works
Agency intent becomes a route that can be explained.
GuidePost supports patrol-routing and coverage decisions through a bounded operating chain. Each consequential transition remains visible to the people responsible for it.
Security & operations
Controls are implemented. Acceptance is environment-specific.
GuidePost is engineered for isolated agency deployments with explicit identity, scope, audit, recovery, and operating gates. Each agency validates the data scope and operating approval for its own environment.
Permissions, patrol visibility, and resources
Roles and permissions constrain command actions and visible patrol scopes. Resources, devices, units, officers, patrol groups, and their links retain explicit operational identity.
Audit records and change review
Operational and administrative events support scoped audit review and authorized export. Security-sensitive state changes fail closed; readiness surfaces factual audit degradation where applicable.
Encrypted backups and transactional restore
Backups are encrypted and deployment-bound, with signed evidence, serialized backup and restore, rollback-before-restart, and interrupted-recovery handling. Each target environment still needs off-host and recovery acceptance.
One agency environment, one active application node
A normal deployment isolates agency configuration and state on one active application node with purpose-specific service containers. Separate deployments represent real security or operational boundaries, not horizontal replicas.
Agency-specific authorization and operations
DNS and TLS, secret custody, approved sources, identities, risk artifacts, browser and runtime smoke, load evidence, audit, backup and restore, rollback, and operating approval are verified for each named environment.
Acceptance follows the agency environment.
CJI scope, CAD connectivity, operational capacity, and production approval are established and documented for each deployment.
Discuss your agency's acceptance pathWhy GuidePost
Place-based patrol support, governed by agency policy.
GuidePost helps agencies turn approved information into coordinated patrol coverage without turning operational support into enforcement automation.
Agency priorities go in.
Historical place-based patterns, patrol geography, available resources, and command intent define the operating context.
Routes and reasoning come out.
Command staff can inspect selected objectives, planned distance, coverage context, alternatives, and rejection reasons.
Dispatch authority follows agency policy.
GuidePost supports patrol and coverage decisions. It does not predict individual behavior or make stop, detention, arrest, charging, or use-of-force decisions.
A credible evaluation
Test the operating model.
An agency conversation can begin with one representative shift: approved data and geography, patrol scopes and roles, dispatch authority, debrief evidence, and the agency's governance and recovery expectations.
01Operational fit
Review how current patrol priorities, staffing, geography, and interruption policy would enter the system.
02Inspectable decisions
Examine selected factors, ranked alternatives, rejection reasons, route continuity, and post-shift evidence.
03Governance and resilience
Confirm access, visibility, audit records, data protection, recovery, and the agency's acceptance process.
04Agency boundaries
Confirm who enters incidents, who authorizes a response, which systems may connect, and what review is required before operational use.
CJI authorization and deployment acceptance remain specific to each agency environment.
Start with your operating reality
Bring us your patrol coverage problem.
Tell us how your agency plans patrol today, what information it trusts, and where command loses visibility. A first conversation focuses on operational fit, evaluation scope, and the questions your team must answer.
Direct email
quinn@guidepost-tech.com