Overview
A Signature Question captures a signature drawn on the device screen as part of a Checklist. Use it for a formal sign-off: a technician releasing a ride, a supervisor approving an opening, or a staff member confirming they have read a procedure.
The signature is saved on the Result as an image, next to the User who completed the Checklist and when. A Signature Question has no options, points or triggers: the only thing it records is the signature.
At a glance |
|
Who can do this | Super Users, a Role with Checklists › Modify (or Create, for Checklists you created), or an Administrator or Editor of the Checklist's permission folder |
Where | Checklists › open a Checklist › Add an element › Signature Question |
Works on | Backend (web) to set up. Answered in the Mobile app and RideOps. |
Availability | All organizations |
💡 Why this matters: For safety-critical sign-offs, a name typed in a text box isn't the same as a signature. A Signature Question puts the actual mark on the Result, alongside the User and time — the accountability record an auditor or insurer expects to see against a ride release or food-safety approval.
Add a Signature Question
1. Open the Checklist editor
In the Mobaro Backend, go to Checklists and open or create a Checklist.
2. Add the question
Click Add an element and choose Signature Question. Enter a Title (required, up to 1,000 characters) that says who signs and what for, for example Maintenance technician sign-off. Add Explanatory Text if the signer needs instructions.
3. Save
Click Accept Changes, then Save the Checklist.
Settings
A Signature Question has no Question Configuration panel. These settings are available:
Setting | Available? | Notes |
Title, Explanatory Text | Yes | The Title is required. |
Reference Images, Manuals, Videos, Links | Yes | Attach the declaration or procedure the signer confirms. |
Question Categories | Yes | Group sign-offs for filtering and reports. |
Action Menu Options | Yes | Allow comments, attachments or Assignments on the question. |
Logic | Yes | Show the signature only when it applies, or use it in other elements' logic. |
Triggers | No | There is no Triggers panel. |
Points or Score Intervals | No | A signature isn't scored. |
Signing in the app
In the Mobaro app, the question shows an empty signature box. The User taps it, signs on the dashed line in the full-screen Signature window and taps Save. To sign again, they tap the signature and redraw it. Tapping Save without drawing anything clears the signature; closing the window keeps the previous one.
Every visible question must be answered, so a Checklist can't be completed until each visible Signature Question is signed. There is no setting to make a signature optional. To ask for it only in some cases, hide it with logic: hidden questions don't need an answer.
In RideOps, Operators sign the same way, starting with the Sign button.
⚠️ Heads-up: The app doesn't check who draws the signature. The Result records the User signed in to the app as the person who completed the Checklist, even if someone else signed on their device. When a different person signs, such as a supervisor, record their name with a Member Question or Text Question next to the signature.
Logic and triggers
A Signature Question can be shown or hidden by any logic condition. Two are especially useful for sign-offs: Based on the checklist state, to show a reviewer's signature only while the Result is Awaiting Validation, and Based on a membership, to show it only to members of a User Group.
Other pages and elements can also depend on a Signature Question, with the operators Answered and Not answered. Signature Questions don't support triggers; see Adding triggers to a checklist for the question types that do. For logic in general, see Adding logic to a Checklist.
Signatures on Results
The signature appears as an image in the Result report and in its PDF. It doesn't add to or lower the Checklist's score, and it isn't shown in dashboard widgets.
A signature can't be changed once the Result is completed. When you edit a completed Result in the Backend, Signature Questions can't be edited or removed, even by a Super User. See Modify Checklist Results.
Best practices
Place the signature after the checks it confirms, as the last item on its page or Checklist.
Name the role that signs in the Title, so it's clear who takes responsibility for what.
Put the declaration the signer agrees to in Explanatory Text or a Manual, so they know what they are signing.
For a supervisor sign-off, use logic on the checklist state and a Schedule that requires validation. See Designing Checklists for the four-eyes principle.
Test the signature step on a phone before you schedule the Checklist.
Frequently asked questions
Can two people sign one checklist, or does each person need to log in?
Yes, two people can sign. Add a Signature Question for each signer; both can sign on the same device, but the Result only records the signed-in User. To have each person sign as themselves, see Completing Checklists across multiple devices and users.
How do I make the signature mandatory?
It already is. Every visible question must be answered, so the Checklist can't be completed until it's signed. There is no separate required setting. To ask for the signature only sometimes, hide it with logic; hidden questions don't need an answer.
Can a supervisor sign only when they validate the checklist?
Yes. Give the Signature Question the condition Based on the checklist state equal to Awaiting Validation, and require validation on the Schedule. The reviewer signs while validating in the mobile app. See Logic based on the Checklist state.
Is there a way to make a dashboard show that signatures were signed?
No. Dashboard widgets report scores and values, and a signature has neither. Open the Result or its PDF to see the signature. Because a visible signature is required, every completed Result has one unless logic hid it.
Someone signed off the wrong checklist by mistake. Can I change or remove the signature?
No. Signature answers can't be edited or removed after completion. If the Result was recorded against the wrong Location, see Changing a result's location; otherwise invalidate it. See Invalidating Results.