Overview
RideOps uses Checklists to bracket every operating day for a ride: a Preopening Checklist that must be completed before the ride can open, and an optional Closing Checklist for end-of-day tasks. Both are assigned per Location in the ride's RideOps Settings.
Users must be Super Users or have a Role with permission to edit Locations and Checklists to configure Checklists for 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 physically cannot open the ride until the checks are done — and, if you require approval, until a qualified person has signed them off. That's your safety process enforced by the system rather than relying on memory.
Configuring a Preopening Checklist
Preopening Checklists verify that a ride is safe and operational before guests board.
1. Create or choose a Checklist
In the Mobaro Backend, go to Checklists and either click + Create Checklist or pick an existing one to use as the ride's Preopening Checklist.
2. Open the ride's RideOps Settings
Go to Locations, select and edit the relevant Location, and open RideOps Settings.
3. Assign it as the Preopening Checklist
In the Checklists section, set the Checklist in the Preopening Checklist field and set a validity period (in minutes) that determines how long a completed Checklist stays valid before RideOps asks for it again.
4. Require approval (optional)
Toggle Require Approval for Preopening Checklist so a completed Checklist must be reviewed by an authorized User before the ride can open. Approval is granted from the Results page of the completed Checklist.
5. Save
Click Save to apply the configuration.
Heads-up: Operators cannot mark a ride as operational in RideOps until the Preopening Checklist is completed — and approved, if approval is enabled.
Configuring a Closing Checklist
Closing Checklists capture end-of-day tasks such as securing the ride and performing maintenance checks. To configure one, open the ride's RideOps Settings as above, set your Checklist in the Closing Checklist field, and click Save.
Note: Closing Checklists don't affect operational status — a ride opens on the strength of its Preopening Checklist. They exist to track end-of-day processes and compliance consistently.
Frequently asked questions
Q: Can I use the same Checklist for multiple rides?
A: Yes. Assign the same Checklist in each Location's RideOps Settings.
Q: What happens if the Preopening Checklist isn't completed?
A: The ride can't be marked operational in RideOps until it's completed — and validated, if approval is enabled.
Q: Are Closing Checklists mandatory?
A: No, but they're recommended so end-of-day processes are completed consistently.
Q: How long does a completed Preopening Checklist stay valid?
A: For the validity period you set, in minutes. After it lapses, RideOps prompts the Operator to complete the Checklist again. See Setting up RideOps for where this sits in the full setup.