Overview
Checklists are the forms your team completes for inspections, maintenance, openings and training. A completed Checklist becomes a Result. Results provide information for reports, Dashboards and follow-up Assignments.
This article maps the Checklist module: the building blocks, how a Checklist goes from the Backend to a completed Result, and where to read more about each part.
At a glance |
|
Who can do this | Build: Super Users, a Role with Checklists › Create or Modify, or an Administrator or Editor of the permission folder. Complete: the Schedule's assignees |
Where | Checklists, Schedules and Results in the Backend |
Works on | Backend (web) to build, schedule and review; Mobile app and RideOps to complete; Public API for Results |
Availability | All organizations |
The building blocks
Component | What it is |
Checklist | The form, with a title, a primary language, optional translations and its settings. |
Pages | A Checklist is split into pages. The page title (up to 30 characters) appears at the top of the screen in the app and in reports. |
Elements | The content of each page: questions that collect answers, plus Text Element and Image Element for instructions. |
Answers | What the User enters for each question. Answers can carry points for scoring, comments and photos. |
On top of this structure you can add logic to show or hide content, triggers that act on answers, scoring, reference material from the Library (Manuals, Videos, Links) and translations.
The Checklist lifecycle
Stage | What happens | Read more |
Build | You create the Checklist in the Backend under Checklists. | |
Schedule | A Schedule publishes it: which Checklists, where (Locations, Location Groups or Assets), who and when. | |
Complete | Assignees fill it in in the Mobaro app, online or offline, or in RideOps for ride Checklists. | |
Review | The submission becomes a Result to view, validate, correct, export or report on. |
⚠️ Heads-up: A Checklist and a Schedule are different things. The Checklist is what gets completed; the Schedule controls where, who and when. A Checklist doesn't appear in the app until a Schedule includes it.
Build and maintain
Utilizing checklist permission folders and Managing permissions for checklists, schedules, and data to control who can edit which Checklists
Question types
Kind of answer | Question types |
Choices | |
Numbers and measurements | |
Text | |
Ratings | |
Evidence | |
Scanning | Scanner Question, with NFC tags |
Water testing | Water Quality Question, if Water Quality is enabled for your organization (setup: How to add water quality checks to a checklist) |
Instructions | Text Element and Image Element (no answer) |
Other question types in the editor include Member Question. If a question shows as unsupported on a device, see Unsupported question when completing a Checklist.
Logic and triggers
Logic controls what the User sees. Start with Adding logic to a Checklist, then the reference for each condition:
Logic based on date and time (weekday)
Triggers control what happens after an answer: see Adding triggers to a checklist, Assignment triggers, Ad Hoc Slot triggers and Requirement triggers.
Scheduling
Completing and reviewing
Key terms
Term | Meaning |
Target | The Location, Location Group or Asset a Schedule publishes the Checklist to. |
Assignee | A User or User Group on the Schedule who completes the Checklist. |
Reviewer | A User or User Group on the Schedule who validates Results and handles Missing Results. |
Schedule | What publishes a Checklist: Calendar, Continuous or Ad Hoc Slots. |
Result | The record of one completed Checklist. The Backend also lists Missing Results, Resumable Results and Invalidated Results. |
Example: a daily ride inspection. An administrator builds a Daily Ride Pre-Opening Inspection Checklist. A Calendar Schedule publishes it to the coaster each morning, assigned to the Ride Operators User Group, with Maintenance Supervisors as Reviewers. The operator on shift completes it in the app, and the Result, with its score, appears on the Dashboard for review.
Best practices
Build one Checklist and adapt it with logic, rather than keeping near-identical copies per ride or day.
Test a new Checklist in the mobile app, following every answer path, before you schedule it.
Assign User Groups rather than individuals, and add Reviewers to every Schedule that needs validation.
After saving a Schedule, check it with Schedule Metrics.
Frequently asked questions
Why can't my team see a checklist I built?
A Checklist only appears once a Schedule includes it, the person is an assignee, directly or through a User Group, and they're a member of the target Location. Calendar and Ad Hoc slots must also be open. See What you need before you can schedule a Checklist.
How do I give a user access to a checklist?
Through a Schedule, not the Checklist: in Schedules, add the Checklist and put the User, or a User Group they belong to, in Assigned to (Users/User Groups). See How to schedule a Checklist.
Can I fill in a checklist in a web browser?
Not in the Backend. It is for building, scheduling and reviewing. Checklists are completed in the Mobaro app on a phone or tablet, or in RideOps for Checklists set up for RideOps. See Completing a checklist in the Mobaro mobile app.
Can staff and supervisors complete parts of the same checklist?
Yes. Show the supervisor's questions only while the Result is Awaiting Validation, so a Reviewer answers them when validating. See Logic based on the Checklist state.