Overview
Checklists are the core of Mobaro — they capture the data behind your Results and dashboards. A Checklist is built from pages and elements (questions, text, and images), with optional scoring, triggers, logic, and reference materials. This guide walks through building one from scratch.
Users must be Super Users or have the following Role to create a Checklist:
Checklists: Create
Why this matters: A well-built Checklist is the difference between data you can act on and a form people rush through. Getting the structure, scoring, and automation right once means every Result it produces is consistent and useful downstream.
Step 1: Create the checklist
Go to
Checklistsand click+to create a new Checklist.Choose a primary language — used when editing, and as a fallback when no translation exists in the User's language.
Give it a clear Title (shown to Users in the mobile app) and Description (visible only in the Backend).
You can also set, now or later via Settings:
Secondary languages — present the Checklist in other languages. See Translate a checklist.
Require Download — the Checklist and its content must download fully before it can start. Useful for staff working with limited connectivity.
Allow attachments from device gallery / from camera — let Users attach existing photos, or only newly taken ones, on every question.
Allow comments — let Users add optional comments that can show on reports.
Allow assignments — let Users raise additional Assignments on questions, beyond any a trigger already created.
Category and Checklist Folder — sort and filter the Checklist in dashboards, Results, and the mobile app.
Step 2: Add content
A Checklist has at least one page. Click the top box to title a page, then Add an element at the bottom of the page to add a question, text, or image. Drag and drop to reorder elements within or between pages.
For the full list of element and question types and what each captures, see the Question Types reference. Per question, you can also:
Assign a Question Category for reporting — see Question Categories.
Attach a manual, external link, or video (added to the Library first).
Add logic and triggers (below).
Step 3: Score answers
On Select (single or multiple choice) questions, you can assign points to each answer. When the Checklist is submitted, Mobaro reports a score: points collected ÷ maximum possible. For example, "OK" on 9 of 10 questions and "NOT OK" on one gives 90%.
Note: Scoring measures quality of a finished Result, not completion. Add points to every answer that should affect the score (including 0), and leave the points field empty for answers that shouldn't — e.g. an N/A option, which is then excluded from the calculation.
Equally important questions — give the positive answer the same points across questions (e.g. OK = 1) so they weigh equally.
Weighted questions — give more important questions higher points (e.g. 5 or 10 vs 1).
Rating scales — assign graded points across answers (e.g. very good → very bad).
Best practice: Add an N/A answer with an empty points field for cases a User genuinely can't assess — it keeps the score fair by excluding that question.
Step 4: Add triggers
Triggers automate workflow from an answer — creating an Assignment, scheduling an ad-hoc Checklist, or requiring extra information. Expand a question's Triggers section and click Add Trigger to choose:
Assignment trigger — creates an Assignment automatically.
Ad-hoc slot trigger — schedules an additional Checklist.
Requirement trigger — collects additional information (e.g. a comment or photo).
Note: Triggers are available on Select, Select Group, Number, Slider, Temperature, Date, Smiley, and Duration questions, plus Water Quality (via its ruleset). See Adding triggers to a Checklist. Assignment and ad-hoc triggers fire once the Result is submitted and received in the Backend.
Step 5: Add logic
Logic shows or hides pages, questions, or elements based on conditions — an earlier answer, the day of the week, a Location Property, the Checklist's state, User Group membership, or another element's visibility. Conditions can be stacked so all or any must be met. See Adding logic to a Checklist.
Step 6: Schedule it
When the Checklist is built, decide which Locations and Users it applies to using a Schedule. See What you need before you can schedule a checklist.
Best practice: Build a template per Checklist type (daily maintenance, training, annual PM) and copy it — keeping settings, triggers, and logic consistent across your program.
Frequently asked questions
Q: Do I need separate checklists for different languages?
A: No. Use the translation tool so one Checklist switches to the User's language automatically.
Q: Why can't I add a trigger to a question?
A: Triggers work only on the question types listed above. Confirm you're using a supported type.
Q: Can I export a blank copy of a Checklist?
A: Yes. Select it in the list view and click Export.
Q: Can I copy Checklists between my organizations?
A: Yes — select it, click copy, and choose the destination organization. Some elements (manuals, user-group triggers) may need re-adding due to different configurations. See How to duplicate a checklist.