--- title: The route dispatch plans is the route the driver sees description: LiteTMS sends the saved route line and stop order from dispatch to the driver app, so both sides work from one plan instead of phone instructions. slug: planned-route-driver-mobile-app locale: en date: 2026-08-18 updated: 2026-08-18 category: product-updates tags: orders, routes, driver-app, dispatch, mobile, navigation cover: https://cdn.litetms.eu/blog/2026/08/scr-20260818-kvnc-cover.jpg cover_web: https://cdn.litetms.eu/blog/2026/08/scr-20260818-kvnc-web.webp cover_thumb: https://cdn.litetms.eu/blog/2026/08/scr-20260818-kvnc-thumb.webp cover_alt: LiteTMS route planner beside the mobile app map showing the same three-stop route author: LiteTMS Team draft: false --- In LiteTMS, the road line dispatch saves for an order is the road line the assigned driver sees in the mobile app. The stop sequence and the relevant route sections travel with the order, so the plan does not have to be rebuilt from a phone call, a screenshot or a separate map pin. ## A list of addresses is not a route plan Three stops in the right order still leave room for a dozen questions. Which road should the truck take between them? Which city should it avoid? Where did dispatch deliberately pull the line away from the route suggested first? That context is easy to lose when the office plans on one screen and then explains the result over the phone. The driver may receive the correct addresses and still leave with a different picture of the job. LiteTMS removes that second telling. Dispatch arranges the stops, calculates the road route and saves it with the order. The driver opens the Map tab in the mobile app and sees the saved line with the same numbered points. One plan. Two screens. ## The app reads the saved route instead of guessing again The distinction matters. The mobile app does not take the addresses and quietly invent another route merely to draw the map. It reads the calculated road sections stored on the order and renders those sections on the phone. If one driver handles the complete order, the app shows the complete planned route. When the job is divided between drivers, each person sees the sections assigned to them, taken from the same office plan. The distance and time shown on the map also refer to that driver's part of the work rather than somebody else's legs. This is the practical meaning of a one-to-one handoff: the line on the phone comes from the plan saved at the dispatch desk. ## A route correction no longer becomes a telephone game Plans change. A stop moves, its order changes or dispatch chooses another road. LiteTMS links the saved geometry to the current stop sequence, so an old line is not presented as if it still matched a changed order. Dispatch recalculates and saves the route once. After the mobile app synchronizes, the driver receives the current geometry. There is no need to send a new screenshot and then explain which part of the old message should be ignored. The same principle applies before a dead zone. Once the order and its route have been synchronized to the phone, the saved map remains available from the local cache. A later office change still needs a connection to reach the device, which is why the app also makes the age of synchronized route data visible. ## Navigation follows the plan without taking ownership of it The driver can start navigation from the order map. LiteTMS builds the trip from the current position through the remaining stops, while using the saved route line and its shaping points to keep the result faithful to the office plan. Live traffic can produce a small deviation in fresh turn-by-turn guidance. The planned line remains the shared reference on the order. Dispatch also controls whether the driver may request a temporary route straight to a selected destination. That option is off by default. When the office enables it, the result stays on the phone and never overwrites the route saved in LiteTMS. A driver can handle the road ahead without silently changing the plan for everyone else. ## Less interpretation means fewer avoidable mistakes Software cannot remove every surprise from a transport job. It can remove the unnecessary retelling. The dispatcher no longer has to describe a line that already exists on the screen. The driver does not have to decide which of several messages contains the latest instruction. Both sides can point at the same order, the same numbered stops and the same saved route. That is a small interface detail with an operational payoff: less room for misunderstanding before the truck moves. [Register your company free](/en/register) and send your next planned route straight to the driver's app. ## FAQ ### Does the driver see the same route that dispatch saved? Yes. The mobile app reads the calculated road sections stored with the order. A driver assigned to the whole job sees the whole plan, while a driver assigned to selected legs sees the corresponding sections from that plan. ### What happens when dispatch changes the route? The dispatcher recalculates and saves the route in the order. The mobile app receives the current saved geometry during synchronization and does not treat a route that no longer matches the stop sequence as current. ### Can the driver overwrite the dispatcher's route? No. Dispatch may allow a driver to request a temporary recalculation, but that result is not saved over the planned route. The office plan remains unchanged. ### Can the driver still view a synchronized route without a signal? Yes. Previously synchronized order details and planned geometry remain available in the phone's cache. New route changes from dispatch require a connection before they can reach the device.