Fleet
Manage fleet vehicles and assign them to rentals.
Overview
Fleet manages your vehicles — vans, trucks, artics, trailers, and cars. Vehicles are their own records with an API, custom fields, files, activities, and warehouse scoping. Fleet stays separate from CRM accounts (contacts, companies, venues).
Fleet UI routes:
| Route | Purpose |
|---|---|
/fleet |
Vehicle index with saved views and CSV export |
/fleet/create |
Add a vehicle |
/fleet/diary |
Fleet diary — every vehicle's runs and route stops for a day |
/fleet/{vehicle} |
Vehicle overview — Today & next and vehicle facts |
/fleet/{vehicle}/utilisation |
Utilisation and flagged assignments |
/fleet/{vehicle}/details |
Compliance information and activities |
/fleet/{vehicle}/history |
Audit history |
/fleet/{vehicle}/edit |
Edit a vehicle |
/fleet/{vehicle}/activities |
Activities against the vehicle |
/fleet/{vehicle}/files |
Vehicle attachments |
/fleet/{vehicle}/custom-fields |
Custom field values |
/fleet/{vehicle}/tabs/{key} |
Plugin-registered tabs |
Vehicle records
The create and edit form groups vehicle identity, dimensions and Warehouse assignments. Expand More details for description and the optional Rental charge item. Custom fields and the profile image follow the main fields.
A vehicle carries a registration plate, payload, volume, and dimensions (length × width × height), plus a configurable vehicle type drawn from a list (Van, Truck 7.5t, Artic, Trailer, Car). Compliance data — MOT, insurance, and service dates — is not built in; admins can add Vehicle custom fields for these dates like any other custom field.
The fleet index supports saved live filters, column configuration, and CSV export. Vehicles also appear in global search under their own group, matched by name and plate.
Optional rental charge item
A vehicle can optionally link to one Rental or Service catalogue item. The fleet form shows that item's available rate ladder as a read-only check; a vehicle without a link remains purely logistical. Sale items cannot be linked.
Assigning vehicles to rentals
Open a rental and use the Vehicles tab (/rentals/{rental}/vehicles) to assign vehicles for the job. Search the fleet, then optionally set a role (Vehicle Assignment Role list), an advisory starts at / ends at window (placeholders inherit from the rental when left blank), and notes. Roles, windows, and notes can be edited inline when you hold vehicles.assign; Unassign removes the row.
When the selected vehicle has a rental/service charge item, Add charge line is offered before assignment. It creates an ordinary rental line with the assignment's concrete window and lets the normal rate engine resolve the price — it does not copy a manual price or pin a rate. Removing an assignment warns that its charge line remains, and removing that line warns that the assignment remains; both actions require a second confirmation and deliberately leave the other record intact.
Cross-rental conflict detection is active for vehicle assignments: overlapping bookings of the same vehicle on different rentals are detected (same-rental multi-leg runs — a delivery and a collection on one job — are legitimate and never conflict). Assigning the same vehicle twice on one rental shows a soft duplicate warning rather than blocking.
The vehicle overview leads with headline registers and briefing, then Today & next in the main column and one vehicle facts sidebar. The registers cover payload and cross-rental conflicts. Utilisation is a direct link to weekly utilisation and flagged assignments. More → Details holds compliance information and activities, and More → History opens the audit history. Custom fields and files have their own subpages. No servicing, MOT or inspection records exist on vehicles; use configured custom fields where needed.
Fleet diary
Resources › Services › Fleet diary (/fleet/diary) is the Resource Timeline's vehicle route day on its own page. It reads the same assignment rows, honours the same warehouse filter and 500-booking cap, and opens the same conflict review.
- Day — one day at a time (
?day=). ‹ Today › and the date picker sit right-aligned in the toolbar and step a day; the strip above the grid shows the week's days with their runs and stops. Today is marked in the brand colour. - Lanes — one per vehicle booking that touches the day, from depot out to depot back, with the vehicle name, plate, rental and status. Route stops sit at their arrival time (▼ delivery, ▲ collection, ◆ pickup, ■ return) with their time on site, inside the rental's shaded delivery or collection window; an arrival after the window is a Late risk. Crew booked on the same rental that day are listed beneath (over 10 hours flagged; none is flagged No crew booked). On today, the now line (Settings › Branding › Schedule) marks the current time. Vehicles with nothing that day are listed as No runs.
- Run sheet — select a vehicle for its booking, crew and every stop, with Print run sheet and Open vehicle; select a stop for its details. Both are view-only and deep-linkable (
?panel=run:{assignment},?panel=stop:{id}); stops are ordered and edited on the rental.

The Fleet diary for one day: vehicles with their runs, numbered stops and crew beneath.
- Unscheduled transport — a read-only tray of orders delivered or collected that day by the company (not the customer) with no vehicle booked.
The diary needs vehicles.view and resource-assignments.access; the Fleet diary button on the fleet list only appears with both. Mileage and a driver role are not stored, so the diary shows travel time between stops and "No crew booked" rather than miles or "No driver". The key is below the grid.
Permissions
| Permission | Grants |
|---|---|
vehicles.view |
See the fleet and vehicle detail |
vehicles.create |
Add vehicles |
vehicles.edit |
Edit vehicles |
vehicles.delete |
Soft-delete vehicles (blocked while the vehicle has active rental assignments) |
vehicles.assign |
Assign and unassign vehicles on rentals |
Warehouse-restricted users see only vehicles whose warehouses intersect their accessible warehouses.
API
Vehicles are served at /api/v1/vehicles. Success responses place the vehicle object or collection in data, with optional root meta. Nested rental assignment routes use the same envelope — see the Vehicles API.