Overview
RideOps uses two Checklists for each ride: a Preopening Checklist that Operators must complete before they can open the ride, and an optional Closing Checklist for end-of-day tasks. You set both per Location, in the Location's RideOps Settings.
This article covers those Checklist settings. For the rest of the setup, see Setting up RideOps; for what Operators see, see Operating a ride in RideOps.
At a glance |
|
Who can do this | Configure: Super Users, or a Role with Locations › Modify. Approve Results: Super Users, or a Role with Results › Validate RideOps. |
Where | Locations › a Location › RideOps Settings › Checklists section |
Works on | Backend (web) to configure; RideOps to complete |
Availability | All organizations. The Location needs Enable Operational Logging and Enable RideOps. |
💡 Why this matters: The Preopening Checklist is the gate between "the ride exists" and "the ride is safe to run." Tying it to RideOps means an Operator can't open the ride until the checks are done — and, if you require approval, until someone qualified has signed them off.
Set a Preopening Checklist
1. Create or choose a Checklist
In the Mobaro Backend, go to Checklists. Create a Checklist with Create, or pick an existing one to use as the ride's Preopening Checklist.
2. Open the RideOps Settings
Go to Locations and open the Location. With Enable RideOps ticked, click RideOps Settings.
3. Set the Checklist and its validity
In the Checklists section, choose the Checklist in Preopening Checklist. In Preopening Checklist Validity (minutes), set how long a completed Checklist stays valid before RideOps asks for it again. The default is 720 minutes (12 hours).
⚠️ Heads-up: If the Checklist contains question types RideOps can't show yet, the dialog warns <Checklist> has content that is not yet supported by the RideOps app. and lists them, for example Smiley Question, Temperature Question or Member Question. Choose a Checklist without them, or remove those questions.
4. Require approval (optional)
Tick Require Approval for Preopening Checklist if a supervisor must approve the completed Checklist before the ride can open. Until then, RideOps shows Awaiting checklist to be approved by supervisor.
The Result is approved in the Backend under Results, with Approve. Super Users and anyone whose Role has Results › Validate RideOps can approve every RideOps Result; they don't need to be reviewers on a Schedule. See How to validate Checklists.
5. Save
Confirm the RideOps Settings dialog, then save the Location.
🛑 Critical: Operators can't open the ride in RideOps until the Preopening Checklist has been completed within its validity period — and approved, if approval is required. Test the Checklist on the tablet before the first operating day, so the ride isn't held at opening.
How the Preopening Checklist is checked
RideOps offers the Preopening Checklist only when nothing else is holding the ride: no outstanding critical-for-operation Checklists, critical Assignments or Blocking Downtime. The dashboard then shows Ready for preopening checklist.
A completed Checklist stays valid for Preopening Checklist Validity (minutes), counted from when it was completed. Closing and reopening the ride within that time doesn't ask for it again.
Only the most recent completion counts. If approval is required, that completion must be approved.
When the validity period lapses, RideOps asks for the Checklist again. This also applies while the ride is open: RideOps then shows Not ready for operation instead of the dispatch and queue widgets until a new completion is recorded.
Set a Closing Checklist
A Closing Checklist captures end-of-day tasks, such as securing the ride. In the same Checklists section, choose it in Closing Checklist, then save. Operators are prompted to complete it when they close the ride. Tick Enable closing time reminder to remind Operators to close the ride.
ℹ️ Note: A Closing Checklist doesn't affect whether the ride can open; that depends on the Preopening Checklist. It exists so end-of-day processes are completed and recorded consistently.
Best practices
Keep the Preopening Checklist to the checks the Operator must do at the panel; schedule maintenance inspections separately and make them critical for operation.
Set the validity to cover one operating day, so a mid-day restart doesn't ask for the Checklist again.
Give Results › Validate RideOps to every supervisor who may need to approve, so approvals don't wait for one person.
Use the same Checklist across similar rides; assign it in each Location's RideOps Settings.
Frequently asked questions
How do I stop a ride opening until a checklist is done?
Set the Checklist as the Preopening Checklist in the Location's RideOps Settings; RideOps won't open the ride until it's completed, and approved if required. For maintenance checks done in the Mobaro app, make the Schedule critical for operation. See Schedule criticality and Location operational status.
Can I have more than one Preopening Checklist, or make one wait for another?
Each Location has one Preopening Checklist. To make it wait for maintenance, schedule the maintenance Checklist as critical for operation: RideOps only offers the Preopening Checklist once critical checks are done.
Who can approve a RideOps checklist?
Super Users and anyone with a Role that has Results › Validate RideOps. They approve the Result in the Backend under Results. To let more people approve, add Validate RideOps to their Role.
Can the Preopening Checklist be done more than once a day?
Yes. While the last completion is within the validity period, reopening the ride doesn't ask for it again. After the period lapses, RideOps asks for a new one. Shorten Preopening Checklist Validity (minutes) to require it more often.
Can I set up RideOps without a checklist?
Yes. Both Checklist fields are optional. Without a Preopening Checklist, the ride can open as soon as nothing else holds it, such as an outstanding critical-for-operation Checklist.
Our opening checklist isn't available for some rides in RideOps. Why?
RideOps offers the Preopening Checklist only when nothing else holds the ride. Complete outstanding critical-for-operation Checklists and resolve critical Assignments or a Blocking Downtime first. Also check that the Location has a Preopening Checklist set.