Service Truck and Van Tracking: What to Check Before Installing

What service truck and van tracking has to survive

A service truck tracker lives a harder life than a family-car tracker, and the difference is not the hardware specification — it is the duty cycle. A van may sit at the yard from Friday afternoon to Monday morning with the doors opening and closing, then run a hundred miles in a day, then sit again. A truck may idle for an hour at a job site in July and start at minus ten in January.

Four conditions do most of the damage. A long parked period drains anything that reports continuously. A jump start or a battery replacement interrupts power to a hardwired unit. Tool loads and rough access roads work loose anything that is only held by friction. And a shared vehicle means the person looking at the screen is frequently not the person who drove it.

The four checks that decide the format

Work through these in order, because each one eliminates options rather than adding them. The answer to the fourth check usually picks the device for you.

Matching the format to the vehicle

Vans and light trucks are the easy case, because they almost always have a working 12V system and an accessible OBD port on 1996 and newer models. An OBD plug-in tracker installs in under a minute and needs no wiring, which makes it the fastest way to cover a mixed fleet of vans. A hardwired unit costs more in labour but never needs to be removed for charging and cannot be unplugged by a driver who does not want to be tracked.

The awkward vehicles are the ones with an occupied OBD port — a telematics dongle for insurance, a diagnostic tool left plugged in, or a fleet card reader. On those, the choice is a hardwired unit or a magnetic self-powered unit placed inside the vehicle. Bucket trucks, trailers and equipment with no electrics need the self-powered format regardless of what the rest of the fleet uses.

Write the pass condition before you install anything

The most common fleet failure is not a bad device; it is a successful install that nobody can prove works. Decide in advance what "installed and accepted" means, per vehicle, and write it down before the installer starts. The table below is the version that works on real fleets, because every row has an owner and a fail example.

Verify identity before you look at the map

Open the account and select the vehicle from the written assignment record, not from memory. Compare the vehicle label with the tracker identifier captured during installation. Only then read the timestamp and the location. Doing it in that order prevents a plausible map point from hiding the fact that the wrong vehicle is selected — which is the single most common false alarm in a new fleet install.

Do not use a driver name as the only vehicle label. The tracker follows an authorized vehicle, and it does not identify who is behind the wheel. Driver assignment belongs in a separate operational record.

Check the parked state, not just the moving one

Most acceptance tests only prove the tracker works while the vehicle is moving, which is the easy case. The state that matters for a service fleet is parked. Leave the vehicle at the yard overnight and confirm the next morning that it still reports, that the timestamp is current, and that the vehicle battery is unaffected. A unit that drains a van battery over a weekend will cost more than the tracker did.

This overnight check is also where a wrong reporting setting shows up. If the account shows continuous position updates for a vehicle that has not moved, the device is configured for live tracking rather than movement alerts, and that setting is what empties the battery.

Run a short commissioning route

Choose a route with a clear start, one normal road segment, one planned stop in an open area, and a return to the yard. Do not make the first test happen during a customer emergency. Write the planned start time and the vehicle identifier before the vehicle moves, and if two vehicles are being tested, separate their departure times so a swapped assignment is obvious rather than something you reconstruct afterwards.

Set the account structure before the second vehicle

Adding the second vehicle is where account mistakes get baked in, because it is tempting to reuse one login and rename the vehicle each time. Decide the structure once: one account, one record per vehicle, and a named person responsible for access. Dispatchers usually need to see all vehicles; drivers usually need to see one, or none.

Label vehicles by an internal identifier that will not change — a unit number, not a driver name or a nickname. When a vehicle is replaced, the new vehicle gets its own record and its own commissioning test rather than inheriting the old one.

Reuse the baseline when something looks wrong

Save the acceptance date, the reviewer, the vehicle identifier, the tracker identifier, the installer, and a note describing the test route. When a tracker later appears to behave differently, compare against that baseline first. Ask whether the vehicle was serviced, the device assignment changed, account access moved, the installation was disturbed, or the vehicle is now parked somewhere with different coverage.

A passed test belongs to one setup at one time. Retire it when the device moves to another vehicle or the installation changes materially, and run a fresh controlled route.

Practical action sequence

1. Answer the four format checks: power, parked reporting, evidence use, and access.
2. Pick the format per vehicle type, not one format for the whole fleet.
3. Write the pass condition with an owner for every row.
4. Install, then verify identity and timestamp before reading the map.
5. Leave the vehicle parked overnight and confirm it still reports.
6. Run a short commissioning route and sign off, or assign a retest.
7. Set the account structure and vehicle naming before the second vehicle is added.

Decision being resolved: A fleet operator is about to install the same tracker across every service truck and van, and needs to know which format suits each vehicle and how to prove the install actually works before the vehicles depend on it.

Keep the scope distinct: Installation guides own the physical wiring steps. The dashboard guide owns general screen interpretation. This page owns pre-installation format selection for service trucks and vans, plus the acceptance test that releases a vehicle back to dispatch.

Frequently asked questions