A truck route app is a car route app that knows what it is driving.
The difference between consumer navigation and a truck route app is not the map. It is that one of them knows the vehicle is 13 feet 6 inches tall, weighs 78,000 pounds and is not allowed down that lane. Everything expensive about this category comes from that single fact, and everything disappointing comes from assuming a routing API already handles it. It is the same shape of problem as the rest of field service apps, with harder constraints.
This page covers what the app has to know about the vehicle, where truck-legal road data actually comes from, how driving hours bound a route before distance does, and what the stop list has to hold beyond an address.
See how the hours bound the routeThe short version
The vehicle constrains the roads, and the clock constrains the day.
Two constraints decide whether a planned route is real. Whether the vehicle can physically and legally use those roads, which depends on height, weight, length and load. And whether the driver has enough hours left to reach the end of it, which depends on rules that do not care how far away the last stop is.
A route that satisfies distance and violates either one is not a route, it is a plan to stop somewhere unplanned. Most homemade fleet tools model the first constraint badly and the second not at all.
The clock runs out before the distance does
Federal hours of service rules for property-carrying drivers set out limits that a route planner has to respect or it is producing fiction. A driver may drive a total of 11 hours, and may not drive after a period of 14 consecutive hours after coming on duty following 10 consecutive hours off duty. Driving is not permitted if more than 8 hours of driving time have passed without at least a consecutive 30 minute interruption in driving status.
On top of the daily limits sit the weekly ones: 60 hours in any 7 consecutive days where the carrier does not operate every day of the week, or 70 hours in any 8 consecutive days where it does. A planner that gets Tuesday right and Friday wrong is still going to strand somebody.
The practical design point is that these are two separate clocks, and the tighter one binds. A driver with 4 driving hours left and 2 hours of window left has 2 hours. An app that shows only driving time remaining will confidently schedule a stop that cannot be reached, which is worse than showing nothing.
49 CFR 395.3, maximum driving time for property-carrying vehicles
Try it
How far the route can legally go
A route that ignores hours of service is a route that ends in a lay-by. Two limits run at once and the tighter one decides.
4 more driving hours
Bound by the 11 hour driving limit. A 30 minute interruption is due within 2 driving hours. A planner that does not know these numbers will confidently schedule a stop the driver cannot legally reach.
What the app has to know about the vehicle
Routing for a truck starts with a vehicle profile, and the fields are not optional extras. Height, width, length, gross weight, axle configuration and whether the load is hazardous all change which roads are legal.
Weight is where people underestimate the complexity. Federal limits on the Interstate System are 20,000 pounds on a single axle, 34,000 pounds on a tandem axle and 80,000 pounds gross. The Federal Bridge Formula then relates weight to axle spacing, and depending on axle count and spacing it may require a lower gross weight than the 80,000 pound figure. So a legal gross weight is not a single number you can store once, it is a function of how the vehicle is configured.
The corollary for the build is that the profile belongs to the vehicle and the load, not to the driver. A tractor that is legal empty is a different routing problem loaded, and an app that stores one profile per driver will get this wrong every time a trailer is swapped.
Where truck-legal road data comes from
This is the part that decides the budget, and it is worth being blunt about it. Consumer routing services are built for cars. They generally do not model bridge heights, weight-restricted roads, hazardous material restrictions or turn restrictions for long combinations, and an API that returns a route quickly is not telling you whether a truck can use it.
Truck-legal attributes come from commercial map data products sold under licence, priced per request or per vehicle. We have not verified the terms of any specific provider, so if your plan depends on truck routing inside your own app, confirm coverage, pricing and redistribution rights with that provider directly before building around it. Treat a confident claim otherwise, including from an AI, as something to check.
There is a cheaper approach that works for a lot of operations. If your vehicles run the same roads most weeks, the real problem is not general-purpose routing, it is remembering which turns and bridges are a problem. An app that lets drivers flag a hazard once and shows it to everyone afterwards solves most of the actual pain for none of the licensing cost. It is not routing, it is institutional memory, and it is frequently what people needed.
A stop is more than an address
The other half of a route app is the stop list, and this is where a generic navigation app stops being useful at all. A delivery stop carries an opening window, an access note, whether a tail lift is needed, who signs, and what happens if nobody is there.
Ordering matters more than distance for most fleets. A stop that cannot receive before ten and a site that closes at three are hard constraints; the shortest path between them is a preference. Planners that optimise distance and ignore windows produce elegant routes that fail on the second stop.
The end of each stop is a record, not a tick. Something has to capture who took delivery and when, which is the job of a proof of delivery app, and the start of the day has its own record in a pre-trip inspection app. Keeping those as separate records rather than flags on the route is what makes the whole thing answerable later.
What each approach gives a driver
| Option | Avoids low bridges | Respects driving hours | Delivery windows | Knows your regular hazards |
|---|---|---|---|---|
| Consumer satnav | No | No | No | No |
| Printed run sheet plus satnav | No | in the planner's head | Yes | in the driver's head |
| Licensed truck navigation | Yes | sometimes | No | No |
| Off-the-shelf fleet platform | Yes | Yes | Yes | generic |
| A route app you build | with licensed data | Yes | Yes | Yes |
Building one around your own fleet
Fleet platforms are built for fleets, priced per vehicle per month, and shaped around telematics hardware. An operation with six trucks doing regular regional work usually needs a fraction of it, and needs one or two things the platform will not do: a stop that only exists on alternate weeks, a customer who has to be phoned an hour ahead, a yard that can only be entered from one direction.
Newly is an AI app builder. You describe the app you want, including the constraints your routes actually have, and it builds and ships a real mobile app you own. Plans start at $25 a month, there is no free plan, and iOS builds ship through App Store Connect. It does not come with licensed truck map data and it is not a telematics product. It is what you use when the platform is built for a fleet ten times your size.
Before deciding anything else, get clear on what location data on a phone will and will not give you, because most disappointment in this category starts with an assumption about location and routing that was never true.
Questions people ask about truck route apps
It plans and follows a route for a commercial vehicle, taking account of what the vehicle is: its height, weight, length and load. That is the whole difference from consumer navigation, which assumes a car and will happily route a 13 foot 6 inch trailer under a 12 foot bridge.
Describe the runs your trucks actually do
Write down the constraints a route has to respect, including the turn everybody knows to avoid, and build the planning around them.
Start building