Overview
For a planned break, use Close Ride to record that the Location is closed, then reopen it when your site’s procedure allows. Closing the ride ends its current uptime period without creating a Downtime.
Use Start Downtime for a stop that your site records as a Downtime. These choices have different staffing, reopening and reporting consequences.
At a glance |
|
Who can do this | Eligible Operators with their own PIN and current required Competencies; administrators manage Location and Downtime settings. |
Where | RideOps › lock control › Close Ride |
Works on | RideOps, Backend (web) |
Availability | Contact your CSM |
💡 Why this matters: Recording the actual closure prevents a planned break from being recorded as time the ride was operating.
Agree the break procedure
Decide in advance whether the event is a planned closure or a categorized Downtime. For an ordinary scheduled break, use the closure workflow below. Do not choose a non-blocking Downtime merely to work around a reopening restriction.
If your site records breaks as Downtime, an administrator should review the Downtime template’s Assignment policy and the organization’s Operator resolution setting. A category labels the event; it does not by itself decide who can resolve it. See Downtime templates.
Close for the break
1. Record the stop
When the ride stops under your site’s procedure, open the lock control and select Close Ride. Leaving it open in RideOps records uptime during the break.
2. Review the closing information
If enabled, review the dispatch and rider fields shown in the closing dialog. The closing fields describe counts since the ride was opened. Check the figures for that operating period rather than entering the full day again after each break. Complete any configured Closing Checklist before confirming the closure.
3. Check the closed status
Confirm RideOps shows the Location as closed. Closing signs out all Attendants from their Positions. The Operator is offered a choice to remain signed in or sign out.
🛑 Critical: A short break still uses the normal closing workflow. Before reopening, restore the required Attendants and check current readiness. Do not assume the staffing or pre-opening requirements remain satisfied because the closure was brief.
Reopen after the break
1. Restore the team
Sign in the eligible Operator if needed, then fill the required Attendant Positions with eligible people. Use the Operator workflow for PIN, staffing and readiness requirements.
2. Check readiness and open
Review any required Checklists, active blocking work and handover information. Reopen only when RideOps permits it and your site’s procedure allows operation. Reopening starts a new uptime period.
If RideOps will not allow reopening, follow the displayed readiness issue. A Closing action does not resolve an existing Assignment or remove a blocking Downtime. A qualified person may still need to resolve that work.
Check the recorded day
Review the closure and next opening in the Location’s Uptime Summary. Use the dispatch and queue guide to check counts and the configured input method. A temporary closure is not a reason to enter the same riders or dispatches again.
A simple closed interval is different from a Downtime registration. Widgets use different calculations, so do not assume every percentage uses opening hours as its denominator. See uptime, downtime and lag time for the reporting definitions.
Best practices
Agree the closure method before the shift.
Check that required Attendant Positions are staffed again before reopening.
Review a representative break’s timestamps and counts when introducing this routine.
Frequently asked questions
Can Operators resolve only break Downtimes, but not other non-blocking Downtimes?
The Operator resolution setting is organization-wide, not a per-category permission. Do not rely on a “Break” category to restrict it. Review the template’s blocking behavior with your administrator; see Downtime templates.
How do I make a Downtime category blocking?
Set the Assignment creation policy on the Downtime template, not on the category. See configuring a blocking Downtime template.
Why do I see riders but zero dispatches after closing?
Check the separate closing-input settings and how your Location records dispatches. Rider totals do not establish a dispatch count by themselves. See dispatch and rider input methods.