Overview
On the web, log book lives inside the existing Operational Log dialog on each Location. It's the most powerful surface for log book — you get the full activity timeline, fine-grained Activity Type filtering, the past/planned split, and User filtering all in one place. Use the web view when you need to investigate, audit, or compare events across a Location's history.
When to use the web view: investigating an issue, building a handover, reviewing a Location's day, or pulling up evidence for an audit. The mobile app and RideOps surfaces are tuned for in-the-moment context; the web Operational Log is tuned for analysis.
Opening the Operational Log on a Location
1. Go to Locations
Open Locations in the Mobaro Backend.
2. Pick the Location
Click into the Location whose timeline you want to review.
3. Open the Operational Log icon
Click the clock/history icon to open the Operational Log dialog. The dialog is named for the Location — for example, Operational Log - Jewel Hunt.
The three filters
The Operational Log dialog has three filters across the top, each answering a different question.
Time frame — Completed vs Planned
The leftmost filter switches between two views of the timeline:
Completed — past activity, what has already happened.
Planned — future activity, what's scheduled to happen.
This is the past/planned split log book introduces. On other surfaces (the Mobaro app, RideOps) the same split is labeled Today and Planned; on the web, it's Completed and Planned because the web view supports arbitrary time ranges, not just today.
Time range — This week, custom, etc.
The middle filter sets the calendar range. This week is the default for Completed views; you can also pick today, last week, or a custom range. Sort by Time for clearest reading.
Activity Type filter
The Activity Type filter (the rightmost icon, opens a checkbox list) controls which kinds of events appear in the timeline. The available types are:
Open Location — when the Location was opened for operation.
Close Location — when it was closed.
Dispatch — internal dispatch entries (count, units, seats).
Update Queue — internal queue time updates.
Authorization — sign-in / sign-out / Role activity.
External Dispatch — dispatch entries pushed in via integration.
External Update Queue — queue updates pushed in via integration.
Notes — operator notes and handover notes attached to the Location.
Assignments — Assignment created, resolved, blocking, etc.
Downtimes — downtime registered and resolved.
Results — completed Checklist Results.
Each type is a toggle. By default, operational state types (Open/Close, Dispatch, Update Queue, Authorization) are checked; the broader types (Notes, Assignments, Downtimes, Results) are toggled on as needed when you want a fuller picture.
Best practice: Start narrow and add types. If you toggle every Activity Type at once, the timeline becomes dense and hard to scan. Begin with the question you're answering — "when did this Location last open?" needs only Open Location and Close Location — then add types only when you need broader context.
Filtering by User
The User filter (the people icon) scopes the timeline to events involving a specific User — useful for shift handovers, performance review, or investigating a specific operator's actions. Combine with the Activity Type filter to ask narrow questions like "every Note this operator added today" or "every Authorization for this User this week."
Worked examples
Example 1: Shift handover review
Scenario: A morning supervisor wants to know what the overnight team logged on a coaster.
Setup: Open the Operational Log on the Location. Time frame: Completed. Time range: custom 22:00 yesterday to 07:00 today. Activity Types: Open Location, Close Location, Notes, Downtimes, Assignments.
Result: One screen shows everything that happened overnight — closures, downtime registrations, handover notes, any blocking Assignments — without scrolling through unrelated dispatch counts.
Example 2: Investigating a guest complaint
Scenario: A guest complained about a long queue around 14:30 yesterday. Operations wants to verify queue and dispatch activity for that window.
Setup: Operational Log on the Location. Time frame: Completed. Time range: yesterday 14:00–15:00. Activity Types: Dispatch, External Dispatch, Update Queue, Downtimes.
Result: The combined view shows dispatch frequency, queue time updates, and any downtime that overlapped the complaint window — enough to respond to the guest with specifics.
Example 3: What's planned for this Location today
Scenario: A Park Director glances at a Location to see what's still scheduled.
Setup: Operational Log. Time frame: Planned. Time range: today.
Result: A list of upcoming Schedules — the afternoon safety check, the evening Result that's still due, the closing Checklist — without flipping between Schedules and Calendars.
See also
Log book — activity timelines across Mobaro — the cross-platform overview.
Log book in the Mobaro app — for the in-the-field surface.
Log book in RideOps — for the dedicated activities page in RideOps.
Updating and adding to the Operational Log — for adding and editing dispatch and queue entries directly.
Utilizing Operational Logging — for enabling Operational Logging on Locations.
Frequently asked questions
Q: Why does my Activity Type list look shorter than someone else's?
A: Available types depend on what's enabled on the Location and on your Role permissions. Authorization, External Dispatch, and External Update Queue only appear when the relevant integrations or features are configured.
Q: Can I export the filtered timeline?
A: The Operational Log dialog itself doesn't export; for downloadable timelines, use the operational reports or pull the data via the Mobaro API.
Q: Does the Time frame: Planned view show every future Schedule indefinitely?
A: It shows planned activity within the time range you've set. Pair Planned with the time range filter to scope to today, this week, or a custom range.
Q: Why don't I see Notes when I expect to?
A: Notes is one of the Activity Types that's off by default. Toggle it on in the Activity Type filter to surface them in the timeline.
Q: Can I filter by multiple Users at once?
A: The User filter scopes to one User at a time. For multi-User views, leave the User filter unset and use Activity Types to narrow instead.