Fleet Management maintains a single operational registry of every vehicle and piece of equipment the organisation owns or operates, and layers the lifecycle activity of each asset on top of it. Its core capabilities fall into a small number of tightly related areas. Inspections cover pre-trip, periodic and regulatory checks, each driven by a schedule and a checklist so that a driver or technician records a consistent, auditable result rather than a free-form note. Repair orders track corrective work whether it is carried out by an internal workshop or an external supplier, itemising parts and labour against the vehicle. Preventive maintenance programmes generate work before failure occurs, triggered by elapsed time or accumulated mileage and surfaced through alerts. Around these sit fuel and mileage tracking, driver assignment and licence management, and cost tracking per vehicle, so that usage, responsibility and expenditure are all attributed to the correct asset. Together these capabilities turn a fleet from a list of registration plates into a managed portfolio of operational assets.

The central entity is the vehicle or equipment asset, carrying its identity: make, model, VIN or serial number, registration, and current assignment to a location, department or driver. Everything else in the module hangs off this record. An inspection combines a schedule, a checklist template and a recorded result, and belongs to an asset and an inspector. A repair order captures a fault, the work performed, the parts consumed and the labour booked, and resolves to an internal or external provider. A preventive maintenance programme defines the interval, whether mileage or time based, and spawns due maintenance events with their alert thresholds. Fuel and mileage entries build the usage history that both drives mileage-based maintenance and feeds cost analysis. A driver record holds licence details, categories and expiry, and links a person to the assets they are cleared to operate.

The unifying concept is cost attribution. Every inspection, repair, part, litre of fuel and maintenance event carries a cost that accrues to its asset, so the model can express total cost of ownership as a first-class figure rather than a spreadsheet reconstruction. The registry is therefore both an operational index and a costing dimension.

The module organises daily activity around a handful of recurring processes. The inspection workflow presents the right checklist for the right inspection type, records pass, fail or advisory results item by item, and where a check fails, opens or proposes a repair order so that a defect is never simply logged and forgotten. The repair workflow moves an order from reported fault through diagnosis, parts and labour booking, and completion, keeping a full history against the vehicle whether the work was internal or subcontracted. The preventive maintenance workflow runs continuously in the background: as mileage accrues or time passes, the programme evaluates each asset against its interval and raises an alert when service is due or overdue, which then becomes a scheduled repair or service order.

Two supporting workflows keep the operational picture honest. Driver assignment couples a cleared, licensed driver to an asset and checks licence validity and category against the vehicle, flagging expiries before they become a compliance breach. Fuel and mileage capture feeds the usage record that both triggers maintenance and populates the cost ledger for each vehicle.

Depth in this module is a matter of discipline rather than decoration. Regulatory inspection is treated as a controlled process: schedules ensure statutory checks are not missed, checklists enforce a defined scope of examination, and recorded results form the evidence trail an operator needs to demonstrate roadworthiness and duty of care. Licence management applies the same rigour to people, holding categories and expiry dates so that an unlicensed or lapsed driver cannot be quietly assigned to a vehicle they are not entitled to operate.

On the financial side, the module is built to support total cost of ownership analysis. Because acquisition, fuel, maintenance, repair, parts and labour costs all attribute to the individual asset, the module can express the running cost of a vehicle over its life and compare assets on a like-for-like basis. Those operational costs are the raw material for allocation into the ledger and for informed decisions on repair-versus-replace and fleet renewal. The registry also aligns operational identity with the asset accounting record, so the vehicle you inspect is demonstrably the vehicle you depreciate.

Fleet Management is deliberately narrow in what it owns and explicit about where it hands off. It integrates with Fixed Assets so that each vehicle and major piece of equipment is linked to its capitalised asset record and its depreciation schedule, keeping operational lifecycle and accounting lifecycle in step. It integrates with Accounting and Control so that fuel, parts, labour and external repair costs are allocated to the correct cost centres and the running cost of the fleet is reflected in the financial position rather than stranded in an operational silo. It integrates with Device Management to draw telematics and IoT signals from the vehicles themselves: odometer readings, location and utilisation data that feed mileage-based maintenance and usage costing without manual re-keying.

This positioning keeps the module coherent. It is the operational system of record for the fleet, and it relies on the suite's financial and device modules for capitalisation, costing and live telemetry rather than duplicating them.

Fleet Management is built for a suite where AI Workers are first-class users, and they operate inside it in several concrete ways. Through conversational query, a manager can ask which vehicles are overdue for service, which drivers hold licences expiring this quarter, or what a given asset has cost to run this year, and receive an answer drawn from live module data rather than a static report. Through action execution, a Worker can raise a repair order from a failed inspection item, schedule a preventive service, or reassign a vehicle, within the permissions granted to it.

AI Workers also watch for anomalies and exceptions: a fuel entry inconsistent with recorded mileage, a maintenance interval repeatedly missed, or a repair cost far above the norm for an asset class, each raised as an alert before it becomes a loss. They perform document and data extraction, reading an external repair invoice or an inspection certificate and populating the corresponding order or record. They offer decision support, weighing accumulated cost against residual value to inform repair-versus-replace calls. And they act as approval or review nodes in workflows, for example screening a driver assignment for licence validity or reviewing a high-value external repair before it is authorised, participating in the same controls as their human colleagues.