Overview
This guide is for the Operator running a ride from the RideOps app on a tablet. It walks through a full operating day — logging in, opening the ride, recording dispatches and queue times, handling downtime, leaving a handover, and closing up. For the one-time admin configuration behind these screens, see Setting up RideOps.
Before you can operate a ride, three things must be in place: you are listed as an Operator on the Location, you hold an active Certification for any Competencies the ride requires, and the tablet is signed in with a RideOps Key that covers the Location.
Why this matters: RideOps is the live record of how the ride ran today. Every dispatch, queue update, and downtime you log feeds throughput reporting, guest-facing wait times, and the operational audit trail. Doing it in the app as you go means the data is accurate without anyone reconstructing the day afterward.
Logging in
1. Select the Location
Open the RideOps app on the tablet. If the RideOps Key covers more than one Location and allows switching, choose the ride you're operating.
2. Identify yourself as the Operator
Log in as yourself — typically by entering your PIN — so the day's activity is recorded against you. If the ride uses Positions, select the Position you're staffing.
Note: If you don't hold the Competencies the ride requires, RideOps blocks you at login. Contact a supervisor — your Certification may be missing or expired.
Opening the ride
1. Complete the Preopening Checklist
RideOps prompts you to complete the Preopening Checklist before the ride can open. If approval is required, a qualified User must sign it off from the Results page before you can continue.
2. Staff any mandatory Positions
Assign Attendants to the ride's Positions. Positions marked Mandatory must have someone assigned before the ride will open.
3. Open the ride
With checks complete and mandatory Positions staffed, tap Open. The ride's status changes to open and — where the Attractions.io integration is configured — the live status and queue time begin flowing to the guest app.
Heads-up: If the ride won't open, it's almost always an incomplete or unapproved Preopening Checklist, an unstaffed mandatory Position, or a missing Critical-for-Operation check. RideOps shows a message explaining what's outstanding.
Running the ride
Recording dispatches
Each time a unit leaves, record the dispatch — enter the number of riders and, if a unit is out of service, how many units were available. RideOps uses this against your dispatch targets to track throughput. If Delayed Dispatches are enabled, you can flag a dispatch as delayed and pick a reason (for example, Guest assistance or Mechanical hold).
Best practice: Log dispatches as they happen rather than in batches. RideOps warns you if too long passes between entries, which usually means a dispatch went unrecorded.
Updating the queue time
Post the current wait time using the queue widget. Keep it current — RideOps warns you when the posted time hasn't been updated within the configured window, and the value is what guests see if a guest-app integration is connected.
Logging downtime
If the ride stops unexpectedly, start Downtime from the app. Add a description and category, or pick a Downtime Template if your park uses them, so the cause is captured consistently. When the ride is running again, resolve the downtime to return the ride to operation.
Note: Downtime is distinct from a planned Close. Use downtime for unplanned stoppages and faults; use close for end-of-day or scheduled closures. See the Attractions.io integration for how each state appears to guests.
Notes and handovers
Use Notes to record anything the next person needs to know — an intermittent fault, a guest incident, a temporary workaround. At a shift change, the incoming Operator acknowledges the handover so it's clear the information was received.
Switching Operator or Position
When another Operator takes over, switch the active Operator so activity is recorded against the right person. If the RideOps Key allows it, you can also switch to another Location from the same tablet without signing out completely.
Closing the ride
1. Close the ride
At the end of the operating day, tap Close. If a Closing Checklist is configured, complete it as part of closing.
2. Confirm the day's figures
If your ride is set up for it, the closing flow asks you to confirm or correct the total dispatches and riders for the day — useful when a manual count differs from what was logged live.
Best practice: Close the ride at the end of every operating day even if it was quiet. A clean close marks the end of the operating period and keeps the next day's preopening flow accurate.
Frequently asked questions
Q: Why can't I open the ride?
A: Usually the Preopening Checklist isn't complete or approved, a mandatory Position has no Attendant, or there's no Critical-for-Operation check on record. The app shows what's outstanding.
Q: I'm blocked at login — what's wrong?
A: You likely lack an active Certification for a Competency the ride requires, or you aren't listed as an Operator on the Location. Ask a supervisor to check your access.
Q: What's the difference between downtime and closing?
A: Downtime is an unplanned stoppage you log and later resolve; closing ends the operating day. Use the one that matches what's actually happening so reporting and guest-facing status stay correct.
Q: Do I need to record every dispatch?
A: Yes — live dispatch logging is what makes throughput and utilization figures accurate. Record each one as it leaves rather than estimating later.
Q: Can two Operators use the same tablet across a shift change?
A: Yes. Switch the active Operator so the day's activity is attributed correctly, and have the incoming Operator acknowledge any handover Notes.