Articles on: Checklists

Create a new checklist template

When you have opened the Template-center you should see a view like the one below.

You can navigate between the Public, Company-shared and Private templates in the different menus.

Template area

Checklist-area (private, company and public templates)

Create a new template

Hit the "Add Template"-button and specify a name for the template and optional also a category.

The example below creates a ventilation template:

Create ventilation system checklist

Structure of checklist template

You have multiple options to customize and edit your templates. The screenshot below shows some of the menus, and below the screenshot, the individual menus are explained.

Structure of a checklist template

1) Information

The information area let's you specify the name and category. These informations are used to identify the template.

2) Visibility

It's in this box you can specify who can see and edit the template. It will as standard always be set as Private, but you can just change that to be shared with your company.

3) Availability

Your template will as default be available on all the projects, you are working on. You can limit the availability to specific projects.

The template will only be available to persons from your company. If you want to share it with persons from other companies on your projects, then tick the box.

4) Other

Various ways of importing items to the checklist - either from other templates, from Excel spreadsheets or by using our AI-integration.

5) Detailed description

In this area it's possible to attach a detailed description, e.g. of the test process.

6) Test procedure

It's down here where you add new checklist items.

Checklist items

The individual checklist items are collected in "blocks" defined by the topic/heading. The screenshot below shows the different options/parameters (description below the screenshot).

Options for checklists

(1) Topic

This is the "block" in which you add the items. You can have a topic for "Inspections" and a topic for "Functional tests".

(2) Test item

This is the only required field. It must describe what the user shall control. You can use line-breaks inside the field, so you can write both the test and the expected outcome.

(3) Scope, Method, etc.

These input fields are optional data fields. You can customize the name of them by clicking on the name of them.

(4) Require if

This field only impacts the items checked in (5). When you activate "Photo" in (5), you can decide when users should submit a photo.

You can decide when the photo is required with the options:
"Only when the item is approved/PASS"
"Only when the item is not approved/FAIL."

(5) Required items

By selecting these options the user must provide the data.

(5) Required items - Photo

Take a photo and attach it (automatic on mobile devices).

(5) Required items - Number

Add a whole number (integer) like: "42" or "1300".

(5) Required items - Text

Add free text

(5) Required items - Decimal

Add a decimal (floating value) like: "3.42" or "0.003"

(5) Required items - Percentage

Add a percentage value like: "20%" or "78%"

(5) Required items - Floorplan

The user must select an available floorplan and put a marker on it.

(5) Required items - Prerequisite

Prerequisites are "essential" checks that ensure users review specific items before others. It doesn't matter if these items pass or fail; they won't block or stop the user from continuing. The crucial point is that they are checked first.

Normally, you have the flexibility to choose whether to start your checklist from the top or the bottom. However, when you use a prerequisite, you determine which items must come first in the list.

If you have multiple prerequisites, users can decide the order themselves.

For example, if you're testing an AHU and want users to always begin by verifying the room number, you can mark that check as a prerequisite.

(5) Required items - File

The user must upload a file. (warning: this can be difficult on mobile devices)

(5) Required items - Answers

This option allows you to define specific answers that users must choose from.

For example, you can create a question like "Select the color: Blue / Red," where users must pick one of the provided options.

(6) Advanced approval

The advanced approval allows you to customize even more.

(6) Advanced approval - Require comment

With this option you can ensure, that the user must add a comment, if they fail an item.

When the user clicks FAIL, the user must provide a comment on why it was failed.

(6) Advanced approval - Third party control

This option will require a third party (another person) to check the checklist item. It's an advanced feature which increases the complexity.

When it is enabled you must select a third-party-approver on the checklist. This person must validate each of the checks, the other person perform.

(6) Advanced approval - Block N/A

This option removes the N/A-button. When it is used only the "Approved" and "Failed" buttons are available.

Updated on: 10/10/2023

Was this article helpful?

Share your feedback


Thank you!