Daily Driver Reports
Formbird FLEET provides several reports for reviewing Daily Driver check sheet completion, identifying missing pre-starts, analysing defects and failures, and correcting meter data.
Daily Driver Analysis Report
The Daily Driver Analysis Report provides a summary of Daily Driver check sheets completed within a chosen date range, broken down by defect and repair outcome.
The report displays a chart and table showing the following counts for the period:
| Metric | Definition |
|---|---|
| Total | All qualifying Daily Driver documents within the date range. |
| No Defects | Documents where no defects were reported. |
| Defects | Documents where at least one check was failed, or a defect description was entered. |
| Repaired < 24hrs | Defects where the time between In Progress Date and Work Complete Date was less than 24 hours. |
| Repaired 24–48hrs | Defects where repair time was 24 hours or more but less than 48 hours. |
| Repaired < 48hrs | Defects resolved within 48 hours in total. |
| Repaired < 30 Days | Defects resolved within 30 days. |
Use this report to monitor defect rates across the fleet, track how quickly reported faults are being resolved by the workshop, and identify assets or periods with elevated fault rates.
Daily Driver Check Duration Report
The Daily Driver Check Duration Report identifies instances of 'tick-and-flick' form completion — where checks appear to have been recorded without actually being carried out. It provides two independent approaches for detecting this behaviour.
The report period defaults to today and is limited to a maximum of 31 days. Enter a Start Date and End Date, optionally enter a Reported By to filter by the person who submitted the form, then select Run Report.
Report by Duration of Completed Daily Driver
This section measures how long the operator took to complete the form — from when it was first opened to when the Inspection Complete checkbox was checked. The assumption is that a complete inspection takes a minimum amount of time; an unusually short duration suggests checks were not genuinely performed.
Results are grouped by the Reported By field and show:
- Link to the Daily Driver request
- Reported by (operator name)
- Time the form was opened
- Time the Inspection Complete checkbox was checked
- Duration between open and complete (minutes)
- Count of completed checks
- Average seconds per check (duration ÷ total checks)
A Count and Average Seconds per Check Type chart displays each check type's average completion time alongside the check count. Hover over a column for detail.
Select Show Links to Checks to display a table of links to the individual check documents.
This section requires minimal configuration — no expected durations need to be set up in advance. However, it assumes operators fill out the form in sequence; if checks are performed before the form is opened, durations may appear artificially short.
Report by Duration of Individual Checks
This section uses timestamps recorded when each check entry is made — either when a radio button is selected or a comment is entered. The time between consecutive check entries is used as a proxy for the time spent on each check.
If an expected completion duration is configured on the check itself, results are grouped by whether the duration was less than or greater than or equal to that expected value.
Results are grouped by Reported By and show, for each user:
- Count of check durations
- Count and percentage of checks completed faster than the expected duration
- Count and percentage of checks meeting or exceeding the expected duration
- Total and average seconds across all checks
- Underlying check data
This section requires expected duration values to be configured on individual check questions. Historical daily drivers without timestamps against every check are excluded.
Daily Driver Check Listing
The Daily Driver Check Listing is a list of Daily Driver check sheets with reported defects. It is the primary tool for reviewing and actioning faults outside of the Workshop Dashboard — workshop staff can work through reported defects individually and action them from a single list without navigating into each asset's record.
See Actioning Daily Driver Faults for the full fault actioning process.
Daily Driver Exception Documents
Lists all Daily Driver Exception documents across the fleet. Use this report to review the history of exceptions and their current status. Each row links to the underlying exception document.
See Daily Driver Exceptions for how exceptions are generated and managed.
Daily Driver Exception Report
The Daily Driver Exception Report summarises exception activity across the fleet for a chosen period — showing which assets triggered exceptions, how many were generated, and their current status. Use it to identify assets where pre-start compliance is consistently poor.
See Daily Driver Exceptions for how exceptions are generated.
Daily Driver Failure Analysis Report
The Daily Driver Failure Analysis Report shows a count of failed checks per asset within a chosen date range. Unlike the Daily Driver Analysis Report — which tracks defect and repair outcomes — this report focuses purely on which specific checks were failed and how many times.
A check appears in this report when a radio button on a Daily Driver is marked as Fail. The report groups results by asset and shows, for each asset, each failed check type with the count of failures in the period.
Filters
| Filter | What it does |
|---|---|
| Asset Group | Limits results to all assets in a selected group. |
| Asset | Limits results to a specific asset. |
| Pre-Set Times / Date range | Sets the Daily Driver date range to search within. |
Use this report to identify assets with recurring check failures — for example, an asset that consistently fails the same lighting or brake check — which may indicate an underlying fault that is being repeatedly reported but not resolved.
Daily Driver Meter Error Management Report
The Daily Driver Meter Error Management Report is a tool for reviewing and correcting meter readings on Daily Driver documents that have been flagged as errors.
When an operator saves a Daily Driver, the meter entries are automatically checked. Readings that fail the checks are flagged as errors and excluded from the nightly asset meter update. This report displays all flagged readings grouped by asset so they can be reviewed and corrected in one place.
Error Types
| Error | What it means |
|---|---|
| Primary Meter < Asset Meter | The submitted reading is lower than the asset's current primary meter value. |
| Secondary Meter < Asset Meter | The submitted reading is lower than the asset's current secondary meter value. |
| Range Error | For assets with fewer than 6 Daily Driver records, the calculated distance or hours since the last reading exceeds 1,600 km or 24 hours. |
| Averaging Error | For assets with more than 5 Daily Driver records, the submitted reading exceeds the expected value based on the historical average, factoring in a configurable error margin. |
| Meter Length Error | The number of digits in the reading is longer than both the previous and next readings — suggesting a transcription error (for example, an extra digit entered). |
Readings flagged with any of these errors have the Excluded From Asset Update checkbox marked on the Daily Driver document, preventing them from being applied to the asset's meter.
Reading the Report
Results are grouped by asset. The asset group header shows:
- Asset ID (linked to the asset record)
- Current primary and secondary meter values
- Total distance or hours consumed across the period (calculated as last reading minus first reading — shown in red if negative)
- A summary of all error types found
Each row in the table shows the Daily Driver document name (linked), the date it was created, the primary and secondary meter readings, and the errors identified.
Correcting Readings
Meter readings are listed in date-ascending order within each asset group.
- Review the readings in sequence. Compare each reading to the ones before and after it to identify what the correct value should be.
- Enter a corrected value in the Primary or Secondary input field on the relevant row.
- Where a Split button appears, selecting it automatically calculates the midpoint between the previous and next valid readings. Use this as a starting point where the exact correct value is unknown.
- Once all corrections are entered, select Apply Updates. This updates the meter fields on the Daily Driver documents and clears the Excluded From Asset Update flag so the corrected readings are eligible for the next nightly update.
When multiple consecutive errors exist, the Split method may not be reliable — the previous and next readings both need to be valid for the split calculation to be meaningful. In these cases, update each document in sequence before applying.
Daily Driver Complete / Not Completed Today Report
The Daily Driver Complete / Not Completed Today Report shows which assets have had a Daily Driver completed today and which have not, given that a pre-start was expected for them. Use it as a daily compliance check to identify assets that have been put into service without a completed pre-start.
Untrained Daily Driver Report
The Untrained Daily Driver Report identifies operators who have not completed the required Daily Driver training. Operators who appear in this report may be unable to submit Daily Driver check sheets depending on your organisation's configuration.
Use this report to track training compliance and follow up with operators or supervisors before gaps affect pre-start coverage.
Published: May 2026 · Formbird FLEET 4.2.8