Overview
Scoring turns a completed Checklist into a measurable Result. By assigning points to answers, Mobaro calculates a percentage score for each submission, helping you gauge quality and compliance across Locations and over time. This article explains how scoring is configured and calculated.
Users must be Super Users or have one of the following Roles to configure scoring on a Checklist:
Checklists: Create or Modify
Why this matters: A consistent scoring scheme makes Results comparable — you can spot a slipping Location or a recurring failure at a glance instead of reading every Report.
Critical: Scoring is not a measure of completion. It assesses the quality of a finished Result. A score can be a simple pass/fail (Satisfactory = 1, Unsatisfactory = 0) or a nuanced scale such as a range of smiley faces.
How points work
When you add a Select or Select Group Question, you can assign points to each answer option:
Add points to every answer that should influence the score. Remember that 0 is a value — assigning 0 still counts the Question toward the maximum.
Leave the points field empty for answers that should not influence the score. This collects information without affecting the percentage, for example a final "Any further comments?" Question.
How the score is calculated
When a Checklist is submitted, Mobaro generates a Report with a score — the points collected divided by the maximum possible, as a percentage.
Note: If a User answers "OK" (1 point) to 9 of 10 Questions and "Not OK" (0 points) to the last, they collected 9 of 10 possible points — a total score of 90%.
Using N/A to exclude a question
Add an "N/A" answer option and leave its points field empty. If a User selects N/A, that Question is excluded from the calculation entirely — neither the collected nor the maximum points change. When you filter Results by Score, non-scoring (N/A) Results are filtered out. See Viewing Checklist Results.
Equal vs. weighted scoring
Equally important Questions — assign the same points to the positive answer of every Question (OK = 1) and the same to the negative (Not OK = 0). Every Question weighs equally.
Weighted Questions — give higher points to more important Questions (5 or 10) while others stay at 1. Use weighting deliberately; overuse makes scores hard to read.
Rating scales — assign different points to each option to let Users rate from very good to very poor.
Where scores show up
The Result Report — a score for the overall Report, and optionally at the Page and Question level.
Results filtering — find Results scoring greater than or less than a value between 0 and 100.
Dashboards and Custom Reports — scores feed Dashboards and can drive an Action Report that surfaces low-scoring Results.
Critical: If you modify a submitted Result, scoring for Questions, Pages, and the Report is recalculated — but editing answers will not re-trigger logic or create Assignments retroactively.
Example: a weighted safety check
Scenario
On a ride inspection, a few safety-critical checks should count far more than routine cosmetic ones.
Setup
Safety-critical Questions score 10 for a pass and 0 for a fail.
Cosmetic Questions score 1 for a pass, and an N/A option with empty points is added where a check may not apply.
Result
A single safety failure drops the score sharply, making at-risk Results easy to spot on the Dashboard, while skipped cosmetic checks don't distort the percentage.
Frequently asked questions
Q: Does a high score mean the Checklist is complete?
A: No. Completion and score are separate. Score reflects the quality of the finished Result, not how much was filled in.
Q: My Question has no points filled in — why is it ignored in the score?
A: Empty points mean the Question is intentionally excluded. Add points (including 0) to any answer you want counted.
Q: Can free-text or number answers be scored?
A: Scoring applies to predefined answer options on choice-based and rating Questions. Open-ended Questions collect data without contributing to the score.