USER GUIDE

A patrol workflow that
stays out of your way.

PatrolPath is designed so most interaction can wait. Start the patrol, timestamp what matters, then do the detailed review when the driving is done.

01

Prepare Patrol

Choose the configured state and patrol area, then confirm the start time. PatrolPath loads the supported road dataset for that area, retrieves current weather, and checks the built-in GPS.

02

Start Patrol

Begin the patrol and let PatrolPath match stable GPS samples to nearby roads. Several samples are required before a road is added, helping reduce false matches around intersections.

03

Timestamp activity

Use the one-tap Traffic Stop, Call for Service, and Other Activity buttons when something happens. Add the details then or wait until the end of the patrol.

04

End and review

End Patrol opens the review screen. Correct the road list, confirm start/end times and weather, add ticket and warning totals, and finish event details.

05

Send it to CAD

Copy the finished CAD-ready narrative to the clipboard or save the generated text file. PatrolPath never needs CAD credentials.

OFFLINE USE

Road data is cached

Supported road data for the patrol area is cached on the MDT for 30 days. A later patrol can use the cached copy when a refresh is unavailable.

RECOVERY

In-progress patrols recover

PatrolPath keeps local crash-recovery data so a laptop restart does not automatically mean losing the patrol you were documenting.

PRIVACY

Raw GPS is not saved

Live coordinates are used in memory for road matching. Raw GPS coordinates are not written into the patrol recovery file or sent to the license service.

BEFORE OPERATIONAL USE

Field-test it on your MDT.

Validate the current PatrolPath release, GPS behavior, and map matching on known local roads before relying on it for operational documentation.