Overview
In RideOps, log book has its own dedicated Activities page for each Location — accessed from the gear/settings icon in the left navigation. It's full-screen, focused, and built for operators and team leads who are running a Location and need an at-a-glance view of recent and planned activity. Less detailed than the web Operational Log, but always visible without leaving RideOps.
When to use the RideOps view: You're operating a ride or running a queue, and you need to see what's happened on this Location today without leaving RideOps. The view stays in the operating context — no popping out to a separate dialog.
Where to find Activities in RideOps
1. Open RideOps for the Location
Sign into RideOps and open the Location you're operating.
2. Navigate to Activities
In the left navigation, click the Activities icon (the gear/settings icon at the bottom of the icon strip). The Activities page opens with the Location's name as the page header.
Today and Planned tabs
The page has two tabs at the top:
Today — the timeline of events that have happened on this Location today.
Planned — events scheduled to happen later today.
Same past/planned split as the Mobaro app and the web Operational Log, with terminology that matches the app's view. Tap a tab to switch.
What each timeline entry shows
Each entry has:
A type icon on the left — distinct icons for Note, Open Location, Sign-in, Downtime, etc.
A title describing the event (Note created, Opened location, Signed in).
For Notes, a preview of the note content immediately below the title.
The User who performed the action.
A full timestamp on the right (29-04-2026 06:34).
Note: RideOps timestamps are full date/time (not relative like 3 hours ago). This is intentional — operators looking at the Activities page often need precise times for incident reporting and shift handover.
Worked examples
Example 1: Operator confirming pre-opening setup
Scenario: An operator opens the ride for the day. Before dispatching the first train, they want to confirm pre-opening Notes and any handover from the prior shift.
Setup: In RideOps, navigate to the Activities page. Tab: Today.
Result: The morning's Sign-in, the Opened location event, and any Notes left by closing staff are right there. The operator can run pre-opening with full context, and any test observations they note get appended to the same timeline.
Example 2: Team lead reviewing what's left for the day
Scenario: An afternoon team lead checks what's still planned on the ride for the rest of the operating day.
Setup: Activities page in RideOps. Tab: Planned.
Result: Upcoming Schedules — the afternoon safety check, evening Result, end-of-day Checklist — visible without flipping out to the web Backend. The lead can plan staffing and timing accordingly.
See also
Log book — activity timelines across Mobaro — the cross-platform overview.
Log book on the web — the Operational Log dialog — for deeper filtering and historical analysis.
Log book in the Mobaro app — for the in-the-field surface on the standard mobile app.
Frequently asked questions
Q: How does the RideOps Activities page differ from the Mobaro app's Activities section?
A: Same data, different framing. The Mobaro app embeds Activities as one section among the live operational stats and Staff list. RideOps gives Activities its own dedicated page so it's always one click away when you're focused on operating a single Location.
Q: Can I filter the timeline in RideOps?
A: RideOps Activities is intentionally low-friction — you see Today or Planned, all event types together. For Activity Type filtering, switch to the web Operational Log.
Q: What if I'm operating multiple Locations from one RideOps session?
A: The Activities page is scoped to whichever Location you're currently operating. Switch Location in RideOps and the Activities page follows.
Q: Will Notes I create in RideOps show up here?
A: Yes. Notes added in RideOps surface in the Activities timeline alongside other operational events, and also flow through to the web Operational Log and the Mobaro app's Activities section.
Q: Why do I see the Staging banner at the bottom?
A: That indicates you're connected to a non-production RideOps environment. Check with your administrator if you expected to be on production.