Overview
The Ride Operations Timeline widget plots when rides were operating across a chosen time range, laying each Location out on a timeline so you can see operating periods, gaps, and lag between dispatches at a glance.
Heads-up: This is a RideOps widget and relies on RideOps operating data being captured. If RideOps isn't enabled for your organization, the widget won't have data to display.
Why this matters: A timeline makes operating continuity obvious — long gaps between dispatches or unexpected stops stand out immediately, which a single throughput number can hide.
Configuration and filters
Add the widget to a Dashboard and scope it with:
FromandToto set the time range the timeline covers.Locations and Location Groups to choose which rides appear.
A lag-time threshold (in minutes) to flag gaps between dispatches longer than the value you set.
An option to filter by opening hours, so only the operating window counts rather than the full day.
Best practice: Set the lag-time threshold to the longest acceptable gap between dispatches for your operation, so anything highlighted is genuinely worth investigating rather than normal load-and-dispatch timing.
Frequently asked questions
Q: Why is the timeline empty?
A: The widget needs RideOps operating data within the selected range. Confirm RideOps is in use at the selected Locations and that the time range covers operating hours.
Q: What does the lag-time threshold do?
A: It highlights gaps between dispatches that exceed the minutes you set, so longer-than-expected pauses are easy to spot.