cms.fleetile.com

Blog

  • Telematics Implementation: A Rollout Plan That Drivers Accept

    Telematics Implementation: A Rollout Plan That Drivers Accept

    A telematics implementation is not an installation project. The hardware goes in over a few days and works. What decides whether the system is still delivering value in six months is a set of choices made before installation and a conversation with drivers that most fleets skip. This is a rollout plan in five stages, written around the failures rather than the brochure.

    Stage one: decide what you are trying to fix

    Fleets that start with a problem get a result. Fleets that start with a purchase get a dashboard.

    Pick one or two problems, in writing, before anything is ordered. Realistic examples: fuel spend rising faster than distance, delivery times being disputed by a customer, vehicles used outside working hours, or maintenance costs concentrated in a few assets. Each one implies different data, different alerts and a different definition of success.

    This stage also sets the number you will be judged on later. If the goal is fuel, record the current fuel spend per vehicle now, because nobody can reconstruct a baseline after the fact.

    Stage two: choose hardware for the vehicles you actually have

    A mixed fleet rarely takes one device type. Owned commercial vehicles want hardwired units, short-term or rental vehicles want plug-in units, and trailers, generators and site equipment want battery devices because there is no power to draw on. Forcing one device across all three creates either a fitting problem or a data gap. The trade-offs are laid out in telematics devices.

    Decide the installation schedule at the same time. Vehicles come off the road for hardwired fitting, and a fleet that has not planned for that will start postponing installations, which is how a rollout stalls at sixty percent coverage and stays there.

    Stage three: brief the drivers before the fitters arrive

    This is the stage that decides everything, and it is the one most often skipped in the hope that nobody notices the new box. They notice.

    A briefing that works covers four points, honestly:

    • What is being collected. Location during working hours, speed, harsh braking, engine on and off. Say it plainly rather than letting people imagine worse.
    • What it is not. No audio, no camera unless you are fitting cameras, no tracking of a personal vehicle.
    • Why. Fuel cost, safety, and being able to prove the driver was where they said they were. That last one is a genuine benefit to drivers and is worth saying out loud, because a tracked driver is protected against a false complaint.
    • What happens with the data. Who sees it, how long it is kept, and whether it will be used for discipline. Answer this before it is asked.

    Put it in writing as a short policy. The reasoning behind that document is covered in employee vehicle tracking and privacy, and a broader version sits in writing a company vehicle policy.

    Stage four: install in phases, then leave it alone

    Fit a pilot group first, ideally five to ten vehicles covering your different vehicle types and route profiles. Run them for two weeks and check three things: every vehicle reports continuously, positions look sane in the places you know are difficult, and event thresholds are not firing on ordinary driving.

    That last check matters more than it sounds. A harsh braking threshold set too sensitively will flag a driver every time they stop at a junction, and once drivers decide the scores are unfair, the behaviour data is finished as a coaching tool.

    Then fit the rest, and resist the temptation to start managing immediately. The first two weeks of full coverage are for a baseline, not for enforcement. You cannot call anything abnormal until you know what normal looks like.

    Stage five: build the routine, not the dashboard

    The system does nothing on its own. What produces the result is a fixed, boring cadence with a named owner.

    Cadence Who What
    Immediate Dispatcher or duty manager Tamper, out-of-hours movement, geofence breach
    Weekly Fleet supervisor Idle time, driver scores, exceptions worth a conversation
    Monthly Fleet manager and finance Fuel per vehicle, cost per kilometre, utilisation
    Quarterly Owner or director Progress against the problem written down in stage one

    Start with three measures rather than twenty. Which three depends on the problem you named at the start, and fleet management KPIs covers how to choose them.

    The four mistakes that kill a rollout

    1. Installing quietly. Drivers find out anyway, and then the project starts with a trust deficit it never recovers from.
    2. Switching on every alert. Volume produces fatigue, fatigue produces ignoring, and ignoring produces a system nobody uses.
    3. Using the first month’s data to discipline someone. It converts the system into a threat, and disabled devices follow.
    4. Leaving it unowned. A tool that is everybody’s responsibility is reviewed by nobody by week six.

    Frequently asked questions

    How long does a telematics implementation take?

    Installation is usually days to a few weeks depending on fleet size and device type. Getting value takes about ninety days, because you need a baseline period before the data means anything and a routine before anybody acts on it.

    Do you have to tell drivers about vehicle tracking?

    Telling them is both the fair approach and the practical one. Fleets that brief drivers openly get cooperation; fleets that install quietly get resistance, disputes and tampering, which costs far more than the conversation would have.

    Should you install telematics across the whole fleet at once?

    No. A pilot of five to ten vehicles covering your different vehicle types lets you catch installation and threshold problems while they are still cheap to fix, then the full rollout goes ahead with settings that already work.

    What should you measure first with a new telematics system?

    Idle time and out-of-hours movement usually produce the first visible savings because both are habits rather than structural problems. Driver behaviour comes next, once there is enough history for the scores to be fair.

    Who should own a telematics system inside the business?

    One named person, usually the fleet manager or operations supervisor, with a fixed weekly review. Systems shared across a team without an owner stop being reviewed within about six weeks.

    Plan the rollout with someone who has done it

    Most of the mistakes above are avoidable in a conversation. Get a Fleetile demo and walk through a rollout plan for your vehicles on the Fleetile platform.

  • Telematics vs GPS Tracking: What You Get for the Extra Money

    Telematics vs GPS Tracking: What You Get for the Extra Money

    The short version of telematics vs GPS tracking is this: GPS tracking tells you where a vehicle is, and telematics tells you what it has been doing and what that is costing you. GPS is one component inside a telematics system rather than a competing product, which is why comparing them feels slippery. The real question is not which technology is better. It is how much of the extra data you will actually use, because you pay for all of it either way.

    What each one gives you

    Capability GPS tracking Telematics
    Live position on a map Yes Yes
    Journey history and route replay Usually Yes
    Geofence alerts Sometimes Yes
    Speeding, harsh braking, cornering Rarely, and often inferred Yes, from motion sensors
    Engine hours, idle time, ignition state No Yes
    Driver scoring and comparison No Yes
    Maintenance scheduling from real usage No Yes
    Cost and utilisation reporting No Yes

    The pattern is clear once it is laid out. GPS tracking covers the questions asked in the moment. Telematics covers the questions asked at the end of the month, which are the ones that involve money.

    “GPS telematics”: when people mean one system, not two

    A lot of people arrive here having searched for GPS telematics, telematics GPS system or telematics GPS tracking, and they are not asking for a comparison at all. In everyday industry use those phrases are a single noun. They describe one product: a system that uses satellite positioning as its foundation and adds the vehicle and behaviour data on top.

    Both readings are correct, which is why the subject feels slippery.

    • “Telematics vs GPS” is a buying question. It asks which of two products to pay for, and the rest of this guide answers it.
    • “GPS telematics” is a category name. It asks what the combined thing is, and the answer is below.

    What a GPS telematics system actually contains

    Sold as one product, a GPS telematics system is four parts that have to work together. A weakness in any one of them shows up as a weakness in the whole system, which is why comparing only the software is a common and expensive mistake.

    Part What it is What goes wrong without it
    The device A unit in the vehicle with a satellite receiver, a motion sensor and, on wired units, a connection to the vehicle’s own data No engine or behaviour data is possible later, whatever the software promises
    The connection A SIM and mobile data plan carrying records to the server Gaps in coverage become gaps in history, unless the device stores and forwards
    The platform Software turning raw records into a live map, alerts, journeys and reports You have data nobody can read, which is the same as having none
    Fitting and support Installation, replacement, and someone to call Vehicles quietly stop reporting and nobody notices for weeks

    The positioning layer is the same in every one of these systems, because they all read the same satellites. What separates them is the three layers above it. Our guide to how telematics works follows a single record through all four stages, and telematics devices explained covers the hardware end in detail.

    So is GPS telematics different from GPS tracking?

    Yes, and the distinction is worth holding onto because it decides what you can measure. GPS tracking is the positioning layer on its own: where the vehicle is, and where it has been. GPS telematics is that layer plus everything the vehicle can tell you about itself. Every GPS telematics system contains GPS tracking. The reverse is not true, and no amount of software upgrades will make a position-only device produce engine data.

    Telematics and telemetry are not the same word

    One more pair that gets confused, and the difference is simple. Telemetry is the general practice of measuring something remotely, used in aviation, medicine, energy and manufacturing. Telematics is telemetry applied to vehicles, with the positioning layer built in. Every telematics system is a telemetry system; most telemetry has nothing to do with vehicles.

    Where plain GPS tracking is genuinely enough

    Plenty of sales copy insists everyone needs the full system. That is not true, and pretending otherwise wastes people’s money.

    • One or two vehicles, owner-driven. If the owner drives the vehicle, driver scoring compares them to themselves. Location and theft recovery is the whole benefit.
    • Recovery as the only goal. If the reason for buying is finding a stolen vehicle, position and tamper alerts do that job.
    • Unpowered assets. A trailer or a container has no engine data to read and no driver behaviour to score. Location is the entire question. See trailer and container tracking.
    • Very short-term hire. If a vehicle is in your fleet for a week, there is no behaviour trend to build.

    Where the extra data starts paying

    The crossover is not about fleet size. It is about whether anyone in the business is accountable for the running cost of the vehicles. Once someone is, three things change.

    You can find waste instead of suspecting it

    Fuel spend that looks high is a suspicion. Fuel spend set against real distance, idle hours and driving style is a diagnosis, and it points at specific vehicles. That is the difference between an uncomfortable conversation and a fixable problem, and it underpins the approach in reducing fuel theft.

    Risk becomes visible before the incident

    Speeding and harsh braking data exists weeks before the accident it predicts. Plain GPS tracking gives you a route line after the fact and nothing to act on before it.

    You can answer questions from other departments

    Finance wants cost per kilometre. Operations wants utilisation. Insurers want a safety record. Customers want proof of arrival time. None of those come from position alone, and all of them are routine outputs of a telematics system. The measures worth building the routine on are covered in fleet management KPIs.

    The cost difference is smaller than people expect

    Buyers usually assume telematics costs several times what basic tracking costs. In practice the hardware is similar, the SIM and data cost is nearly identical, and the difference sits in the software subscription. The larger cost is not on the invoice at all: telematics only returns anything if somebody looks at it weekly. A fleet that will not commit to that routine should buy the cheaper option honestly rather than buy the better one and ignore it.

    The full cost picture, including the recurring items people forget, is in what fleet GPS tracking costs.

    How to decide in five minutes

    1. Who drives the vehicles? If it is employees rather than owners, behaviour data has a job to do.
    2. Is fuel a cost you are trying to reduce? If yes, idle and behaviour data is the mechanism.
    3. Does anyone dispute your delivery or arrival times? If yes, journey and geofence records settle it.
    4. Do you schedule maintenance by date? If yes, usage data will change what you spend.
    5. Will someone review a weekly report? If nobody will, the extra data is decoration.

    Two or more yes answers, and telematics is the correct buy. Fewer than two, and plain tracking is not a compromise, it is the right fit.

    Frequently asked questions

    What is the difference between telematics and GPS tracking?

    GPS tracking provides the vehicle’s position. Telematics uses that position and adds driving behaviour, engine and usage data, alerts, scoring and reporting, so it answers how the vehicle was driven and what it cost rather than only where it is.

    Is GPS the same as telematics?

    No. GPS is a positioning technology and one input into a telematics system. Every telematics system uses GPS, but a GPS tracker is not a telematics system.

    Is telematics more expensive than GPS tracking?

    Somewhat, and mostly in the software subscription rather than the hardware or the SIM. The bigger difference is the time commitment, since telematics only returns value when someone reviews the data regularly.

    Can you upgrade from GPS tracking to telematics later?

    Often yes on the software side, but the hardware decides what can be measured. A device without motion sensing or an engine connection cannot produce behaviour or usage data no matter what software it reports to, so the device choice is worth getting right first.

    Which is better for a small fleet?

    It depends on who drives. If employees drive the vehicles and fuel is a real cost, telematics pays back faster in a small fleet than a large one because a single problem vehicle is a bigger share of the total. If the owner drives, plain tracking is usually enough.

    What is a GPS telematics system?

    One product built from four parts: a device in the vehicle, a mobile connection carrying its records, software that turns those records into maps and reports, and the fitting and support behind it. The satellite positioning layer is the foundation; the vehicle and behaviour data sits on top of it.

    What does GPS telematics mean?

    It is used as a single term for the combined system rather than as a comparison between two things. When someone says GPS telematics they usually mean tracking plus engine, behaviour and reporting data in one platform.

    Is GPS telematics the same as GPS tracking?

    No. GPS telematics includes GPS tracking, but adds the vehicle’s own data on top. A position-only tracker cannot be upgraded into one through software, because the hardware decides what can be measured.

    Does telematics track your location?

    Yes. Location is the foundation every other measurement is attached to, which is why a telematics system always includes what a GPS tracker does.

    What is the difference between telematics and telemetry?

    Telemetry is remote measurement of anything, from aircraft to hospital equipment. Telematics is telemetry applied to vehicles, with satellite positioning built in.

    Compare them on your own vehicles

    The comparison is easier when it is your fleet on the screen instead of a feature table. Get a Fleetile demo and see what the Fleetile platform reports beyond the map.

  • Telematics Data: What It Contains and How to Use It

    Telematics Data: What It Contains and How to Use It

    Telematics data is everything a tracked vehicle reports about itself: where it is, how it is moving, what the engine is doing, and which of your rules it has just broken. Fleets rarely suffer from having too little of it. They suffer from having six categories of it and a routine built around only one, which is why so many tracking systems get described as a map that nobody looks at.

    This guide covers what each category contains, what it is genuinely good for, and what to do with the parts that are not worth your attention.

    The six categories

    Category Examples Decision it supports
    Location Current position, route line, stop points Dispatch, customer questions, recovery after theft
    Journey Start and end times, distance, duration, stop length Billing, timesheets, delivery disputes
    Behaviour Speeding, harsh braking, acceleration, cornering Coaching, insurance conversations, accident risk
    Engine and usage Ignition, engine hours, idle time, fault codes Maintenance scheduling, fuel waste, replacement timing
    Exceptions Geofence events, out-of-hours movement, tamper alerts Immediate response while it still matters
    Derived Driver scores, utilisation, cost per kilometre Management decisions and reporting upward

    Notice that the categories get more useful as they get further from the raw signal. Location is the most detailed and the least decisive. Derived data is the most processed and the most likely to change what somebody does on Monday.

    Which data changes decisions

    Idle time is the fastest win

    Idle time is engine-on, vehicle-stationary time. It is easy to measure, easy to explain to a driver, and mostly habit rather than necessity, which is why it moves faster than almost anything else you can attack. It also has a direct fuel cost attached, so the argument for changing it makes itself. The detail sits in reducing vehicle idling.

    Behaviour data works only when it is shared

    A driver score kept in the office changes nothing. The same score shown to the driver changes a surprising amount, because most people adjust once they know a number exists and is being looked at. The data has to be fair to survive that conversation, which is why event thresholds and device quality matter as much as the reporting.

    Engine hours beat the calendar

    Service intervals based on dates treat a van doing constant city drops the same as one doing weekly motorway runs. Engine hours and real distance describe how hard each asset has actually worked, which is the basis of the approach in fleet maintenance management.

    Exceptions are the only data that needs to be live

    Everything else can be reviewed weekly. Exceptions cannot, because their value expires: a geofence breach or an out-of-hours movement is worth acting on within minutes and worth almost nothing in a monthly report.

    The part nobody warns you about

    The common failure is not missing data. It is alert fatigue. A fleet switches on every available notification, receives hundreds a week, and stops reading them by the second week. From then on the system is technically working and practically ignored.

    The fix is unglamorous:

    1. Turn on the smallest set of alerts that would make someone act immediately. For most fleets that is out-of-hours movement, tamper and geofence breach.
    2. Give every alert an owner and a response. An alert nobody is expected to act on should be a report line instead.
    3. Review the alert list monthly and delete anything that has never produced an action.
    4. Move everything else to a weekly summary, where volume is fine because nobody is expected to respond in the moment.

    How long to keep it

    Retention is worth deciding deliberately, because telematics data has two very different jobs. Operational use is short-lived, usually days. Evidential use is long, and it is the one that catches fleets out: an insurance claim, a customer dispute or a staff grievance can arrive months after the journey and is unanswerable without the history.

    • Live and recent detail: days to weeks, at full resolution.
    • Journey and event history: months, because disputes are slow.
    • Summaries and scores: years, since they are small and make trends visible.

    Keeping detailed data forever is not automatically the safer choice. Data about employees carries obligations, and holding more of it for longer than you have a reason to is a risk in itself, which is covered in employee vehicle tracking and privacy.

    Who should see what

    Telematics data is not one audience. A dispatcher needs the live map and nothing else. A fleet manager needs behaviour and exceptions. Finance needs distance, fuel and cost per kilometre, and has no use for the map at all. A customer, if you expose anything to them, needs the arrival time for their own delivery and nothing more.

    Setting this up as roles rather than one shared login is what stops the system feeling overwhelming, and it is also what keeps sensitive data away from people who have no business reason to see it.

    Frequently asked questions

    What is telematics data?

    It is the record a tracked vehicle produces about itself, covering location, journeys, driving behaviour, engine and usage, rule breaches, and the scores and totals calculated from all of those.

    What is telematics data used for?

    Mainly four things: reducing fuel and idle waste, coaching drivers and lowering accident risk, proving service times to customers, and scheduling maintenance on real usage rather than on a calendar.

    How long should telematics data be kept?

    Detailed data for weeks, journey and event history for months, and summarised scores and totals for years. The history matters because insurance claims and customer disputes often arrive long after the journey they concern.

    Is telematics data accurate enough to act on?

    For operational decisions, yes. Position is accurate to a few metres in open conditions, and engine and motion data comes from the vehicle itself. Small differences between tracked distance and an odometer reading are normal and do not indicate a fault.

    Who owns telematics data from company vehicles?

    The business operating the vehicles holds the data, but data about identifiable drivers carries obligations regardless of ownership. A written policy stating what is collected, why, and who can see it is the practical answer, and it is also what keeps drivers cooperative.

    Turn the data into a routine

    Data that nobody reviews is a cost rather than an asset. Get a Fleetile demo and see how the Fleetile platform puts each category in front of the person who can act on it.

  • Telematics Devices: The Four Types and How to Pick One

    Telematics Devices: The Four Types and How to Pick One

    A telematics device is the unit fitted to a vehicle that records where it is and what it is doing, then sends that record to your software. It is the least discussed part of a tracking system and the part that sets the ceiling on everything else, because software can only report what the device bothered to measure. There are four types in common use, and the right one depends less on budget than on what the vehicle is and what you need to prove.

    You will also see these called telematics units, telematics hardware or telematics equipment. They are the same thing. This guide covers the four types and how to choose between them; if you want to know what is physically inside one and how a record travels from the vehicle to your screen, see how telematics works.

    The four types

    Type How it fits Best for Main limitation
    OBD plug-in Into the diagnostic port under the dashboard Cars and light vans, short-term fleets, rentals Visible and removable in seconds
    Hardwired Wired to the vehicle’s power, hidden Owned fleets, anything where theft matters Needs a fitter and an hour per vehicle
    Battery powered Magnet or bolt, no wiring Trailers, containers, unpowered assets Reports less often to save battery
    Camera integrated Hardwired, with road and cab views Fleets managing accident risk and disputes Higher cost per vehicle and more data

    Most fleets end up with two of these rather than one. A mixed fleet with trucks, trailers and a few pool cars is badly served by insisting on a single device across everything.

    1. OBD plug-in devices

    These push into the diagnostic port that every car and light van built in the last two decades carries, usually under the dashboard near the steering column. Because the port supplies power and vehicle data together, the device starts reporting the moment it is pushed in, with no wiring and no fitter.

    That convenience is also the limitation. The port is in the cabin, in reach, and a device can be unplugged in the time it takes to bend down. For a rental fleet or a vehicle leaving in six months that is a fair trade. For a vehicle where theft is the reason you bought tracking, it is the wrong choice, because the first thing anyone taking the vehicle does is look for the tracker in the obvious place. Covered further in OBD2 GPS trackers.

    2. Hardwired devices

    These are wired directly to the vehicle’s power and hidden somewhere a casual search will not reach. They can be connected more deeply into the vehicle than an OBD unit, which is what makes engine data and remote commands possible, including immobilisation.

    The cost is an hour of a fitter’s time per vehicle and a vehicle off the road while it happens. Fleets usually schedule these in batches for that reason. This is the default for anything owned rather than rented, and the only sensible option where remote immobilisation is part of the plan.

    3. Battery-powered devices

    These have no connection to the thing they are attached to at all. They are magnet-mounted or bolted on, and they wake on movement rather than reporting continuously, which is what lets them run for a long time on a sealed battery.

    They answer one question well: where is it. They cannot answer how it was driven or how many hours the engine ran, because there is no engine to ask. That is not a shortcoming when the thing being tracked is a trailer, a generator, a bowser or a container, where location is the entire question. See trailer and container tracking and asset tracking systems.

    4. Camera-integrated devices

    A hardwired device with road-facing and often cab-facing cameras attached, so an event in the data has footage against it. When a harsh braking event is disputed, data says the brakes were applied hard and footage says a car pulled out. Only one of those settles an insurance claim.

    The trade is cost per vehicle, more data to move and store, and a conversation with drivers that has to be had properly rather than sprung on them. See video telematics and dashcams.

    What separates a good device from a cheap one

    Two devices with the same spec sheet can produce very different data. Four things decide it.

    Onboard storage

    Coverage gaps are normal on any route that leaves a city. A device with memory keeps recording during the gap and uploads the backlog when the signal returns, so the journey record stays complete. A device without it simply loses those kilometres, which shows up later as a mysteriously short trip in a report somebody is relying on.

    Sensible reporting logic

    The device decides when to send. Good logic reports frequently while moving, rarely while parked, and immediately on an event. Bad logic reports on a fixed timer regardless, which either wastes mobile data or misses the short stop that the whole delivery dispute turns on.

    A real accelerometer

    Harsh braking, harsh acceleration and cornering come from motion sensing, not from position. Devices that infer these from GPS speed alone produce noisy, unfair driver scores, and drivers stop trusting the numbers very quickly. This matters more than most buyers expect, because behaviour data is where the safety and fuel gains sit. Our guide to driver behaviour monitoring covers what those events are used for.

    Tamper detection

    A device that reports when it loses power or is unplugged is worth substantially more than one that goes quiet. Silence is ambiguous; a disconnect alert is not.

    Matching the device to the job

    • Owned commercial vehicles. Hardwired, every time. It is hidden, it cannot be pulled out at a stop, and it can read more from the vehicle.
    • Rental or short-term vehicles. OBD plug-in, because installation is measured in seconds and there is nothing to undo when the vehicle leaves the fleet.
    • Trailers, generators, containers and site equipment. Battery devices, accepting that you get several position reports a day rather than a live line. That is enough to answer where the asset is, which is the actual question.
    • Motorcycles. A compact hardwired unit with good tamper detection, since the theft risk profile is different. See motorcycle GPS trackers.
    • High-risk or high-dispute operations. Camera integrated, where the footage settles what the data alone only suggests. Covered further in video telematics and dashcams.

    Telematics devices in cars, and what factory-fitted units do not give you

    Car fleets have an extra complication that trucks do not. Many newer cars leave the factory with a telematics unit already built in, and buyers reasonably ask why they should fit another one.

    The built-in unit reports to the manufacturer, not to you. It exists to support breakdown assistance, servicing reminders and the maker’s own app. In most cases there is no route from it into a fleet platform, no way to see several brands of car on one map, and no access to the raw record when you need to prove something. It is a good feature and a poor fleet system.

    An aftermarket device solves the problem the factory unit creates, which is that a fleet of five brands means five apps and no single view. For cars specifically:

    • Owned company cars: hardwired, since the vehicle stays for years and private-versus-business mileage records matter.
    • Employee or grey-fleet vehicles: OBD plug-in, because it can be removed cleanly when the arrangement ends and nothing has been altered in someone’s own car.
    • Rental and pool cars: OBD plug-in, fitted and pulled in seconds as vehicles rotate.

    Installation decides how much of this you actually get

    A well-chosen device fitted badly performs like a cheap one. Three installation points matter more than any spec.

    1. Sky view. The device needs the antenna facing upward with as little metal above it as possible. Tucked under a metal bracket is the most common cause of poor position quality on an otherwise good unit.
    2. A permanent power source. Wiring into a circuit that dies with the ignition means the vehicle disappears whenever it is parked, which is exactly when theft happens.
    3. Somewhere not obvious. If the device is where a driver or a thief would look first, tamper detection is doing all the work on its own.

    What a telematics device cannot do

    Worth saying plainly, because a lot of buying disappointment comes from expecting one of these.

    • It cannot report data the vehicle does not publish. Fuel level, engine hours and fault codes come from the vehicle’s own systems. On an older vehicle that does not publish them, no device and no software will produce them.
    • It cannot fix a poor mounting position. An antenna under metal gives poor position quality regardless of how good the unit is.
    • It cannot see inside the load. Temperature, door state and weight need their own sensors wired to the device, not just the device.
    • It cannot identify who was driving unless a driver identification method is added, such as a key fob or a login. Without it, the data belongs to the vehicle rather than to a person, which matters before anyone builds a driver league table.
    • It cannot make up for retention limits. If the platform keeps thirty days of detail, a question asked in month three has no answer no matter what the device recorded.

    The cost that is not on the price tag

    Device hardware is a one-off number that people compare carefully. The recurring numbers matter more over three years: the SIM and data plan, the software subscription, installation labour, and replacement for the units that fail or get damaged. A cheaper device that reports poorly also has a hidden cost, which is every decision you did not make because the data was not trustworthy. The full picture is laid out in what fleet GPS tracking costs.

    Frequently asked questions

    What is a telematics device?

    It is the hardware fitted to a vehicle that records position, movement, engine state and motion events, then transmits them over the mobile network to tracking software. It is what turns a vehicle into a source of data.

    What is the difference between an OBD and a hardwired telematics device?

    An OBD device plugs into the diagnostic port and can be fitted or removed in seconds, which suits rentals and short-term use. A hardwired device is wired into the vehicle’s power and hidden, which suits owned fleets and anywhere the device needs to survive someone trying to remove it.

    Do telematics devices drain the vehicle battery?

    A correctly installed device draws very little and switches to a low-power state when the vehicle is parked. Battery problems usually come from an existing weak battery, a vehicle that sits unused for weeks, or an installation wired to the wrong circuit.

    Can a telematics device be installed on any vehicle?

    Effectively yes. Cars and vans generally take an OBD or hardwired unit, trucks and buses take hardwired units, and anything without its own power, such as a trailer or a generator, takes a battery-powered device instead.

    How long does telematics installation take?

    An OBD device takes under a minute. A hardwired device typically takes under an hour per vehicle for an experienced fitter, and it is usually scheduled in groups so vehicles come off the road together rather than one at a time.

    What are telematics devices?

    Units fitted to vehicles or equipment that record position and activity and send it to tracking software. Four types are in common use: OBD plug-in, hardwired, battery-powered and camera-integrated, and most fleets end up using more than one.

    What are the main types of telematics device?

    OBD plug-in for cars and short-term vehicles, hardwired for owned fleets and anywhere theft matters, battery-powered for trailers and equipment with no power of their own, and camera-integrated where footage is needed alongside the data.

    Is telematics hardware the same as a telematics unit?

    Yes. Telematics device, telematics unit, telematics hardware and telematics equipment all describe the same thing, the box fitted to the vehicle. The terms are used interchangeably by different suppliers.

    Do I need a telematics device if my car already has one built in?

    Usually yes, if you are running a fleet. The factory unit reports to the manufacturer rather than to you, so a mixed-brand fleet ends up with several apps and no single view. An aftermarket device puts every vehicle, whatever the badge or age, on one platform.

    Can one telematics device cover a whole mixed fleet?

    Rarely, and insisting on it is a common mistake. A fleet with trucks, trailers and pool cars is served properly by hardwired units on the trucks, battery devices on the trailers and OBD units on the cars, all reporting to the same platform.

    Get the device choice right the first time

    The wrong device is expensive to discover six months in. Get a Fleetile demo and see what each device type actually reports on the Fleetile platform before you commit a fleet to one.

  • How Does Telematics Work? The Journey From Vehicle to Dashboard

    How Does Telematics Work? The Journey From Vehicle to Dashboard

    Telematics works by moving one small piece of information through four stages: a satellite tells a device where it is, the device adds what the vehicle is doing, the mobile network carries that record to a server, and software turns thousands of those records into something a person can read. Understanding how telematics works is not academic. It explains why one system updates every ten seconds and another every two minutes, why data sometimes arrives late in a batch, and what to check first when a vehicle stops reporting.

    If you need the definition before the mechanism, read what telematics is first. This guide follows the data.

    The short answer

    A box in the vehicle listens to navigation satellites to work out where it is, adds what the vehicle is doing at that moment, and sends both to a server over a mobile connection. Software on the other end stitches those records into a map, a journey history and a set of alerts.

    Four things decide whether the result feels good or useless: how often the device reports, what it counts as worth reporting, whether it stores data when the network drops, and how much history the software keeps. Everything below is those four choices in detail.

    Stage one: the satellites work out where the vehicle is

    A GNSS receiver in the vehicle listens for signals from navigation satellites. Each signal carries the time it was sent, and because those signals travel at a known speed, the difference between sending and receiving gives a distance. With signals from four or more satellites, the receiver solves for a single point on the earth, plus altitude and a very accurate clock reading.

    Two things follow from this. First, the receiver only listens; it never transmits to the satellite, which is why position itself costs nothing to obtain. Second, the receiver needs a reasonably clear view of the sky. Underground car parks, dense high-rise streets and metal container yards are where position accuracy degrades, because the signal arrives reflected rather than direct.

    Most modern receivers use more than one constellation, not only the American GPS system, which is why accuracy in built-up areas has improved considerably over the last decade. Our guide to how GPS vehicle tracking works covers this layer in more detail.

    What is actually inside a telematics device

    “Telematics device” sounds like one component. It is really five, and knowing which is which makes most faults easy to place.

    Part Job What it explains
    GNSS receiver Works out position from satellite signals Why accuracy drops with no sky view
    Modem and SIM Sends records to the server Why there is a monthly cost per vehicle
    Accelerometer Detects braking, acceleration, cornering, impact Why driver scoring works without vehicle data
    Onboard memory Holds records when the network is unavailable Why a journey can complete after a coverage gap
    Power and wiring Draws power, and on wired units reads the vehicle bus Why some devices report engine data and others cannot

    The fifth one is where devices differ most. A unit plugged into a diagnostic port reads what the vehicle already publishes about itself. A unit wired in properly can also send commands back, which is what makes remote immobilisation possible. A battery-powered unit has neither, which is why it suits trailers and equipment rather than vehicles.

    This page is about how the parts work. If you are choosing between them, see telematics devices explained, OBD2 trackers and how to choose a device.

    Stage two: the device adds context

    A position on its own is a dot. What makes it useful is everything the device records alongside it.

    • Ignition state, which separates a vehicle that is parked from one that is stationary with the engine running.
    • Speed and heading, derived from successive positions and, on better devices, cross-checked against motion sensors.
    • Motion events from an accelerometer: harsh braking, harsh acceleration, sharp cornering, and impact-level forces.
    • Vehicle data, on devices wired into the vehicle’s own diagnostic connection, which can include engine hours, fault codes and fuel readings.

    The device does not send every reading. It applies rules: report every few seconds while moving, far less often while parked, and immediately when something notable happens. That logic is the single biggest difference between a cheap device and a good one, because it decides how much detail survives and how much mobile data the system burns.

    It is worth being concrete about what “notable” means, because this is where systems quietly differ. A well configured device treats ignition on and off, a geofence crossing, a harsh event and a power disconnection as things to send immediately, and treats ordinary movement as something to sample on a timer. A poorly configured one either sends everything, which is expensive, or sends on a timer only, which loses the events that matter.

    Stage three: the mobile network carries it

    The device holds a SIM and sends its records over the mobile network to a server. This is the stage that costs money per vehicle per month, and it is also the stage that fails most often, for entirely ordinary reasons: a coverage gap on a rural route, a tunnel, an area with congested towers.

    Good devices handle gaps by storing records in local memory and uploading the backlog when the connection returns. That is why a vehicle can vanish from the live map for twenty minutes and still produce a complete journey record afterwards. If your system loses the journey entirely during a coverage gap, the device is not buffering, and that is a hardware choice rather than a signal problem.

    This is also the difference people mean when they compare live tracking with the cheaper alternative that only stores data for later collection. Our comparison of real time versus passive tracking sets out where each one is honest value and where it is a false economy.

    Stage four: the software makes it readable

    The server receives a stream of records that mean nothing individually. The software’s job is to turn them into the four things a fleet actually uses.

    Raw input What the software produces
    Successive positions A route line, distance travelled, and a replayable journey
    Positions plus a drawn boundary Geofence entry and exit events with timestamps
    Speed readings plus road context Overspeed events rather than a wall of speed values
    Motion events over time A driver score that can be compared week to week

    This is also where map matching happens. Raw positions scatter slightly, so the software snaps them onto the road network to produce a clean line. Without it, every journey looks like the vehicle was weaving.

    What a telematics dashboard actually shows

    The word dashboard covers two different screens, and confusing them is why people sometimes feel a system is missing something it has.

    The live view answers where things are right now: every vehicle on one map with position, speed, heading and ignition state, refreshed continuously, with the last-seen time when a vehicle is out of coverage. This is the screen used during the working day.

    The reporting view answers what happened: journeys you can replay, hours worked, idle time, distance, alerts raised and how drivers scored. This is the screen used weekly, and it is the one that decides whether a system changes anything. See how to read fleet reports and what route playback gives you.

    Telematics in a car, and how it differs from a truck

    The mechanism is identical in a car. What changes is where the device comes from and what the data is used for.

    Factory fitted. Many newer cars leave the factory with a telematics unit already installed, reporting to the manufacturer. It is useful for breakdown assistance and servicing, but the data goes to the maker rather than to you, and it usually cannot be pulled into a fleet system.

    Aftermarket. A device you fit yourself, or have fitted, reports to a platform you control. This is what makes a mixed-age, mixed-brand fleet appear on a single map, which no factory system will do.

    The data emphasis shifts too. Car and van fleets lean on driver behaviour, private versus business mileage and fuel. Trucks and plant lean on engine hours, fuel monitoring and maintenance intervals. The platform should handle both without being a different product. See fleet telematics for the operational side.

    Telematics and navigation are not the same thing

    Both use satellite positioning, so they get confused constantly, but they point in opposite directions.

    Navigation works for the driver, inside the vehicle, in the present tense. It takes a position and gives directions to a destination. Nothing leaves the vehicle.

    Telematics works for the operator, away from the vehicle, and keeps a record. It takes the same position and sends it somewhere with a timestamp, so that someone elsewhere can see it now and refer back to it later.

    A vehicle can have both, and they do not talk to each other unless a system is built to join them. Route planning sits in between: it uses telematics history to decide better routes and then hands those to navigation. Our guide to route optimisation covers that overlap, and telematics versus GPS tracking covers the other comparison people ask about.

    Why systems feel different

    Two systems can use identical hardware and feel nothing alike. The differences almost always trace back to three choices.

    1. Reporting interval. A ten second interval feels live. A two minute interval feels like a slideshow and hides short stops entirely.
    2. What counts as an event. A system with badly tuned thresholds reports harsh braking every time a driver stops at a light, and the alerts get ignored within a week.
    3. How history is stored. Systems that keep detail for months can answer questions asked after the fact. Systems that summarise aggressively cannot.

    What to check when the data looks wrong

    Most reported faults are one of a small set of causes, and they are worth working through in order before assuming the device has failed.

    • Vehicle not reporting at all: power first, then SIM status, then device placement. A device moved under metal during a service is a common cause.
    • Position jumping around while parked: normal receiver scatter in a poor sky-view location, and usually harmless.
    • Distance slightly under the odometer: expected. The system measures straight lines between samples, and the odometer measures wheel rotations.
    • A missing chunk of journey that reappears later: a coverage gap with buffering working correctly.
    • Engine data missing while position works: the device is reading satellites but not the vehicle, so the fault is in the wiring or the diagnostic connection rather than the tracker.

    Step by step diagnostics are in GPS tracker troubleshooting, and choosing a GPS tracking device covers what to look for before buying rather than after.

    Frequently asked questions

    How does telematics work in a vehicle?

    A device in the vehicle receives satellite signals to calculate its position, records engine and motion data alongside it, and sends those records over the mobile network to software that turns them into live maps, alerts and reports.

    What is a telematics device?

    A small unit fitted to the vehicle containing a satellite receiver, a mobile modem and SIM, a motion sensor, onboard memory and a power connection. Wired units can also read the vehicle’s own data and send commands back to it.

    Does telematics use GPS or mobile data?

    Both, for different jobs. Satellites supply the position and cost nothing to receive. The mobile network carries that position to the server, which is the part that needs a SIM and a monthly data allowance.

    Is telematics the same as navigation?

    No. Navigation works for the driver, giving directions inside the vehicle, and nothing leaves the vehicle. Telematics works for the operator, sending timestamped records out so someone elsewhere can see them now and refer back to them later.

    How does car telematics work?

    Exactly as it does in any other vehicle. The difference is the source: many newer cars have a factory-fitted unit reporting to the manufacturer, while an aftermarket device reports to a platform you control and can cover vehicles of any age or brand on one map.

    How accurate is telematics data?

    Position is typically accurate to a few metres in open conditions and degrades in tunnels, underground parking and among tall buildings where signals arrive reflected. Engine and motion data taken from the vehicle itself does not depend on sky view at all.

    How often does a telematics device report?

    It varies by configuration. A common pattern is every few seconds while moving, much less often while parked, and immediately when an event such as harsh braking or a geofence crossing occurs. Shorter intervals give more detail and use more mobile data.

    What happens to telematics data when there is no signal?

    A device with onboard storage keeps recording and uploads the backlog once coverage returns, so the journey history stays complete. The live map is the only thing genuinely lost during the gap.

    What does a telematics dashboard show?

    Two things, on two screens. A live view with every vehicle’s current position, speed and ignition state, used during the day. And a reporting view with journeys, hours, idle time, distance, alerts and driver scores, used weekly to decide what to change.

    See the whole chain working

    Reading about the stages is one thing; watching a vehicle move across a live map with its own alerts firing is another. Get a Fleetile demo and see the Fleetile platform handle the full journey from vehicle to dashboard.

  • Fleet Telematics: What It Is and What It Actually Changes

    Fleet Telematics: What It Is and What It Actually Changes

    Fleet telematics is the practice of collecting data from vehicles while they work and turning it into decisions a manager can act on. A device on each vehicle records position, movement, speed and engine activity, sends it over the mobile network, and software on the other end assembles it into live maps, alerts and reports. The word combines telecommunications and informatics, but the useful definition is simpler: it is how a fleet finds out what its vehicles did without asking anyone.

    If you want the broader concept rather than the fleet application, start with what telematics is. This guide is about the fleet side: what the data covers, what it replaces, and what changes once it is in place.

    What fleet telematics actually collects

    Most fleets picture a moving dot on a map. That is the smallest part of it. A working telematics setup produces four broad families of data, and the value sits mostly in the last three.

    Data family What it contains What it answers
    Position and journey Location, route taken, stops, arrival and departure times Where is the vehicle, where has it been, how long did it stay
    Driving behaviour Speed, harsh braking, harsh acceleration, cornering How is the vehicle being driven, and by whom
    Engine and usage Ignition state, engine hours, idle time, distance How hard is the asset working, and when is it wasting fuel
    Exceptions Geofence entries and exits, out-of-hours movement, overspeed events What happened that should not have

    The first family answers questions. The other three raise them, which is where the return comes from. A fleet that only looks at the map is using a fraction of what it is paying for.

    Fleet telematics versus a plain vehicle tracker

    A consumer tracker tells you where one car is. Fleet telematics assumes many vehicles, many drivers and somebody accountable for the total cost of running them. That difference shows up in the features rather than the hardware.

    • Comparison, not observation. Fleet software ranks vehicles and drivers against each other, so the outliers surface without anyone hunting for them.
    • Exceptions, not watching. Nobody can stare at a map all day. The system pushes an alert when something breaks a rule you set.
    • Reporting for people who were not there. Finance, insurers and customers all ask questions after the fact. Fleet telematics answers them from a record rather than from memory.
    • Roles and access. A dispatcher, an owner and a client each need a different view of the same vehicle.

    The practical test is this: if the software cannot tell you which three vehicles cost you the most this month and why, it is a tracker rather than a telematics system.

    What fleets use it for

    Controlling fuel

    Fuel is usually the largest cost a fleet can actually influence. Telematics attacks it from three sides at once: it exposes idling, it exposes the driving style that burns fuel faster, and it exposes routes that are longer than they needed to be. It also makes losses visible by matching fuel purchases against distance genuinely travelled, which is the starting point for the work described in reducing fuel theft in your fleet.

    Reducing risk

    Speeding, harsh braking and fatigue-shaped driving patterns are visible long before they turn into an incident. Fleets that act on that data are managing risk while it is still cheap. The alternative is finding out from a damage report.

    Proving service

    Arrival and departure times recorded automatically settle delivery disputes without argument. For contract work, that record is often worth more than the fuel savings, because it protects the contract itself.

    Keeping assets alive

    Engine hours and distance drive maintenance schedules far more accurately than a calendar does. A van doing city drops and a van doing motorway runs age at different speeds, and only one of them is well served by a fixed service interval.

    What changes in the first ninety days

    Fleets that get value quickly follow a similar path, and it is deliberately unambitious at the start.

    1. Weeks one to two: baseline. Install, confirm every vehicle reports, and then change nothing. You need an honest picture of normal before you can call anything abnormal.
    2. Weeks three to four: the obvious waste. Idle time and out-of-hours movement usually produce the first savings, because both are habits rather than hard problems.
    3. Weeks five to eight: behaviour. Share driver scores with drivers. Most of the improvement comes from people knowing the number exists, not from discipline.
    4. Weeks nine to twelve: routine. Pick a handful of measures, give them an owner, and review them on a fixed cadence. Our guide to fleet management KPIs covers which ones earn a place.

    The failure mode is the opposite: switching on every alert on day one, drowning in notifications, and quietly ignoring the system by week three.

    What it does not do

    Telematics does not manage a fleet. It removes the excuse of not knowing, which is a different thing. It will not fix a routing problem you have not looked at, coach a driver nobody has spoken to, or reduce a cost nobody owns. Fleets that treat the dashboard as the outcome tend to conclude the technology did not work, when what did not work was the routine around it.

    It also does not need to cover everything on day one. Starting with the vehicles that carry the most cost or the most risk gives you a result you can point at, which is what funds the rest of the rollout.

    Frequently asked questions

    What is fleet telematics in simple terms?

    It is a device in each vehicle that records where it goes and how it is driven, and software that turns those records into maps, alerts and reports. It lets a fleet manage vehicles on evidence rather than on what drivers report at the end of the day.

    Is fleet telematics the same as GPS tracking?

    GPS tracking is one part of it. GPS supplies the position; telematics adds driving behaviour, engine and usage data, alerts and reporting on top. A system that only shows location is doing the smallest part of the job.

    How many vehicles do you need before telematics is worth it?

    There is no threshold. The economics depend on how much fuel and risk sit behind each vehicle rather than on the count, and small fleets often see a faster payback because a single problem vehicle is a larger share of the total.

    Does fleet telematics work without mobile signal?

    Yes, with a delay. Devices store data while out of coverage and upload it once the connection returns, so the journey record stays complete even though the live view pauses.

    What is the hardest part of adopting fleet telematics?

    The conversation with drivers, not the installation. Fleets that explain what is measured and why get cooperation; fleets that install quietly get resistance and disabled devices. The privacy side of employee vehicle tracking covers how to handle it.

    See your own fleet’s data

    Every number above comes from vehicles doing real work, not from a template. Get a Fleetile demo and see what the Fleetile platform reports for a fleet like yours.

  • Last Mile Delivery Tracking: How to Fix the Most Expensive Leg

    Last Mile Delivery Tracking: How to Fix the Most Expensive Leg

    A parcel can travel hundreds of kilometres cheaply and then consume a disproportionate share of its total delivery cost in the final few. That final leg is where the vehicle stops constantly, where traffic and parking eat the schedule, where addresses turn out to be wrong, and where the customer is not home. Last mile delivery tracking is how delivery operations get control of it, by making every stop visible, every arrival provable and every ETA honest. This guide covers what to track, what it fixes and how to measure whether it worked.

    Why the last mile is so expensive

    The economics are simple. On a trunk route, one driver moves a full load between two points. On the last mile, the same driver makes dozens of individual stops, each with its own approach, parking problem, walk to the door and possible failure. Cost per parcel rises steeply as drops become smaller and more scattered.

    Three costs dominate, and all three are visibility problems before they are logistics problems:

    • Failed deliveries, where the customer is absent and the parcel must be carried again another day, effectively doubling the cost of that drop.
    • Support load, from customers calling to ask where their delivery is, which is pure overhead.
    • Overtime, when routes planned optimistically run past the shift.

    What last mile tracking actually gives you

    Live position and honest ETAs

    The most valuable output of last mile tracking is not the map, it is the estimated arrival time derived from it. A customer told a realistic window is far more likely to be present, which directly reduces failed deliveries. An ETA based on live position and real travel times is honest; one based on a plan made at 6am is a guess that gets less accurate all day.

    Proof of arrival, automatically

    Geofences around delivery addresses record arrival and departure without the driver doing anything. That produces an objective record of when the vehicle was at the door, which settles the most common delivery dispute of all: the customer who says nobody came. The mechanics are covered in geofencing for fleets.

    Real service times per stop

    How long a drop actually takes varies enormously between a ground-floor shop and a fifth-floor apartment. Tracking captures the real figure per address, which feeds directly back into planning. This is the single biggest input to realistic routing, as described in route optimization for delivery fleets.

    Fewer “where is my order” calls

    Every customer who can see where their delivery is does not call to ask. For high-volume operations this alone can justify the system, because support calls scale with parcels while a tracking platform does not.

    The metrics that tell you it is working

    Metric What it shows
    First-attempt delivery rate The headline measure of last mile efficiency
    Stops per hour Route quality and realistic scheduling
    Average service time per stop Where time actually goes at the door
    On-time rate against the promised window Whether your ETAs are honest
    Distance per parcel Routing efficiency, independent of volume
    Failed delivery reasons Which failures are fixable and which are not

    First-attempt delivery rate deserves the most attention, because every failure costs a second journey. Improving it usually means better ETAs and better address data rather than faster driving, which makes it one of the safest levers available.

    Motorcycles, vans and mixed fleets

    Last mile operations increasingly run mixed fleets, with motorcycles handling dense urban drops and vans handling bulkier loads. Tracking has to cover both on one map, otherwise dispatch cannot see which unit is genuinely closest to a new order. Motorcycles bring their own considerations, particularly around theft, which we cover in the guide to the motorcycle GPS tracker.

    Dispatch is where a mixed fleet either works or does not. Assigning by live position rather than by whose turn it is, or by who the dispatcher happens to remember, is the difference between a fleet that absorbs an unexpected order and one that delays three others to fit it in.

    Practical steps to improve the last mile

    1. Measure your first-attempt rate honestly, broken down by area and time of day.
    2. Replace planned service times with recorded ones, so routes stop being optimistic fiction.
    3. Give customers a real ETA derived from live position, and narrow the window only as far as you can actually deliver.
    4. Geofence delivery points so arrival is recorded without driver input.
    5. Review failed deliveries weekly and separate the fixable causes from the genuinely unavoidable ones.
    6. Feed everything back into planning monthly, so each cycle of routes is built on better data than the last.

    The reporting behind this, live tracking, geofenced timings, trip history and stop analysis, sits together on the Fleetile platform, and the wider cost picture is covered in GPS tracking for logistics and delivery fleets.

    Frequently asked questions

    What is last mile delivery tracking?

    It is the tracking of vehicles and riders during the final leg of a delivery, from the local depot to the customer’s door. It combines live vehicle position, geofenced arrival records at each stop, and estimated arrival times shared with the customer.

    How does tracking reduce failed deliveries?

    Mainly through better arrival estimates. A customer given a realistic, live-updated window is far more likely to be available, and a failed delivery avoided saves an entire second journey. Recorded arrival times also resolve disputes about whether an attempt was actually made.

    Does last mile tracking work for motorcycle fleets?

    Yes, and motorcycles are common in dense urban delivery precisely because they handle congestion and parking better. The same live tracking, geofencing and dispatch tools apply, with theft protection carrying extra weight because bikes are easier to steal.

    What is a good first-attempt delivery rate?

    It varies widely by area type, customer mix and delivery model, so your own trend matters more than any external benchmark. Establish a baseline, break it down by area and time slot, and work on the segments that underperform your own average.

    Can customers see the delivery vehicle’s location?

    Many operations share a live view or a narrowing ETA with the recipient, which reduces support calls and improves the chance someone is there to receive the parcel. How much detail to share is a business decision, and an arrival window is often sufficient without exposing the vehicle’s full route.

    Fix the most expensive leg

    The last mile rewards visibility more than any other part of the delivery chain. Get a Fleetile demo and see live tracking, geofenced arrivals and stop reporting working on one screen.

  • Employee Vehicle Tracking and Privacy: Doing It the Right Way

    Employee Vehicle Tracking and Privacy: Doing It the Right Way

    Employee vehicle tracking fails more often for cultural reasons than technical ones. The hardware works, the map loads, the alerts fire, and yet the programme stalls because drivers believe it was installed to catch them out. Once that belief takes hold it is very hard to reverse, and a fleet ends up with a system nobody trusts and data nobody acts on. This guide covers how to introduce GPS tracking to a workforce transparently, what to disclose, and where the sensible line sits between managing a vehicle and monitoring a person.

    The distinction that matters: vehicle, not person

    The clearest principle in this whole subject is that you are tracking a company asset during working hours, not an individual. That sounds like a technicality, but it shapes every decision that follows and it is the honest framing.

    A company vehicle is an expensive asset carrying company liability, and knowing where it is during the working day is ordinary management. What crosses the line is following someone into their private life: tracking a take-home vehicle overnight and at weekends when personal use is permitted, or using location data for purposes nobody was told about. Keep the purpose tied to the vehicle and the working day and most objections dissolve.

    What to disclose, before anything is fitted

    Disclosure is not a formality to complete afterwards. Undisclosed monitoring damages trust permanently and undermines any action you later try to take based on the data. Cover all six of these in writing, in plain language:

    • What is collected: location, speed, engine on and off, harsh braking, idle time, trip start and end.
    • When it is collected: during working hours only, or continuously, and if continuously then why.
    • Who can see it: which named roles have access, and who does not.
    • What it is used for: dispatch, safety coaching, fuel reconciliation, theft recovery, claims defence.
    • How long it is kept: a specific retention period, not “as long as necessary”.
    • What it will not be used for: this is the reassurance drivers actually want, and stating it explicitly is worth more than the rest combined.

    These belong in the company vehicle policy and should be walked through in person, not emailed as an attachment nobody opens.

    Handling take-home vehicles and personal use

    This is where most genuine privacy concerns live, and where policies are usually weakest. If a driver takes a vehicle home and is permitted to use it personally, continuous tracking means recording their private movements, which is a materially different thing from tracking a working shift.

    There are reasonable approaches. Some fleets restrict monitoring and reporting to working hours. Some provide a privacy mode the driver can enable for personal trips, which records that a private journey occurred without logging where it went, while still protecting the vehicle through theft alerts. Some simply do not permit personal use, which removes the problem entirely but is not always practical.

    What matters is choosing an approach deliberately, writing it down, and applying it consistently. Drivers accept clear rules far more readily than they accept ambiguity, because ambiguity invites them to assume the worst.

    Introducing tracking without losing trust

    1. Announce it before it happens. Discovering a tracker fitted quietly is the single fastest way to poison a programme.
    2. Explain the actual reasons. Theft recovery, faster dispatch, fuel reconciliation, protection against false claims. These are real and drivers understand them.
    3. Show what it protects them from. Tracking data defends a driver accused of speeding they did not do, of an accident they did not cause, or of a late arrival that was actually a traffic closure.
    4. Apply it to everyone. Including managers and directors with company vehicles. Exceptions at the top destroy credibility instantly.
    5. Start with information, not enforcement. Run an initial period where the data is shared and discussed rather than used for discipline.
    6. Let drivers see their own data. Access to their own trips and scores changes the relationship from surveillance to feedback.

    That last point is the most underrated. Drivers who can see their own figures tend to improve without being asked, which is the same dynamic described in driver behaviour monitoring.

    Where tracking genuinely protects drivers

    Situation How tracking helps the driver
    Accused of causing a collision Speed and position record supports their account
    Blamed for a late delivery Trip history shows the actual delay and where it occurred
    Accused of a traffic offence Records establish which vehicle was where, and when
    Unsafe schedule Data shows the route cannot be run legally in the time given
    Vehicle stolen while parked Recovery is fast, and the driver is not left under suspicion

    Access control and data discipline

    Transparency also means limiting who can see what. Not everyone in an organisation needs live location access, and unrestricted access invites casual curiosity that has nothing to do with managing a fleet. Define roles, grant the minimum each role needs, review the list periodically, and remove access when people change jobs.

    Set a retention period and stick to it. Keeping everything forever creates a growing liability with no operational benefit, while keeping too little leaves you unable to defend a claim. Match retention to a real need, such as the period during which a claim could be brought, and document the reasoning. The permissions and reporting controls that support this are part of the Fleetile platform.

    Frequently asked questions

    Is it legal to track employee vehicles?

    Tracking company-owned vehicles used for work is normal practice in most places, provided employees are informed and the purpose is legitimate and proportionate. The specific requirements vary by jurisdiction, particularly around personal use and data retention, so confirm the rules that apply to you and put the disclosure in writing.

    Do I have to tell employees their vehicle is tracked?

    Yes, and you should want to. Beyond any legal requirement, undisclosed tracking destroys trust and weakens your position if you ever rely on the data in a disciplinary or claims process. Explain it clearly before installation, not afterwards.

    Can we track a vehicle outside working hours?

    Only where there is a clear reason and it has been disclosed, such as theft protection on a parked vehicle. If personal use is permitted, restricting monitoring to working hours or offering a privacy mode for private trips is the fairer approach and avoids recording an employee’s private movements.

    How do I get drivers to accept tracking?

    Announce it early, explain the real reasons, show the situations where it protects them, apply it to everyone including management, and give drivers access to their own data. Programmes fail when tracking appears suddenly and the first thing anyone hears about it is a complaint about their driving.

    Who should be able to see tracking data?

    Only the roles that need it for a defined purpose, such as dispatch, fleet management and safety. Access should be granted by role rather than shared informally, reviewed periodically, and removed when someone changes position or leaves.

    Set it up so people trust it

    A tracking system people accept produces far better results than one they resent. Get a Fleetile demo and see the access controls, driver-facing views and reporting that make transparent tracking practical.

  • GPS Tracking and Fleet Insurance: How Telematics Affects Your Premium

    GPS Tracking and Fleet Insurance: How Telematics Affects Your Premium

    Fleet insurance is priced on risk, and risk is priced on evidence. Without tracking, an insurer has very little evidence about your fleet beyond claims history and a few generic factors, so you are rated largely on the average of fleets that look like yours. GPS tracking changes that conversation, because it produces an actual record of how your vehicles are driven, where they operate and what happens when something goes wrong. This guide covers the four ways tracking affects your insurance position, and only one of them is the premium.

    1. Lower risk, evidenced

    Insurers care about the behaviours that precede claims: speeding, harsh braking, night driving, and operating in high-risk areas. A fleet that monitors these and can show a downward trend is objectively lower risk than one that cannot say anything about them.

    The important word is evidenced. Telling an underwriter that your drivers are careful is worth nothing. Showing speeding events per hundred kilometres falling quarter on quarter, with a coaching programme behind it, is a different conversation entirely. Our guide to driver behaviour monitoring covers how that programme works, and fleet management KPIs covers how to present the numbers.

    2. Faster, cleaner claims

    Most of the cost of a claim is not the repair, it is the time spent establishing what happened. Tracking data shortens that dramatically. Where the vehicle was, what speed it was doing, which direction it was travelling, and whether it braked before impact are all recorded automatically with timestamps.

    That means claims are settled faster, disputes over fault are shorter, and your own version of events is documented rather than remembered. Route replay, described in route playback, is often the single most useful thing you can hand an insurer.

    3. Protection against false and inflated claims

    This is the benefit fleets consistently underestimate until it happens to them. Staged accidents and exaggerated claims are a real cost, and they rely on the absence of independent evidence. A claim asserting that your vehicle was somewhere it was not, or was travelling far faster than it was, collapses immediately against tracking data.

    The same applies to claims that a vehicle caused damage while it was demonstrably parked elsewhere. Trip history is not an opinion, and that changes the negotiating position entirely.

    4. Stolen vehicle recovery

    Recovered vehicles produce smaller claims, and quickly recovered vehicles often produce none at all. Live tracking, movement alerts and remote engine cut all improve recovery odds, which over time shows up in your claims history and therefore your renewal. The security side is covered in preventing vehicle theft in your fleet.

    What insurers actually look for

    Insurers want to see What it demonstrates
    Speeding events, normalised by distance Driving culture, not just mileage
    Harsh braking and acceleration trends Whether risk is improving or worsening
    Driver scores over time An active management programme
    Out-of-hours and unauthorised use Control over when vehicles are on the road
    Theft protection in place Reduced total loss exposure
    Documented coaching actions That the data leads to change

    The last row is the one fleets skip. Data alone shows you are watching. Data plus a record of what you did about it shows you are managing, and that is what earns credibility with an underwriter.

    How to use tracking data at renewal

    Do not wait until renewal week. Build the case over the year:

    1. Establish a baseline early so you have a starting point to improve from.
    2. Track the safety metrics consistently, normalised by distance so the numbers are comparable across drivers and periods.
    3. Document what you changed: coaching sessions, policy updates, route changes, vehicles taken off night work.
    4. Show the trend, not a snapshot, because direction of travel matters more to an underwriter than any single figure.
    5. Bring it to the renewal conversation as a short pack rather than raw exports nobody will read.

    Ask your broker or insurer directly what data they would find useful, since some will have specific formats or metrics they prefer. A fleet that arrives with organised evidence is a fleet that gets underwritten on its own record rather than on a category average.

    A realistic expectation

    It is worth being straightforward about this: installing trackers does not automatically reduce a premium, and any supplier promising a specific discount is guessing. What tracking does is give you the evidence to argue your case, the tools to genuinely lower your risk, and the records to settle claims faster and defeat false ones. The premium effect follows from the improved claims record over time, which is a slower but far more durable result. The underlying capability, live tracking, alerts, driver scoring and trip history, sits on the Fleetile platform.

    Frequently asked questions

    Does GPS tracking reduce fleet insurance premiums?

    Not automatically. Tracking gives you evidence of lower risk and the tools to reduce it, and premiums follow from an improving claims record and a credible safety programme. Treat any promise of a guaranteed discount with caution, and ask your own insurer what evidence they will actually take into account.

    Will insurers accept GPS data as evidence in a claim?

    Tracking records are widely used to establish location, speed and timing during claims and disputes, and they are often decisive where accounts conflict. What matters is that the data is complete, timestamped and retrievable, which is why data retention and export are worth confirming with your provider.

    Can tracking protect against false claims?

    Yes, and this is one of its clearest benefits. A claim placing your vehicle at a location or speed that the tracking record contradicts is very difficult to sustain, which discourages both staged incidents and honest but mistaken accounts.

    What tracking data should I keep for insurance purposes?

    Trip history with positions and timestamps, speed records, harsh event data and driver scores, kept for at least as long as a claim could realistically be brought against you. Confirm the retention period your provider offers and whether the data can be exported if you ever change systems.

    Do I need a dashcam as well as GPS tracking?

    They answer different questions. GPS tracking establishes where, when and how fast, while video establishes what happened in view of the camera. Fleets with high claim exposure often use both, as covered in our article on video telematics and dashcams.

    Build the evidence before you need it

    The best time to start recording your fleet’s safety record is well before renewal. Get a Fleetile demo and see the reports that make the case for you.

  • Company Vehicle Policy: What to Include and How to Enforce It

    Company Vehicle Policy: What to Include and How to Enforce It

    Most organisations have a company vehicle policy somewhere. Rather fewer have one that anybody reads, and fewer still have one that can actually be enforced. The gap matters, because a policy is what you fall back on when a vehicle is damaged, when fuel spend does not add up, or when someone is stopped driving a company car at midnight on a weekend. If the rules were never clear, or were never measurable, those conversations go badly. This guide covers what belongs in a company vehicle policy and how GPS tracking turns each rule into something you can verify.

    Why most vehicle policies fail

    Vehicle policies usually fail for one of three reasons. They are vague, using words like “reasonable” and “appropriate” that mean different things to different people. They are unmeasurable, prohibiting things nobody can detect. Or they are unenforced, which teaches everyone that the rules are optional and makes the first attempt at enforcement look arbitrary.

    A good policy avoids all three by being specific, measurable and applied consistently from the day it starts. That last part is the hardest and the most important.

    What to include in a company vehicle policy

    1. Who may drive, and under what conditions

    State who is authorised to drive each vehicle, what licence checks are required and how often they are repeated, and whether family members or colleagues may ever drive. Insurance usually depends on getting this right.

    2. Personal use rules

    This is the most disputed area, so it deserves the clearest language. Say plainly whether personal use is permitted, when, within what geographic area, and who pays for the fuel. If commuting is allowed but weekend use is not, write exactly that rather than something open to interpretation.

    3. Fuel rules

    Cover how fuel is paid for, which stations may be used, what receipts or records are required, and that fuel purchases will be reconciled against vehicle location. Fuel is where most quiet losses occur, as covered in reducing fuel theft in your fleet.

    4. Driving standards

    Set out the speed expectation, the position on mobile phone use, seatbelt requirements, and what happens with traffic fines. State that speed and harsh driving events are monitored, and what level triggers a conversation.

    5. Vehicle care and reporting

    Define the daily or weekly checks expected, how damage must be reported and how quickly, and who arranges servicing. Late damage reporting is a common and expensive problem, and it is almost always a policy gap rather than a discipline one.

    6. Tracking and privacy

    Explain that vehicles are tracked, what data is collected, when it is collected, who can see it, how long it is kept, and what it is used for. Being explicit here is not just fair, it is what makes the rest of the policy enforceable. This deserves proper treatment, and we cover it separately in employee vehicle tracking and privacy.

    7. Incidents and accidents

    Provide a simple sequence to follow after any incident: who to call, what to record, what not to admit at the roadside, and when the report is due. People do not think clearly after a collision, so the instructions must be short enough to follow under stress.

    8. Consequences

    State what happens when the policy is breached, with a graduated scale rather than a single severe penalty. A policy with no stated consequence will not be taken seriously, and one with only a harsh consequence will not be applied.

    How tracking makes each rule enforceable

    Policy rule How it becomes measurable
    No unauthorised personal use Out-of-hours movement alerts and trip history
    Stay within the operating area Geofence around the permitted region
    Observe speed limits Speed alerts and events per hundred kilometres
    Fuel only for company use Fuel purchases reconciled against vehicle position
    Minimise idling Idle time per vehicle and per driver
    Report damage promptly Harsh impact events timestamped against the report

    The point is not surveillance for its own sake. It is that a rule you cannot measure is a suggestion, and suggestions do not hold up when a dispute arises.

    Introducing the policy without a fight

    How a policy is launched determines whether it is accepted or resented. A few things consistently help.

    Explain the reasons rather than only the rules, since drivers accept a policy far more readily when they understand it protects the business, their colleagues and often themselves. Involve drivers before publishing, because they will spot rules that are impossible to follow in practice and that feedback is worth having early. Apply it to everyone including managers, as nothing destroys a vehicle policy faster than visible exceptions at the top. Give notice before enforcement begins, and start with a period where breaches are discussed rather than penalised. Finally, review it annually, because vehicles, routes and technology change and a stale policy loses credibility.

    Keep it to one page people will read

    A long policy document is a policy nobody knows. Write the full version for the record, then produce a one-page summary covering the handful of rules that come up in daily life: personal use, fuel, speed, phone use, damage reporting and what is tracked. That is the version drivers should sign and keep. The measurement behind it, alerts, geofences, trip history and reports, all sits on the Fleetile platform, and the metrics worth reviewing are covered in fleet management KPIs.

    Company car policy, fleet policy or vehicle policy?

    The same document goes by several names and the choice is mostly about what you run. A company car policy usually covers cars allocated to individuals, where personal use and tax treatment are the difficult parts. A company fleet policy covers vans, trucks and shared vehicles, where the difficult parts are who is authorised to drive what and how vehicles are handed between people. A company fleet vehicle policy is simply both of those in one document.

    Whatever you call it, the structure below works for all of them. If you run both allocated cars and shared commercial vehicles, write one policy with a short section that states which rules apply to which group, rather than maintaining two documents that will drift apart.

    Company vehicle fuel policy

    Fuel is where most policies are weakest, because the rule is usually written as an instruction rather than a limit. “Use fuel responsibly” cannot be enforced. A workable company vehicle fuel policy answers four questions in plain terms:

    • Who pays, and how. Fuel card, reimbursement on receipt, or company account. Name the method and say what happens when someone uses another one.
    • What may be fuelled. The assigned vehicle only. This one line is what makes filling a private car on the company card a policy breach rather than an argument.
    • What counts as a private mile. Whether private mileage is permitted, and if so how it is recorded and settled.
    • What is reviewed and how often. Fuel spend against distance travelled, per vehicle, monthly.

    That last point is what makes the rest enforceable. Fuel purchased is a number you already have; distance travelled is a number tracking gives you. A vehicle whose fuel spend does not match the distance it covered is the only reliable way to see a problem that no one is going to report. Our guide to reducing fuel theft covers what to do once you spot one.

    Vehicle tracking policy: what to write

    If vehicles are tracked, the tracking needs its own section rather than a line buried elsewhere. A vehicle tracking policy exists to do two things: satisfy the legal requirement to tell people, and remove the suspicion that grows when the rules are unstated. It is short, and it should answer exactly these questions:

    • What is recorded. Location, trips, speed, idling and the other fields you actually use. List them.
    • When it is recorded. Working hours only, or at all times. If vehicles go home with drivers, say what happens outside working hours.
    • Who can see it. Named roles, not “management”.
    • What it is used for. Safety, fuel, dispatch, proof of service. Say what it will not be used for as well.
    • How long it is kept. A retention period, and what happens at the end of it.

    A company vehicle tracking policy written this way is usually accepted without much argument, because it answers the question people are actually worried about. One written vaguely, or introduced after the devices are already fitted, rarely is. Employee vehicle tracking and privacy covers the legal and practical side in more detail.

    Driver safety in the policy

    A company fleet usage and driver safety policy is the same document with the safety rules made explicit rather than assumed. The safety section is worth separating because it is the part that has to survive an incident investigation, and vague wording there is expensive.

    Cover the things that can be measured: speed against posted limits, harsh braking and acceleration, seatbelt use, mobile phone use while driving, hours behind the wheel and mandatory rest, and what a driver must do after any incident however minor. Then state how performance is reviewed and what happens at each stage, so a driver knows the sequence before they are ever in it.

    A company vehicle policy template

    Use this as the skeleton and fill in your own figures. It is deliberately short, because a policy people read is worth more than a policy that is complete.

    1. Purpose and scope. Which vehicles and which employees this policy applies to, and the date it takes effect.
    2. Eligibility to drive. Licence requirements, minimum experience, licence checks and how often they are repeated, and who authorises a new driver.
    3. Permitted use. Business use, commuting and private use stated separately, with named exceptions.
    4. Other drivers. Whether family members or colleagues may drive, and the approval needed.
    5. Fuel. Payment method, what may be fuelled, private mileage treatment, and the monthly review.
    6. Driving standards. Speed, phone use, seatbelts, alcohol and drugs, hours and rest.
    7. Vehicle care. Daily checks, cleanliness, servicing intervals, tyres, and how defects are reported and by when.
    8. Tracking. What is recorded, when, who sees it, what it is used for, and how long it is kept.
    9. Incidents and accidents. What to do at the scene, who to notify and within what time, and the paperwork required.
    10. Fines and penalties. Who pays, and how they are recovered.
    11. Leaving the company. Return of the vehicle, keys, fuel card and equipment, and the condition expected.
    12. Breaches. The stages, who decides, and the right of appeal.
    13. Acknowledgement. A signature line and date, kept on file.

    The acknowledgement line at the end is the part most often left off and the part most often needed. A policy nobody signed is difficult to rely on later.

    Frequently asked questions

    What should a company vehicle policy include?

    At minimum: who may drive, personal use rules, fuel rules, driving standards, vehicle care and damage reporting, what tracking is in place and why, the procedure after an incident, and the consequences of a breach. Each rule should be specific enough that both sides can tell whether it was followed.

    Can we restrict personal use of company vehicles?

    Yes, provided the restriction is set out clearly in the policy and in employment terms, and applied consistently. Vagueness is the usual problem: state whether commuting counts, what geographic limits apply, and who pays for fuel on personal journeys.

    Do we have to tell employees vehicles are tracked?

    You should always tell them, both as a matter of fairness and because undisclosed monitoring undermines any action you later try to take based on it. Explain what is collected, who sees it, how long it is kept and what it is used for, and check the specific requirements that apply in your jurisdiction.

    How do we handle traffic fines?

    State in the policy who is responsible, how fines are identified to a driver, and how payment or recovery is handled. Trip history makes it straightforward to establish who was driving at the time, which removes most of the argument.

    How often should the policy be reviewed?

    Annually is a sensible default, and sooner if you change vehicle types, add tracking capabilities or run into a situation the current policy did not anticipate. Every review should be communicated rather than quietly filed.

    What is the difference between a company car policy and a fleet policy?

    A company car policy usually covers cars allocated to named individuals, where personal use and tax are the awkward parts. A company fleet policy covers shared vans, trucks and commercial vehicles, where authorisation and handover are the awkward parts. Most organisations that run both are better served by one document with a section stating which rules apply to which group.

    What should a vehicle tracking policy say?

    What is recorded, when it is recorded, who can see it, what it is used for and what it will not be used for, and how long the data is kept. Keep it to those five points and put it in the policy before the devices are fitted rather than afterwards.

    Is a company vehicle policy template enough on its own?

    A template gives you the structure, not the decisions. The figures, the approval routes and the consequences are yours to set, and they are the parts that make it enforceable. Use the outline above as a skeleton and fill in what actually applies to your fleet.

    Make the policy measurable

    A vehicle policy is only as strong as your ability to see whether it is being followed. Get a Fleetile demo and see how alerts, geofences and trip history turn written rules into something you can actually verify.