Templates — Overview
Build reusable checklists and organize them into collections for multi-part inspections.
Templates define what gets checked during an inspection. Build individual checklists with specific items, then group them into collections for comprehensive multi-part inspections.
Two-Level System
| Level | What It Is | Example |
|---|---|---|
| Checklist | A list of items to inspect — one template per inspection type | "Reinforcement Inspection" (12 items: rebar spacing, cover, ties, etc.) |
| Collection | A group of checklists run together as one inspection | "Concrete Pre-Pour" = Reinforcement + Formwork + Safety checklists |
Templates Page
The Templates page has two tabs:
| Tab | What It Shows |
|---|---|
| Templates | Collections — grouped checklists with item counts and version |
| Checklist Library | Individual checklists with their sections and items |
Checklists
Each checklist contains inspection items with:
| Property | Description |
|---|---|
| Label | What to check (e.g., "Rebar spacing at 150mm c/c per drawing") |
| Instructions | Additional context or specification detail for the inspector |
| Severity | Critical, Major, Minor, or Observation — critical items flag more prominently on failure |
| Evidence required | Whether photos are mandatory for this item, and which evidence type it names |
| Requires test result | Whether a measurement must be entered before the verdict can be saved |
| Standard reference | Optional code reference (e.g., "ACI 318-14 §25.2", "IS 456:2000"), recorded on the template |
Every item is judged the same way in the field — Pass, Fail or N/A. There is no per-item response-type setting.
Items are organized into sections — group related items under headers (e.g., "Main Bars", "Stirrups", "Cover").
Collections
Collections group related checklists:
- Name and description
- Checklists — ordered list, each marked required or optional
- Version — auto-incremented on save
When you create an inspection from a collection, all included checklists appear as sections in the inspection.
Checklist Categories
A checklist carries one category, chosen when you create it. Collections have no category of their own.
| Category | Icon | Typical Checklists |
|---|---|---|
| Concrete | 🧱 | Reinforcement, Formwork, Pre-Pour, Post-Pour |
| Steel | 🔩 | Structural Steel, Welding, Bolting, Coating |
| MEP | ⚡ | Electrical, Plumbing, HVAC, Fire Protection |
| Safety | 🦺 | PPE, Fall Protection, Housekeeping, Excavation |
| Closeout | 📦 | Punch Walk, Final Inspection, Documentation |
| Custom | — | Any project-specific inspection type |
Management Actions
| Action | What It Does |
|---|---|
| Create | New checklist or collection |
| Edit | Modify items, sections, or settings |
| Activate/Deactivate | Toggle availability for new inspections |
| Promote to Org | Make a project-level checklist available across all projects in the organization. One-way — it cannot be reverted to project scope |
| Delete | Removes it from the library. Inspections already created keep the copy of the items they were built with |
Version Tracking
- Every save auto-increments the version number
- Active inspections use the version they were created with
- Template updates do not affect in-progress inspections
Next Steps
- Building Templates — Step-by-step guide to creating checklists and collections
- Creating Inspections — How to use templates when creating an inspection
Questions
Why can't I find Templates on my phone?
Templates are set up on a computer. The Admin pages don't show at phone width.
Who can build and edit templates?
The Templates page opens for roles with full access to inspections. Out of the box that's the project owner. What each role allows is set in Settings → Members & Roles.
What happens to running inspections if I delete or deactivate a checklist?
Nothing. Inspections already created keep their own copy of the items. A deactivated or deleted checklist just stops being offered in the new-inspection wizard.