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.
See Reports Overview for how to find these reports. The Daily Driver Report also appears directly on the Workshop Dashboard.
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.
Set a Report Start Date and Report End Date, or choose a range from the Pre-Set Times dropdown (Yesterday, Last Week, Last Month, Last Calendar Year, Last 7 Days, Month To Date, Current Financial Year To Date, Previous Financial Year, Last (rolling) 12 months), then select Run Report.
The report displays a pie 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 Report Start Date and Report End Date, optionally filter by Reported By, Asset, or Asset Group, then select Run Report. Daily Driver requests with only one check are excluded, as a single check has no meaningful duration to compare.
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 (Completed Checks (excl. Additional Checks), shown in red if it doesn't match the total number of checks assigned) and Additional Checks — any checks the operator added beyond the standard assigned checklist
- 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
Select a row in the summary table to filter the underlying check data table below it down to that person only; deselect to clear the filter. In the underlying data, each check's duration is shown in green if it met or exceeded its expected duration, or red if it was faster than expected.
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 lists completed Daily Driver check sheets, whether or not they generated a repair. 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.
By default the list is filtered to Display Failed Only (checked, shows only check sheets with a failed check and a defect description) and Show Status set to Pending and Open — untick or change these to see closed or defect-free check sheets. Also available: Created Date >/Created Date < to filter by date, and Display Urgent Only to show only Urgent priority faults. The Failed Checks column lists which specific checks failed, Request Generated shows whether a repair request already exists for the check sheet, and Duplicate Failure Last Reported (within 30d) lists prior fail dates for the same fault within the last 30 days, to help spot repeat faults.
Use the Grid Click Function dropdown to choose what selecting a row does: Select (the default, for the actioning workflow below) or Display Checklist, which instead opens the full check sheet inline.
See Actioning Daily Driver Faults for the full fault actioning process.
Daily Driver Completion Exception Documents
Lists Daily Driver Exception documents. The list defaults to today's date range; set Start Of Day > and < End Of Day to widen it. Columns show the exception's Responsible Person, Asset, Date Created, driver details (Driver Name / Email, Driver First Name, Driver Surname — populated from the telematics integration, so may be blank if the integration doesn't provide them), and trip details (Trip Start, Trip End, Driving Duration, Distance). Each row links to the underlying exception document. Exception documents have no status field — they are a fixed record of what happened, not something to action from this list.
A Checked For Driving Assets note near the top shows how long ago the exception-generation check last ran, refreshing automatically every minute.
See Daily Driver Management for how exceptions are generated and managed.
Daily Driver Exception Report
The Daily Driver Exception Report summarises exception activity per asset for a chosen period, showing which assets triggered exceptions, how many Daily Drivers they completed in the same period, and how many of those Daily Drivers were created after an exception had already been recorded for that day (a sign the operator eventually caught up, just not before being flagged). Use it to identify assets where pre-start compliance is consistently poor.
It defaults to Yesterday and runs automatically on load. Choose a different Pre-Set Times range or set Start Of Day >/< End Of Day directly, then select Run Report. Only assets with Daily Driver Check Required and an active telematics device are included. Totals for Total Exceptions, Total Daily Drivers, and Total DD Created > Exception Date are shown above the table.
Select an asset's row in the summary table to load a detail table below it, listing each exception day for that asset with its Exception Trip Stop Date, Responsible Person, and (where one exists) the matching Daily Driver, its DD Creation Date, and DD Created By.
See Daily Driver Management 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 completed Daily Driver is marked as Fail — Daily Drivers not yet marked as Inspection Complete are excluded. The report groups results by asset and shows, for each asset, each failed check type with the count of failures in the period. A bar chart above the table totals failure counts per check type across every asset in the results, showing which specific checks fail most often fleet-wide.
Filters
| Filter | What it does |
|---|---|
| Asset Group | Includes all assets in the selected group. |
| Asset | Includes specific assets. Can be combined with Asset Group — the results are the assets in the group plus the individually selected assets, not an intersection. Leave both empty to include every 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 next scheduled asset meter update (which runs daily). This report displays all flagged readings grouped by asset so they can be reviewed and corrected in one place. There are no filters — it loads every flagged reading across the fleet automatically, and can take a while to load on a large fleet.
Error Types
| Error | What it means |
|---|---|
| Primary/Secondary Meter < Asset Meter | The submitted reading is lower than the asset's current primary/secondary meter value. |
| Primary/Secondary Meter < Previous DD Meter | The submitted reading is lower than the highest previously recorded reading on another Daily Driver for the same asset. |
| Range Error | Primary meter only. Compares the reading against the asset's Daily Driver Max Daily Distance (km) or Max Daily Hours setting (defaults 1000 km / 12 hrs per day), multiplied by the number of Daily Driver readings submitted since the asset's meter last actually changed. If the increase since the last known value exceeds that allowance, it's flagged. |
| Meter Length Error | The number of digits in the reading is longer than both the previous and next readings, or shorter than both, suggesting a transcription error (for example, an extra or missing digit). |
Averaging Error may also appear on older data. It refers to a historical-average comparison that is no longer generated by any process in the current version of Formbird FLEET — if you see it, treat the reading the same as any other flagged error.
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. A supervisor can also clear this checkbox directly on the Daily Driver document (subject to access permissions) to manually accept a reading without going through this report.
Reading the Report
Results are grouped by asset. Select the asset group header to collapse or expand its rows. Each group header shows:
- Asset ID (linked to the asset record)
- Current primary and secondary meter values
- Total distance or hours consumed across the flagged records (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, shown in red if it has an error), the date it was created, the primary and secondary meter readings, and the errors identified. Use Reload to refresh the whole report from the server.
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, or select Ignore to accept the reading exactly as recorded (this fills the input with the existing value, so it still needs Apply Updates to take effect).
- 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 scheduled 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 Drivers Completed / Not Completed Today
The Daily Drivers Completed / Not Completed Today report shows which assets have had a Daily Driver completed on a given date 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. Only assets with Daily Driver Check Required ticked are included.
Set the Daily Driver Created Date (defaults to today), optionally narrow it to specific Assets, then select Run Report. A bar chart summarises Completed vs Not Completed counts for the date, and the table below lists every included asset with its Responsible Person and their Department, Supervisor, Section Admin, and Section, the DD Exception Driver Name / DD Created By (who reported the exception, or completed the Daily Driver, whichever applies), and Daily Driver Created (YES/NO, highlighted green or red). Use Show Complete, Show Incomplete, or Show All to filter the table, or the column search boxes for anything more specific.
Select an asset's row to drill into its three-month Daily Driver history: a timeline chart (Completed, Not Completed, Fault Request, Asset Not In Use, Daily Driver Exception) and a detail table of that asset's Daily Driver documents in the period (Request, Created, Failed Checks, Reported By, Priority, Primary Meter). Use Prev and Next to move the three-month window backward or forward.
Untrained Daily Driver Report
The Untrained Daily Driver Report lists Daily Driver check sheets that were submitted by an operator who didn't hold a Current training record for a training type the asset requires. Submitting isn't blocked — the operator sees a warning notification naming the missing training type when they select the asset, but can still complete and save the check sheet. This report is how that gap gets tracked afterwards.
Columns show the Asset, the Daily Driver's Name (linked), Date, and Assignee (the operator). There are no filters; the list shows every untrained submission.
Use this report to track training compliance and follow up with operators or supervisors before gaps affect pre-start coverage.
Updated: August 2026 · Formbird FLEET 4.2.8