Overview
Checklists are the core of Mobaro. They're the digital forms your team completes in the field — inspections, audits, maintenance routines, openings, and training — and they generate the data behind your Results, Reports, and Dashboards. This article maps the Checklist module: the building blocks, the terminology you'll see across the platform, and how a Checklist travels from an idea in the Backend to a completed Result you can act on.
Why this matters: Understanding how Checklists, Schedules, and Results fit together is what lets you build once, publish to the right Locations and people, and trust the data that comes back.
The building blocks of a Checklist
Every Checklist is assembled from the same components.
Component | What it is |
Checklist | The overall form, with a title, a primary language, optional secondary languages, and configuration settings. |
Pages | A Checklist is organized into one or more Pages. The Page title appears at the top of the screen in the mobile app and is used in reporting. A Checklist always has at least one Page. |
Elements | The content on each Page — Questions that collect answers, plus text and image Elements that give instructions or context. |
Answers | The responses a User gives to each Question. Depending on the Question type, answers can carry points for scoring. |
Note: Think of it as a hierarchy — a Checklist contains Pages, and each Page contains Elements.
What you can layer onto a Checklist
Beyond the basic structure, you can make Checklists dynamic and automated:
Logic — show or hide Pages and Elements based on conditions like a previous answer, the day of the week, or a Location property. See Adding logic to a Checklist.
Triggers — automatically create Assignments, schedule Ad Hoc Slots, or require a comment or photo based on specific answers. See Adding triggers to a checklist.
Scoring — assign points to answers so each Result is graded as a percentage. See Understanding checklist scoring.
Reference materials — attach manuals, links, and videos from the Library so Users have guidance while they work.
Translations — present one Checklist in multiple languages based on each User's profile language. See Translate a checklist.
The Checklist lifecycle
A Checklist typically moves through four stages:
Build — an administrative User creates the Checklist in the Mobaro Backend, adding Pages, Elements, logic, triggers, and scoring. See How to create a checklist.
Publish — a Schedule makes the Checklist available, defining the Targets (Locations, Assets, or Location Groups), the Assignees, and how often. See How to schedule a Checklist.
Complete — Assignees fill out and submit the Checklist in the Mobaro mobile app.
Review — a submitted Checklist becomes a Result that can be viewed, filtered, scored, approved, exported, or corrected. See Viewing Checklist Results.
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 won't appear in the mobile app until it's included in a Schedule.
Key terms to know
Term | Meaning |
Target | The Location, Asset, or Location Group a Checklist is completed against. |
Assignee | The User or User Group responsible for completing the Checklist. |
Reviewer | A User who can review and validate Results without necessarily completing them. |
Result | The record created when a Checklist is completed or missed. Types include Regular, Missed, Resumable, and Invalidated. |
Schedule | The mechanism that publishes a Checklist. Types include Calendar, Continuous, and Ad Hoc. |
Example: a daily ride inspection
Scenario
A park needs its coaster checked every morning before opening, by whoever is on shift.
Setup
An administrator builds a Daily Ride Pre-Opening Inspection Checklist with one Page of Select Questions.
A Calendar Schedule publishes it to the coaster Location each morning, assigned to the Ride Operators User Group.
Result
The operator on shift completes it on mobile; the submission becomes a Result with a score, visible on the Dashboard and available for audit.
Frequently asked questions
Q: Why can't my team see a Checklist I built?
A: A Checklist must be added to a Schedule before it appears in the mobile app, and Assignees need access to the Target Location. Check the Schedule and Location permissions.
Q: What's the difference between a Checklist and a Result?
A: A Checklist is the template you build. A Result is a single completed or missed instance of it, containing the actual answers, comments, attachments, and score.
Q: Can one Checklist be used in many places?
A: Yes. A single Checklist can be published through multiple Schedules to many Locations and Users, keeping content consistent and easy to maintain.