Overview
Handover notes push critical, time-bound information to a ride's RideOps Operators and make each Operator acknowledge it before they can operate the ride. A handover note is an ordinary Note, created in the Mobaro Backend with Require operators to acknowledge this note ticked.
This article is for administrators. For the Operator's side, see Acknowledging handover notes (for operators).
At a glance |
|
Who can do this | Super Users, or a Role with Notes › View Notes in Backoffice and access to the Location. Editing a saved note needs Notes › Modify. |
Where | Administrate › Notes › Create |
Works on | Backend (web) to create; RideOps to acknowledge |
Availability | Early access — ask Mobaro to enable Handover Notes |
🚀 Early access: Handover notes are an early-access feature. Mobaro turns them on per organization with the Handover Notes feature access setting. Until it's on, the Require operators to acknowledge this note checkbox doesn't appear and RideOps doesn't check for handover notes. Contact your CSM or Mobaro Support to request it.
💡 Why this matters: Shift-critical information often lives on a radio or a clipboard, with no proof anyone read it. A handover note makes reading it a condition for opening the ride, with a timestamped record.
How a handover note works
Setting | What it controls |
Require operators to acknowledge this note | Turns the Note into a handover note. While it's active, an Operator can't open or operate the ride in RideOps until they've acknowledged it. |
Display behavior | When the note is active: Starts at and Ends at, the weekdays in Available every, and any Active time intervals. |
Acknowledgement | Recorded once per Operator for the life of the note. Each Operator acknowledges it separately. |
Only Notes can require acknowledgement, and only from the Backend. Checklists and triggers can't.
Create a handover note
1. Open Notes
In the Mobaro Backend, go to Administrate › Notes and click the + button (Create). Notes only appears in the menu once your organization has at least one Note Type — see Setting up Note Types.
2. Fill in General
In the General panel, enter:
Title (required): a short summary, such as Car 2, Seat 3 is out of service.
Description/Note: the full instruction, with rich-text formatting.
Location (required): the one Location the note applies to.
Type (required): the Note Type.
3. Require acknowledgement
Tick Require operators to acknowledge this note. The Display behavior panel appears.
🛑 Critical: With this ticked, every Operator who signs in to RideOps while the note is active is held at Not ready for operation until they acknowledge it. Use it for information that must be read before the ride opens, such as out-of-service seats, safety constraints or restricted operating procedures. For information that shouldn't hold the ride, leave it unticked.
4. Set the display behavior
The Display behavior panel decides when the note is active in RideOps:
Starts at and Ends at (required): the date and time window the note applies to. Ends at must be after Starts at.
Available every (required): pick at least one weekday. The note is only active on the days you pick; until you pick one, the editor shows Select at least one day the handover note is available.
Active time (optional): click Add active interval and set Active from and Active to. Each interval must end after it starts on the same day, so an interval can't run past midnight. With no interval, the note is active the whole of each selected day inside the window.
Days and times are read in the Location's time zone.
5. Save
Click Save. The note appears in the Notes list.
How RideOps holds the ride
When a handover note is active and the signed-in Operator hasn't acknowledged it, RideOps shows Not ready for operation and lists the note under Handover notes requiring acknowledgement. The Operator can't open the ride until they acknowledge it.
Handover notes stack with the other conditions that hold a ride: outstanding critical-for-operation Checklists, critical Assignments, a Blocking Downtime or an incomplete Preopening Checklist. The ride opens only when all of them are cleared.
Situation | What the Operator sees |
Note active, not yet acknowledged by this Operator | Not ready for operation, with the note listed and a View button. The ride can't be opened. |
This Operator acknowledges it | The note stops holding the ride. If nothing else is outstanding, the ride shows Ready for operation. |
Another Operator signs in, even while the ride is open | Not ready for operation again, with the note listed, until that Operator acknowledges it. |
⚠️ Heads-up: Handover notes also apply to an open ride. If a note becomes active (this can take a few minutes to show) or another Operator signs in, RideOps replaces the dispatch and queue widgets with Not ready for operation until the signed-in Operator acknowledges it. The ride isn't closed. Opening the Location from the Backend or the Mobaro app isn't held by handover notes.
What Operators see in RideOps
On sign-in, RideOps shows Not ready for operation with the handover notes and any other required checks.
Tapping View opens the note with its title, description and type, and the message This note requires acknowledgement by an operator before the ride can continue operating.
Tapping Acknowledge records the acknowledgement against that Operator. Once nothing else is outstanding, the ride shows Ready for operation and can be opened.
In RideOps Notes, handover notes are listed under Handover notes, marked Pending acknowledgement or Acknowledged.
⚠️ Heads-up: Each Operator acknowledges a note only once, for its whole lifetime. A note that is Available every Monday won't ask an Operator who acknowledged it last Monday to acknowledge it again. For information that must be re-confirmed every day or shift, create a new note each time.
Audit acknowledgements
Open the note from Administrate › Notes. Its activity feed lists who created it, every change (for example This note now requires operators to acknowledge it) and each Acknowledged this handover note entry, with the user and the time.
Example: a seat out of service
Scenario: a faulty seatbelt puts Car 2, Seat 3 of The Pirate out of service for the day.
Setup: create a Note titled Car 2, Seat 3 is out of service. for The Pirate, tick Require operators to acknowledge this note, set Starts at and Ends at to today's operating day, pick today in Available every, and save.
Result: the opening Operator acknowledges the note before the ride opens. An Operator who signs in later is held at Not ready for operation until they acknowledge it too. The activity feed records each acknowledgement.
Best practices
Tick Require operators to acknowledge this note only for information that should hold the ride. Informational notes don't need it.
Set Starts at and Ends at to when the information really applies, and shorten Ends at once the issue is fixed.
Create a new note when information must be re-confirmed each day or shift; an existing note is acknowledged only once per Operator.
Make notes active before the ride opens where you can. A note that becomes active mid-operation interrupts dispatch until the Operator acknowledges it.
Frequently asked questions
How do we get handover notes turned on?
Ask your CSM or Mobaro Support. Handover notes are early access and Mobaro enables them per organization. Until then, the Require operators to acknowledge this note checkbox doesn't appear.
Can a handover note keep a ride non-operational even after the daily checks are done?
No, only until each Operator acknowledges it. Use a Blocking Downtime (a Downtime with an Assignment linked) instead. It holds the ride when your organization has Red if a blocking downtime is active on the location turned on. See Using downtime in Mobaro.
Can I record who handed the ride over from maintenance to operations, and when?
Partly. A handover note's activity feed records when each Operator acknowledged it. The maintenance sign-off is recorded on the Checklist's Result: who completed it and when, and who approved it if approval is required. See Viewing Checklist Results.
Does a recurring note have to be acknowledged again every day?
No. Each Operator acknowledges a note once, for its whole lifetime, even if it's Available every day. If information must be re-confirmed every day or shift, create a new note each time.
A new Operator took over while the ride was open. Do they have to acknowledge the note?
Yes. When they sign in, RideOps shows Not ready for operation with the note instead of the dispatch and queue widgets until they acknowledge it. The ride stays open; it isn't closed.
Can Operators create handover notes in RideOps?
No. Operators can create ordinary Notes in RideOps, but only the Backend can require acknowledgement. To give Operators ready-made wording for ordinary Notes, see Setting up note templates.