Overview
Log book is the activity timeline that lives on every Location in Mobaro — a chronological record of openings, closings, downtime, Checklists, Assignments, Notes, sign-ins, and Schedules, both past and planned. It surfaces in three places, each tuned for a different way of working: the web Backend (deepest filtering, historical analysis), the Mobaro mobile app (in-the-field operational context), and RideOps (in-the-moment view for operators). Same underlying data, three different doorways.
The mental model: Log book answers "what's happening on this Location?" at three levels of zoom. Web is the wide-angle lens for analyzing patterns across days. The Mobaro app is the mid-zoom for understanding a Location while you're standing near it. RideOps is the macro lens for the operator running it right now.
What log book shows
Log book is a Location-scoped timeline. For any given Location it can include:
Open Location and Close Location events.
Dispatch entries (and External Dispatch if integration-based).
Update Queue entries (and External Update Queue).
Authorization activity — User sign-in, sign-out, Role assignments where applicable.
Notes attached to the Location, including handover notes.
Assignments created, resolved, or marked blocking.
Downtimes registered and resolved.
Results — completed Checklist Results.
Planned activities — upcoming Schedules and Slots.
Which types appear depends on what's enabled on the Location, your Role permissions, and the surface you're using (web has the most options).
Note: Log book is for reviewing operational events. It's not a replacement for detailed reporting or for the screens where you actually do work (Schedules, Checklists, Results). Think of it as the consolidated timeline view, not a workflow tool.
The three surfaces
Pick the surface that matches what you need.
Web — the Operational Log dialog
The deepest view. Filters by Activity Type, Time frame (Completed / Planned), Time range (this week, custom), and User. Best for investigations, audits, and shift-spanning analysis. See Log book on the web — the Operational Log dialog.
Mobaro app — Activities section
Embedded under Operations → Location → Activities, alongside live stats and Staff sign-in. Today / Planned toggle. Best for in-the-field context. See Log book in the Mobaro app.
RideOps — Activities page
A dedicated full-page Activities view for the Location you're operating. Today / Planned tabs, full timestamps. Best for operators running a Location in real time. See Log book in RideOps.
Past vs planned
Every surface offers a way to switch between past and planned activity, with surface-specific labels:
Web: Time frame: Completed vs Planned (because the web supports custom time ranges, not just today).
Mobaro app: Today vs Planned toggle above the Activities section.
RideOps: Today vs Planned tabs at the top of the Activities page.
Same underlying split — different terminology to match each surface's typical use.
Questions log book is good at answering
Use log book when you need to know:
What already happened on this Location today?
Has the pre-opening Checklist been completed?
Was there downtime earlier? Who registered it?
What's planned later today?
Has a blocking Assignment been created or resolved?
What did the prior shift leave in the handover Notes?
Who has been signed in on this Location, and when?
Who benefits most
Log book is especially useful for:
Supervisors — quick review of what's happened on the Locations they oversee.
Operators — picking up shift context without flipping between modules.
Maintenance teams — seeing downtime history alongside Assignments and Notes.
Park leadership — reviewing readiness before opening or auditing the day after.
Best practices
Get the most out of log book by working these habits into the team's flow:
Use Notes consistently — Notes are the most context-rich entries in log book. Capture handover info, observations, and exceptions as Notes so they show up in the timeline rather than being trapped in messages.
Make sure Checklists and Assignments are completed against the right Location — log book is Location-scoped, so misattributed work doesn't appear where you'd expect.
Review log book at handover — the timeline is the fastest catch-up read for the incoming shift.
Pick the right surface for the question — web for analysis and audits, app for in-field context, RideOps for active operating. Trying to investigate a multi-day pattern from RideOps is the wrong tool for the job.
See also
Updating and adding to the Operational Log — for adding and editing dispatch and queue entries.
Utilizing Operational Logging — for enabling Operational Logging on Locations.
Frequently asked questions
Q: What is log book in Mobaro?
A: A Location-scoped activity timeline available across web, the Mobaro app, and RideOps. It shows openings, closings, downtime, Checklists, Assignments, Notes, sign-ins, and planned events.
Q: Is log book available in all Mobaro products?
A: Yes — across web, Mobaro app, and RideOps, with surface-specific framing. See the linked sub-articles for each.
Q: Can I see future planned activity?
A: Yes. Each surface offers a past/planned switch — Completed / Planned on the web, Today / Planned in the Mobaro app and RideOps.
Q: Does log book show activity for all Locations at once?
A: No. Log book is Location-scoped — open it on a specific Location to see that Location's timeline.
Q: Why do the available activity types vary?
A: They depend on what's configured for the Location, your Role's permissions, and the surface (web has the most filtering options). External types only appear when integrations are configured.
Q: How is log book different from the existing Operational Log?
A: Log book extends the existing Operational Log dialog on web with new Activity Types (Notes, Assignments, Downtimes, Results, planned activities) and brings the same data into the Mobaro app and RideOps with surface-appropriate views. The mechanics for adding dispatch and queue entries directly haven't changed — see Updating and adding to the Operational Log.