What this guide covers
Plan the trip. Send it to the cab. Change it when operations change. See what the truck actually did. NavGuru connects the driver's navigation with the back office, and this guide is the dispatcher's and operations owner's side of it: where things are in the dashboard, how trips reach the cab, how to change a running trip, what live monitoring shows, how to read the compliance numbers, and how to trace a trip when something looks wrong.
Setup, the pilot test plan and troubleshooting live on Get started. What the driver sees is in the Driver guide.
Signing in and finding your fleet
The dashboard lives at platforms.mapup.ai/navguru/dashboard. First-time steps (log in, set your password, switch from your personal account to the fleet account, open NavGuru under Active Subscriptions) are on Access your NavGuru dashboard.
If your organization manages more than one fleet, the account switcher sits at the bottom left of the NavGuru dashboard. It lists every NavGuru account connected to yours; pick the fleet you want to work in. Dispatches, vehicles and reports are per fleet account.
If a page shows an error
Reload the page. If it keeps happening, do a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to clear the browser cache, then tell us. The rest of the dashboard stays available from the sidebar.
What is where
| Sidebar item | What you do there |
|---|---|
| Dashboard | Fleet overview: trips on route and off route right now, dispatches, reroutes, excess miles against plan, flagged trips, top vehicles by excess miles. Filter by period, vehicle or driver. |
| Live monitoring | Live: every vehicle currently navigating, on the map and in a list, with status and last update. Historical: every session, active or finished, by trip ID, vehicle, driver, status, source, reroutes, progress, distance and out-of-route miles. Open a session to follow it or replay it. |
| Dispatches | Create a dispatch, see dispatches that arrived from your TMS or Platform Science Workflow, open Details to see and edit stops. |
| Route compliance | Planned against actual per dispatch: on-route percentage, out-of-route miles, excess miles, deviations, and the driver and vehicle lists dispatch reviews. |
| Routing: Route planning | Plan and price a route without dispatching it. Useful for checking how a vehicle profile or a zone changes the route before you send it. |
| Routing: Setup | Route preferences, avoid zones, via points, geofences, driver alerts and Map explorer: the fleet's routing policy and zones. FuelGuru fuel stops (the fleet's network, prices, active or blocked) sit below. |
| Fleet | Vehicles, drivers and vehicle profiles (height, weight, length, axles, hazmat). |
| Reports and Settings | Reports; account settings and members. |
| Release notes | What changed in each release. NavGuru ships every two weeks. |
How a trip reaches the cab
Three paths, and they can run side by side.
- From your TMS through Platform Science Workflow. The job arrives on the tablet in Workflow as it always has. When the driver taps Navigate on a stop, NavGuru opens with that stop, and the dispatch shows in your Dispatches list with its stops in order. Nothing is re-keyed. On Platform Science each stop is driven as its own leg, so a multi-stop dispatch shows one NavGuru session per leg, all filed under the same dispatch.
- From the NavGuru dashboard. Create the dispatch under Dispatches: vehicle, driver, stops, and the route. It appears on the driver's device. On a Platform Science tablet the driver can accept a dashboard dispatch only when the truck is stopped; the tablet blocks app switching while moving.
- By API from your dispatch system. Same result as the dashboard. Your MapUp contact has the integration reference.
A vehicle shows in Live monitoring once its driver has started NavGuru and the truck moves. If you expect a truck and do not see it, the driver has not started navigation yet, or you are looking at a different fleet account.
Route choice and changes while the truck is moving
When you create or open a dispatch you see the route options for that vehicle profile: the practical route NavGuru recommends, alternatives, and the driver's choice where the fleet allows it. The route sent to the cab is the one the driver navigates; what the driver actually drives is compared against it afterwards (next section).
Changing a running trip. Edit the route or the stops in the dashboard. The change reaches the driver's screen in about two seconds without interrupting navigation. A mandatory change is applied after the driver's current maneuver and announced; an optional change is offered with the added miles and minutes. Changes made by dispatch are attributed to dispatch, so they do not count against the driver's compliance.
Adding a stop. Three ways:
- In the cab, the driver taps a place on the route (truck stop, rest area, parking) and adds it as a waypoint. Quickest while on the road.
- In Live monitoring, open the session and use Dispatch via points to add a location by address.
- Under Dispatches, open Details on the dispatch, click Add stop and enter the address or the latitude and longitude. The route updates to include it.
Changes made in your TMS. Platform Science does not push a change from Workflow into a running navigation session, and a Platform Science dispatch cannot be edited once created; a changed job arrives as a new dispatch. If you need a route change while the truck is moving, make it in the NavGuru dashboard against the Platform Science trip.
First stop and stop order on Platform Science
Workflow is the source of truth for stop state. NavGuru will not advance to stop B until the driver marks stop A departed in Workflow, and it never routes back to a stop already completed or passed. That is deliberate: a truck can pass near a pickup without completing it.
Live monitoring
Open Live monitoring, choose Live or Historical, and select the session. The session view shows:
- Planned route, actual path and out-of-route segments on the map, with start, stops and end. After a deviation the panel shows "Computing off-route segments" for a few seconds while the excess is calculated.
- Live telemetry: speed, fuel level, position and last update. Position updates every few seconds while the truck moves.
- Reroutes, numbered in order, each tagged with who caused it (driven, dispatch, system). Open one to see where the truck left the route and the route it was given back.
- Trip progress and route details: distance, duration, estimated cost with tolls and fuel, on-route percentage, geofence crossings on this trip, and the event timeline.
- Speed over time, fuel over time and idle time charts.
Places. Map controls (top left of the session map) has a Places layer: fuel and truck stops, parking and rest, weigh and inspection, CAT scales, repair, truck wash and restrictions along the route. Turn on the categories you want; they show on the map for the session you have open.
Reading the compliance numbers
Two figures look alike and measure different things. Knowing which is which saves a lot of confusion.
| Figure | What it measures | When it updates |
|---|---|---|
| On-route % (live) | How much of the drive so far has stayed on the route currently active in the cab. When the driver leaves the route and NavGuru reroutes, the new route becomes the reference, so this figure can stay at 100% through several reroutes. | Continuously during the trip |
| Route adherence (post-trip) | The actual path compared against the route the dispatch was sent with. You can also compare the same drive against each of the other route options in the replay view to see which route the driver effectively followed. | At trip end; visible in Route compliance and in the session replay |
| Out-of-route miles and excess miles | Miles driven off the dispatched route, and miles beyond the planned distance. Miles added by a safety reroute (clearance, weight, hazmat, closure) are attributed to the system and excluded from the driver's score. A mandatory dispatch change re-baselines the corridor, so no deviation is recorded. | At trip end |
| Reroutes | Count of times a new route was computed, with the cause. A high count with low out-of-route miles usually means short detours (a fuel stop, a customer gate); a low count with high miles means one long deviation. | Live |
| Geofence crossings and out-of-corridor events | Entries and exits of fleet zones, and departures beyond the fleet's corridor threshold. | Live |
The corridor deviation threshold (miles or percent), whether the driver sees a deviation chip, and whether a reason-code prompt appears at the next stop are fleet settings. Both switched off gives silent scoring: nothing is shown to the driver and the deviation is still recorded.
Fuel level and FuelGuru in the dashboard
The fuel level on the session view comes from the truck's engine data through the telematics platform. Float senders in a moving tank read a wave, so the raw reading moves up and down by several percent on curves and grades; every telematics vendor filters it. The chart shows the raw series. FuelGuru smooths the series before it uses it for a prescription, so a reading that differs from the cab gauge by a few points at any one moment is expected.
Where FuelGuru is enabled, the prescribed stop and gallons sit inside the driver's route, and the dashboard shows the prescription, the stop actually made and, when card data is connected, the gallons bought in and out of network. A trip on a short lane, or one where no priced in-network station falls inside the out-of-route limit, returns "no stop needed" with the reason; that is the correct answer, not a missing prescription.
Vehicle profiles and alerts to dispatch
Vehicle profiles. Platform Science and other telematics feeds give NavGuru the vehicle ID, VIN and engine data, not the truck's height, weight, length, axles or hazmat status. Set those under Fleet before the first trip. Until you do, a standard 5-axle profile is used, which is why a fleet with 12 ft equipment can see clearance alerts for structures its trucks pass under. Drivers confirm the profile before each trip and see the source and version.
Alerts to dispatch. Zone entries and exits, corridor departures and other events can be sent to the dashboard, to email and to connected systems once an alert rule is configured for your fleet under Settings. By default there is no notification on every deviation: a truck leaves its planned line many times a day for a gate, a rest stop or a detour, and large fleets review the after-trip list rather than a live ping. Configure a rule for the events you want in real time; review the rest in Route compliance.
Tracing a trip when something looks wrong
Trace the workflow in order, and the record tells you which kind of issue it is.
What did dispatch send?
Trip, driver, stops, vehicle. Check the dispatch in Dispatches, Details.
What did the integration deliver?
Did the job reach NavGuru with the stops in order? On Platform Science, did it come through Workflow or from the dashboard?
What did NavGuru receive?
Correct vehicle profile, correct stops, correct routing policy. The profile that was applied is the first thing to check on any restriction question.
What did the driver see?
Route, alerts, trip changes. The session view and the driver's report.
What happened on the road?
The actual GPS path, the reroutes and their causes, the stops made.
What did the dashboard record?
Trip events, changes, reroutes, alerts, adherence. Use the trip record rather than memory from the cab.
That usually places the issue in one of five buckets: navigation, integration, configuration, data, or driver workflow. Each has a different owner, and the fix is different. Known issues and fixes are on Get started, section 11.
The weekly review
A 30-minute weekly review is the habit that turns the data into savings. The numbers to bring:
- Enrolled trucks, active trucks, loads dispatched, loads navigated in NavGuru (adoption).
- Route compliance and out-of-route miles per vehicle and per driver, with deviations attributed to driver against dispatch.
- Where FuelGuru is on: prescription compliance, gallons in against out of network, cents per gallon captured.
- Tolls on navigated loads against what the fleet paid on the same lanes before, where toll data is connected.
- The three most-raised driver items and what shipped for them.
Ask your MapUp contact to set up the Monday summary email for your operations owner; it is built from the same production data as the dashboard.