Skip to main content
All CollectionsAdmin PanelChecklists
Create and build your checklist
Create and build your checklist
Written by Håkan Holmgren
Updated over a week ago

Here you can read more about how easy it is to create, adapt and organize your checklist.

Level 1 – the checklist

The first level is the checklist itself and the name you give it. The checklist is then assigned to either units or rounds.

Level 2 – checkpoint

What is a checkpoint in a checklist?
A checkpoint is a part of the checklist. Take this example where we have created a checklist under the name “Wheel loader”. This checklist includes several checkpoints like “Daily inspection” or “Tire Measurement”.

Setting your check intervals
When creating a checkpoint you can choose between these alternatives:

  • Daily Check – The check is performed once every day. The name cannot be changed.

  • Weekly Check – The check is performed once per week. The name cannot be changed.

  • Monthly Check – The check is performed once per month. The name cannot be changed.

  • Custom interval – Specify your own interval for when the check is to be performed, for instance every other day, or every sixth week. You can give custom intervals have custom names.

  • No interval – The check does not need to be carried out during a certain timeframe. You can assign a custom name to this option.

  • Odometer – If you want the check to count down towards an odometer. For example, it may be a lubrication schedule to be performed in the interval every 100 hours on a unit.

Level 3 - questions in the checkpoint

Drag and drop the type of control points you need in your checkpoint. In the menu to the left of your checkpoint you have several different types of questions to choose from. To every question you can add an information text and a help text. The info text is shown underneath the heading and we recommend you do add this to help the user who has to perform the check-up. Every type of question has an icon next to it, which helps you understand what type of question it is.

  • Comments – A text field that can be added underneath the checkpoint heading. To be filled out by the user during the check-up.

  • Text – A regular question that consists of a heading.

  • Text and Image – A regular question with the option to attach an image-file from your computer. The image will be shown underneath the heading of the question.

  • Odometer – The user fills in a numerical value , for instance the mileage of a unit. The input value updates the mileage for the unit in the Admin panel.

  • Number – The user fills in a numerical value with or without decimal points.

  • Dropdown, multiple choice, menu – Lets the user choose from a dropdown menu. A recommended menu when there are several options to choose from.

  • Checkbox, multiple choice, menu – Lets the user choose one or more options from one or several checkboxes.

  • Radio buttons, multiple choice, menu – Lets the user choose one option from one or several radio buttons.

  • Take a photo – Lets the user take a picture using their smartphone camera. When set as mandatory, the check cannot be finalized unless the user submits a photo. A photograph cannot be selected from the photo library on the smartphone or tablet. It has to be taken from within the app.

  • Signing – Lets the user sign off by drawing on the screen.

Level 4 - deviation cause

At least one deviation cause must be assigned to every question in the check, otherwise a user cannot report a deviation. Drag and drop your deviation cause underneath the question heading while creating your check, name the deviation cause by clicking the cog-icon.

Level 5 - components

Under cause of error you can add a number of different types of components that the user can choose from when filling out the deviation. The components Comments and Take Photo are always default under a cause of error.

Tip ...
See our video showing you how to build and customize your checklist.

Did this answer your question?