Notes are how your teams capture observations, issues, and information against a Location — a quick log of "here's what's happening" that lives alongside the rest of your operational data. A Note carries a Title, a Type, a description, and optional attachments, and can be routed for approval when it needs follow-up. This article covers what's in a Note, creating one, and managing it through to resolution.
New: Notes now have a Title — a short headline shown above the description. Titles make Notes far easier to scan in lists, on Dashboards, and in exports, so give each Note a clear, specific one.
Working with Notes uses these Role permissions: Notes — View, Modify, Delete, and Approve (to clear a Note's pending follow-up).
What's in a Note
Field | What it's for |
Title | A short headline summarizing the Note — the scannable label shown in lists and on Dashboards. |
Type | The category of Note, used to group and filter. Types are configured for your account — see Setting up Note Types. |
Location | The Location the Note relates to, so it shows up in the context of that ride, area, or facility. |
Description | The detail — what was observed, what happened, or what needs attention. |
Attachments | Photos or files that add context — a picture of the issue, a document, a reference image. |
Create a Note
Notes can be created from RideOps and from the Mobaro Backend. Start a new Note and choose its Location and Type, give it a clear Title, then add the description with the detail. Attach any photos or files that help explain it, and save — the Note is now logged against the Location and visible to anyone with access to it.
Best practice: Write the Title as you'd want it to read in a list a week later — Queue gate latch sticking, not Issue. A specific Title is the difference between a Note someone acts on and one that's scrolled past.
Note: To speed up logging on RideOps, set up Note Templates that pre-fill the Title, description, and Type — see Setting up note templates.
Approval and follow-up
Some Notes flag something that needs action. These can be routed for approval: a reviewer with the Notes: Approve permission reviews the Note and either approves it — clearing the pending follow-up — or rejects it. This keeps a clear line between "logged" and "dealt with", so nothing flagged quietly disappears.
Track and report on Notes
Activity history — each Note keeps a record of its changes and approvals, so you can see who did what and when.
Filtering — find Notes by Location, Type, who raised them, date range, or whether they're still unhandled.
Dashboards and exports — surface Notes on a Dashboard with the Notes Widget, or export a summary for reporting.
Frequently asked questions
What's the new Title field for?
It's a short headline above the description that makes Notes scannable in lists, on Dashboards, and in exports. Keep it specific.
Where can Notes be created?
From the Mobaro mobile app, RideOps, and the Mobaro Backend. They're all the same Note, logged against a Location.
What does approving a Note do?
It clears the Note's pending follow-up, marking it as handled. Approving requires the Notes: Approve permission.
How do I categorize Notes?
With Note Types. See Setting up Note Types.