Checklists
Create and configure checklists, elements and element groups.
Checklists are structured questionnaires that drivers fill out at defined points during tour execution on the mobile app. They standardise control processes — for example, vehicle checks at the start of a tour, damage recording during loading, or confirmation of delivery during unloading.
Completed checklists can be viewed and edited under Monitoring › Checklists.
1. Prerequisite
The checklist function must be globally enabled:
App Settings › Enable Checklists = On
If this setting is inactive, the checklist menu entries are not displayed and no checklists are transmitted to the app.
Additional setting: "Show only completed and required checklists in the signature dialog" — if this option is active, the signature dialog on the app only shows checklists that have been completed and have the option "Show on APP with signature" enabled. If inactive, all available checklists always appear in the dialog.
2. Navigation
| Page | Path |
|---|---|
| Checklist Elements | Master Data › Checklist Elements |
| Checklist Element Groups | Master Data › Checklist Element Groups |
| Checklists | Master Data › Checklists |
Recommended order
1. Create checklist elements → 2. Create checklist element groups → 3. Assemble checklist
Elements and groups are first created as reusable building blocks and then used in any number of checklists.
3. Checklist Elements
A checklist element is a single question or input field within a checklist (e.g. "Vehicle damaged?", "Mileage", "Photo of load").
Create an element
- Open Master Data › Checklist Elements.
- Click "Add Checklist Element".
- Fill in the fields and save.
Basic data
| Field | Description |
|---|---|
| RefId | Unique reference ID. Must be unique per client. |
| Name | Display name of the element (multilingual). Shown to the driver as a question/label. |
| Active | Inactive elements cannot be newly assigned to a checklist. |
Type
The type determines what kind of input the driver can make:
| Type | Description |
|---|---|
| Text | Free-text input (any string). |
| Integer | Numeric input without decimal places (e.g. mileage). |
| Decimal | Numeric input with decimal places (e.g. temperature, weight). |
| Checkbox | Yes/No selection (tick or leave empty). |
| Images | Driver takes one or more photos or selects from the gallery. |
| Barcodes | Driver scans one or more barcodes/QR codes with the camera. |
Further settings
| Field | Description |
|---|---|
| Value required | The driver must fill in this field before the checklist can be submitted. |
| Additional text enabled | In addition to the main value, the driver can enter optional free text. |
| Additional text required | The free text is mandatory (only relevant if "Additional text enabled" is set). |
| Image rotation | Sets the rotation of the captured photo in the PDF/output (0°, 90°, 180°, 270°). Only relevant for type "Images". |
4. Checklist Element Groups
An element group combines several elements into a selection question. The driver selects from the options — either one (single selection) or several (multiple selection).
Examples:
- Single selection: "Condition of goods" → (Good / Damaged / Not checked)
- Multiple selection: "Type of complaint" → (Packaging / Contents / Quantity / Label)
Create a group
- Open Master Data › Checklist Element Groups.
- Click "Add Checklist Element Group".
- Select type, assign elements and save.
Fields
| Field | Description |
|---|---|
| RefId | Unique reference ID. |
| Name | Display name of the group (multilingual). |
| Type | Single selection (RadioGroup): driver selects exactly one option. Multiple selection (MultiSelect): driver can tick several options. |
| Checklist Elements | List of elements contained in the group. The order can be adjusted by drag and drop and corresponds to the display order on the app. |
| Active | Inactive groups do not appear in checklists. |
Note: The elements within a group must be of type Checkbox for the selection to work correctly.
5. Configure a Checklist
A checklist bundles elements and groups into a complete questionnaire and defines when and under what conditions it is displayed to the driver.
Create a checklist
- Open Master Data › Checklists.
- Click "Add Checklist".
- Configure basic data, trigger point and restrictions.
- Add elements and groups to the checklist.
- Save.
Basic data
| Field | Description |
|---|---|
| RefId | Unique reference ID of the checklist. |
| Name | Display name of the checklist (multilingual). |
| Active | Inactive checklists are not transmitted to the app. |
| On demand only | The checklist is only transmitted to the app if it has been explicitly named in the tour or order. |
Trigger point ("Show checklist at")
Defines at what point in the tour workflow the checklist appears on the app:
| Value | Description |
|---|---|
| At tour start | When the driver confirms the start of the tour. |
| At tour end | When the driver confirms the end of the tour. |
| After depot start | After the start of the depot departure. |
| On return to depot | When the vehicle returns to the depot. |
| At loading start | When the driver confirms the start of loading at a stop. |
| At loading end | When the driver confirms the end of loading. |
| At unloading start | When the driver confirms the start of unloading. |
| At unloading end | When the driver confirms the end of unloading. |
| At first TP after pre-load | At the first transport point after a pre-load stop. |
| At loading position start | At the start of an individual loading position (shipment position). |
| At loading position end | At the completion of an individual loading position. |
| At unloading position start | At the start of an individual unloading position. |
| At unloading position end | At the completion of an individual unloading position. |
Restrictions (Scope)
Checklists can be restricted to specific conditions. If no restrictions are set, the checklist applies to all applicable stops.
| Restriction | Description |
|---|---|
| Product | Checklist appears only if a specific product is included in the shipment. |
| Product group | Checklist appears only for shipments with products from this group. |
| Locations (POI) | Checklist appears only at specific stops/locations. |
| Location type | Checklist appears only at locations of a specific type. |
| Location category | Checklist appears only at locations of a specific category. |
Multiple restrictions of the same type act as an OR condition. Different types act as an AND condition (e.g. "Product X" AND "Location Y").
Display options
| Setting | Description |
|---|---|
| Input required for all elements | The driver must complete the checklist fully before proceeding. |
| Show on APP with signature | The checklist is displayed in the signature dialog on the app. |
| Show in tour overview | The checklist is visible in the dispatcher's tour overview. |
| Show on delivery note | The completed checklist appears on the generated delivery note PDF. |
| Export | The checklist and its answers are included in the data export. |
| Manual creation only | The checklist is not created automatically when the trigger point is reached but must be started manually by the driver. |
Adding elements and groups
In the lower section of the form, any number of elements and element groups can be assigned to the checklist. The order determines the display order on the app and can be adjusted by drag and drop.
6. Preview
Using the "Preview Checklist" button in the toolbar, you can see after saving how the checklist will appear to the driver on the app. The preview is informational only and does not save any data.
7. Notes
- A checklist can only be deleted if it is no longer assigned to any tour or shipment and contains no completed instance data. Otherwise the message "Checklist element is still in use or has already been deleted" appears.
- Element groups cannot be deleted while they are used in a checklist.
- The RefId of an element must be unique across the entire client. For duplicates the message "A checklist element with the same reference already exists" appears.