Overview
Use several Scanner Questions when an inspection visits several checkpoints within one Location. Give each checkpoint a distinct code and put its question beside the checks performed there.
A checkpoint scan records a matching code. It does not independently prove physical attendance or prevent someone using a photograph of the label.
At a glance |
|
Who can do this | Super Users, Checklists › Modify, or an authorized Checklist folder Editor. |
Where | Checklists › question editor › Question Configuration |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: Distinct checkpoint codes help staff confirm they are inspecting the intended area instead of reusing one Location label for the whole route.
Plan the checkpoints
List the places that need separate confirmation, such as a control room, lift access point and equipment cabinet. Give each a clear question title and a distinct value, for example “ASTER-CHECKPOINT-03”. These are example names, not required formats.
Use Specific validation for these internal checkpoints. Location validation accepts the Checklist Location’s code; Asset validation accepts its target Asset. Those options solve a different identification task. See scanner code types.
Configure each Scanner Question
1. Choose Scanner Question
Open the Checklist and select Add an element. In the question picker, choose Scanner Question.
2. Describe the checkpoint
Enter a Title and Explanatory Text that tell staff which physical label to scan. For example, name the equipment cabinet and explain where its label is attached.
3. Set the checkpoint value
Under Question Configuration, set Validation to Specific and Method of Scanning to QR/Barcode. Enter the checkpoint’s Scanner Code Value. Despite that method label, use a QR code for the Mobaro mobile app.
4. Repeat and save
Accept the question changes, then add the remaining checkpoint questions with their own values. Save the Checklist using the save icon in its top toolbar. Keep required inspection content visible; a hidden Scanner Question does not provide confirmation for that part of the route.
Print and test the route
5. Print the checkpoint labels
Click the QR code beside a Specific value to open it for printing. To export the Specific codes together, select the Checklist and use Export Scanner Codes. Place durable labels where staff can scan them while following your site’s access and work procedure.
6. Test the correct and incorrect labels
Start a test inspection at the intended Location and use Scan on each Scanner Question. Confirm the correct label is accepted, then try a different checkpoint’s label and confirm it fails.
Open any required reference files and test in the actual lighting and connectivity conditions. These labels answer questions inside a Checklist. They do not open that particular Checklist from a phone camera.
Maintain the labels
Keep a list of checkpoint names and values. Changing a question’s Specific value means an old label no longer matches that question; replace the label and test the updated Checklist together.
You can reuse the same checkpoint value in an opening and closing Checklist when both should accept the same physical label. Scanner Questions do not create Assignment Triggers; put fault questions and their triggers alongside them.
Best practices
Use a unique value for each distinct checkpoint.
Include a readable checkpoint name beside the printed code.
Test a wrong label as well as the right one.
Frequently asked questions
Which scanner validation should I use for several checkpoints?
Use Specific with a different value for each checkpoint. Location and Asset validate the work’s target, rather than a particular point along the route.
Can the checkpoint QR code open this Checklist?
No. A Specific code answers its Scanner Question. Location and Asset QR codes navigate to their target in Mobaro, where the User chooses available work.
Can I reuse a checkpoint label on another Checklist?
Yes. Configure its Scanner Question with Specific validation and exactly the same Scanner Code Value. Keep different physical checkpoints distinct.






