RRECKTEKTransitAll sample reports
Sample report · illustrative data · not a real fleet

Data quality

October · 8,740 trip records · Example Paratransit Co. (fictional)

Complete records
58%
every required field present
Fields checked
10
required fields
Impossible values
111
records to correct
Least complete field
Cancel reason
62% filled

Completeness by field

Share of records with a value

Cancel reason62%Attendant flag71%Rider mobility need84%Space type88%Trip distance91%Drop-off time (actual)95%Pickup time (actual)97%Driver ID98%Funding source99%Vehicle ID99%target 95%

Values that cannot be right

Records failing a logic check

CheckRecords
Distance below zero37Fix at source
Drop-off before pickup22Fix at source
Trip longer than 4 h9Fix at source
Duplicate trip ID14Fix at source
Space type conflicts with vehicle29Fix at source

Completeness trend

Share of complete records

40%48%55%62%70%W1W2W3W4W5W6W7W8W9W10W11W12

■ Complete records

Findings

  • Cancel reason and attendant flag are blank most often; both are typed by hand.
  • Times recorded by the phone are nearly always present.
  • Negative distances come from odometer entries keyed in reverse.

Actions

  • Make cancel reason a required pick-list.
  • Take distance from GPS instead of odometer entries.
  • Reject drop-off-before-pickup at entry.
Every name and figure on this page is invented to show the report format. RRECKTEK Transit · rreck@rrecktek.com