Dispatch from a timestamped vehicle view
A dispatcher needs to decide which van can take the next job. Fleet shows vehicle status and its latest report, with a live map and a follow view. The status can distinguish moving, idling, parked, offline, overdue and no GPS fix. Read the report age before committing a driver to a new pickup. A van last seen twenty minutes ago may be nearby, but the map does not prove it. Where coverage is interrupted, later reports can fill in the history without making the earlier point live again. Set a simple office rule: call the driver when the latest report is too old for the decision at hand.
The day trail provides trips, stops, distance and driving time. That helps answer a customer query about a vehicle’s movement, but it does not give a customer ETA or a proof of delivery. If your process needs those, identify the separate job records and communications that supply them. A stop near an address may be a delivery, a break or traffic. Treat it as a prompt to check, not a completed job marker.
Choose alerts the dispatch team can act on
Zone entry can tell a team that a vehicle reached a registered place. After-hours and unplug alerts can prompt a security check. Speed or harsh movement can prompt a safety review. Each rule should name an owner and an action. Fleet can send alerts to the bell, phone push or e-mail with recipients selected by role or person, while location scope constrains who sees vehicle data. A flood of messages with no action is not useful. Begin with a small number of rules and review false positives with drivers and dispatch.
Private use is another dispatch boundary. If vans may be used outside work, describe exactly when private mode is allowed and how the private-mode control works. Fleet keeps private trip distance but no position, so dispatch should not expect to see a private route. Test a real private trip before relying on the policy. The fact that a van has a tracker does not remove the employer’s obligation to explain monitoring and limit it to a justified purpose.
Review fuel against the right vehicle and period
Fleet imports fuel-card statements and reviews entries by vehicle and driver. A van that changes driver often needs consistent vehicle identification in the source file. Compare litres and spend with the vehicle’s recorded distance for the same period, then inspect exceptions. Idling hours can add context, with idle fuel shown as an estimate if a rate is configured. Do not call that number a measured tank level. A delivery route with many stops can look different from a long intercity journey, so an unusual chart should start a review rather than decide one.
Before rollout, pilot one high-use van and one van whose route or parking is difficult for reception. Check the power and SIM arrangement, vehicle assignment, manager scope and a real trip. Then show dispatch what offline and no-fix look like. That training keeps a useful map from being read as more certain than its data allows.
Set up the morning dispatch view
Start with the list of vehicles expected to work, their home locations and usual assignments. A dispatcher should see which vans have reported, which are moving or parked and which have an overdue or no-fix status. Do not allocate a nearby job from a marker whose timestamp is too old for that decision. Set an office threshold for when to call the driver instead. If the latest valid fix is from a covered car park, remember that the van may have moved before the next report appears.
Where a key identifies a driver, confirm it was used on the trip. Otherwise the displayed name may be the usual driver for that van. That distinction matters when a vehicle is shared or a replacement driver covers a shift. Staff attendance can be inspected beside the vehicle trail, but the clock-in remains the record of staff time. A van’s first trip does not automatically start a shift and its final stop does not automatically end one.
Handle a missed stop or late report
A customer calls about a delivery. The dispatcher opens the relevant van’s day, checks the trip times and sees whether there was a stop near the destination. If reports are missing, the dispatcher records the gap and calls the driver or checks the delivery system. A stop is evidence of the vehicle, not proof that goods changed hands. If a delayed batch later fills in the trail, use the original timestamps and update the operational note. Do not rewrite the delivery record solely because a map point appeared later.
For a vehicle that has gone offline, inspect the last report, power and SIM status if available. A no-fix state is different from no mobile report. A possible unplug alert is a reason to check, not a conclusion about intent. Assign one person to make contact and one to record the outcome. When the van returns, ask whether a common parking place or route repeatedly produces gaps and include it in the next installation review.
Make private use understandable to dispatch
If the business permits a van to be used privately, write down when the driver may turn private mode on, how the private-mode control is operated and what the office will see. In Fleet, private trips keep distance and duration but no position or route. Dispatch must not treat the absence of a private route as a device fault. Train staff on that display before the first private journey, and test it with a representative vehicle.
Private mode does not settle every data-protection issue. The organisation still needs a purpose for public tracking, a notice, restricted access and a retention decision. It should decide how to handle an emergency involving a privately used vehicle without promising capabilities the product does not have. If the control fails or a vehicle is rewired, pause reliance on the policy until the installation is checked. A privacy promise is credible only when the fitted device and server behavior match it.
Close the month with traceable vehicle costs
Fuel statements, kilometres and idling hours can be reviewed for the same vehicle and period. Start from the card file, match plates and resolve duplicate or malformed entries. Then compare with the trips that the vehicle actually reported. Missing trips or a card posted in another period can make consumption look strange. A shared van also needs careful driver attribution. Do not spread its fuel cost across people by assumption.
Use exception notes rather than silently adjusting data to match expectations. If the vehicle had a service visit, an unusual load or a route with many stops, record that context. The Fleet fuel view can highlight patterns and estimate idle fuel from a configured rate, but the FTC164 does not report tank level. A monthly meeting can use the figures to decide what to investigate and which installation or workflow needs improving. It should not treat the chart as a complete account of every litre.
A delivery-day operating rule
Before the first assignment, inspect the list of vans expected on shift and the age of each latest report. The dispatcher may use a recent valid point to choose a nearby vehicle, but calls the driver when the report is too old for the decision. A key-identified driver and a usual-driver assignment should be shown as different evidence. The staff clock-in is checked separately. This avoids treating the first vehicle movement as the start of paid time.
When a customer asks where a delivery is, open the relevant day and check the route, stop and timestamp. If the route has a gap, say that the vehicle’s position is unconfirmed for that period and check the delivery or job system. Do not infer a customer ETA from a map dot. If stored reports arrive later, update the internal note with their original times. A stop near a customer can support a question to the driver; it is not proof of delivery.
After the shift, review only actionable exceptions: an alert with a named response, a fuel transaction that needs matching or a vehicle that stayed offline. Keep private trips out of location review because their position is not stored. A monthly summary can compare litres and distance when both periods match, while labelling idle fuel as an estimate. A useful rule is one the office can explain to drivers and apply the same way next week.
Apply the same records to different van work
For delivery, the useful question is which van can take the next job and when the last stop happened. The FTC164 can record distance and turn points frequently; Fleet presents a timestamped live map, day trail, zones and driving alerts. It does not publish a customer ETA. For rental cars, restricted-area, crash, tow and unplug alerts help a reviewer check an incident. The FTC164 has a GNSS odometer and a device immobiliser, while Fleet has no remote immobiliser control or CAN door-unlock feature.
Taxis can use iButton identity and speed or harsh-driving alerts; Fleet has no taximeter integration. School-bus operators can review routes, stops and speed rules; a parent-facing bus app is outside the current service. Security patrols can review Fleet zone visits, while a wired panic button on the tracker remains an input capability that Fleet does not expose. State the actual recipient and response for each alert before enabling it.
Sources
Frequently asked questions
Does a stop prove a delivery?
No. It is a vehicle stop. Use your delivery or job record to confirm the work.
Can the map give a customer ETA?
No. Fleet has no customer ETA workflow. Use the latest report as context for a human decision.
What if a van is used privately?
Agree a policy, test the private-mode control, and confirm that Fleet stores no private position.
Related guides
GPS Tracking in Cyprus: The Complete Guide
Plan vehicle GPS tracking in Cyprus: devices, data, installation, privacy, costs, staff hours and a practical buyer checklist.
GPS tracker for vehicles in Cyprus
Choose a vehicle GPS tracker in Cyprus. Understand FTC164 support, wiring, SIM data, fix quality, private trips and installation checks.
Telematics in Cyprus: from reports to decisions
Understand fleet telematics in Cyprus: live reports, trip and stop records, alerts, permissions and the limits of vehicle data.
Fuel monitoring for Cyprus fleets
Plan vehicle fuel monitoring in Cyprus using transaction records, card imports, vehicle context and careful review of exceptions.
Driver behaviour monitoring in Cyprus
Use recorded speed, harsh movement and vehicle alerts for careful fleet reviews in Cyprus without inventing driver scores.
Construction fleet tracking in Cyprus
Plan tracking for construction vans and site crews in Cyprus with trip records, place zones, staff hours and clear equipment limits.
Employee vehicle tracking and GDPR in Cyprus
Plan proportionate employee vehicle tracking in Cyprus with notice, access limits, private trips and documented review.
Discuss your fleet requirements
Ask for a quote based on your vehicles and operational needs.
