Skip to main content

How to Use Conditional Logic in Dashpivot Checklists and Inspections

Learn how to use conditional logic in Dashpivot checklists and inspections to automatically prompt photo fields when an issue is identified, ensuring evidence is always captured.

Written by Nina Yang

Checklists and inspections in Dashpivot are some of the most common places to use conditional logic — keeping items clean when everything is fine, and automatically prompting for follow-up when something isn't.


The Scenario

When running inspections and checklists in Dashpivot, most checklist items will be marked as passing on any given day. Showing photo fields or follow-up questions for every single item — regardless of outcome — clutters the form and slows workers down in the field.

But when an item is marked as failing or flagged, you need evidence captured immediately at that point in the form. Missing photos after the fact is a common compliance and quality risk on site.

Conditional logic solves this by keeping follow-up fields hidden until they're needed — and optionally making them required when they are, so nothing gets missed.


How It Works

Each Yes/No field in the Dashpivot checklist template acts as its own trigger. When a checklist item is marked "Yes" — indicating an issue — a photo field appears automatically beneath that item in the Dashpivot form. When the item is marked "No", the photo prompt stays hidden.

This can be applied to every checklist item independently — each Yes/No question has its own logic block with its own set of follow-up fields. The photo field can be made required, meaning if an issue is flagged the user must capture a photo before the form can progress.

Whether to make the photo required or optional is up to you — it depends on your team's compliance requirements and how strictly you want evidence enforced.


How to Set It Up

Setting up conditional logic on Yes/No fields in a Dashpivot checklist template follows the same steps as any other conditional logic setup.

Tip: When building a long checklist in Dashpivot, you can copy and paste Yes/No fields. If the first Yes/No field already has a logic block configured, that logic is automatically copied to all newly created Yes/No fields — making it fast to build long checklists with consistent logic applied across every item.


Did this answer your question?