Handover notes let you push critical, time-bound information to RideOps operators and require them to acknowledge it before they can operate the ride. When a note is created with Require operators to acknowledge this note enabled, the Location is held in a Not ready for operation state — alongside any other gating condition such as an outstanding CFO Checklist or a high-priority Assignment — until the currently signed-in operator acknowledges the note. Because each acknowledgement is recorded against the operator and a timestamp, a handover note turns shift-critical information that usually lives on a radio or a clipboard into a hard gate with a defensible audit trail. This article covers creating a handover note from the Mobaro Backend, configuring when it is active, the operator experience in RideOps, and how to audit acknowledgements.
Early access: Handover notes are an early-access feature that Mobaro must enable for your organization. To turn it on, reach out to your Mobaro contact or [email protected].
How a handover note works
A handover note is a standard Note with acknowledgement enforcement layered on top. Three things drive its behavior:
Element | What it controls |
Require acknowledgement | Whether the note gates operation. When enabled, the Location is held Not ready for operation until the signed-in operator acknowledges the note. |
Display behavior | When the note exists at all ( |
Acknowledgement scope | Each operator who signs in during the active period must acknowledge the note individually. One operator acknowledging does not clear it for the next operator's shift. |
Note: Acknowledgement is per operator, not per ride. When a new operator signs in during the note's active period, the ride returns to Not ready for operation until that operator acknowledges the note — even if the previous operator already did. This is intentional: a handover note is information each person on shift needs to have personally seen.
Creating a handover note
Handover notes are created from the Notes section of the Mobaro Backend, under Administrate. In the Mobaro Backend, go to Notes and click the + button to create a new Note.
Complete the General panel — give the note a Title (a short, scannable summary such as Car 2, Seat 3 is out of service.), a Description/Note with the full detail and rich-text formatting, the Location it applies to, and the Type (its Note Type). Title, Location, and Type are required.
Check Require operators to acknowledge this note. This is what turns a standard Note into a handover note — operators will see it at sign-in and must acknowledge it before proceeding.
Critical: With acknowledgement enabled, this note will hold the Location in a Not ready for operation state for every operator who signs in during its active period. Use it for information that genuinely should block dispatch — out-of-service seats, safety constraints, restricted operating procedures. For information that doesn't need to gate operation, leave this unchecked and the note behaves as a standard Note.
Set the Display behavior, which controls when the note exists and when it is live in RideOps: Starts at / Ends at (the overall date-time window, required), Available every (an optional weekday recurrence so the note repeats on a schedule rather than running continuously), and Active time (one or more daily Active from / Active to intervals — click Add active interval for more than one window in a day).
Best practice: Match the Active time to your operating hours, not 24 hours. A note set active 08:00–22:00 only gates operators who sign in during operating hours, which is when the information is actionable. Use Available every for recurring constraints (e.g., a known weekly maintenance condition) instead of creating a new note each time.
Click Save. The note is now live according to its display behavior and appears in the Notes list, where it can be searched, filtered, edited, and audited.
How the Location is gated
When a handover note is active and unacknowledged by the signed-in operator, it is added as a reason the Location is Not ready for operation — the same readiness model used by CFO Checklists, high-priority Assignments, and Blocking Downtimes. The conditions stack: clearing the handover note does not make the ride ready if a CFO Checklist is still outstanding, and vice versa.
State | What the operator sees in RideOps |
Note active, not acknowledged | Location is Not ready for operation. The Operation Dashboard lists the note under Handover notes requiring acknowledgement with a |
Note acknowledged by current operator | The handover note condition clears. If no other gating condition remains, the Location becomes Ready for operation and the ride can be opened. |
New operator signs in | The note returns as a gating condition for the new operator until they acknowledge it themselves. |
The operator experience in RideOps
During the note's active period, every operator who signs in goes through the same flow. On sign-in, the Operation Dashboard shows Not ready for operation, with handover notes requiring acknowledgement listed alongside any other required checks, such as a Pre-opening Maintenance Inspection.
Tapping VIEW opens the note, showing the title, full description, and type. The dialog states that acknowledgement is required before the ride can continue operating.
Tapping Acknowledge records the acknowledgement against that operator and clears the handover note as a gating condition. Once no gating conditions remain, the ride shows Ready for operation and can be opened.
Note: Operators can also see handover notes for the selected Location under the Notes area in RideOps, where an unacknowledged note shows as Pending acknowledgement. Acknowledgement still gates dispatch and queue-time updates until it is completed.
Auditing notes and acknowledgements
Every handover note and its acknowledgements are auditable from the Notes section of the Mobaro Backend. Opening a note shows an Activities feed recording who created the note and which operator acknowledged it, each with a timestamp.
Best practice: Use the Notes filters (time period, Location, type) to review acknowledgement history during incident reviews or compliance audits. Because each operator's acknowledgement is individually recorded with a timestamp, the Activities feed provides a defensible record that the operator on shift saw the information before operating.
Current scope
Heads-up: Creating handover notes is currently limited to the Mobaro Backend. The same acknowledgement behavior for Checklists and triggers isn't available yet — it's on the roadmap. Stay tuned for an update when that arrives.
Example: a seat out of service for the day
Scenario — During an early-morning maintenance check, a technician finds that Car 2, Seat 3 on The Pirate has a non-functioning seatbelt. The seat must stay out of service all day, and every operator who works the ride needs to know before they dispatch.
Setup — In the Mobaro Backend, create a Note titled Car 2, Seat 3 is out of service. with a description explaining the seatbelt is not functioning and the seat must remain blocked. Set Location to The Pirate, Type to Observation, check Require operators to acknowledge this note, set Active time to the full operating day (for example 08:00–22:00), and save.
Result — The opening operator signs in and the ride shows Not ready for operation, listing the handover note alongside the pre-opening maintenance check. They view and acknowledge it; once the maintenance check is also complete, the ride becomes Ready for operation. At each shift change, the next operator signs in and the ride returns to Not ready for operation for them until they personally acknowledge the same note. At the end of the day, the Notes Activities feed shows each operator's acknowledgement with a timestamp — a complete record that everyone who ran the ride knew the seat was out of service.
Frequently asked questions
What's the difference between a regular Note and a handover note?
They're the same object. A handover note is simply a Note created with Require operators to acknowledge this note enabled. Without that setting, the Note is informational and does not gate operation.
Does one operator acknowledging clear the note for everyone?
No. Acknowledgement is per operator. Each operator who signs in during the note's active period must acknowledge it individually before they can operate, even if a previous operator already did.
What exactly is blocked until the operator acknowledges?
The Location is held Not ready for operation, which prevents dispatching and updating queue time. The operator can still view the note and other information; they just can't operate the ride until they acknowledge.
How does this interact with CFO Checklists and high-priority Assignments?
They stack. An unacknowledged handover note is one of several conditions that can hold a Location Not ready for operation. The ride becomes ready only when every gating condition — handover notes, CFO Checklists, high-priority Assignments, Blocking Downtimes — is cleared.
Can I make a handover note recur, for example every Monday?
Yes. Use Available every in the Display behavior panel to set a recurrence, and Active time to set the daily window it is live in RideOps.
Where can I see who acknowledged a note and when?
Open the note in the Notes section of the Mobaro Backend. The Activities feed records the creator and every acknowledgement with the operator's name and a timestamp.
Can I require acknowledgement on a Checklist or trigger?
Not yet. Acknowledgement enforcement currently applies to handover notes in RideOps. The same capability for Checklists and triggers is planned — stay tuned for an update.
Can operators create handover notes from RideOps?
Operators can create Notes from RideOps, but the require-acknowledgement gating behavior described here is configured when the Note is created from the Mobaro Backend. For consistent, predefined Notes on RideOps, see Setting up note templates.