Build and publish an inspection template
From a blank template to a published checklist your team can run: sections, response sets, logic and signatures.
8 min read · Last reviewed 18 Aug 2026
Create the template
- 1
Open Inspections → Templates and create a new template.
- 2
Name it for the job (“Weekly warehouse walk”, “Forklift pre-use”) and set how conducted inspections will be titled.
- 3
Add sections for the walk’s natural chapters, then questions inside each one.
Tip: Build the template in the order someone walks the route, not the order the policy document lists topics. A checklist that fights the route gets pencil-whipped.
Pick response types that grade themselves
Choose from response types like pass/fail, multiple choice, text, numbers, dates, media and signatures.
Response sets (shared answer scales like “Good / Fair / Poor”) keep grading consistent across templates, and updating a global set flows into templates that use it.
Mark responses that should count as failures, so a bad answer can be flagged and followed up rather than buried in the report.
Add logic so the form stays short
- 1
Attach logic to a question so follow-ups appear only when they apply: “If ‘Damage found’, show the photo and severity questions.”
- 2
Nest logic where the job needs it; the editor keeps the structure visible so you can see what triggers what.
Tip: Every question the conductor can see costs attention. Logic is how a thorough template stays a five-minute form.
Signatures and publishing
- 1
Add signature slots for the roles that must sign (conductor, supervisor, witness), each slot named for who signs it.
- 2
Publish the template. Publishing freezes this version; inspections started from it will reference it forever.
- 3
To change a published template later, edit and publish again. That creates the next version. Inspections already underway keep the version they started on.
Note: Version history is what makes an old inspection defensible: you can always show exactly which questions were asked on the day.