FleetTime by DesignWorks
FLEETTIME SUPPORT

How can we help?

Answers follow the approved 2.9.13 manual, with the 2.9.14 driver-entry update. Match instructions to your installed version. This is searchable guide help, not conversational AI.

Still need help? Open a support ticket

Features

Connected records.
Clearer daily decisions.

Explore the main areas of FleetTime and follow the links between the records that make up your operation.

01

Fleet asset and equipment cards

Find vehicles, trailers and equipment through compact connected records. Review status, due dates, evidence and the selected main photograph without creating duplicate assets.

02

Miles, kilometres and plant hours

Keep the unit, reading date and source visible. Equipment can use operating hours, distance, both or neither. Explicit conversion avoids silently relabelling a vehicle reading.

03

Licence and CPC records

Record checks, points, entitlements, expiry dates and evidence against one driver. The Driver Card separates the last licence check, next check and CPC verification. This is manual check logging, not automatic DVLA verification.

04

Working-time monitoring

Review weekly working time and reference averages, with missing weeks kept explicit. The normal 17-week reference, 48-hour average and separate 60-hour weekly ceiling are distinct. Daily driving, rest and break checks need sufficient activity data.

05

Optional maintenance costs

Record parts, labour, other costs, VAT, cost centre and invoice reference against work. January–December charts and detailed reports distinguish actual costs, estimates and unknown amounts.

06

Fuel, fines and incidents

Review recorded purchases, cases, payments and costs by division and period. Use trend panels, filters and linked records to investigate exceptions. An alert indicates a review need, not confirmed misuse or liability.

07

Documents in one place

Search permitted document metadata across the operation, preview supported originals and return to the source record. Access follows the user’s section and document permissions; automatic full-text OCR is not promised.

08

Central reviewed imports

Bulk Uploads provides one starting point for the operational import tools. Review recognised columns, dates, units, duplicate warnings and unmatched records before committing source data.

09

Individual access and recovery

Create individual accounts and grant the sections/actions needed. Network administrators review computer pairing requests separately from user permissions. Complete backups include uploaded originals and can use encrypted multipart archives.

Inside FleetTime

See the actual software.

These illustrations are captured from the 2.10.0 testing build using fictional demonstration records. Click an image to see it at full size. Features and instructions should be matched to your installed version.

Fleet Dashboard in the FleetTime 2.10.0 fictional demonstration workspace
Fleet Dashboard · fictional data
Fleet Asset Card in the FleetTime 2.10.0 fictional demonstration workspace
Fleet Asset Card · fictional data
Equipment Card in the FleetTime 2.10.0 fictional demonstration workspace
Equipment Card · fictional data
Driver Card in the FleetTime 2.10.0 fictional demonstration workspace
Driver Card · fictional data
Fuel overview in the FleetTime 2.10.0 fictional demonstration workspace
Fuel overview · fictional data
Fines overview in the FleetTime 2.10.0 fictional demonstration workspace
Fines overview · fictional data
Accidents and incidents in the FleetTime 2.10.0 fictional demonstration workspace
Accidents and incidents · fictional data
Bulk Uploads in the FleetTime 2.10.0 fictional demonstration workspace
Bulk Uploads · fictional data

The operational detail

Keep evidence and decisions connected.

Assets and relationships

Keep a permanent asset ID alongside registration, Ministry identifier, VIN or serial number. Trailers and linked equipment retain their own maintenance and VOR history. Applicability and actual evidence determine which checks matter.

Inspections and insurance

Review supported provider lists, matches, findings, certificates and supplied insurer schedules. A source Active status or a schedule match does not independently prove safe availability or insurance cover. Provider API onboarding and live validation remain separate.

Workshop and recovery

Plan maintenance and equipment movements with location and job references. Keep originals with the record and verify a complete backup before upgrades or recovery. Cloud-sync folders can hold backup sets; ordinary synchronisation is not a live multi-user database connection.

2.10.0 is a testing build. RAM collection needs acceptance testing against the user’s RAM account. Browser-store publication, commercial code signing and Microsoft Store release are separate publisher work.