العودة إلى المدونة
Corporate Solutions

Fleet Management Software: How to Track Company Vehicles

The difference between vehicle tracking and fleet management software, where the GPS device fits, inspection, insurance and service calendars, driver assignment, fuel and fine tracking, off-the-shelf or custom.

Araç TakipFilo YönetimiAraç Yönetim ProgramıKurumsal Çözümler

Fleet management software is not a map showing where company vehicles are; it is a system that keeps, in one record per vehicle, who has it, what it costs and which deadline is approaching. The GPS device provides location, and the fleet software ties that location to the vehicle, the driver and the cost. A company with five vehicles can run this in a spreadsheet; a company with twenty vehicles, three branches and rotating drivers will sooner or later face an overdue inspection, a traffic fine nobody owns and a fuel bill nobody can explain.

Is vehicle tracking the same as fleet management?

The two terms are used interchangeably in searches, but they answer different questions. Vehicle tracking asks "where is the vehicle now, how fast is it going, when was the ignition turned on", and the device fitted to the vehicle answers it. Fleet management asks "what did this vehicle cost us this month, who is it assigned to, when is its inspection, when does its insurance expire", and that answer comes from records, not from a device. Many businesses buy devices first and discover a few months later that nobody looks at the map, because the real pain is not location but dates and costs.

A GPS device is a data source, not fleet management. The device says "the vehicle stopped for 40 minutes"; the software tells you which order, which driver and which cost line that stop belongs to.

For companies that ship and deliver goods, the load on the vehicle and proof of delivery are a separate topic, covered in our post on software for transport and logistics companies. This post covers the problem every business with company cars shares, whatever its sector: managing the vehicle itself.

Records belong to the vehicle, not the driver

This is the first decision in the data model. Drivers change, the vehicle stays; inspection, insurance, service history and the odometer line are properties of the vehicle. The driver is linked to the vehicle with a date range: Ahmet from 3 March to 18 April, Mehmet from 18 April onward. If this link is not time-stamped, the most common dispute cannot be resolved: a speeding fine or toll violation that arrives three weeks later is assigned by who was driving on that day. "Who has it now" does not answer that question; "who had it on that date" does.

  • Vehicle card: plate, VIN, model, registered owner, ownership type (owned, long-term lease, financial lease).
  • Assignment history: driver, start and end date, odometer and damage notes at handover and return.
  • Date calendar: inspection, emissions test, mandatory traffic insurance, comprehensive cover, lease contract end.
  • Service log: work done, odometer, amount, workshop; the date and mileage threshold for the next service.
  • Cost lines: fuel, tolls, fines, tyres, damage repair, lease payments.

Inspection, insurance and service: never missing a date

The most tangible loss in fleet management is a missed date. Driving a vehicle with an expired inspection risks fines and the vehicle being taken off the road; damage under expired insurance comes straight out of the company’s pocket. The software should not just list these dates but create a task for the responsible person as they approach. For servicing, the rule is a double threshold: a set mileage or a set period, whichever comes first. A rarely used vehicle may never reach the mileage, but its oil and filter interval still expires. The same logic we described from the workshop side in auto repair shop software is set up here from the fleet owner’s side.

type Vehicle = {
  plate: string;
  odometerKm: number;
  inspectionDue: Date;
  insuranceDue: Date;
  lastServiceKm: number;
  lastServiceDate: Date;
};

const SERVICE_KM = 15000;
const SERVICE_MONTHS = 12;
const WARN_DAYS = 30;

function addMonths(date: Date, months: number): Date {
  const d = new Date(date);
  d.setMonth(d.getMonth() + months);
  return d;
}

function daysBetween(a: Date, b: Date): number {
  return Math.floor((b.getTime() - a.getTime()) / 86400000);
}

export function upcomingTasks(v: Vehicle, today: Date): string[] {
  const tasks: string[] = [];
  if (daysBetween(today, v.inspectionDue) <= WARN_DAYS) tasks.push('inspection');
  if (daysBetween(today, v.insuranceDue) <= WARN_DAYS) tasks.push('insurance');

  const kmLeft = v.lastServiceKm + SERVICE_KM - v.odometerKm;
  const serviceDate = addMonths(v.lastServiceDate, SERVICE_MONTHS);
  if (kmLeft <= 1000 || daysBetween(today, serviceDate) <= WARN_DAYS) {
    tasks.push('service');
  }
  return tasks;
}

The thresholds in the example are illustrative; the real service interval depends on the manufacturer and usage and is stored as a separate field per vehicle. What matters is that mileage is not a number typed in by hand but a value that arrives automatically from the GPS device or the fuel card. Manually entered mileage stops being updated by the third month, and service reminders quietly break.

Fuel, tolls and fines: where does the cost go?

The real cost of a fleet is not the purchase price but running costs, and these come from scattered sources: fuel card statements, toll notifications, traffic fine notices, workshop invoices. Once the software pulls these in, two reports become meaningful: cost per kilometre per vehicle and violation history per driver. On the fuel side, the most useful check is simple: does the fuel card purchase match the distance GPS recorded that day? A mismatch is not always misuse, but it is a deviation that needs explaining.

  • Fuel card and toll data should be imported regularly through files or a service; a cost report based on manual entry cannot be trusted.
  • Fines are entered with date and time, and the system finds the driver automatically from the assignment record at that moment.
  • Damage records are linked to the vehicle with photos, the incident report and the insurance claim number.
  • Cost per kilometre is compared by vehicle type; a large gap between two vehicles of the same model points to a maintenance or usage problem.

Location data and employee privacy

A vehicle’s location is the location of the person driving it, so it is treated as personal data. In practice three principles apply: the purpose is defined in writing up front (safety, cost, operations), employees are informed, and for vehicles allowed for private use outside working hours, the handling of location is set out in a clear rule. A retention period should also be defined; years of minute-by-minute location history are both a risk and a cost. For more detail see our post on KVKK-compliant software. This post is not legal advice; confirm your approach with your legal counsel.

Off-the-shelf or custom software?

Most companies that sell GPS devices also provide a dashboard, and for small fleets that may be enough. Custom software usually makes sense in the following situations; if at least two apply, consider it seriously:

  • The fleet has devices from different vendors, or vehicles with no device, and all must appear on one screen.
  • Vehicle costs need to flow automatically into accounting, HR or the ERP system.
  • Assignment, approval and fine recharge rules are company-specific (branch budgets, a policy for recharging drivers).
  • Vehicles are part of another business process: field teams, service technicians or rentals.

Before deciding, ask whether your current device exports its data: if there is an API or a regular data feed, a management layer can be built on top without replacing the device. We explain how such connections work in what is API integration; for the general decision framework see custom software or an off-the-shelf solution. If the vehicles are used by teams working in the field, building it in the same system as field service management software avoids double data entry.

Conclusion

Good fleet management software starts with a calendar, not a map: once each vehicle’s card, assignment history, upcoming dates and cost lines live in one record, GPS data gains meaning too. Open the record on the vehicle, link drivers by date range, track servicing by mileage and time thresholds, and take costs from the source rather than from spreadsheets. If you are planning a management system for your fleet, see our corporate solutions page or get a quote.

Let's Build Your Project

Get a free consultation for your website, mobile app, or corporate software project.

Get a Free QuoteExplore our Corporate Solutions service