Overview
The log book is a Location’s activity timeline. It brings together what happened at a ride — openings and closings, RideOps dispatches and queue times, sign-ins, Notes, Assignments, Downtimes and RideOps Checklist Results — and what’s planned for the coming week.
You read the same timeline in three places: the Operational Log in the Backend, Activities in the Mobaro app, and the Activities page in RideOps. This article explains what the log book records and which place to use; each place has its own article.
At a glance |
|
Who can do this | Anyone who can see the Location. Adding or correcting dispatch and queue entries needs Operations › Manage Dispatch Entries or Manage Queue Entries |
Where | Backend: Locations › View Operational Log. App: Operations tile › a Location. RideOps: the Activities page |
Works on | Backend (web), Mobile app, RideOps |
Availability | All organizations. Openings, closings and RideOps entries need Enable Operational Logging |
💡 Why this matters: The log book answers “what happened at this ride, and what’s next?” in one place, instead of checking Notes, Assignments, Downtimes and Results separately at every handover.
What the log book records
The log book doesn’t have entries of its own: it reads them from the features that create them. Everything is scoped to one Location.
Activity | Comes from |
Opened and closed location | Opening and closing the Location in the Backend, the app or RideOps |
Dispatches and queue times | RideOps, or added in the Backend Operational Log |
External dispatches and queue times | Integrations such as Safari AI |
Sign-ins and sign-outs | Operators signing in to RideOps, as operator or a Position |
Notes | Notes created, approved or rejected at the Location, and Assignments they trigger |
Assignments | Assignments raised from operations at the Location, such as from Notes and Downtimes: created, started and resolved. Assignments created by hand, from a Schedule or through the API don’t appear |
Downtimes | Downtimes started and resolved, and Assignments created from them |
Results | RideOps Preopening and Closing Checklists completed, approved or disapproved |
Openings, closings and RideOps entries are only recorded for Locations with Enable Operational Logging. See Utilizing Operational Logging.
Where to read it
Place | Shows | Use it for |
Backend: Operational Log dialog | Every activity type, any past period, and Planned. Filters by type and User | Investigations, audits, reviewing a shift, correcting RideOps entries |
Mobile app: Activities section | Today since midnight and Planned. No dispatches or queue times, no filters | Catching up at the ride |
RideOps: Activities page | Today and Planned, for the Location the tablet runs. Same activities as the app | Operators checking the day before or during operation |
The app and RideOps load the log book live, so they need a connection. To add or fix a dispatch or queue time, see Updating and adding to the Operational Log. Openings and closings are corrected in the Uptime Summary, not in the log book.
What “Planned” means
All three places have a Planned view covering now until the end of the seventh day ahead. It lists two things only:
The Location’s RideOps Preopening and Closing Checklists, at the opening and closing times in its opening hours.
Unfinished Assignments raised from operations at the Location, such as from Notes and Downtimes, that have a start and due date in that period.
⚠️ Heads-up: Planned doesn’t list Checklists from your Schedules or Calendars. To see what’s due from Schedules, check the Schedules or a Dashboard widget.
Best practices
Read the log book at every handover: it’s the quickest way to see what the last shift did.
Record handover information as Notes at the Location, so it shows in the timeline. See Handover notes.
Make sure Results, Notes and Downtimes are recorded against the right Location; the log book only shows what belongs to that Location.
Use the Backend for multi-day questions; the app and RideOps only show today and the week ahead.
Frequently asked questions
Will my scheduled or ad hoc Checklists show under Planned activities?
No. Planned only shows the Location’s RideOps Preopening and Closing Checklists and unfinished Assignments. Checklists from Schedules appear in the app and RideOps Checklist lists, not in the log book.
Can I see the ride’s status over the last hour in RideOps?
Yes. The RideOps Activities page, on Today, lists Opened location, Closed location and Downtimes with their times. For more detail, such as dispatches, use the Backend Operational Log.
Can I see who was signed in, and in which Position?
Yes, in the Backend Operational Log with Authorization ticked. The app and RideOps show sign-ins for today too. See Log book on the web.
Can I see the log book for all Locations at once?
No. The log book is always for one Location. For figures across Locations, use Dashboard widgets such as the Operational History Details Widget.
Can I export the log book?
No. None of the three places has an export. Dispatches, queue times, uptime periods and Downtimes are available through the Public API; see Getting started with the Mobaro API.