By the end of this article you'll be able to build a template structure in Visibuild that handles non-linear, multi-phase inspection processes — where daily, per-element, and post-install checks all need to be captured under a single parent record.
When you need this approach
Most inspection templates follow a linear sequence: a checklist of tasks completed in order, once, at a single location. But some inspection processes don't work that way.
Take a piling programme as an example. Your quality requirements might look like this:
Pre-start checks completed daily across the whole piling area
Individual pile records completed per pile as each one is installed
Post-install checks completed once the level is finished
These three phases happen at different frequencies, in different locations, and on different timescales. A single flat checklist can't capture that cleanly. Visibuild's nested template structure can.
How the structure works
The approach uses two template types working together:
An Overall Checklist — a parent inspection template assigned to the top-level location (e.g. Retention Piles). This is the container that holds the whole process together.
Specific Checklists — child task templates added inside the Overall Checklist and assigned to individual child locations (e.g. each pile). These capture the per-element detail.
The result is one parent record with all phase-specific checks nested inside it, visible in a single view and exportable as a single PDF.
How to set it up
Step 1 — Build your location tree to include all child locations
Before creating your templates, make sure your location tree reflects the physical breakdown of the work. For a piling programme, each pile should be a child location under the parent piling area.
Step 2 — Create the Overall Checklist template and assign it to the parent location
Build an inspection template for your daily or phase-level checks (e.g. "Daily Piling Checklist"). Assign it to the parent location such as Retention Piles. This becomes the container for all child records.
Step 3 — Add the Specific Checklist inside the Overall Checklist and assign to child locations
Inside the Overall Checklist, add your per-element task template (e.g. "Pile Record") and assign it to the relevant child locations. You can select multiple locations at once to bulk create all child records in one go.
The result
You end up with a single parent inspection record containing all phase-specific checks nested by location. Each pile has its own record, all visible and manageable from the parent, and the whole programme exports as one coherent document.
What's next
If you're new to building templates, start with How to build and edit a template before applying this structure. For multi-stakeholder templates where different companies own different tasks, see How to build a multi-stakeholder inspection template.