Skip to main content
How to build & edit a checklist template

Guidance on building and editing a checklist template for use.

Heath Phelan avatar
Written by Heath Phelan
Updated over a week ago

Building and editing quality inspection templates is easy and can be completed directly in the Visibuild Web App. The article below outlines the step-by-step process of building and editing quality checklist templates.

Once you've nailed the basics down, click here to learn how to build a multi-trade inspection checklist.

The quickest and easiest method of creating a checklist is to use the template builder on the Visibuild Web App; project admins are able to create and edit templates on their project by navigating to โš™๏ธ Project setup > Templates.

Video Guide

The video below provides a step-by-step demonstration of building and editing a checklist directly in the Visibuild Web App.

If videos aren't your thing, check out the text tutorial below.

Step-by-Step Tutorial

To start building your Inspection Templates hit the "+ New template" button in the top right corner.

Creating Visis under your Inspection Checklist

  1. To begin building out your Inspection template, start by hitting the "Add +" button.

  2. This will allow you to create an Inspection or a task.

  3. When a task is created, you have the option to add a required field to this task.

Creating Required Fields in a Task

When crafting required responses to a task, take into consideration that there are always 3 standard actions that you can take on a task:

  • Close a Task

  • Mark it as N/A

  • Mark it as Can't Close

Required fields are *mandatory fields* to prompt the assignee to provide information before they can close a task. There are 5 options to choose from: Checkbox, Short Answer, Attachment, Multi-Choice or Date Picker.

To provide context to the the reader, you must write a title for the required field, otherwise 'save changes' or 'publish' button will be disabled.

The options for required fields are:

  1. Checkbox

    Requires a confirmation click to close the field.

  2. Short Answer

    Requires a value to be added to close the field (text or number. Example: 40mPa)

  3. Attachment

    Requires an Attachment to close the task (PDF, Image, etc.)

  4. Multi-Choice

    Requires a choice to be picked from a list of choices that are defined at template level.

  5. Date

    Requires a Date to be picked from a calendar. Provides precise data and avoids various formatting issues when manually typing in dates.

Arranging Visis

The Up and Down arrows allow you to move tasks and inspections into the order that you desire!

The 'Move to' button allows you to move visis in and out of a parent inspection. This gives you full control and customisation for the ordering of your Visi.

Setting an Assignee, Reviewer or Viewer

The image below highlights three key areas on the inspection template.

The buttons from left to right are:

  1. Assignee

    • This can be assigned to an Individual or a Company who is responsible for closing out the task.

    • If its assigned to a Company, any member of that Company can jump in and close the task.

  2. Reviewer

    • Similarly, the Reviewer will be asked to review the Visi once all tasks have been closed and has been submitted for review.

  3. Viewer

    • Viewers can be assigned to a template to give them visibility of this inspection template. This is useful if you want to share information to a subcontractor, client or consultant.

    • By default, the owner of the project are already able to see all inspections on the project.

Save as Drafts or Publish

When you're not ready to publish, click 'Save changes' to store your progress in a draft state. Team members, with admin permission, can pick up from where its left off.

Remember to 'Publish' your template to start creating an inspection from the template.

Tips for building out an effective checklist

  1. Ensure the title of all inspections or tasks is succinct and easy to read.

  2. Order the tasks to closely resemble the actual workflow onsite, for example rough-in will always happen before fit-off and this should be reflected in the checklist.

  3. Required fields should be used to capture data on the most important tasks - not all tasks need to have required fields.

  4. Remember that the checklist is likely to be completed on the mobile app in the field, therefore try to reduce large blocks of text where possible.

  5. 'Nested' inspections are super useful to ensure all checks relevant to a particular element (concrete pre-pour in the example below) are captured in one location. This makes it easy to track progress onsite.

  6. 'Nested' inspections can be assigned to any company or individual user that exists on the project. In the example below, each of the relevant inspections could be assigned to the form worker, steel fixer, concreter and services trades as required.

Linking Subcontractor Inspections

Once you've gotten your checklist together and a few subcontractor templates created you can link those templates together.

Check out the article below to find out how to link templates together to create one coherent Inspection!

Did this answer your question?